Notes for owners · MVP and Product Development
Should You Turn Your Internal Software Into a SaaS Product?
Turn internal software into a SaaS product only when buyers outside your business have offered to pay and expect to sign up without your staff. With one outside customer, or only your own branches, it is premature. GullySystem’s productisation review sorts what carries forward and what must change before any build is committed.
Ganesh HS, Strategy and Technology, GullySystem · · 3 min read
What a product needs that an internal system lacks
Software written for one company assumes one company. Rate rules, document formats, approval levels and the branch list belong to that single business. Every report runs over one pool of records.
A product sold by subscription needs parts an internal system was never given. These are not extra screens. They are the layer around the screens.
- A boundary that keeps each customer’s data apart
- Plans that decide what each customer gets
- Signup that works without a staff member
- Recurring collection with rules for failed payments
- A console to run accounts, limits and support
Signals that the move is worth making
The clearest signal is demand. Others in your trade have seen the system and asked to use it. Some have offered to pay.
A second signal is strain from selling it already. Each customer runs a separate copy, so a fix goes out one server at a time. Renewals are tracked on a spreadsheet and chased on WhatsApp.
A third is code full of exceptions. One customer asked for an extra approval, another for a different invoice. Each change was small, but a change for one can now break another.
When a SaaS build is the wrong spend
If nobody outside the company has offered to pay, multi-tenancy is premature. A focused first version can test demand for far less effort.
If the software serves only your own branches or franchisees under one owner, a multi-branch system fits better. With exactly one outside customer and no second in sight, a well-configured single installation is enough.
A no-code builder or a white-label product is worth trying while the offering is standard. It costs little to abandon. It stops fitting once your own workflow or pricing is why customers choose you.
What usually carries forward and what changes
The screens, business rules and reports users already trust are normally kept. That is most of the value. The foundation underneath is what gets reworked.
Every record and file needs an account it belongs to. Conditions that name individual clients become settings or feature switches. Where the code is very old or has no clear data model, rebuilding some parts can be more practical than adapting them.
Questions to answer before asking for a quote
A quote rests on the decisions made before it. Settle these with whoever owns the commercial side, not only with the developers.
Pricing questions are a common cause of delay. Answering them early shortens every later step.
- Who would buy, and how many such buyers exist?
- What do you charge for: users, branches, vehicles or students?
- Who will handle renewals and support calls?
- Who can decide plan prices without a long internal loop?
- Are two or three real customers willing to go first?
Productisation readiness sheet
A worksheet with one row per part of your current system: screens, rules, reports, masters and integrations. Mark each as keep, rework for many customers, or drop. Add a final column naming the customers who asked for it.
Open a blank worksheet to printQuestions owners ask
Is one interested outside customer enough reason to build a SaaS platform?
No. With a single outside customer and no second in sight, a well-configured separate installation is the simpler answer. Revisit the question when more buyers appear.
Do we have to rebuild the whole system?
Usually not. Screens, rules and reports are normally kept, while the data foundation is reworked so every record belongs to one account. Very old code may need parts rebuilt.
Who owns the product once it is built?
You should. Source code, hosting, the payment gateway account and customer data sit in your name. There should be no licence fee or revenue share to the developer.