Pricing · How it works
How Business Central pricing works.
Every figure on the pricing page lands inside one of the structures below: how we tier each service line, what moves an estimate, and the change-order discipline that keeps a fixed price fixed. Structure you can verify before you sign.
Complexity tiers
Three tiers per service line. Zero ambiguity about what is in.
Every quote we issue maps to one of these tiers. The discovery call exists to place your project on this grid, and the proposal you receive names the tier, the deliverables, and the fixed price.
Scope protection
Customizations and ISV licenses are always scoped separately. They never silently expand a fixed price. If something is not on the included list, it is not in the price, and it only enters the project through a written change order you approve first.
implementation
Implementation
Moving from spreadsheets, QuickBooks, or legacy ERP onto Business Central. Tier is set by entity count, module depth, and how much of your history comes with you.
- 01
Standard
Greenfield deployment for a single company on standard modules.
What's included
- Discovery, fit-gap, and chart of accounts review
- Tenant and environment setup: dimensions, posting groups, approvals, permissions
- Master-data migration with validation and reconciliation sign-off
- Role-based training for AP, AR, sales, inventory, and finance users
- Scripted go-live cutover + 30-day hypercare
Scoped separately
- Custom AL extensions
- Integrations to external systems
- ISV apps and their licenses
- Historical transaction migration
- 02
Extended
Implementation plus scoped customization and a small set of integrations.
What's included
- Everything in Standard
- Scoped AL extensions: custom pages, fields, and logic
- Up to two integrations (Shopify, Salesforce, Power Platform, etc.)
- Advanced workflow + approval matrices
- Extended power-user training, 60-day hypercare, documentation + IT handover
Scoped separately
- Integrations beyond the two in scope
- ISV apps and their licenses
- Multi-entity consolidation
- EDI trading-partner onboarding
- 03
Complex
Multi-entity, manufacturing or warehousing depth, or integration-heavy landscapes.
What's included
- Everything in Extended
- Multi-company and intercompany configuration
- Premium modules (manufacturing, service management) and advanced warehouse setup
- Deep data migration including historical transactions
- Phased go-live with a rehearsed cutover per entity
Scoped separately
- ISV apps and their licenses
- Mid-project customization requests, handled as change orders
- Ongoing managed support after hypercare
al development
AL development
Custom extension work on an existing Business Central tenant. Tier is set by object count, upgrade exposure, and whether we're building new or rescuing inherited code.
- 01
Standard
A single scoped extension with clear acceptance criteria.
What's included
- Table and page extensions, new pages and reports, event subscribers
- Packaged as an upgrade-safe, AppSource-grade AL app, with no per-tenant patches
- Code review against Microsoft's AL guidelines
- UAT environment per milestone, then tenant deployment
Scoped separately
- Integrations to external systems
- AppSource submission and Microsoft validation
- Performance work outside the agreed objects
- 02
Extended
Multiple workstreams: extensions, upgrades, and performance in one engagement.
What's included
- Everything in Standard
- Background jobs, report suites, and multi-object extensions
- C/AL-to-AL conversion or version-to-version upgrades with regression test plans
- Performance tuning: SIFT and index analysis, slow-report remediation
Scoped separately
- Rescue work on inherited codebases
- AppSource submission and Microsoft validation
- Telemetry instrumentation programs
- 03
Complex
Rescue projects, AppSource submissions, and tenant-wide performance programs.
What's included
- Everything in Extended
- Inherited-codebase diagnosis: we rebuild only what is needed
- AppSource validation owned end to end through Microsoft review
- Telemetry instrumentation and posting-routine profiling
Scoped separately
- ISV apps and their licenses
- Net-new features surfaced mid-rescue, handled as change orders
- Ongoing retainer support after handover
integrations
Integrations
Keeping Business Central in sync with the rest of your stack. Tier is set by system count, sync direction, and how much failure handling the volumes demand.
- 01
Standard
One integration, one primary system, a well-known API surface.
What's included
- Integration discovery: systems, data flows, volumes, failure modes
- Written design contract: entities, sync direction, conflict rules
- Idempotent processing with retries and a replay path
- Reconciliation report + operational runbook handoff
Scoped separately
- Additional entities or endpoints
- Bi-directional sync beyond the agreed entities
- ISV connectors and their licenses
- 02
Extended
Bi-directional sync across several entities with full failure handling.
What's included
- Everything in Standard
- Bi-directional sync with explicit conflict rules: primary-wins, last-write-wins, or quarantine
- Dead-letter handling, alerting, and telemetry you can actually watch
- UAT against production-like volumes + failure-recovery rehearsal
Scoped separately
- Additional systems joining the landscape
- EDI trading partners beyond the initial set
- Post-go-live monitoring, handled under a support retainer
- 03
Complex
Multi-system landscapes, EDI, and event-driven architecture.
What's included
- Everything in Extended
- EDI (850, 810, 856, 855, 997) with trading-partner onboarding and exception handling
- Azure Service Bus and event-driven patterns
- Streaming into Azure Data Lake, Synapse, or Fabric for analytics
Scoped separately
- New trading partners after go-live, handled as change orders
- ISV middleware and its licenses
- Ongoing monitoring, handled under a support retainer
Cost drivers
What drives cost
User count
Licensing scales per user at Microsoft's published list rates. That part is arithmetic. On the services side, cost tracks distinct roles more than raw headcount: every role adds permission sets, approval routing, and a training track of its own.
Current system
Coming from nothing or spreadsheets means designing processes from scratch. QuickBooks migrates along a well-worn path. NAV or on-prem Business Central adds object-by-object code assessment. Another ERP, such as NetSuite or SAP B1, means heavier mapping and parallel-run validation. Each step up the ladder moves the estimate.
Data-migration depth
Master data plus open balances is the standard, predictable path. Pulling historical transactions across multiplies mapping, validation, and reconciliation effort. It is routinely the single biggest swing in an implementation estimate, which is why we price it as its own line.
Integration count
Every integration carries its own discovery, design contract, failure handling, and UAT. None of that is shared overhead. Count moves the estimate linearly; complexity (bi-directional sync, EDI, event-driven volume) moves it faster than count does.
Customization appetite
Every gap closed with configuration is cheaper than code, and our fit-gap says which is which. Where AL is genuinely warranted, it's scoped as named objects with acceptance criteria. “Make it work like the old system” is the most expensive sentence in ERP, and the most controllable cost lever you have.
Change orders
Scope grows. The price does not, until you say so.
- 1
Scope growth gets written down
When new work surfaces, our team writes it up as an explicit change order: what it is, why it surfaced, and the impact on hours and price. No verbal scope, no “we will sort it out at the end.”
- 2
You approve or reject in one click
The change order arrives by email with one-click Approve and Reject buttons, with no portal sign-in required. The decision is recorded, and rejected work simply does not happen. The fixed price stands.
- 3
Billing follows approval, never the other way
Approved change orders join the scope and appear on your invoice as their own line. Anything not approved in writing is never billed. Full stop.
Fixed-fee offers
Two ways to start small
Both are fixed fee, agreed in writing before any work begins. A bounded engagement that ends with a document you own, whether or not you go further with us.
Business Central Health Check
From $4,750
10 business days
A certified Business Central developer reviews your tenant, extensions, integrations, and performance, and a PM runs the readout with your stakeholders.
- Written findings across configuration, code, integrations, and performance
- Prioritized roadmap: what to fix now, next, and never
- Delivered by a senior developer with a PM-run readout
Migration Readiness Assessment
$7,500
7 business days
Before you commit to an implementation, know exactly what moves, what does not, and what it costs, in writing, from the team that would deliver it.
- Current-state review of your NAV, GP, QuickBooks or other ERP data and processes
- Data-migration map: what migrates, what archives, what gets rebuilt
- A fixed-price migration proposal you can act on
Speed to number
A written fixed-price proposal within five business days of discovery.
That is the commitment. After the discovery call, we place your project on the tier grid above and send a proposal with milestones, deliverables, and the fixed price, within five business days. If something cannot be priced fixed yet, we say so and tell you exactly what would make it priceable.