# Prototype to Production

> A scoped AI Pod that takes a prototype built in Cursor, Lovable, v0, Bolt, Replit or Claude Code and makes it safe to put in front of customers.

Source: https://www.koombea.com/ai-pods/catalog/prototype-to-production/

---

Someone built the thing in a weekend and it works. Then a real user found the second edge case. This Pod takes a prototype to production without throwing away what already works.


## The problem

Prototypes built in Cursor, Lovable, v0, Bolt, Replit, Windsurf or Claude Code are genuinely useful. They answer the question of whether the product is worth building, in days, for almost nothing. That is a real advance and it is not the problem.

The problem arrives the week someone wants to charge money for it. The auth is a placeholder. The data model has no migrations. There are no tests, no error handling on the paths nobody demoed, and an API key sitting in the client bundle. None of that was a mistake. It was the right trade for a prototype and the wrong one for production.

We do not rewrite it. A rewrite discards the one thing the prototype proved, which is that this shape of product is worth having.

- The working product loop survives the engagement
- Findings are ranked by what blocks launch, not by what offends taste
- You get the assessment as a standalone deliverable before committing to a build

## What this Pod ships

- **Auth, secrets and access control**: Real authentication, keys off the client, and permissions enforced on the server rather than in the interface.
- **A data model that can change**: Migrations, constraints, and a schema that survives its first production edit.
- **Tests and gates**: Scenarios written from the spec, enforced in the pipeline, so the next change does not undo this one.
- **Deploy, monitor, recover**: An automated pipeline, error tracking, and a documented path back when a release goes wrong.

## The assessment comes first

The first stage is 15 to 25 points and stands on its own. We audit the prototype against the things that actually block a launch, and hand you a ranked findings list with a costed remediation plan.

Sometimes that document says the honest answer is a rebuild, and we say so. Buying a small assessment to discover that is a much better outcome than discovering it four months into a hardening engagement.


## What it costs

Two numbers, because these are two decisions. The assessment is 15 to 25 points and produces the estimate for the build. The build typically runs 100 to 250 points. That range narrows to a committed figure once the assessment is done.

The assessment credits in full against the build if it starts within 90 days, the same window banked points run on.

- Assessment: 15 to 25 points, two weeks, standalone deliverable
- Build: typically 100 to 250 points, committed after the assessment
- The assessment credits in full against the build if you start within 90 days
- Your prototype, your repository, your IP throughout