Skip to content
available for projects000%
All writing
ENTRY-015Product decisions7 August 2026 · 1 min read

SER-02 · SER-02.05 · From Prototype to Production

When should an MVP be rewritten, and when should it be rescued?

I do not rewrite because code looks ugly. I consider rewrite when the core system can no longer carry the product reliably and incremental repair stops reducing total risk.

Starting over is attractive because it promises a clean slate. It also means rediscovering production edge cases, migrating data and running two realities during transition.

Rescue signals

  • Core data model is mostly sound.
  • Problems cluster in a few domains.
  • Consumers can migrate incrementally.
  • Production behavior can be measured.

Rewrite signals

  • Core model cannot represent the product.
  • Security boundaries cannot be introduced safely.
  • Every small change creates unpredictable regression.
  • Platform constraints block the core requirement.
ts
const rewriteCost =  implementation + dataMigration + regressionDiscovery +  parallelOperation + userMigration + releaseRisk;
Rewriting an unvalidated product can be nothing more than rebuilding uncertainty with cleaner code.
  • MVP
  • Rewrite
  • Technical Debt
  • Architecture
  • SaaS

SER-02 · SER-02.05

From Prototype to Production

Turning a working MVP into a dependable product: production checks, modular refactoring, data migration, audits, rewrite decisions and release gates.

AVAILABLE FOR PROJECTS · PRODUCT & SYSTEMS ARCHITECT · TAKEOVER / STABILIZE / OPERATE · WEB · ANDROID · WINDOWS · AHMET CANAL

Contact

Has your product grown faster than its system?

Send the current situation, your biggest blocker and the outcome you want. We will clarify scope together.

Availability

Open to new consulting and project-based work.