How a Project Runs, From First Message to Launch
Founder-led means you talk to the person who designs your architecture, not an account manager. Here is exactly what happens, in order.
Day 0
You send a short brief
Tell us what you want to build through the contact form. We reply within 24 hours. If you'd like an NDA in place before sharing details, ask and we'll sign yours or send ours.
After we reply
A free 30-minute scoping call
You talk to the engineer who would lead the work, not a salesperson. You leave with an honest view on whether we're the right fit and a rough range. If we're not the right fit, we'll say so.
Before any code
A written scope and quote
You receive a written scope that says what is included and what is not, split into milestones, with a fixed quote. Nothing is built until you agree it. Typical ranges are published on our engagement models page.
Typically 8–12 weeks for an MVP
The build, in milestones
The code lives in your repository from day one, so you can see every commit. You get a dedicated Slack channel with the engineers and a video walkthrough of working software every two weeks. Anything outside the written scope is estimated and agreed with you before work on it starts.
End of the build
Launch and handover
Before handover you receive setup and deployment documentation, environment configuration and a walkthrough, so your own developers or another team can take over. You own the bespoke code, database design and documentation we write for you.
60–90 days after launch
Warranty, then optional ongoing work
A 60–90 day warranty covers defects in what we delivered. After that, ongoing work is optional and scoped separately as a monthly contract.
Questions about the process
What happens after I contact you?
We reply within 24 hours. Next is a free 30-minute scoping call with the engineer who would lead the work, then a written scope and fixed quote. Nothing is built until you agree the scope.
How will I know how the project is going?
The code is in your repository from day one, you have a dedicated Slack channel with the engineers, and every two weeks you get a video walkthrough of working software.
What if I want to change the scope during the build?
Anything outside the written scope is estimated and agreed with you before work on it starts, so the price never changes without your say.
What does the warranty cover?
For 60–90 days after launch, we fix defects in what we delivered. New features and ongoing changes are optional and scoped separately.
What if we stop working together?
The repository, hosting and third-party accounts are in your company's name, and handover includes setup and deployment documentation, so your own developers or another team can take over without a rewrite.
More detail on security, ownership and continuity is on our trust page.
Start with a 30-minute scoping call
Tell us what you want to build. You get a reply within 24 hours, a 30-minute scoping call with the engineer who would lead it, and a written scope and quote.
Not ready to build? Validate Your Idea First