The MVP that does not need a rewrite
Speed and durability are not opposites. Most MVP rewrites come from three avoidable decisions.
By Amrelia Technologies Engineering · Engineering team
Founders are told to move fast and expect to rewrite later. The rewrite is not inevitable. It usually comes from one of three choices made in week one.
1. Skipping the tenant model
Adding organisations, roles and permissions after launch touches every table and every screen. Design a tenant column and row-level security on day one; it costs a day and saves a quarter.
2. Hand-rolling authentication and billing
Use a proven auth provider and Stripe from the start. The edge cases in password reset, session security and proration are solved problems you should not fund.
3. Clever technology
Boring is a feature. PostgreSQL, TypeScript, Next.js and a managed host will carry a product further than most founders expect, and every engineer you hire will already know them.
What you should cut instead
- Features nobody has asked for twice.
- Custom design where a design system pattern exists.
- Integrations before the first paying customer needs them.