Microsoft updates, ISV releases, your own extensions, a setup change in another department — any of them can break a business process nobody was watching. We build parameterized test scripts for your core business processes, the way your team actually works. Run them in one click, in a sandbox, before any change goes into production. Video proof of every run.
30-minute live walkthrough — no commitment
Where breaks come from
Microsoft tests standard Business Central. Nobody tests your combination of it — your ISVs, your extensions, your setup, your data — except you.
Release waves twice a year, monthly updates in between. Pages move, actions get renamed, reports get replaced.
Your apps update on their own schedules. One app’s change can land in a process another app — or your team — depends on.
A developer changes an extension for one department. Another department’s posting routine runs through the same code.
A mandatory field, a posting-date range, a dimension rule, a new approval step. Set up in one area, felt in another.
Your scripts follow each business process end to end, so they cross those lines even when the people making changes don’t.
How it works
You bring one hour per business process and a sandbox. We do the rest.
Features
Purpose-built for the Business Central ecosystem — designed for how partners and IT teams actually work.
Scripts use BC’s built-in Page Scripting tool. Your functional consultants can read, run and maintain them — no developer needed.
Every test run is recorded on video. Stop spending hours reproducing bugs — scrub to the exact moment of failure and see it happen.
Run every script against every connected company in one click, or pick the few a change touches. Know in minutes — not days — whether it broke something.
Step-level logs with millisecond timing show exactly which action failed and why. No more guessing where things went wrong.
Full run history shows pass/fail trends over time. Build a track record that shows every change was tested before it reached your users.
BC credentials are stored with enterprise-grade encryption. Set up your tenant connection once, then focus on the results.
Pricing
Two parts: a one-time Coverage Pack that builds your scripts, and an Update Validation subscription that keeps them running through every change.
Three business processes, scripted and parameterized
Five business processes, scripted and parameterized
More than 10 processes, ISV-driven UI, warehouse, manufacturing, intercompany
A six-month term spans one Microsoft release cycle, preview included, and every change you make in between. Twelve months covers both waves at the lower rate.
Example: 5 Processes + 12-month Update Validation = $4,295 today, then $200/month per company.
Questions
No. Scripts are built with BC’s built-in Page Scripting tool — the same tool your functional consultants already know. We build and parameterize them; your team can read, run and extend them without code.
Yes. Credentials are encrypted at rest and in transit. We never store your business data — we only interact with your BC sandbox or tenant during test execution.
The delivery clock starts when your sandbox, master data and a named SME are ready. From there: one discovery hour per process, then we build, parameterize and run the baseline. Most 3- and 5-process packs are live within two to three weeks.
Run your scripts against the preview in a sandbox before the wave reaches production, and again on release. Script repair is included when an update — Microsoft’s, an ISV’s or your own — changes how a script reaches a page but your process steps stay the same. When the process itself changes (a new step, a different page), the script changes with it: $350 per script, whatever caused it.
No. Microsoft’s release waves are the most predictable change, but breaks come just as often from the combination: ISV updates, your own extensions, setup changes. Run your scripts in a sandbox before any of them reaches production — the full suite or just the ones the change touches.
Integrations with systems outside Business Central: we test the business process inside BC, not the external system. Permission-set testing is on the roadmap — tell us what else you’d like it to cover. Fixing what the tests find stays with you or your partner.