Process

Five steps, no surprises.

Discover → Scope → Build → Review → Launch. Same process for every tier. The scale differs — the rigour doesn't.

01
Discover
30 min call

Free discovery call. We surface the real problem, the real audience, and whether an MVP is the right move. No pitch.

Outcome: Decide to move forward or not.

Your part

No preparation needed — just show up ready to talk.

02
Scope
1–2 days

Written scope doc. Every screen, every workflow, every edge case defined in writing. You sign it — that's the build contract.

Outcome: Signed scope. Clear deliverables. No scope creep.

Your part

Review, comment, and approve the scope doc.

03
Build
Bulk of timeline

Daily async Loom updates. Weekly live demo. You have read access to the repo from day one — no waiting for a big reveal.

Outcome: Working software, iterating in real time.

Your part

15 min / week on demos. Async feedback via comments.

04
Review
3–5 days

You use the product as your users would. Report bugs, friction points, and anything that doesn't feel right. We fix and iterate.

Outcome: Polished build ready for launch.

Your part

Use the app as a real user. Write down what feels off.

05
Launch
1 day

Deploy to production. Transfer code, secrets, and documentation. The post-launch fix window begins on launch day.

Outcome: Live product. You own everything.

Your part

Plan your first user acquisition push.

What you can count on

Fixed scope

Everything in the scope doc gets built. Nothing outside it does — without a change order.

Daily visibility

Loom updates every build day. No black boxes, no sudden surprises before demo day.

You own the code

Full source code, deployment config, and credentials handed off on launch day.

Bug-fix window

30 days (Starter/Lean) or 60 days (Growth) of bug fixes after launch. Included.

Step one is always the same: a 30-minute call.

No prep required. No commitment. We figure out if this is the right fit — for both sides.