Your Industry Expertise Is the Product

TL;DR: The people who've spent decades mastering an industry - learning its edge cases, workarounds, and unwritten rules - are sitting on the most valuable input for building software. AI now lets small teams turn that expertise into products. The domain knowledge is the product.

Every industry has what I think of as invisible infrastructure. The unwritten rules, the exception handling, the operational workarounds that keep businesses running but never make it into a requirements doc.

At Carro, we saw this constantly. Our ops teams had ways of doing things that made perfect sense on the ground but were completely invisible to the engineering team. People used their personal phones to call customers because it was faster than going through the CRM. WhatsApp groups became the real escalation system, not the ticketing tool. Spreadsheets persisted even after we built proper systems because they were just more flexible for edge cases.

This knowledge - the kind that lives in people's heads and in the workarounds they've built over years - is too granular, too contextual, too obviously obvious to the people who live it. But it's exactly what determines whether software gets adopted or becomes shelfware.

The Adoption Problem Nobody Plans For

I've watched systems we spent months building get ignored because they couldn't handle a workflow that the operations team considered trivially basic. The developers didn't know to ask. The operators didn't know it needed to be said.

Here's what I learned the hard way: building is only 20% of the story. Change management is the 80%. You can build the most powerful tool in the world, but your people might not adopt it. Labour is relatively affordable in our part of the world, which means automation is always a choice, not an inevitability. If the person on the ground doesn't see how the tool benefits them personally, they'll work around it. They want to finish their work with the least effort possible and go home to their lives. They're not going to take extra steps just because an engineer somewhere thinks the data model needs it.

And there's a corollary that I think about constantly: if it's not in the SOP, it's not behaviour. You can't deploy new software as a by-the-way. It needs to be embedded into actual procedures - how people start their day, how they close a ticket, how they hand off a task. The domain expert knows where those procedures live. The engineer doesn't.

Why Vertical Keeps Winning

Vertical SaaS - software built for a specific industry - is growing 2-3x faster than horizontal tools. And I think it's a market correction that's been a long time coming.

For years, businesses tried to make generic tools work. We did this at Carro. We tried Salesforce, HubSpot, Zendesk, Freshdesk, Intercom, MessageBird. Every time, we'd spend months configuring widgets and plugins, bending the tool to fit our workflow. The providers all wanted their platform to be the centre of action, even when CRM was just one part of the flow. All that customisation creates fragile, undocumented systems that only one person understands. And the result is still a compromise.

Vertical SaaS wins because it starts from industry reality. When your system understands your specific workflow - the entities, the relationships, the edge cases - you don't need to configure that. It just works. Better retention. Higher lifetime value. Faster adoption. Businesses choose vertical software because it works on day one.

The Gap

Here's the tension. The people with the deepest industry knowledge - the operators, the domain experts, the people who've run these businesses for twenty years - don't build software. And the people who build software don't understand the industry deeply enough to build the right thing.

This gap kills most digitisation attempts. Either the domain expert hires an agency that builds something technically solid but operationally naive. Or a tech team builds something clever that nobody on the ground uses. The only thing that works is building together - not handoffs, not specs, not weekly status calls. Actually sitting alongside each other, constantly finding the best resolution to problems that the domain expert knows about.

Why Now

Two things changed.

AI made small teams wildly capable. What needed a large engineering department can now be built by a small, experienced team in months. The barrier between having deep industry knowledge and turning it into a real product has never been lower. (I wrote about this here.)

And the market is starving for it. Across Southeast Asia, almost every industry I've spoken to - logistics, clinics, dealerships - is still running critical operations manually. The ASEAN digital transformation market is projected to hit $295 billion by 2030. A significant chunk of that is industry-specific solutions - not another horizontal platform, but software that actually understands the job.

If you've spent years mastering an industry - learning its edge cases, its pain points, its unspoken rules - you're sitting on something more valuable than most tech startups have: genuine product-market insight. You don't need to become technical. You don't need to raise a Series A and hire an engineering team. You need a partner who can turn what's in your head into a product.

That's what we do at First To Fly. We believe that businesses have common operational patterns - sales, CRM, scheduling, inventory, fulfilment - and we bring a decade of experience building and rebuilding these systems at Carro. What we need from partners is the domain nuance. Once we understand the specifics of your industry, we can apply very distinct solutions to it. In automotive and dealership-related systems, we're already confident we're the best in Southeast Asia. We want to extend that to other industries where our systems knowledge can make a real difference.

Your expertise isn't just useful context for a requirements doc. It's the product.

Tell us what you're working on.