Is the process standard or your competitive edge? That distinction decides which tool to invest in. Four practical questions to clarify the answer.
Accounting, email, payroll — these are standard processes. Thousands of companies run them the same way. Off-the-shelf packages (SAP, QuickBooks, Workday) are mature, secure and cheap. Building custom software here is usually a waste.
But your "competitive edge" — a proprietary pricing algorithm, a customer-specific integration, a particular operational flow — becomes generic the moment you shove it into a packaged tool. The 20 % of the business that actually generates value drops to 0 %. Here custom software is non-negotiable: if you run the same tools as your competitor, you produce the same result.
Before picking a side, answer these four:
1) Is the process industry standard or company-specific? 2) Does the data model change with the outside world (billing, integrations)? If yes, packaged software or SaaS with an open API is fine. 3) Will your business model around this process shift in the next 24 months? If yes, a packaged tool's configuration ceiling will bind you. 4) Is your competitive edge hiding inside the process? If you cite the process when you explain "why customers pick us", custom software is mandatory.
Two or more "distinctive" answers (unique, concealed competitive edge) point to custom. Otherwise start with a packaged tool and migrate when you hit the ceiling — that's the cheapest strategy.
In real life, most B2B decisions are not "all custom" or "all off-the-shelf" — they are the smart combination of both. The playbook: run the standard layer (accounting, HR, CRM backbone, email) on best-in-class packaged software; build the differentiating layer (pricing engine, customer portal, operational flow, data transformation) as custom software integrated to the packages via APIs.
This gives you three things: (1) vendor safety and low total cost of ownership on the commodity layer, (2) full control and fast iteration on the differentiator, (3) each layer can evolve at its own pace. In practice this usually lands as "SaaS + API + a thin custom application layer". As you grow the custom layer expands; the packaged layers stay stable. At Setviva about 70 % of customers start hybrid — those who ask for a fully custom build often decide, once we map the flows, that they prefer to move standard processes to packaged tools too.
The mistake B2B decision-makers make most often: comparing only the license fee or project price. Real cost sits below the waterline. When you move to packaged software, add: data migration and cleanup, training, productivity loss during transition, integration development, reporting customization, and process redesign. These typically total 3–5× the license fee. When you move to custom, add: design and discovery, development, testing, training, maintenance and continuous iteration, infrastructure (servers, monitoring, backups), and ownership risk (who runs it if the team leaves). These typically total 1.5–2× the build fee.
For an honest comparison, write out a 24–36 month total cost of ownership (TCO) and compare the two options on the same footing. In every Setviva proposal we present this line-item TCO upfront so the decision rests on "actually cheap", not "looks cheap". Getting the migration cost right can matter more than the choice itself.