Custom application or SaaS: how to choose for your SME?
Concrete criteria to decide between an off-the-shelf SaaS and a custom application, with typical Swiss SME scenarios.
The right choice between an off-the-shelf SaaS and a custom application does not depend on company size or budget: it depends on the gap between your real processes and what a standard tool can do. Here are the concrete criteria to decide, without dogma.
When an off-the-shelf SaaS is more than enough
A standard SaaS is the right choice in three situations:
- Your processes are fairly generic. Basic accounting, e-signature, shared calendar: well-tested tools handle this at low cost and zero maintenance.
- The business stake is light. If the tool does not touch your core value or sensitive data, paying a subscription beats commissioning development.
- You are at the very beginning. Before five recurring customers, Notion plus Stripe plus a calendar is often enough to validate the business.
When custom becomes the right investment
Conversely, a custom application becomes relevant as soon as one of these signals appears:
- You work around the SaaS limits every day. Manual exports, intermediate Excel files, copy-paste between two tools: each workaround costs time and increases the risk of errors.
- Your business uses specific vocabulary. Arborists do not think in "leads" and "deals" the way a generic CRM assumes. Forcing external vocabulary slows the team down.
- You have business logic that differentiates you. SaaS flattens it; a custom application turns it into a competitive advantage.
- You stack several pricey SaaS for partial functions. Three tools at CHF 200/month equal CHF 7,200 per year: a custom investment pays off quickly.
The often-overlooked hybrid options
The choice is not binary. Three hybrid patterns work particularly well in Swiss SMEs:
- SaaS + custom layer: A standard CRM on the commercial side, plus a custom application that consumes the CRM API to automate specific business tasks. The best of both worlds.
- Internal hub + integrations: A custom application that aggregates data from several SaaS (accounting, calendar, e-signature) into a unified view adapted to your daily work.
- Custom prototype, then SaaS later: Validate the idea and the process in custom mode, then move to a SaaS once the market offers a mature standard solution.
Three questions to decide
- How many hours per week do your teams "compensate" for the current SaaS misfit? If the answer exceeds 3 to 5 hours, custom is almost certainly profitable.
- Is there any data or know-how you would refuse to store with a third-party vendor? If yes, the question is settled.
- What is the expected lifespan of the tool? Under 18 months, SaaS often wins. Beyond that, the depreciation of custom becomes obvious.
Why agentic engineering changes the equation
Historically, custom development was disqualified for SMEs because its cost and timeline were incompatible with project size. Agentic engineering changes the picture: a custom prototype in 2 to 3 weeks for CHF 5,000 to 10,000 makes the option viable even to validate an idea. The "SaaS vs custom" calculation reopens and often tips toward custom for genuinely specific business processes.