Author
Exclolab
Articles, guides, and insights from the Exclolab team — covering custom software, operational systems, and building for service businesses in Southeast Asia.
The most common failure mode in custom software is invisible until it is expensive to fix. Discovery-first development is the structural fix — and it starts long before a line of code is written.
Off-the-shelf tools have a seductive pricing model. The true cost only becomes visible over time, in workarounds, integrations, and the growing gap between what the tool does and what your business actually needs.
Operational efficiency is not glamorous. It does not appear in vision statements. But in service businesses, operational systems are the closest thing to a durable competitive advantage that most companies will ever build.
Technical debt is not a developer problem. It is the natural result of building under uncertainty — making reasonable decisions with incomplete information, and then not revisiting them as the information improves.
The term MVP has become so overused that it has almost lost meaning. Before deciding to build one, ask what assumption you are actually trying to test — and whether a smaller thing can genuinely test it.
The problem is not the spreadsheet. It is the moment when the spreadsheet becomes load-bearing — when the business depends on it in a way that the tool was never designed to support — and nobody notices until the fragility becomes a crisis.
The typical procurement process for a software development partner reliably produces the wrong result because it evaluates the wrong things. Here is the framework that actually works.
API integration projects have a higher failure rate than most other software projects. They work on delivery, then break six months later when something upstream changes — and nobody knows why because the integration was never properly documented.
The most valuable insights about a product come from observing actual use, not from testing during development. The first month after launch generates more actionable learning than the entire development period — but only if your team is watching.
Many organisations run Discovery Sessions as a ceremony — a scheduled event that produces a document and reassures the stakeholders. The difference between a ceremonial session and a genuine one is not the format. It is the quality of the questions asked, and the willingness to let the answers change what gets built.