Guide
When to use standard Business Central, a marketplace app, a low-code tool or a custom extension
Start with the simplest option that fits, and move on to the next only when it does not. This guide is a checklist, not a sales page. Microsoft Dynamics 365 Business Central is a product of Microsoft. AppoGen is an independent service and is not affiliated with, endorsed by or sponsored by Microsoft.
Decision table
| The need | Best-fit category | Why |
|---|---|---|
| A rule or screen the standard product already offers (a setting, a workflow template, a role centre change) | Standard Business Central | It is supported as part of the product and moves with updates. A custom extension adds something to maintain. |
| A need many companies share (for example a common industry feature or a well-known connector) | A packaged marketplace app | A packaged app is built for many users and has a published price. Check that it fits your process. |
| A simple automation between systems, with no new screens or posting rules | A low-code automation tool | It runs outside the system, so check how it fails, who owns it and what it costs as usage grows. |
| A one-off or occasional report | Standard Business Central reports and analysis tools | Often no build at all. Reserve a custom report for one used every day. |
| A rule or approval specific to how your company works. Examples: a second approval, a limit that stops a posting, a checklist, a nightly reminder | A custom extension | If nothing off the shelf matches your process, the standard product should still not be changed. An extension adds the feature beside it. |
| A feature that will need regular change as the business changes | A custom extension, with a change process | It can be updated on its own. Compare against the cost of a subscription and change requests. |
| A tight link that must post or validate inside Business Central | A custom extension | Posting and validation live inside the system. |
| Anything that works around the product's security or licensing | None of these | We do not build it. |
When custom is the wrong choice
The standard product already does it
Check setup first. A setting costs nothing to maintain.
A packaged app already fits
If it covers most of the need and you can adapt your process to the rest, a packaged app may be less to look after.
You are not sure what you need yet
Building before the need is clear is risky. Write the need down first.
The need is temporary
A one-time data fix or a short project rarely justifies an extension.
You cannot test it
An extension needs a sandbox and someone to test in it. If you cannot give that time, wait.
It is very large
Some requests need a closer look. For those we prepare a custom quote, or tell you honestly that another route is better.
It would change the standard product
We do not change the standard product.
Where AppoGen fits
If you have worked through the table and a custom extension is the right route, AppoGen can design, build, test and install it. It is one route among several.
Describe the need
You describe what you need in plain words. No technical knowledge needed.
We check the standard product first
We research how standard Business Central already handles your need, so your extension fits the way the system works.
Review before the build
You review the design as a storyboard and a functional document. The storyboard is illustrative. Nothing is built until you approve one.
Fixed rules for the price
The build price comes from the size of the approved design.
Sandbox first
We install in your sandbox, where you test, then in production when you accept.
Changes later
A change after approval is a change request, priced on the difference.
Questions
Where do I start?
With standard Business Central: check whether a setting, a workflow or a report already covers the need.
How do I choose between a marketplace app and a custom extension?
Ask how much of the need a packaged app covers. If most, adapt your process for the rest. If your process is specific to you, custom fits better.
When does a low-code tool stop being enough?
When the logic has to run inside Business Central, for example to stop a posting or add a screen.
Do you ever say a custom extension is not the right route?
Some requests are very large or need a closer look. For those we prepare a custom quote, or tell you honestly that another route is better.
What does a custom extension cost?
Simple extensions usually cost USD 2,000 to 5,000, standard ones USD 5,000 to 12,000 and advanced ones USD 12,000 to 20,000. Above USD 20,000 we prepare a custom quote after reviewing the design.
Is AI involved?
AppoGen uses AI to help with research, design, building and testing.
Is a custom extension the right route?
Describe the need in plain words and see the design before anything is built.
Microsoft Dynamics 365 Business Central is a product of Microsoft. AppoGen is an independent service and is not affiliated with, endorsed by or sponsored by Microsoft.