Subscription SaaS MVP
A first sellable version of a B2B product: teams, roles, subscription billing and the one feature customers will pay for.
- Ruby on Rails
- PostgreSQL
- Stripe
- AWS
Example project · Finish
SaaS product abandoned at 70% complete
An agency-built platform that ran out of budget before launch — assessed honestly, then finished.
This is a representative example of a project type we take on — a typical situation, approach and scope — not a description of a specific client engagement. Timelines are indicative; yours will depend on the details.
The situation
An agency built most of a product, then the relationship or the money ran out. The owner has a repository, a half-working staging site and no way to judge how far from done it really is. “70% complete” is the agency's number.
How we approach it
- Get the code running locally and write down everything that does and doesn't work.
- Separate what is unfinished from what is finished badly; they need different treatment.
- Give a fixed-scope plan to reach launch, keeping whatever is sound.
- Add tests around the paths that handle money and customer data before changing them.
What gets delivered
- Independent completion assessment
- Prioritized launch plan with costs
- Finished and tested product
- Deployment, backups and handover documentation
Related
Similar examples
Flutter app stuck before store approval
An app that works in the demo but keeps getting rejected — finished, hardened and taken through review.
- Flutter
- Firebase
Customer portal for a field-services business
A self-service portal where customers book visits, approve quotes and pay invoices — replacing phone calls and emailed PDFs.
- React
- TypeScript
- Node.js
- PostgreSQL
Does this sound like your project?
Tell us how yours differs. The details are where the real plan comes from.