Process · 12 weeks
A typical engagement, one week at a time.
Every project bends this plan, but the bones stay: frame it, shape it, build it with real users watching, launch it and hand over every key.
Week by week
Kickoff and the problem on one page
Two days in Little Rock or at your office. We interview you, read everything you have and talk to five of your users or would-be users.
Who is on it
- Partner
- Designer
- Engineer
You get
A one-page problem statement both sides sign
Founder time this week
6 hours
After week 12
Handoff means you could fire us the next day.
(Please don’t. But you could.)
- A
Every account in your name
Repository, hosting, app stores, analytics, domain and email. We remove ourselves on the last day.
- B
Docs a new engineer can follow
Setup in one command, architecture notes and a recorded walkthrough of each part of the system.
- C
30 days of support
A shared channel stays open. Bugs we wrote, we fix, free.
- D
A plan for the next 90 days
What to build next, who to hire first and what to measure, written with you.
Want to see what your twelve weeks would cost?
Pick services, people and weeks, and get a range and a timeline in a minute.