- Use the standard wherever it covers the process well; build only what sets you apart or what the standard does not solve.
- Prefer extensions connected to the ERP over changing the system core.
- Require documentation, code you own and a maintenance plan.
- Start small, validate with users and evolve.
Not every need justifies development. But some processes are not covered, or are poorly covered, by off-the-shelf software. Knowing how to tell them apart saves time and money.
Buy, configure or build
| Option | When it makes sense |
|---|---|
| Use the standard | The process is common and the software covers it well. |
| Configure | The system has parameters and flows that fit your case. |
| Extend | A specific feature is missing and connects to the existing system. |
| Build tailor-made | The process is unique, strategic or there is no suitable solution. |
Signs a tailor-made solution may pay off
- The process is a differentiator for the business.
- The team uses spreadsheets and messages to fill a gap.
- There are sector or organisation-specific rules the standard does not provide for.
- Systems that do not talk to each other need connecting.
Risks and how to reduce them
| Risk | How to reduce it |
|---|---|
| Dependence on whoever built it | Documentation, accessible code and a clear contract on ownership. |
| Difficulty updating the base system | Extensions that do not change the core. |
| Scope that grows without control | Short deliveries, priorities and approval by phase. |
| Failures and lack of support | Testing, follow-up after go-live and a maintenance plan. |
| Poorly protected data | Access control, action logs and backups from the design stage. |
How to build well
- Map the process with the people who run it.
- Define the essentials of the first version and what waits.
- Build in short cycles, showing results and gathering feedback.
- Test with real users before launch.
- Follow up and evolve based on use.
Questions to ask the supplier
- Who owns the code and documentation?
- How is the connection to the ERP and other systems made?
- How are base system updates handled?
- What testing and follow-up are included?
- How are support and evolution handled after go-live?
Scenarios and solutions
The team uses spreadsheets for a specific process.
Custom application connected to the ERP, delivered in short cycles.
Process supported, without duplicating data.
Code and documentation stay with whoever built it.
Documentation, code you own and extensions that do not change the core.
Evolution without being locked in.
Next step
RegalTec builds custom applications and extensions connected to the ERP, and always starts by checking whether the standard solves it.