HOLIXORAThe question we hear most often from other founders who know what Holixora is building is: how do you actually do that? Six products, a lean team, simultaneously in development. The honest answer is that you do it by treating engineering capacity as a finite resource and building systems to manage it, not by asking people to work harder.
The Product Separation Principle
The first thing we established was clear product ownership. Each product has a primary maintainer — someone whose name is on it, who knows its codebase better than anyone else, and who makes the architectural decisions. Cross-product work happens, but it does not happen accidentally. It requires explicit coordination.
Without this, developers context-switch between products constantly and own nothing fully. The work gets done but the knowledge stays shallow.
Shared Infrastructure vs. Product Code
We invest heavily in shared infrastructure: authentication services, notification systems, billing integrations, observability tooling. Work done once in the infrastructure layer benefits every product. Product-specific code stays product-specific.
This sounds obvious but it requires discipline to maintain. The temptation when building a feature in Mercora is to build it in Mercora and move on. The discipline is to ask first whether this belongs in shared infrastructure that Hanoman and HRD would also benefit from.
Async-First Communication
With multiple products and a team distributed across different working rhythms, synchronous communication does not scale. We default to written async communication for everything that is not genuinely time-sensitive. Decision documents, architecture notes, and status updates are all written, not verbal.
This sounds like overhead but it is the opposite. Written communication creates a record. Decisions made in meetings disappear; decisions made in documents accumulate.
What We Sacrifice
Running lean across multiple products means you move slower on each individual product than a focused single-product team would. That is a real trade-off. We have made it deliberately because we believe the product portfolio is strategically more valuable than any single product would be alone.