We build custom solutions and regularly advise against it. This is where the line is.
A standard package is almost always the wisest choice when your process is similar to that of others: it is available tomorrow, cheaper and someone else maintains it. custom development pays off when your process sets you apart, when you connect multiple packages, or when licensing costs are higher than building for your number of users.
NEXT TO EACH OTHER
The differences at a glance
| ASPECT | Standard package | custom development |
|---|---|---|
| Available | Immediately, often the same day | Weeks to months |
| Upfront costs | Low or none | One-time investment |
| Ongoing costs | Per user per month, persistent | Hosting and maintenance only |
| Fits your process | You adapt to the package | The system follows your process |
| Maintenance | Supplier does it | Your responsibility or that of your builder |
| Property | You rent access | You own the code |
| Stop | Cancel, export data | You keep everything, but also the maintenance |
| Risk | Supplier changes price or stops | Wrong assumptions are expensive to build |
WHEN WHAT
When which
The rule of thumb we use: if an existing package covers roughly eighty percent of what you need, take that package. Solving that last twenty percent with custom development almost always costs more than it yields.
The tipping point usually lies with the number of users or when you have to connect five packages together to complete one process.
- Standard for a common process — accounting, email, storage: don't build that yourself.
- Standard for few users — licensing costs then remain low.
- Standard in haste — working tomorrow beats perfect in three months.
- Standard for a small budget — a half-custom system doesn't help anyone.
- custom development if the process is what sets you apart — then you don't want to squeeze it into a template.
- custom development for many users — licence costs per person are increasing structurally.
- custom development for five linked packages — one system is often cheaper.
- custom development if you want to be the owner — no supplier who determines your price.
FREQUENTLY ASKED QUESTIONS
More about the choice
Do you really ever recommend a standard package?
Regularly. If an existing package covers your process, custom development is a waste of money and we will say so in the first conversation. We would rather make no money from a project that should not have existed than from a system that you will regret in a year's time.
Can I start with a standard package and switch later?
Often yes, provided your data is exportable. Check that export option before you start, not after you have already built up two years of history.
How much does custom development cost approximately?
One defined process starts at €2,950. A full portal with links is usually between €8,000 and €20,000. The classes are detailed on our cost page for web applications.
What if I don't know?
Count how many hours per week the current process takes and how many users are working with it. Those two numbers usually already determine the calculation. We make that calculation free of charge.
CONTINUE READING
Of course, continue reading about this subject.
Which side suits your situation?
Tell us which process is problematic and with how many people. We charge for both sides.