02Step 02 · Architecture & design

Map it out

Now we work out how it's actually put together — the decisions that are cheap to make now and expensive to change later. This is where a project quietly succeeds or sets itself up to fall over.

Typical timeRoughly a week, depending on scope

What it sets upThe expensive decisions made on purpose — not discovered halfway through the build.

What happens

We design the data model around the way the app will really be used.
We map the screens and how a person flows through them.
We choose the stack and the key libraries, and write down why.
We plan the tricky parts — payments, auth, real-time — before they turn into surprises.

What you get

A data model and the shape of the APIs.
Screen flows for the main journeys.
The key technical decisions, written down, so nothing is a mystery later.

Previous · 01Figure out what we're building Next · 03Build it in pieces

Got something in mind?

So, what are we building?

Send us the rough idea, even if it's messy. We'll come back with how we'd build it and roughly how long it'd take, usually within a day.

Tell us about it Or just email us