Why five products instead of one platform
Every tool that starts focused eventually gets asked to become a platform. Here is why we are not going to, and what that costs us.
The obvious move for a studio with five tools is to merge them into one platform with five modules, sell one subscription, and put “unified” in the headline.
We are not going to do that. It is worth being explicit about why, because the pressure to do it will not go away.
What a platform actually optimises for
A platform is a good deal for the vendor. One account, one bill, one sales conversation, and a switching cost that grows every month you stay.
It is a good deal for the customer in exactly one case: when the modules genuinely need each other to work. Accounting and payroll belong together because the same numbers flow through both. Inventory forecasting and transactional email do not.
When the modules do not need each other, “unified” mostly means you are paying for four things to get one, and that the one you actually wanted is now shaped by the needs of the other four.
The specific failure we are avoiding
Focused tools die a predictable death. It goes:
- The tool does one thing very well.
- Customers ask for an adjacent thing. Reasonably — they trust the tool.
- The adjacent thing ships, roughly, because it is not the core competency.
- Now there are two things, one good and one adequate.
- Repeat.
Five iterations later the product does nine things adequately and nothing exceptionally, the settings screen has tabs, and onboarding takes an afternoon. The thing that made it worth buying is still in there somewhere, buried under the features that were added to justify the price increase.
We have all used that product. Several of them.
What we are doing instead
Each SimplifyBase product solves one problem completely and is priced on its own. SimplifyStock forecasts demand. It does not run your team’s chat. If you never want SimplifyStock, nothing about SimplifyFlow is worse for it.
They share three things and no more:
- An account, so you do not manage five logins.
- A design language, so the second one you use is familiar.
- Data, when it genuinely helps — SimplifyStock can post a low-stock alert into a SimplifyFlow channel if you have both. It works fine without it.
That last point is the line. Integration is a convenience, never a dependency. If removing one product breaks another, we have built the platform we said we would not.
What this costs us
Being honest about the trade:
Higher acquisition cost. Five products means five things to explain and five audiences to reach. A platform is one story.
Lower revenue per customer, at least at first. Most people will buy one thing. That is the intended outcome, but it is not the one a spreadsheet prefers.
More maintenance surface. Five codebases, five documentation sets, five release cycles. The shared design system helps; it does not eliminate the cost.
No lock-in. If SimplifyStock stops being the best option, leaving costs you nothing but the export. That is a feature from where you sit and a risk from where we sit, and we would rather earn the renewal.
The test we apply
Before anything ships, one question: does this make the product better at the one thing it does, or does it make the product bigger?
Bigger is easy to sell and hard to undo. We would rather ship the fifth good tool than the first adequate platform.