Get your AI-built app ready for real users
Most work starts with a review of what you have, moves on to fixing and launching it, then keeping it running. Each step stands on its own, and you can stop after any of them. Starting from scratch instead? Say so on the call.
Production review
A senior engineer reads the code your AI tool wrote and tells you, in writing, what will hurt you first, and whether it’s worth fixing or cheaper to rebuild.
TYPICAL LENGTH · 1 to 2 weeks
Good fit for
- An app built with Lovable, Bolt, Replit or v0 that you want to launch
- A Cursor project that has grown past what you can hold in your head
- Taking over a codebase someone else abandoned
- A second opinion before you spend more on it
You get
- A written assessment you keep, whether or not we continue
- Security and data-access findings, ranked by what to fix first
- A straight answer on fix versus rebuild
- A fixed quote for the fixes, if you want them done
Launch and fix
The work between a demo and a product people pay for: real accounts and roles, database rules that hold, payments, email, backups, tests and a deploy pipeline in your name.
TYPICAL LENGTH · 2 to 8 weeks
Good fit for
- An AI-built app about to go in front of paying customers
- An app that slows down or falls over as users arrive
- An AI feature that has to behave in front of customers
- Finishing a build someone else abandoned
- Replacing a spreadsheet that quietly became the system
You get
- Fixes in your repository, as pull requests you can read
- Accounts and infrastructure in your name
- Tests and CI that block a bad deploy
- For AI features, an evaluation set from your real cases and cost per request, measured
- A written handover, a walkthrough call, and 30 days of support after launch
Keep it running
A set number of senior days each month for the updates, fixes and small features a live app keeps needing. Keep prompting your own tool in between if you like.
TYPICAL LENGTH · rolling, 30 days’ notice
Good fit for
- A launched app with nobody technical on call
- Dependency and security updates you keep putting off
- Small features that need someone who knows the code
- Agencies needing overflow capacity, white-labelled
You get
- Named days, booked in advance
- Work in your repository, as pull requests you can read
- Updates and security patches applied, not just flagged
- A monthly note on what changed and what is next
Review or scoping call
Thirty minutes. If the app already exists, this is usually where a production review gets booked. If it does not, it is scope, cost and fit.
Fixed proposal
Scope, price and dates in writing within two business days. No hourly estimate that drifts.
Weekly builds
Something running on a real URL every week, so progress is visible rather than reported.
Handover
Your repository, your accounts, your deploys, and a walkthrough. Support afterwards if you want it.
The questions that come up on every call
- Who owns the code?
- You do, from the first commit. The repository lives in your organization and every account is created in your name.
- Do I have to stop using Lovable or Cursor?
- No. Plenty of people keep prompting their tool for small changes. The difference afterwards is that tests and a deploy pipeline catch it when a change breaks something.
- Will you rewrite it from scratch?
- Rarely. Most AI-built apps have a sound core and a handful of problems that matter. The review says which, and a rewrite is only on the table when it costs less than the fixes.
- Is my app secure?
- Nobody can say without reading it. The usual gaps are keys in the browser, database rules that let anyone read everything, and pages that check who you are but not what you are allowed to see. The production review looks for each of them.
- Fixed price or hourly?
- Projects are quoted fixed against a written scope, so the number does not move unless the scope does. Retainers are monthly. Hourly billing rewards slowness, so we avoid it.
- Why is there no pricing on the site?
- Because a number on a page is read as a quote, and what this costs depends on what you need. You get a fixed figure in writing within two business days of the call, before anything is built.
- What if the scope changes?
- It usually does. Changes are quoted as an addendum before any of it gets built, so nothing arrives as a surprise on an invoice.
- Who actually does the work?
- Yousef, on every project. When a specialist joins for part of it, you are told who and which part.
- Do you build new apps too?
- Yes, web and SaaS applications from scratch, with the same handover. Interface design is included. Brand identity and marketing sites we hand to people who do it better.
Still not sure which one you need?
That is what the call is for. Thirty minutes, no deck.