Classes, students and payments all need one home.

What they said

It started with one sentence on a call. Everything below traces back to it.

What I heard

In the first call I listen for the problem under the request. 3 notes came out of it, and they became the brief.

The plan

Before any pixels, a sketch everyone could point at and argue with. Cheap to change, and it keeps the client's words in the room.

+--------+---------------------------+
| menu   |  classes        [ + new ] |
| ----   |  +------+ +------+ +----+ |
| ----   |  | mon  | | tue  | | we | |
| ----   |  +------+ +------+ +----+ |
|        |  payments  $____  ____ %  |
+--------+---------------------------+

The decisions

1. 01One promise up front: the platform bends to your programs, not the other way round.From “Nothing talks to anything.”
2. 02Upcoming payments shown before they're late, with a pay button right there.From “We find out about late payments too late.”
3. 03A design system built from scratch, so every module feels like the same product.From “Every screen looks different.”

rostly

1. Said
2. Heard
3. Sketch
4. Design
5. Shipped

What changed

• One platform instead of four tools.
• Class, student and payment work in one flow.
• A design system the team can keep building on.

rostlyLiveView live site

1. Said
2. Heard
3. Sketch
4. Design
5. Shipped