A process designed to remove waiting, not to bill for it
Most of what makes agency projects slow is coordination overhead that exists to justify a retainer. Four phases, roughly three hours of your time, and a date agreed in writing before anything begins.
- 01
48 hours
Scope lock
You pick a tier or send a brief. We come back with a written scope, every screen, every integration, a fixed price, and a ship date. Nothing starts until you approve it, and nothing outside it is assumed.
- 02
Day 1
Asset handoff
A single onboarding form collects logins, brand assets, and access. One call if the project needs it, none if it does not. We select the stack and start the same week.
- 03
The bulk of it
Build in the open
Senior delivery from day one, no junior handoff. You get a walkthrough video at every functional milestone and a live preview URL you can open at any point, so there is no reveal at the end.
- 04
Launch + 30 days
Ship and hand over
It goes live on your infrastructure, in your accounts, with the repository transferred. Thirty days of support covers the bugs and questions that only appear once real users arrive.
On-time guarantee
Miss the timeline on a fixed-price build and your deposit comes back. No negotiation, no invoicing games.
Working agreement
What we do and what we deliberately do not
Both lists are short on purpose. Knowing what is not included is what makes a fixed price trustworthy.
What we do
- Write a scope document before taking payment
- Give you a live preview URL from the first week
- Send a walkthrough video at every milestone
- Build on your accounts and transfer the code
- Tell you when a cheaper option would solve it
- Pause the clock and say so if we are blocked
- Support the build for thirty days after launch
What we do not do
- Run a paid discovery phase before quoting
- Bill hourly or invoice for overage
- Hand your project to a junior after the sales call
- Hold your hosting, domain, or deployment keys
- Require a retainer to keep the work running
- Schedule weekly status calls nobody needs
- Take a project we do not think we should build
FAQ
Process questions
How the engagement runs in practice.
How much of my time does a build take?
Around two to four hours in total across the whole project. One scoping call, one onboarding form, and a consolidated review at each milestone. The single biggest cause of a late project is a client who cannot free up two hours in week one.
How do I see progress?
A live preview URL you can open at any time, plus a walkthrough video at each functional milestone. There is no weekly status call because the preview link makes it unnecessary.
What happens if I go quiet mid-build?
The clock pauses. The on-time guarantee is written against elapsed working days where we are not blocked, so if an approval sits for a week the date moves by a week. We will tell you when the pause starts rather than absorbing it silently.
Who actually writes the code?
The engineer who scoped it. There is no handoff to a junior, no offshore team, and no account manager between you and the person building. That is also why we run a limited number of projects at once.
What does the handover include?
The repository transferred to your GitHub, environment variables documented, a README covering local setup and deployment, and a recorded walkthrough of the architecture. Enough that a developer you hire later can pick it up without contacting us.
Tell us what you need built
Send a brief and get a fixed price and a ship date within 48 hours. If a productized tier fits, you will know today.
No retainer, no hourly billing. Quote in 48 hours.