The system fits your business, not the other way round.
Off-the-shelf software makes your business bend to its screens, and whatever will not fit ends up in a spreadsheet alongside. We build ERP and CRM around the way you already work: no licence per user, no modules nobody ever opens.
- No licence per user
- The code is yours
- Fixed price after the consultation
Four signs you will probably recognise from your own office.
Licences for occasional users
Someone in the warehouse books a delivery in twice a month; the bookkeeper looks in once a quarter. The seat is paid for in full either way, month after month.
The spreadsheet beside the system
A step the software does not cover moves into a spreadsheet. The file grows, and at some point the truth lives there while the system holds only a version of it.
The same address in three places
Customers in the CRM, invoices in the accounts, stock in the warehouse tool. When an address changes it changes in one place, and from then on the lists contradict each other.
Modules nobody opens
Production, staff planning, project time: the whole package is paid for and part of it is used. Dropping the rest one by one is rarely on offer in a catalogue product.
Six areas we draw on to assemble what you use every day. And nothing else.
Orders and projects
From quotation to order to invoice, with status, dates and documents in one place. Everyone can see where a job stands without having to ask.
Customers and contacts
Addresses, the people behind them and the whole history: quotations, orders, complaints, last contact. Whoever answers the phone knows who is on the line.
Stock and materials
Levels, goods in and out, serial numbers and reordering. What gets used is booked against the job as it happens, instead of being estimated at the end of the month.
Invoicing and payments
Invoices with a QR bill, reminder runs, outstanding items and matching against the bank account. Anyone who has already paid stops receiving reminders.
Hours, absences and staff
Time booked to a job or a project, holidays and absences, expenses. At the end of the month the basis for the payroll is already there.
Reports that agree
Margin per job, utilisation, outstanding items, turnover per customer. Every figure comes from the same records, so nothing contradicts anything else.
What you already hold comes with you
A changeover rarely fails because of the new software. It fails because of the old data. So we plan the migration from the start, and not in the last week before going live.
What gets carried over
Customers and contacts, articles and prices, outstanding items, closed jobs and the documents behind them. The history stays readable: what happened last year is still there in the new system.
Cleaning up is half the work
The same firm spelled three ways, addresses of customers who no longer exist, article numbers following two different schemes. We tidy that before the move, otherwise the errors simply move house with everything else.
Running in parallel, not on a cut-off date
Where it makes sense, the old and the new system run side by side for a while and we compare the figures. You switch over once both say the same thing.
Your spreadsheet is the best specification there is
Almost every business has a file in which part of the operation is genuinely mapped out. It has grown over years and describes the process more precisely than any requirements list we could draft around a meeting table.
The columns are the fields
Whatever has a column in the sheet needs a field in the system. The tabs are the steps, and the colours somebody uses to mark rows are, in truth, states.
The formulas are your rules
Surcharges, discount bands, working out a deadline: the formulas say how your business calculates. We read them, ask about the two places that stay unclear, and build them in.
What the sheet cannot do
Several people at once, permissions, a history of who changed what and when, and a link to the job it belongs to. That is exactly where the sheet stops and the system starts.
Made to measure or off the shelf?
Both routes work. The difference does not show on day one; it shows in year three.
Fit with your process
ERP made to measure
The software follows the way of working your people already know.
Standard ERP from a catalogue
The process follows the software, and the remainder moves into a spreadsheet alongside.
Licence per user
ERP made to measure
None. Anyone who needs to take part gets access, even for twice a month.
Standard ERP from a catalogue
Per seat and per month, however rarely somebody signs in.
Modules you do not need
ERP made to measure
We build what gets used. What is missing can be added later.
Standard ERP from a catalogue
Included in the package, paid for, and rarely dropped one by one.
When the business changes
ERP made to measure
The change is built in, because the code belongs to you.
Standard ERP from a catalogue
You wait for the supplier’s next release or pay for a special adaptation.
Who owns the result
ERP made to measure
Source code and data sit with you, with the accounts in your name.
Standard ERP from a catalogue
You rent the right to use it, and the data comes out in the supplier’s export format.
Dependence on the supplier
ERP made to measure
Someone else can take over the maintenance: a handover, not a rebuild.
Standard ERP from a catalogue
Price rises, a forced upgrade or the end of a product line are the supplier’s decision.
Honestly: if a catalogue package covers almost everything you need, buying it is cheaper. We will say so at the initial consultation rather than build you something that already exists.
Four stages, and after each one you know where you stand.
- 1
Watching the work where it happens
We walk through the job in the place where it actually happens: the office, the warehouse, the workbench. Not only with management, but with the people who will be using the system every day.
- 2
The plan and a fixed price
Before the first line of code you see which modules come in which order, what the screens look like and what the whole thing costs. The price holds for exactly that scope.
- 3
Module by module, the most urgent first
We build in stages, and the first stage is whatever hurts most today. Your people are already working in the new system while the rest is still being built.
- 4
Migration, training and go-live
The data moves across, your people are trained on the finished system, and we stay close through the first weeks of operation. After that the code, the data and the accounts are yours.
When we advise against it
- If a catalogue package already covers almost everything you need: buying it is cheaper, and we will tell you so.
- If your processes still change every month: they have to settle first, or we build a version of the business that will no longer exist by the autumn.
- If nobody in-house is willing to look after the data: a system is only as good as what is kept up to date inside it.
- If the aim is only to move from one licence supplier to another: a system of your own is not the way to do that.
What does an ERP made to measure cost?
It depends on how many areas the system has to cover and how much has to come across from the software you use today. That is why we do not name a figure before we have seen how you work. At the free initial consultation we settle the scope, and you then receive a fixed price for exactly that scope. Many start with a single module and build outwards from there, so the budget can be released in stages rather than all at once.
Free initial consultationDo we have to replace everything at once?
No, and usually that is the worse idea. We start with the area that costs the most time today and leave the rest running for now. APIs let the old and the new system talk to one another until the old one becomes redundant piece by piece. That way the business carries on while the changeover happens.
What happens to the data in the software we use today?
It comes across. Customers, articles, outstanding items and closed jobs with their documents are carried over so the history stays readable. Before that we clean up: duplicates, addresses of customers who no longer exist, the same firm spelled two ways. Where a supplier offers no usable export, we tell you before the quotation what can be retrieved and what cannot.
Can the system be connected to our accounts package?
As a rule, yes. Bexio, Abacus, Sage and most till and shop systems offer APIs. The figure is then entered once and agrees on both sides, instead of someone typing it twice. Where a system has no API, we say so before the quotation and look for another route, such as a controlled exchange of files.
What if our processes change later on?
Then the software is changed. Because the code belongs to you, that does not depend on whether a supplier takes the change into its next release. The places that tend to move most, such as prices, discounts and forms, we build from the start so that you can adjust them yourself without ringing us.
Who trains our people?
We do, on the finished system and with your own data rather than a sample company. That includes a short guide to the handful of steps that come up every day. During the first weeks after going live we stay close, because that is when the questions appear that nobody asks in a training room.
Show us the spreadsheet sitting next to your system.
At the free, no-obligation initial consultation we look at how you work and tell you honestly whether a system of your own pays off or whether a catalogue package is enough. We reply within 24 hours.
Book an initial consultationJust a quick question? The AI assistant in the bottom right answers straight away.
Ready for the summit?
Tell us about your project. We reply within 24 hours with an honest assessment. Free and without obligation.
hallo@aurphi.chAurPhi MoukrimMarktstrasse 18, 8853 Lachen SZ, SwitzerlandPostal address, no walk-in service. Appointments by arrangement.