Services / Custom Business Applications
Custom business applications, built to the bar a marketplace listing has to pass.
Extensions and integrations for Microsoft Dynamics 365 Business Central, engineered upgrade-safe by the team whose own apps have to clear Microsoft's technical validation — 8 times so far. Here, custom work is a last resort, never a first invoice.
Before anything is built
Most of what gets quoted as custom is standard functionality nobody switched on.
So the first phase of any build here is a fit-gap against standard Business Central, and the deliverable of that phase is often a shorter scope than you arrived with.
Why we work this way
Every line of custom code is something that has to be understood, tested and carried forward through every future release — by us, because we are also the team that supports it after go-live. A firm that bills for the build and hands the maintenance to someone else has no reason to keep the build small. We do.
What genuinely has to be built, we build properly. The section below is what “properly” means in practice.
What we build
Four kinds of work, and the shape of each.
Extensions to Business Central
Behaviour your process genuinely needs, added alongside standard Business Central rather than on top of it — so the next Microsoft release is an update, not a project.
Integrations
Your other systems usually work. The job is a clean, defined boundary between them and Business Central, with failures that are visible and re-runnable instead of silent.
Data migration and cutover tooling
The scripts and reconciliations that get you from the old system to the new one with balances that tie — and a rehearsal before the weekend it has to work.
Turning a one-off into a product
When something we built for you turns out to be worth shipping, we know the path: we have taken 8 of our own through it.
The bar
There is no second, looser standard for client code.
What we build for you goes through the same gates as what we ship on the marketplace. It is the same team, so there is nowhere for a lower standard to hide.
8 listings, each past Microsoft’s AppSource technical validation
Upgrade-safe by construction
Built so that a Business Central update is something you take, not something you survive. This is the single largest hidden cost in custom work and it is decided at design time.
Versioned and source-controlled
Every change has a version, a history and a reason. What is running in your tenant is recoverable and explainable months later.
Tested before you see it
Scripted acceptance testing with traceability from the requirement to the result — the same discipline we sell as a product, applied to your build.
Documented, and yours
Handover documentation and operator guides come with the build. Whether the result stays private to your tenant or becomes something you commercialise is your decision, not ours.
Straight answers
What clients ask before commissioning a build.
How do we know a requirement really needs custom code?
You mostly do not, at the point you are asking — which is why we fit against standard Business Central first and price the build afterwards. A significant share of what arrives described as custom turns out to be configuration, a standard feature nobody switched on, or a process that was designed around a limitation the previous system had.
Will custom work break when Microsoft updates Business Central?
Not if it is built to extend rather than to override, and that is a design decision made in the first week. We hold client builds to the same upgrade discipline our own listings have to clear, because we are the ones who would be fixing it either way.
Who owns what you build for us?
You do. It is your build, in your tenant, with the source and the documentation handed over. If it later makes sense to turn it into a commercial app, that is a separate conversation with separate terms — never an assumption folded into the original contract.
Can you work on extensions somebody else wrote?
Often, yes. The first piece of work is usually an honest read of what is there: what is upgrade-safe, what is load-bearing, and what is cheaper to replace than to keep patching. We will tell you which of the three it is before quoting the work.
What does a small piece of custom work actually look like?
A defined change, a fixed price, a version, a test, and documentation — the same shape as a large one. The size changes the duration, not the process. Work without those five things is how a system becomes unmaintainable one small favour at a time.
Do you take on custom work without an implementation?
Yes, on a Business Central that is already live and already someone else’s implementation. What we will not do is build something we can see the standard product already does — we would rather lose the invoice than add to a system that is already carrying too much.
Next step
Describe the requirement. We’ll tell you if standard Business Central already does it.
Thirty minutes with an engineer, not a deck. If it turns out you do not need us, that is a useful answer and it costs you nothing.
sales@dynamicspro.ca · Serving North America · 416-843-6575