Prototype rescue

Your AI-built prototype is not production software yet.

Claude, Cursor, Lovable, Replit, Bolt, v0 and similar tools are brilliant for reaching a demo. Kyln helps work out whether the result should be salvaged, refactored or rebuilt before customers depend on it.

Start with a reviewRead the launch checklist
Fit and buying triggers

The right pressure leaves marks.

Architecture, auth, permissions, database design, deployment, observability, testing, cost control and ownership.

Good fit
  • Built with AI coding, no-code or low-code tools.
  • The product looks impressive but breaks under real use.
  • There is a pilot, waiting list, investor pressure or real internal users.
  • The team needs an adult review, not a generic agency pitch.
Buying triggers
  • The app keeps breaking or cannot deploy reliably.
  • Nobody fully understands the database, auth, permissions or hosting.
  • There are no tests, logs, backups, monitoring or security model.
  • The prototype has been shown to customers and now needs to survive them.
What changes

From heat to useful form.

Outcome 01

A clear salvage, refactor or rebuild recommendation.

Outcome 02

A launch-readiness score across architecture, security, data and deployment.

Outcome 03

A prioritised fix list tied to user and business risk.

Outcome 04

A route from impressive demo to credible pilot.

How it works

Three steps: review, build, run.

Whatever you start with, the first paid step is a review: we find the real constraint and the one number it is costing you, then prescribe the path. It leads to a scoped build, then a Kyln Care plan after launch.

Step 01 · The diagnosis

Start with a review

We find the real problem first: the constraint slowing your business and the one number it is costing you. Then we prescribe the technical path: salvage, refactor, rebuild, or a build plan with costs.

The constraint named: what is gating revenue, slowing the team or leaking money.
The one number we are trying to move, and where it sits today.
Architecture, auth, data and security read, where something is already built.
The prescription: salvage, refactor, rebuild, or a build plan with costs.
Fixed-scope review · from £1,500.
Start with a review
Step 02 · The build

Product & platform build

A scoped product, MVP or platform build, made production-grade. Auth, data, security, payments and deployment, priced after the review rather than from a guessed feature list.

Discovery, flows and UI direction.
Full-stack build with infrastructure.
Auth, permissions, payments and admin tools where needed.
Testing, deployment and handover.
Scoped build from ~£20k, priced after the review.
Scope a build
Step 03 · After launch

Kyln Care

Ongoing care for what we build: hosting, monitoring, maintenance, small fixes and calm technical ownership. Fractional-CTO direction where you need it.

Hosting oversight, SSL and backup checks.
Monitoring, security patching and incident support.
Small fixes and an optional development allowance.
Monthly product and technical review.
Flat monthly care · CTO direction from £3,000/mo.
Discuss ongoing care
Proof shapes

The work is judged by what keeps behaving.

Product strategy · MVP build

Founder builds

Turning a commercial idea into a scoped product, a usable first release and a supportable technical foundation.

Audit · Launch readiness

Prototype rescue

Reviewing fragile AI-built products across architecture, auth, data, security, deployment and ownership before launch pressure hardens the wrong decisions.

Infrastructure · Support

Production infrastructure

Deployment, hosting, monitoring, backups, permissions and maintenance for web products that need to keep behaving after the first release.

Qualification

Questions before the clay goes in.

These are the questions that separate serious work from vague intent.

Q01

What tool was it built with?

Q02

Is the code accessible?

Q03

Is it live anywhere?

Q04

Are real users using it?

Q05

What breaks most often?

Q06

How are auth, data, hosting and backups handled?

Q07

Are you trying to salvage, refactor or rebuild?

Production readiness · free · 2 minutes

Is your AI-built product safe to sell yet?

The Production Readiness Scorecard is a two-minute self-assessment that grades how close your product is to something you can safely put in front of paying customers, and names the risks standing in the way.

  1. 01

    Describe what you built

    One line on what your product does and how many paying customers it has today.

  2. 02

    Answer honestly

    A short set of pointed questions across auth, data, security, testing and operations.

  3. 03

    Get your grade and risks

    An instant letter grade and a “% ready” score, then your three biggest risks ranked worst-first, specific to what you’ve built.

Get your gradeFree · no account · top-line grade is instant
Kyln

C

64% ready

Promising, but not safe to charge for yet. Three issues would bite a real customer first.

Top risks · worst first

  • 01Admin endpoints have no authentication
  • 02API keys are committed to the repository
  • 03No automated tests run before deploy

Sample · your result is personalised

Prototype rescue questions

Want to talk through the fit? Email contact@kyln.digital

No. The point of the audit is to decide honestly. Some prototypes can be hardened. Some need a clean rebuild. Some are useful only as product discovery.