Why not more services, or a standard ERP?
All three routes have a drawback. Here they are side by side, so you can choose with open eyes.
| Property | More SaaS services | Standard ERP | Your own system |
|---|---|---|---|
| Fit | Each service solves its part | You adapt to the system | Built around your processes |
| Data | Spread over several services | Gathered, in the vendor's model | Gathered, in your own database |
| Automation | Connections between services | Within the system's processes | Across the whole company, from a single data source |
| Cost | Per user and year, without end | Licences plus consultants | Fixed project price plus fixed service agreement |
| Exit | Export if the service offers it | A big and expensive project | Everything is already on your accounts |
| Drawback | Double work and many contracts | Long implementation | Requires a decision maker at your end and a developer: us through the service agreement or someone you choose |
Signs it fits
- The same data is typed in several places
- Excel holds the month-end together
- Your own tools live beside the systems
- The CEO or owner decides the same week
- A key person can set aside time for review
Signs it does not
- A standard system works and few users complain
- Procurement requires a larger vendor
- So few employees that the licences hardly show
- Nobody at your end can decide or review
- You want a finished product with an industry guarantee
One hour, free of charge
Bring the list of your services and what they cost. After the meeting we both know whether an AI review is worth doing.
Niels Bosma, niels@bosmainteractive.se