“Should we stay on our standard package or have something custom built?” We hear that question almost every week. The honest answer is rarely black and white. A standard package like AFAS, the widely used Dutch suite for accounting, HR and payroll (afas.nl), is often the fastest and cheapest choice for those processes. Custom software only wins when your distinctive process does not fit a standard package. And surprisingly often the answer is not either-or, but both at once. This article puts off-the-shelf and custom side by side honestly, with cost, a four-year TCO and a clear decision checklist. For the wider story on building custom software and what custom costs we have separate guides.
What is off-the-shelf software, and what is custom?
Off-the-shelf software (a standard package such as AFAS or Exact) is one ready-made product that thousands of companies use the same way: accounting, invoicing, HR, payroll and project admin in one suite. You rent it per month, it runs in the cloud, and the vendor maintains and updates it for you.
Custom software is the opposite. It is built around your process, your rules and your way of working. You own the code, you set the roadmap, and you pay once for the build plus a lower yearly bill for maintenance.
The difference is not quality, it is direction. With standard, you adapt to the package. With custom, the software adapts to you. That sounds obvious, but the effect on cost, speed and freedom is large. If you already feel a standard tool fighting you, read Airtable and Notion versus a custom platform: the same trade-off, different tools.
When is off-the-shelf the right choice?
Off-the-shelf is the right choice the moment your process sits close to the industry standard and you mainly want reliable admin. Think accounting, payroll and HR: work that runs roughly the same everywhere. You get proven software, launch within weeks and manage nothing yourself. For these situations we almost always advise off-the-shelf:
- Accounting, invoicing and payroll. This works roughly the same at every company. Building what AFAS already does perfectly is money down the drain.
- HR and leave tracking. Standard modules cover about 90 percent of the need.
- You have no heavy custom logic. No sector-specific calculations a package cannot handle.
- You do not want to manage software. Updates, security and hosting sit with the vendor.
- Speed over flexibility. You want to be live next month, not next quarter.
In short: for the administrative backbone of your business, a standard package is almost always the sensible start. The question only gets interesting for the process where you stand out.
When does custom software win?
Custom wins the moment a standard package starts working against you on the process that makes your company unique. Not on accounting, but on your own calculation logic, a customer-facing portal or integrations no package offers. If you are building workarounds to make AFAS do something it was never built for, that is the signal. The signals are recognisable:
- You are building workarounds. Loose spreadsheets, double entry and manual steps to make the package do something it was not built for.
- Custom logic no package handles. Think of the points calculation we built into a custom platform for Mastone, something no standard package delivers out of the box.
- A customer-facing interface with your own branding. A portal your clients work in that feels like your product, not a generic screen.
- Integrations the package does not offer. Links to machines, legacy systems or industry-specific services.
- Your process is your competitive edge. If the way you work is why customers choose you, you do not want to force it into a standard mould.
With these signals, custom delivers more than convenience, it delivers real gain: less manual work, fewer errors and a process that moves with your business instead of the other way around. That said, large ERP projects also run out of control when you rebuild a standard package down to the details: on average, large IT projects run 45 percent over budget and deliver 56 percent less value than predicted (McKinsey). And in a recent survey, more than a quarter of organisations exceeded their ERP budget, with extra software and unforeseen customisation the leading causes (Panorama Consulting). Heavy customisation on top of a standard package is often the most expensive of both worlds.
Off-the-shelf versus custom: the comparison
The biggest difference is direction and ownership. With AFAS you adapt to the package, launch fast and pay per user, but the code stays with the vendor. With custom the software adapts to you, you pay more up front and you own the code yourself. The table below sets the nine most important points side by side.
| Trait | AFAS (off-the-shelf) | Custom software |
|---|---|---|
| Fits your process | You adapt | Software adapts to you |
| Time to launch | Weeks | Weeks to months |
| Cost up front | Low (subscription) | Higher (one-time build) |
| Cost per year | Scales with users | Fixed (maintenance + hosting) |
| Custom logic | Limited | Unlimited |
| Customer-facing interface | Generic | Fully your own |
| Code ownership | No (vendor) | Yes (your repo) |
| Maintenance | By the vendor | By you or your studio |
| Vendor lock-in | High | Low |
Pricing and features verified 2026-07; check the source for changes.
What does off-the-shelf cost versus custom?
Standard and custom have completely different cost models, and that is exactly where comparisons go wrong. A package like AFAS bills per employee per month, so you start cheap but keep paying as long as you use it. Custom costs more up front, but the yearly bill is lower and predictable.
| Cost item | AFAS (off-the-shelf) | Custom software |
|---|---|---|
| Up front (build or setup) | €5,000 to €20,000 setup | €25,000 to €60,000 build |
| Per year (30 employees, indicative) | €12,000 to €20,000 licences | €4,000 to €9,000 maintenance + hosting |
| Grows with | Number of users | Barely (fixed hosting) |
| Ownership | Vendor | You |
The AFAS figures are indicative and depend on your modules; see afas.nl for current pricing. The pattern is what counts: standard is a recurring cost that grows with you, custom is an investment with a low fixed tail. For the full build-up of custom pricing, see our price guide for custom software.
Four-year TCO: standard, custom and hybrid
Over four years, pure AFAS often works out pricier than it looks: in our example with 30 employees, standard lands near 107,000 euro, full custom near 74,000 and the hybrid setup near 78,000. An honest sum counts more than the vendor’s invoice, it also counts the internal hours lost to workarounds. Here is the full picture, indicative.
| Cost item | AFAS (off-the-shelf) | Custom (full) | Hybrid (AFAS + custom) |
|---|---|---|---|
| One-time (setup or build) | €12,000 | €45,000 | €28,000 |
| Licences / hosting 4 years | €64,000 | €24,000 | €40,000 |
| Workaround hours 4 years (at €65) | €31,200 (120 h/yr) | €5,200 (20 h/yr) | €10,400 (40 h/yr) |
| Total 4 years | €107,200 | €74,200 | €78,400 |
What stands out: pure off-the-shelf looks cheap until you count the workaround hours for the process that does not fit. Full custom is the sharpest over four years, but asks for the largest investment up front. The hybrid setup, where you keep AFAS for admin and build custom for your core, sits close behind and spreads the risk. Always run this with your own numbers, because the tipping points shift with your team size and the number of workarounds.
The hybrid approach: standard and custom, connected
This is the option missing from most comparisons, and the one we recommend most often. You do not have to choose between all standard or all custom. Keep AFAS for where it shines, accounting, payroll and HR, and build custom for the process that makes you unique. Between the two, you put a connection.
AFAS has an open API for exactly this. With GetConnectors you read data out of AFAS, with UpdateConnectors you write back, so your custom application and AFAS stay in sync without double entry. In practice that means, for example: your customers and staff work in a custom portal that follows your process exactly, and invoices and hours flow automatically into AFAS for the admin.
- You keep the strengths of standard. Reliable accounting and payroll you do not have to maintain yourself.
- You get the freedom of custom. A process and interface that are fully yours.
- You avoid double work. The connection keeps both sides current.
Want a portal on top of your admin? Read how we build customer portals. And with custom, always mind code ownership and vendor lock-in: with AFAS the code sits with the vendor, with custom it belongs to you. Picking widely used tech helps here too. PostgreSQL, React and TypeScript are among the most-used tools among developers (Stack Overflow Developer Survey 2025), so you are never stuck with a single party who alone understands your code.
AFAS or Exact: does it matter?
A common question is “AFAS or Exact?”. Both are Dutch standard packages for accounting, ERP and HR, and they differ in modules, pricing model and user experience. But conceptually they sit in the same category: off-the-shelf software you adapt to. For your admin, the choice between AFAS and Exact is a real trade-off. For your distinctive process, the real question is not AFAS versus Exact, but standard package versus custom. Decide that first, and only then which package.
Decision checklist: standard, custom or hybrid?
Choose per process, not for your whole company at once. If a process sits close to the industry standard and it is admin, AFAS wins. If you have custom calculation logic, a customer-facing screen or you are already building workarounds, custom wins. If you have both, hybrid is the logical outcome. Run through these five questions:
- Does this process sit close to the industry standard? Yes, and it is admin: choose standard (AFAS).
- Are you already building workarounds to force the package? Three or more: time for custom on that process.
- Do you need custom logic or a customer-facing interface? Yes: custom.
- Do you want code ownership and independence from one vendor? Yes: custom or hybrid.
- Do you have both strong admin and a unique process? Almost always: hybrid, with a connection between them.
If you recognise yourself in question 2, 3 or 5, pure standard is probably not your final stop. Unsure whether to build in-house or outsource? First weigh a software studio versus a freelance developer.
How do you get started?
Start small and sharp. Write on a single page which process fights you most, apart from any package. Match it with this guide: admin belongs in standard, your distinctive core deserves custom. Want to test custom without a big budget? Start with an MVP: one core process built well, connected to your AFAS.
Book a free intake call. In thirty minutes we look at your process and give honest advice: standard, custom or the mix. With or without working together, you walk away with a clear picture.
