CIO / CFO / IT buyer · Compare SI time-and-materials/retainer with the Skalp credit model

SI time-and-materials/retainer vs Skalp AI credit model — who bears the risk?

In time-and-materials or retainer mode, you pay for time spent or availability — never for the delivered outcome.

TL;DR

SI time-and-materials and retainer vs Skalp AI credit model for D365 F&O: billing unit, risk, visibility, outcome-based payment. Factual comparison.

Log in
Microsoft D365 F&O expertise
10 ans
D365 F&O
1 credit / ticket
≈ €400 on Basic, €200 on Pro
vs €1,000-1,500 per day at a D365 F&O partner
Market benchmark observed by Skalp AI (2026)
2–4 h
Average delivery time
Azure DevOps
Validated by your IT
The problem with your current vendor

SI models shift the risk onto the buyer

  • ✗Time-and-materials bills days, with no result or deadline commitment.
  • ✗The retainer dilutes the unit cost and bills peaks on top.
  • ✗Budget hard to forecast and to challenge in governance.
How SKALP solves it

The credit: a transparent unit price, paid on outcome

  • ✓1 credit (≈ €400 on Basic; €200 on Pro and Max, degressive in packs) per developed ticket, the same whatever the complexity.
  • ✓No volume commitment or deposit; cost follows real consumption.
  • ✓Free chat, qualification and design: the credit is only consumed when the code is generated.

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 2–4 h on average.

3

Validation on your Azure DevOps

Pull request submitted on your repository. Your IT lead reviews and validates before merge.

4

Delivered — 1 credit (≈ €400 on Basic, €200 on Pro)

The credit is only consumed when the development is generated (smart contract). Once merged, it's delivered. No billing if the ticket isn't resolved.

The factual comparison

CriterionSI time-and-materials / retainerSkalp credit model
Billing unitPerson-day or monthly retainer1 credit (≈ €400 on Basic, €200 on Pro) per developed ticket
Overrun riskHigh (uncapped time)None (fixed price per ticket)
Unit-cost visibilityDiluted / variableTransparent, same on every ticket
Volume commitmentOften imposedNone
Outcome-based paymentNo (time or availability)Yes (credit only consumed when code is generated)

Frequently asked questions

Aren't the Pro and Max subscriptions a retainer?+
The Pro subscription (€2,000/mo/env.) funds the permanent connection to your context (MCP + Azure DevOps) and deployment, not the development itself, which stays per-credit and outcome-based. Basic has no subscription.
Is the credit really degressive?+
Yes: a credit is worth ≈ €400 on Basic and ≈ €200 on Pro, and, on Pro and Max, the unit price drops when buying in packs. You budget to the decimal (capacity × credit price).

Submit your first ticket

1 credit (≈ €400 on Basic, €200 on Pro) if resolved. Nothing if not. Chat and needs analysis free.