Every sector believes its operations are unusual. Restaurants will tell you hospitality is nothing like retail. Clinics will tell you healthcare has requirements ordinary business software cannot meet. Manufacturers will tell you a factory floor is a different world entirely.
They are all partly right, and the part where they are wrong costs a great deal of money.
Most of what any business does — recording a transaction, tracking what it holds, knowing who owes what, closing the books — is structurally identical across sectors. The genuinely sector-specific portion is real, but it is narrower than it feels from the inside, and it sits in specific identifiable places. Knowing where the line falls is the single most useful thing you can establish before evaluating any software, because it determines which of three very different purchases you should be making.
What is actually different between sectors, and what isn't
Take a transaction. A restaurant serving a table, a pharmacy dispensing a prescription, a distributor releasing a consignment and a clinic completing a consultation are, at the data level, doing the same thing: recording that something was provided, to whom, at what value, reducing something held, and creating an obligation to be settled.
The nouns differ. The structure does not.
The universal portion
In almost every operation, these are the same problem wearing different vocabulary:
- Recording that a transaction occurred
- Knowing what you currently hold
- Knowing who owes you money and for how long
- Knowing what you owe, and to whom
- Closing a period so the numbers are trustworthy
- Knowing which parts of the operation are performing
This is the majority of what business software does. A system that handles it well handles it well in any sector.
The genuinely sector-specific portion
The real differences cluster in four places, and it is worth checking your own operation against them honestly:
Regulatory obligation. A clinic has record-retention and confidentiality requirements a café does not. A food business has traceability duties a design studio does not. This is the least negotiable category — it is not preference, it is law.
Unit of measure and its conversions. A distributor buying in cases and selling in units, a manufacturer moving between raw weight and finished count, a fabric business dealing in metres and rolls. Where conversion is constant and error-prone, it is genuinely structural.
The shape of the transaction. A restaurant order is modified repeatedly before it settles. A construction project bills against milestones over months. A subscription renews without anyone acting. These are different transaction lifecycles, not different labels for one.
What time means. Professional services sell hours. Hospitality sells covers within a service window. Manufacturing runs shifts against output targets. Where the business is fundamentally scheduling something, that scheduling is not a bolt-on.
If your sector's difference does not fall into one of those four, it may be a difference of vocabulary rather than structure — which is a much cheaper problem to solve.
Three ways to buy, and when each is right
Vertical software built for your industry
Software written specifically for dental practices, or restaurants, or freight.
Right when your sector's regulatory or transactional structure is genuinely unusual, and the product has been shaped by years of that specific domain. A clinic buying a system that already understands prescription records is buying real accumulated knowledge.
The cost is that you adapt to it. Vertical products encode one opinion about how the work should be done. If yours differs, you either change your process or fight the software permanently. They also tend to be strong in the specialist area and weak everywhere else — excellent at appointments, poor at inventory.
A general system configured to your operation
A capable general platform, configured to your vocabulary, workflow and modules.
Right when most of your work is the universal portion above, and your sector difference is vocabulary, reporting or a workflow variation rather than regulatory structure. This covers more businesses than the vertical-software market would suggest.
The cost is that configuration quality decides everything. Configured badly, you get generic software with your words pasted on. Done properly, the staff never experience it as generic because it uses the terms they already use.
A custom build
Software written for your operation specifically.
Right when the operation genuinely has no analogue, or when the process is the competitive advantage and encoding it in software compounds that advantage.
The cost is that you own it forever — maintenance, changes, the knowledge of how it works. Custom is frequently chosen for reasons that would have been better served by configuration, and the bill arrives over years rather than at purchase.
Questions that reveal which you need
Before evaluating any product, answer these about your own operation. They are more diagnostic than any feature comparison.
What must be true by law? Write down every regulatory obligation touching your records. If the list is substantial and specific, vertical software becomes much more attractive.
Where does the work already break? Not what you would like — what actually fails now. Stock that never matches. Invoices raised late. Information that lives in one person's head. Software should be bought against real failures, not aspirations.
What do you call things? List the terms your staff use daily. If a product forces different words, every user performs a translation forever, and adoption suffers in a way that is invisible in a demo.
What happens at your busiest hour? Most software is evaluated calmly and used under pressure. If it cannot be operated at peak, it will be bypassed — and a bypassed system produces data nobody trusts.
What would you need to leave? Ask about export before you buy. A vendor who cannot answer clearly is telling you something.
How Truffaire approaches sector work
We build across sectors, and the pattern we keep encountering is that businesses overestimate how unusual they are and underestimate how much their vocabulary matters.
The systems we have delivered on SPEXA include a multi-outlet retail ERP, a clinic management system, warehouse and inventory systems, delivery and logistics management, production monitoring, factory operations and billing and operations management. Ten deployments, ten different systems. What varied between them was rarely the underlying structure — it was the language, the reporting, the specific regulatory obligations, and which modules were needed at all.
That is why our first phase is not building. It is sitting in the operation and documenting how it actually runs, including the parts that live on paper and in habits. You cannot judge whether a sector difference is structural or vocabulary from a requirements document. You can usually tell within a day of watching the work.
Two positions this leads to:
Fewer modules, actually used. The instinct in sector software is to ask for everything the industry might need. A module nobody updates is worse than no module, because it presents stale data as confidently as fresh data.
The counter decides. Whether the system fits the sector is settled by whether staff can operate it during the busiest hour, not by whether it matched a feature list.
What we tell people who should not buy from us
If a business is single-location, with simple stock, and one person holds the whole picture, we say so. If a sector has a genuinely unusual regulatory structure and a mature vertical product already encodes it, buying that product is often the better decision than configuring a general one.
Sector expertise that only ever concludes "you need us" is not expertise.
Where SPEXA fits
SPEXA is the business operating system Truffaire builds — configured per client rather than sold as a fixed sector product. It covers billing and sales, inventory, CRM, accounting, dashboards and AI assist, in the vocabulary of the business rather than a generic one.
It suits the middle case above: operations where most of the work is universal and the sector difference is language, workflow and reporting. It is not the right answer for every sector, and where a regulatory structure demands genuine specialist depth we will say so.
More on the architecture in what a business operating system actually is, and on the failure mode it is built against in why most business software breaks at the counter. SPEXA is live here, and the systems page covers where it sits in Truffaire's work.
Frequently asked questions
Is industry-specific software always better for my industry?
No. It is better when your sector's regulatory or transactional structure is genuinely unusual. Where the difference is mainly vocabulary, a well-configured general system usually fits better, because it bends to your process rather than the reverse.
How do I know if my sector difference is real or just terminology?
Test it against the four categories above — regulation, units and conversions, transaction lifecycle, and the role of time. If your difference does not fall into one of those, it is likely vocabulary, which configuration solves.
Should a small business buy vertical software?
Often not. Vertical products are usually priced and scoped for established operations in that sector, and small businesses end up paying for specialist depth they do not use while accepting weakness in the basics they use constantly.
What if we operate across two sectors?
This is the strongest argument against vertical software. A business that both manufactures and retails will find that any sector-specific product covers one side well and the other poorly, leaving you running two systems and reconciling between them.
How long does sector configuration take?
For the deployments we have run, weeks rather than months. The variable is not the sector — it is how much of the existing process is documented versus living in people's heads.
Where to start
Do not begin by shortlisting products. Begin by establishing where your operation actually differs from any other business, using the four categories: regulation, units, transaction shape, and time.
If the differences are substantial and legally binding, look seriously at vertical software. If they are mainly vocabulary and workflow, a configured general system will usually fit better and cost less to live with. If the process itself is your advantage, custom may be justified — but be honest about owning it for years.
The most expensive mistake is not choosing the wrong category. It is choosing before you know which category you are in.
If you want an assessment of which one applies to your operation, get in touch — including if the answer is that you should buy something other than ours.