From idea to running product
Five stages, each with a deliverable you can hold. You always know where the project is, what it costs, and what happens next.
- Intro call
- Scope
- Build
- Launch
- Run
Intro call
You describe the idea or the problem. We ask the awkward questions early: who pays for this, what already exists, what breaks if it works. By the end you will know whether it is buildable and roughly what scale of project it is.
You get
- A straight verbal read on feasibility
- A recommendation, even if it is "do not build this"
Scoping sprint
We interview you, sketch the screens, pick the architecture, and price the whole build. This is real design work, not a sales document. If you take the plan to another team, it will work there too.
You get
- A build plan with screens and milestones
- A fixed quote with a delivery date
- The first honest risk list you have seen
Build
We build the product. Every Friday you get a demo of working software in your own browser, plus a short note on what changed. Scope changes are priced before they happen, never discovered on an invoice.
You get
- A working demo every Friday
- Weekly plain-language progress notes
- Hosted and run on our accounts, transferable to you anytime
Launch
Domain, production hosting, analytics, backups, monitoring. We carry the product into production and check it under real traffic. Launch is a stage with a checklist, not a handoff email.
You get
- The product live on your domain
- Monitoring and alerting in place
- A written runbook for the whole system
Run
We keep the product fast, secure, and current: security updates, dependency upgrades, uptime monitoring, support. Included iteration hours mean small improvements ship monthly instead of piling up. You read one report a month and get back to the business.
You get
- Hosting, updates, and same-day incident response
- Included iteration hours each month
- A monthly report you can read in five minutes
What we need from you
About two hours a week, and the things only you know: how the business makes money, what your customers complain about, and which corners must never be cut. We bring everything else.
Asked on most intro calls
Who owns the code?
We do, by default. The repository, hosting accounts, domain, and data live in accounts we own and operate, so you never have to manage infrastructure. Whenever you want it in house, we transfer everything to your own accounts for a one-time fee.
What happens if we stop working together?
We transfer everything to accounts you own for a one-time fee, then hand off cleanly: a documented codebase, a runbook, and a transition call with whoever takes over. The exit being easy is deliberate. It keeps us accountable every month before it.
What do you build with?
Proven, widely used technology that any competent team can pick up: the kind of stack that still has answers on the internet in ten years. AI goes in where it earns its place, not as decoration.
How much of my time does this take?
Plan on about two hours a week during the sprint and the build: one standing call plus decisions over email. We need your judgment about the business, not your evenings.
Can you take over something another team built?
Usually, yes. We start with a short paid audit instead of a scoping sprint, then quote the takeover the same way we quote a build.
Numbers live on the pricing page.
Start with a straight read on your idea.
A free 30-minute intro call. No deck, no follow-up sequence — just an honest read on whether it can be built and what it would take.