After launch
The 30 days after launch are already paid for. Day 31 is your call.
Every build includes a 30-day scaling programme at no extra cost. After that you continue on a retainer, take a documented handover and go independent, or run a hybrid where we own architecture and your team owns day-to-day. You own the code either way.
What goes wrong
The four things that kill a product in month one
The bugs only real users find
Your testers clicked the way you expected them to. Real users do not. Whoever is watching production in week one decides whether a broken signup gets fixed that afternoon or discovered in a churn report a month later.
Queries that were fine at ten users
Nothing is slow at ten users. The query that scans the whole table only shows itself when the table is big, which is exactly the week you have people worth losing.
Signups that never come back
You will have the acquisition number and no idea which screen lost them. If analytics was not wired to the real funnel before launch, the drop-off stays invisible until the cohort is already gone.
Building the wrong thing next
Month one is when founders build whatever the loudest user asked for. The usage data usually points somewhere else, but only if someone is reading it every week.
Included with every build
The 30-day scaling programme
Four weeks, no additional cost, and not a trial that converts into billing.
Week 1 — Foundation and optimisation
Daily monitoring and same-day fixes on anything real users hit. Load testing and performance work. Analytics wired to the funnel rather than to pageviews. A security review of auth, secrets and the payment path — a review, not a certification, and we will not describe it as one. Then a call to agree what the 30 days are actually for.
Week 2 — User feedback and refinement
We read what people actually did, not what the roadmap assumed they would. Feature usage, funnel drop-off, the screens nobody reaches. You get the three optimisations worth doing, we ship the cheap ones inside the week, and the A/B framework goes in so the next argument is settled with data instead of opinion.
Week 3 — Growth and scaling preparation
Indexes and queries reworked before traffic finds them. Rate limiting and caching on the APIs. A CDN for users outside your region. Alerting that wakes a human rather than filling a dashboard. And a written capacity plan naming where the next ceiling is.
Week 4 — Transition and next steps
A written 30-day report and a technical debt assessment — our honest read of what we cut, why, and what it will cost you to undo later. A 90-day roadmap we build with you. Retainer scope and price if you want one. Handover documentation whether you do or not.
Then one of three paths
What happens at day 31
Continue with a retainer
Growth Retainer at $2,999 per month. 40 hours of development a month, weekly strategy calls, and priority support. This is the path most growing startups take.
Go independent
We hand over the complete codebase with full documentation. Any developer can maintain and scale it. You own 100% of the code, and this costs you nothing extra.
Hybrid
We stay on for strategy and architecture decisions while your in-house team handles day-to-day development. Common once founders make their first engineering hire.
Questions, answered
Do you only build MVPs, or do you support products long term?
Both. Every build includes a 30-day scaling programme at no extra cost, and most clients continue on a Growth Retainer at $2,999 per month covering 40 hours of development, weekly strategy calls and priority support. The 21-day figure describes how fast the first version ships, not how long the relationship lasts.
Will I be left with technical debt once you scale?
Week 4 of the 30-day programme is an explicit technical debt assessment, delivered in writing alongside a 90-day roadmap. We also hand over documented, readable code built for another team to take over. We run App Rescue, a service dedicated to repairing other people's broken AI-generated builds, so we see exactly what shortcut engineering costs and we do not ship it.
What happens if I want to leave after launch?
You take everything and you owe us nothing further. You own the code, the repository, the infrastructure and every account it runs on, from day one rather than on final payment. We provide documentation and a knowledge transfer session so any developer can pick it up.
Are you SOC 2 or HIPAA certified?
No. We are a lean studio and we do not hold formal compliance certifications, run a 24/7 support desk, or provide account managers. If your project requires certified compliance, a regulated-industry audit trail, or a large legacy migration, an enterprise firm is the safer choice and we will say so on the call.
What technology do you work in?
TypeScript is our default and it is what most of our shipped work runs on: React, Next.js, React Native, Node.js and NestJS, on managed cloud infrastructure. That is where we are fastest. We take on other languages, stacks and legacy migrations where the project calls for it, scoped individually rather than sold as a fixed package.
What if I do not know exactly what to build yet?
Then the fixed-price sprint is the wrong starting point, and we will tell you that rather than sell you one. Start with a call so we can scope the problem properly. Fast delivery works when the decisions are made, and it fails when discovery is still open.
Can I switch to a retainer at any point?
Yes. The formal transition happens in Week 4, but you can move to a retainer at any point during the 30-day programme.
Is the 30-day programme really included?
Yes, in every package, at no additional cost. It is not an upsell and it is not a trial that converts into billing unless you choose a retainer.