Services
Two ways to engage
Both are scoped as fixed-fee, deliverable-based work — not open-ended hourly billing.
Not sure which one fits? Choose the Assessment if you're currently estimating or scoping a client upgrade and need to quantify integration risk before submitting a fixed-price bid. Choose Re-architecture Capacity if you already have a signed SOW and defined spec, but no available AL developer bandwidth to execute it.
Lead offer
Integration re-architecture capacity
For VARs with signed client SOWs needing immediate AL delivery capacity.
Contained, fixed-fee work items — migrating specific Dynamics NAV integration points to Business Central SaaS patterns — delivered directly into your repository, to your coding standards, against an agreed deliverable and acceptance criteria.
Who this is for
- A Microsoft Dynamics VAR with a signed client commitment to migrate or extend an integration, and no available C/AL or AL developer bandwidth to execute it on the committed timeline.
- Teams that need the legacy pattern — direct SQL table access, .NET interop assemblies, file-drop/polling jobs — replaced with AL HttpClient calls, OAuth 2.0 client-credentials or on-behalf-of flows, and Azure-side middleware where appropriate.
- Engagements where the deliverable can be scoped in advance: a defined integration point, a defined target pattern, a defined acceptance test.
Representative pattern mapping
| Legacy NAV pattern | Target BC SaaS pattern |
|---|---|
| Direct SQL table access | AL HttpClient + REST API |
| .NET interop assembly | Azure Function / Logic App middleware |
| File-drop / polling job | Event-driven webhook or queue trigger |
| Hardcoded service credentials | OAuth 2.0 client-credentials flow |
Actual target pattern is confirmed per integration point during scoping — this table is representative, not a substitute for assessment.
How it works
- Pricing
- Fixed fee per deliverable, agreed before work starts — not hourly.
- Delivery
- Asynchronous. Work lands as commits/PRs in your repository, with core availability overlapping European afternoons through US Eastern mornings. No live meetings.
- Confidentiality
- NDA signed before any client- or codebase-specific detail is discussed.
- Attribution
- White-label. The work is delivered under your standards and your repository history — your end client is never made aware of a third party.
- Scope
- Defined per engagement: one integration point, or a batch of related ones, with explicit acceptance criteria agreed up front.
How async delivery works
Repository access
Delivery via branch or pull request directly in your private GitHub or Azure DevOps repository — no separate delivery channel.
Code quality
Every commit includes AL Test Codeunits and follows your team's AL Linter / CodeCop rules.
IP ownership
100% white-label. Full IP transfers to your repository on delivery — no retained rights, no attribution.
Secondary offer
NAV Integration Cloud-Readiness Assessment
For VARs scoping upcoming upgrades who need to quantify integration risk upfront.
A flat-fee, time-boxed assessment for a VAR that needs to understand the shape of a client's integration surface before committing to a migration project — or before scoping the work above.
What's delivered
USD 2,500–4,000 flat fee · 3–5 business day turnaround
Invoiced in USD; EUR/GBP-equivalent invoicing available on request at the prevailing rate.
A written findings document covering:
- Inventory of existing integration points in the current NAV environment — direct SQL access, .NET interop, file-drop/polling jobs, and any other custom integration surface.
- SaaS-compatibility classification for each integration point — will it work as-is on Business Central SaaS, does it need re-architecture, or is it a dead end that needs replacing entirely.
- Remediation effort estimate per integration point, so the migration project can be scoped and priced with real numbers.
- Recommended sequencing — which integrations to tackle first, and which dependencies block which.
Illustrative report structure
- Executive summary
- Integration inventory
- Risk / SaaS-compatibility classification
- Remediation roadmap
| Integration point | Status | Target pattern | Effort |
|---|---|---|---|
| Direct SQL sales sync | Incompatible with SaaS | AL API page + Azure Function | Medium |
Sample structure shown for illustration only — not drawn from any real client engagement; actual findings are specific to your environment.
Who this is for
VARs scoping a Business Central migration for a client and needing a credible, independent technical inventory of the integration risk before quoting the project — without committing to the full re-architecture engagement first.