CIO / Technical Director · Internalize or outsource D365 X++ development
X++ D365 development: in-house vs outsourced — the Skalp AI third way
In-housing X++ costs €200-400k/year and stays risky. SI outsourcing costs €150-300k/year with technical lock-in. Is there a third way?
TL;DR
X++ Dynamics 365 development comparison: in-house team (€250-400k/year), SI (€150-300k/year) or Skalp AI (€120-140k/year). 7 criteria.
Microsoft D365 F&O expertise
10 ans
D365 F&O
€200 / ticket
Fixed price per resolved ticket
vs €800-1,200 at a typical SI
48 h
Average delivery time
Azure DevOps
Validated by your IT
The problem with your current vendor
In-house or outsourced X++ — each option has its limits
- ✗In-house: 2-3 specialized FTEs (architect + 1-2 devs) cost €250-400k/year loaded, with no guarantee of expertise depth across all D365 modules.
- ✗SI outsourcing: €150-300k/year AMS, technical lock-in, high exit cost.
- ✗Turnover risk on senior X++ profiles: 18-24 months average tenure before switching companies.
How SKALP solves it
Skalp AI: 1 in-house FTE steers + AI executes = full autonomy at €120-140k/year
- ✓1 in-house D365 lead (€90-100k/year loaded) steers, reviews, validates. Skalp AI produces X++ code.
- ✓Expertise depth: Skalp AI covers all D365 modules (Finance, SCM, Project, HR, Retail) without multi-profile hiring.
- ✓Guaranteed continuity: no dependency on a single senior, no turnover risk on the production chain.
How it works
1
Submit your ticket
Describe the business or technical need in a few lines. No 50-page spec required.
2
AI generates the extension
X++ code, unit tests and documentation produced in under 48 hours.
3
Validation on your Azure DevOps
Pull request submitted on your repository. Your IT lead reviews and validates before merge.
4
Delivered — you pay €200
Once merged, it's delivered. No billing if the ticket isn't resolved.
The factual comparison
| Criterion | Full in-house (dedicated X++ team) | In-house lead + Skalp AI |
|---|---|---|
| Total annual cost | €250-400k (2-3 loaded FTEs) | €120-140k (1 FTE + Skalp) |
| Expertise depth | Limited to modules covered by team | All D365 F&O modules |
| Initial hiring delay | 3-6 months per profile | 1 profile to hire (1-3 months) |
| Turnover risk | High on senior X++ profiles | Limited to the lead (immediate reversibility) |
| Vacation service continuity | Risk if single senior on leave | Skalp AI absorbs, lead resumes on return |
| Training / ramp-up cost | €20-50k per profile over 6-12 months | Included in Skalp AI cost |
| Code & doc capitalization | Yes, if team discipline | Yes, delivered with every ticket |
Frequently asked questions
Does the "in-house lead + Skalp AI" option replace a senior D365 architect?+
For X++ production (extensions, classes, integrations), yes: Skalp AI applies Microsoft patterns more consistently than a rushed human architect. For target architecture (data-model choice, integration strategy, redesigns), a senior consultant stays relevant in occasional engagement mode.
Exactly what profile should we hire in-house?+
A D365 F&O functional architect or senior D365 developer who can read X++, review a Pull Request and challenge a proposed solution. Profile can come from an SI, a former D365 customer, or in-house upskilling. Market cost €80-100k/year loaded.
What if I want to fully internalize eventually?+
It's actually enabled by Skalp AI: all code and docs are in YOUR Azure DevOps. You can gradually hire X++ devs that pick up the stack with no transfer cost. The "lead + Skalp AI" model can be a transitional step toward a full in-house team.
Related pages
To go deeper on the same topic, seen from other angles.