A workflow takes too many steps. A report does not show finance what it needs. A customer wants something the standard system does not do. The first reaction is usually “can we just customize it?” For Business Central customization vs ISV, the better first question is whether you should, and whether the problem already has an answer.
What is customization in Business Central?
Customization means adding or changing functionality beyond what standard Business Central provides. Today that is done with extensions written in AL, which add to the product without changing its base code, unlike the direct code modifications common in older Dynamics NAV systems. Examples include custom workflows, pages, reports, approval processes, calculations and integrations. Whatever is built, your organization owns it and must maintain it.
What is an ISV solution?
An ISV, or independent software vendor, builds software that extends a platform. Many Business Central ISV apps are listed on Microsoft AppSource and cover areas such as expense management, advanced warehousing, eCommerce, payroll, shipping, document management, field service, payments and electronic document exchange. You adopt functionality someone else has built, tested and supports. That does not make it right by default, but it should be considered before any custom build begins.
The real question: build, buy or change the process
Many requirements exist because a process was designed around an old system or a spreadsheet. Moving to Business Central customization vs ISV is a chance to simplify it. Ask:
- Does standard Business Central already do this?
- Can configuration solve it?
- Can the process be simplified?
- Is there a suitable ISV app?
- Is the requirement truly unique to us?
- What will it cost to maintain over time?
When Business Central customization vs ISV makes sense
- The process is a real differentiator and forcing it into a generic app would hurt
- No suitable ISV app exists after you have evaluated what is available
- The benefit is measurable, such as hours saved or errors avoided, not “users would prefer it”
- You need an integration with a proprietary or legacy system that has no connector
When an ISV app is usually better
- The need is common across many businesses, such as payments, expenses or shipping
- The functionality is complex, such as tax rules, payment processing or electronic document exchange
- It needs ongoing updates as regulations and Business Central change
- Speed matters: a mature app can be live sooner than a custom build, though it still needs evaluation, configuration and testing
The hidden cost of customization
Compare five-year cost, not the quote.
| Cost area | Question to ask |
| Development | What will it cost to build? |
| Testing | How much testing across scenarios and releases? |
| Upgrades | Who keeps it working as Business Central updates twice a year? |
| Support | Who troubleshoots when it fails? |
| Documentation | Can a new developer understand it? |
| Knowledge dependency | What if the developer leaves? |
| Future change | What will it cost to modify when the business changes? |
As an illustration only: a custom build quoted at $20,000 can cost more over five years than an ISV subscription priced higher at the start, once upgrades, support and changes are included. Run the numbers with your own quotes.
How to evaluate an ISV app
| Criterion | What to check |
| Functional fit | Does it meet the requirement without major customization around it? |
| Compatibility | Does it support your Business Central version and deployment? |
| Vendor stability | How long has the vendor been in market, and what is the roadmap? |
| Upgrade approach | How quickly does the vendor support new Business Central releases? |
| Support | What are response times and who answers? |
| Licensing | What is the full cost by user, company, module and year? |
| Exit | What happens to your data if you stop using it? |
Ask for references from organizations like yours.
A simple decision order for Business Central customization vs ISV
- Does standard Business Central meet the need? If yes, use it.
- Can configuration solve it? If yes, configure.
- Can the process be simplified? If yes, change the process.
- Is there a suitable ISV app? If yes, evaluate it.
- Is the requirement unique and valuable? If yes, consider custom.
- Can you justify the five-year cost? If not, do not build it yet.
Do not customize the problem
Ask the people who use the process why they do it this way, what step solves what problem, whether the requirement still exists and what would happen if they stopped. Sometimes the best customization is the one you do not build.
Next step
If you are deciding whether to configure, customize or buy, a Business Impact Assessment from 360 Visibility reviews the requirement, the options and the long-term cost so you can make the call before development starts.