HOLIXORAThe conventional software company playbook is well-established. Build a minimum viable product, hire sales, close customers, use the revenue to build more product. Sales drives revenue. Revenue funds engineering. The cycle repeats.
We did not follow that playbook. We built seven products before we hired a single salesperson.
This was not an accident or an oversight. It was a deliberate choice based on a specific theory about what kind of company Holixora is and what our customers actually need.
The Argument Against Early Sales
Sales is expensive in a specific way. It creates commitments. A salesperson who closes a customer creates expectations: delivery timelines, support obligations, feature requests. Each customer closed before the product is complete adds to the commitment stack.
For a company building complex business software, premature sales create a particular problem. The customer closes on a promise. The product delivers a reality. When those two things diverge, which they always do when sales outruns engineering, the relationship starts in deficit. The team spends energy on remediation instead of building.
We wanted to avoid this cycle. Not because sales is unimportant. Because we wanted the product to be the primary argument for the business, not the salesperson.
What Building Seven Products First Actually Means
When we talk about building seven products, we mean: Mercora POS, Hanoman HMS, the HRD module, Accounting, the Credit System, Orbit, and Archily Studio. Seven distinct products covering different operational areas, all sharing one technical foundation and one data model.
Building this without a sales team meant building without a customer acquisition feedback loop. We were not getting weekly signals from prospects about what they needed. We were building based on our own understanding of how Indonesian businesses actually operate.
This is a risky approach. It can result in building things nobody wants. The discipline required is deep domain knowledge before you write the first line of code.
Our team spent time in the operations of Indonesian retail businesses, hotels, and construction firms before specifying product requirements. Not just reading market reports, actually understanding what a hotel front desk does at 2am when there is a reservation dispute, what a retail owner is looking for when they check the previous day's numbers, what a construction firm needs from BOQ estimation when a client wants a cost breakdown in 24 hours.
That domain knowledge is what we built the products against.
The Integration Argument
There is a second reason to build the full stack before selling. Integration is not a feature you add later. It is an architectural decision you make at the beginning.
A company that sells a POS system and then separately sells an accounting module is building two products that talk through an API. The data model is different. The integration is bolted on. When it breaks, fixing it requires understanding two separate systems.
We built one stack from the start. The data model is shared. Orbit is the integration layer by design, not by retrofit. When a customer adopts Mercora POS and later adds Accounting, the integration is already done. It was never a separate project.
This only works if you build the whole stack together. Selling the POS first and building accounting three years later means the integration work is always playing catch-up.
What Comes Next
We built the products. Now we are activating the go-to-market layer.
This does not mean hiring a large sales team. It means finding the right early customers, running them through the full stack, and letting the product demonstrate what it can do. Our bet is that a customer who runs their retail business on Mercora, their HR on the HRD module, and their finances on Accounting, all integrated through Orbit, becomes the best possible demonstration of what the stack does.
That customer does not need a salesperson to explain the value. They live it.
We are still in the early stages of this. But the foundation is built deliberately, and the sequence was right.
Holixora is a tech studio building integrated business systems for Indonesian operators. Contact hello@holixora.com if you want to be part of the early customer cohort.