Why we exist
Business technology should make sustainable growth, operational efficiency and long-term success easier, not harder. That sounds obvious until you have watched a company organise itself around its software instead of the other way round: a month-end that takes three weeks, a warehouse that trusts the paper list over the screen, a sales team keeping the real prices in a spreadsheet.
Our mission is narrower than "digital transformation" and, we think, more useful: make sure the system fits the business on day one and still fits in year five. We do that by looking at the policies, processes and people behind the technology before we look at the technology.
Why ERP?
Because at some point every business needs one truth. One place where a purchase order, a goods receipt, a supplier invoice and a payment are the same transaction seen from four sides, and where the sales order, the delivery, the customer invoice and the cash that comes in connect to it. We call that the transactional spine: procure-to-pay on one side, order-to-cash on the other, inventory and finance in the middle. Everything else (CRM, projects, manufacturing, HR) hangs off it.
Spreadsheets and point solutions carry a business surprisingly far. They stop scaling at the same moment for everyone: when the same fact has to be entered twice, by two people, and one of them is on holiday.
An ERP is also how a company meets obligations it did not choose. Books must be kept, VAT must be filed, and invoices increasingly must be issued as structured data through government or network platforms 1. That work does not shrink because the company is small.
Why ERP for small and medium-sized companies, and family businesses?
Three reasons, none of them about being "ready for enterprise software".
Regulation no longer scales with size. Belgium's B2B e-invoicing mandate applied to every VAT-registered business from 1 January 2026, regardless of turnover. Poland's KSeF reached most VAT payers in April 2026. Since 1 September 2026, every French business must be able to receive structured e-invoices, with SMEs issuing from September 2027. Germany's issuing obligation lands in 2027 and 2028 1, 2. A ten-person company faces the same clearance systems as a ten-thousand-person group, with a fraction of the finance staff.
Key-person risk is the SME's biggest system risk. In many mid-sized companies the process lives in one head. When that person retires, resigns or falls ill, the process leaves with them. An ERP with documented processes turns personal knowledge into institutional knowledge: the difference between a company that can be handed to the next generation and one that has to be re-learned.
Growth is cross-border by default. A Swiss or German SME that adds a sales entity in Poland or a subsidiary in the US inherits a new GAAP, a new tax regime, a new bank protocol and a new payroll. The system has to carry that without a second implementation. Why ERP systems differ
Why process first, technology second, even in the age of standard cloud software?
The argument for "just take the best practice" is seductive: modern cloud ERPs ship with pre-configured processes, adopt them and be done. We agree with half of it. Standard beats custom almost every time. But a best practice is an average of other companies' decisions. It tells you how most businesses approve a purchase; it cannot tell you whether your approval limits are sensible, who should hold them, or what happens when the approver is on the shop floor without a laptop.
That is why we start with a Target Operating Model in four layers:
Use the arrow keys to move between the parts of the model.
Direction
Vision
Why the business exists and where it wants to be. Everything below it, from the business idea to the last system setting, should trace back to it.
Direction
Mission
What the business does, for whom, day after day, to move towards the vision. It decides which ideas, plans and strategies belong to the business at all.
Direction
Strategy
The choices that turn vision and mission into priorities: the business strategies and, derived from them, one strategy per function. In the operating model, strategy ends where policies begin.
Direction
Tactics
How the strategy is carried out: the processes that run the work, the people who run the processes and the technology that enables both. This is the part of the model an ERP implementation touches most.
Corporate pyramid
Business idea
Connect the vision and mission to the customer need the business exists to meet. Make the intended value explicit before deciding how to organise delivery.
Evidence: an agreed purpose, target customers and the value promised to them.
Corporate pyramid
Business plan
Describe the business model, expected demand, resources and economics. Test whether the ambition can be sustained and which assumptions need evidence.
Evidence: a viable plan, measurable outcomes and accountable owners.
Corporate pyramid
Business strategies
Choose where to compete, how to serve customers and which capabilities the business must develop. Translate corporate choices into coherent priorities for each function.
Evidence: agreed priorities, capability gaps and a coordinated change portfolio.
Functions
Functional strategies
Selected function
Each function derives its own strategy from the business strategies: research and development, marketing, sales, contracting, service, support, HR, IT and finance. Each function then needs an operating model of its own; the model enlarges Finance as the example.
Functions
Finance Target Operating Model
The finance strategy made operational in four layers, agreed in this order: policies, processes, people and technology. In an implementation, every functional stream drafts the same four layers for its own scope before anything is configured.
Technical services (customisation and integration) follow the functional leads. Never the other way round.
Target Operating Model
Policies
What the business has decided, and why: approval limits, credit rules, revenue recognition, what counts as a project.
Processes are understood in terms of their purpose, not merely as "how we have always done it".
Role in operationalisation
Leader & Director of Operationalisation
- Simple & Clear, not Complex & Vague
Evidence: policy owners, approval limits and agreed treatment of exceptions.
Target Operating Model
Processes
How those decisions are executed, end to end.
Role in operationalisation
Leader & Director of Operationalisation
- executing streamlined Processes
Evidence: future process maps, control points and representative acceptance scenarios.
Target Operating Model
People
Who executes each step, with which skills, in which location and language.
The right people are identified early and enter the testing and training plans by name, so availability gaps and staff transitions are called before they become risks.
Role in operationalisation
Organisation of Resources for Operationalisation
- executing streamlined Processes
Evidence: role ownership, access needs, capacity commitments and a training plan.
Target Operating Model
Technology
Which system, which configuration, which integration supports the three layers above.
The 3Ps are the three layers above: policies, processes and people.
Role in operationalisation
Enabler & Accelerator of Operationalisation
- enabling the predefined 3Ps
- executing streamlined Processes
Evidence: a traceable solution design, tested configurations and assigned operational ownership.
Configure the technology before the first three layers are agreed and you get a templated business run by nobody in particular. Agree them first and standard software configures itself quickly, because the questions it asks already have owners and answers.
Process first. Technology second.
It is the sentence we repeat most often, and it is the reason our projects look different.
Sources
All regulatory statements as of September 2026.
- E-invoicing mandates in Europe, 2026 overview (Belgium, Poland, France, Germany, ViDA): finbite.eu and spscommerce.com
- France Finance Act 2026 / DGFiP timeline; Germany 2027 to 2028 issuing obligation: novutech.com