Every ERP vendor will tell you that you needed one two years ago. Most of the time that is wrong. Spreadsheets and a decent accounting package carry a company much further than the sales conversation suggests, and moving too early buys complexity you cannot yet absorb.
Moving too late is expensive in a different way. A 30-person retailer with two shops and a webshop can lose a day a week to copying stock figures between systems before anyone calls it a problem, because the cost arrives as overtime and errors rather than as an invoice.
This article sets out the five signals that mean it is time, how common an ERP actually is at your size, what Swiss law does and does not require of your systems, the cheaper steps to try first, and what a first ERP costs and takes.
How do you know it is time to move to an ERP?
When reconciling your systems by hand costs more than running one system would. In practice that shows up as five signals: the same number in three places, someone's week spent reconciling, a slower month-end at the same volume, customers waiting on a colleague for an answer, and audit requests that take days. One signal is normal. Three at once means it is time.
One: the same number exists in three places and nobody knows which is right. Not "the reports differ", which is normal. This is when a decision gets delayed because two people brought different figures to the same meeting.
Two: someone's full week is reconciliation. Add up the hours spent copying between systems, chasing statuses and rebuilding the same report. When that reaches roughly one full-time person, the system is now cheaper.
Three: month-end takes longer than it did last year, at the same volume. That is the clearest early indicator of structural strain rather than a busy period.
Four: you cannot answer a customer without asking a colleague. Stock, delivery date, order status. If the answer lives in someone's head, growth is capped by that person's availability.
Five: a compliance or audit request takes days. Swiss law requires business records to stay complete and readable for ten years (Code of Obligations, Art. 958f). Traceability that has to be reconstructed by hand each time is a risk that will eventually be priced.
One signal is normal. Three at once means the reconciliation cost has crossed over.
How many companies your size actually run one
Fewer than the marketing suggests. Across the EU in 2025, 41.1% of small enterprises with 10 to 49 employees used ERP software, against 88.7% of enterprises with 250 or more, according to Eurostat. Wholesale and retail trade sits above the average at 53.8%, accommodation and food service lowest at 26.7%.
Eurostat summarised the same survey as a 48 percentage point gap between small and large enterprises, and ERP is still the most widely used of the business applications it tracks. The survey does not cover Switzerland, and it starts at ten employees. That matters here: the Federal Statistical Office counts 561,952 micro-enterprises with fewer than ten employees, nearly nine in ten Swiss market enterprises, and another 52,476 small enterprises. For most of them an accounting package plus a few well-kept lists is not a stage to be ashamed of. It is the normal state of a company that size.
What Swiss law does and does not require of your systems
The obligations are real, and a good Swiss accounting package already meets them. Under the Code of Obligations, legal entities, and sole proprietorships or partnerships with at least CHF 500,000 in revenue, must keep full accounts; smaller sole proprietorships and partnerships only need records of income, expenditure and assets. Records must be kept for ten years and stay readable.
VAT adds an audit trail. The Federal Tax Administration describes it in its guidance on VAT audits as the ability to follow a transaction from the individual voucher through the accounts to the VAT return, and back, at any time, regardless of which tools you use. Invoicing adds the QR-bill, which replaced Swiss payment slips on 1 October 2022 and has accepted only structured addresses since November 2025. Payroll reporting can run through Swissdec's ELM standard, which serves all payroll data recipients with one electronic transmission.
None of this needs an ERP. It needs an accounting and payroll setup that supports the current standards, and records that someone keeps in order. What compliance does expose is traceability done by hand: if answering an auditor means rebuilding a trail from three spreadsheets, that is signal five, and it is a reason to act.
What are the cheaper things to try first?
Fix the numbering, fix the master data, and connect the two systems you already have. Most small companies get a year or more of runway from consistent article and customer codes, one owner for master data, and a single integration between the webshop or CRM and the accounting package.
That is weeks of work rather than a programme, and it is not wasted if you do eventually move: clean master data is the largest cost line in any migration, so you are pre-paying it either way. The reasons are set out in ERP data migration.
For a retail or consumer-goods business, the usual first integration is between the webshop, the tills and the accounting package, with the payment provider's settlement reports as the fourth source that never quite matches. Deciding how payments are reconciled is part of the same work, covered in taking payments in Switzerland. Consistent article codes across shop and webshop are also what any later stock forecast depends on, as demand forecasting without a data science team explains.
What does an ERP actually cost a small company?
For a company of 10 to 30 people, a first-year total between CHF 25,000 and 80,000 is a typical Swiss market observation, covering licences, configuration and data cleanup. The figure rises steeply with integrations, parallel running and the number of processes in scope. Internal time is the line most often left out of the budget, and it is a real cost.
| Company size | Typical first-year total | Where the money goes |
|---|---|---|
| 10–30 people | CHF 25,000–80,000 | Licences, configuration, data cleanup |
| 30–100 people | CHF 80,000–250,000 | Above, plus process work and integrations |
| 100–300 people | CHF 250,000–700,000 | Above, plus parallel running and training |
Indicative Swiss market observations, varying widely with complexity and how clean your data is. Two things are consistently underestimated: data migration, and the internal time your own people spend, which is real cost even though no invoice arrives for it. How to compare those costs with the benefit before committing is in how to measure ROI on a digital transformation, and what outside help should cost is in what a Swiss company should pay for consulting.
How long does a first ERP take to implement?
For a company of 15 to 50 people with one legal entity and largely standard processes, three to six months from signed contract to go-live is a typical observation, provided master data was cleaned beforehand. Companies that start the cleanup only after signing usually add a quarter. Most of the time goes into decisions and data, not into setting up software.
The calendar matters as much as the duration. A retailer should not go live in November or December, and anyone who files VAT quarterly is better off starting at the beginning of a VAT period, so that each return comes from one system rather than two. The first weeks after go-live are slower than the old way, and the people who know the old workarounds need protected time to learn the new routine. At 15 people that is almost everyone; at 80 it is a handful of key users per department, who then teach the rest.
Choose the smallest thing that solves it
A small company does not need the platform a 2,000-person manufacturer needs. The Swiss market has options that fit properly at this scale, including finance-and-payroll-first products that handle local compliance natively and remove an entire integration workstream. Swissdec publishes the list of certified payroll software, which is a quick first filter.
The trap is buying for the company you hope to be in five years. You will migrate again anyway when you get there, and in the meantime you pay for complexity you are not using. Pick for the next three years. Two questions sort most cases: how many hours reconciliation costs each week, and how complex the processes really are.
What breaks when you move too early
A system bought before the company needs it arrives without the discipline to run it. Nobody owns master data, so the new system inherits the same duplicates in a structure that is harder to correct. Nobody has agreed the process, so it gets configured around whoever was in the room. And because the pain it was meant to solve had not yet appeared, no one can tell whether it worked.
The visible cost is the licence. The real cost is that a company of 25 people now spends part of every week feeding a system, and the flexibility that made it fast is gone. That trade is worth making, but only once the reconciliation cost has genuinely crossed over.
A worked example: a 35-person retailer
Take a hypothetical 35-person retailer of outdoor equipment with two shops and a webshop. The numbers are illustrative. It runs an accounting package, a webshop platform, a till system and a stock spreadsheet that one person updates every morning.
Three signals are present. The webshop sells items the shops have already sold. The person who maintains the spreadsheet spends about two days a week on it. Month-end takes eight working days, two more than a year ago at similar volume.
Rather than start a selection, the owner spends six weeks on the cheaper steps. One article code, the barcode already on the product, becomes the key in tills, webshop and spreadsheet. The finance lead is named owner of the article list. The webshop is connected to the accounting package so that orders and payments post automatically. Three months later, month-end is back to six days and the spreadsheet takes half a day a week. One signal remains: stock across three locations still cannot be seen in one place. That is now a specific, testable requirement, and the selection that follows is shorter and cheaper because of it.
What to do before you talk to a vendor
Write down the ten things about your operation that break a standard system. Not three hundred requirements, ten. Then have vendors run those ten as scripted scenarios with your own data, rather than showing you a demo they rehearsed.
The federal SME portal makes the same point in its guidance on digitalisation as a multi-step process: analyse where the company stands before changing anything or buying a new program, then look at processes and data before setting goals. Our version of that fits on a page, as described in how to write a digital strategy for an SME, and the first quarter of work is sketched in digital transformation for an SME: the first 90 days.
The selection method itself, and why the requirements matrix fails, is set out in ERP selection for the Swiss mid-market. Once you are running the programme, the constraint stops being technology and becomes how fast your own organisation answers questions, the pattern in why ERP programmes stall.
If the honest answer is "not yet"
Say so, write down the three signals you will watch, and revisit in six months. A deferred decision with a trigger is a decision. Our ERP consulting practice tells companies to wait fairly often, and that conversation costs nothing.
Sources
- Eurostat — E-business integration, Statistics Explained, ERP use by size class and economic activity, 2025
- Eurostat — Larger enterprises used more e-business apps in 2025, news release, 20 May 2026
- Federal Statistical Office (BFS) — Kleine und mittlere Unternehmen, enterprises by size class, 2023
- Fedlex — Swiss Code of Obligations, SR 220, Art. 957 duty to keep accounts, Art. 958f retention
- Federal Tax Administration (ESTV) — MWST-Kontrolle, the VAT audit trail and retention periods
- SIX — QR-bill, replacement of payment slips and structured addresses
- Swissdec — Lohnstandard-CH (ELM), electronic payroll reporting
- Swissdec — Certified ERP and payroll software, register of certified products
- SECO SME Portal — Digitalisierung als mehrstufiger Prozess, maturity analysis before buying software
Related reading
- ERP selection for the Swiss mid-market
- ERP data migration: the part that overruns, and why
- Why ERP programmes stall in Swiss mid-market companies
- Digital transformation for an SME: the first 90 days
- ERP consulting
Working on this right now?
Tell us where you are in two questions. A consulting partner reviews every enquiry within 2 business days.
