Skalp AI onboarding guide
From account creation to your first delivered Dynamics 365 F&O ticket — in 30 minutes. Step by step, no detour.
Prerequisites
Before you tackle your first Skalp AI ticket, make sure these are in place. Most are already present in a standard D365 team.
- An active Dynamics 365 Finance & Operations environment (cloud LCS or accessible dev sandbox).
- An Azure DevOps project with a Git repository containing your D365 code (models, classes, forms, extensions).
- An Azure DevOps Personal Access Token (PAT) with scopes Work Items (Read & Write), Code (Read), Build (Read).
- A professional email account to create your Skalp AI account (Starter offer or higher).
- At least one IT-side person able to review and validate X++ Pull Requests (architect, D365 lead or senior developer).
Step 1 — Create your Skalp AI account
Account creation is online, no commitment and no credit card. You only pay for tickets actually resolved.
Join the waitlist
Submit your contact details via /contact with your D365 F&O version, annual ticket volume, and IT team size. Reply within 24-48 business hours.
Sign the framework agreement
A framework contract covers terms: €200 flat fee per resolved ticket, no billing on unresolved tickets, 100% client code ownership, GDPR compliance. No volume commitment.
Receive your access
You receive a Skalp AI admin login, a signed DPA (Data Processing Agreement), and the contact details of your dedicated person for kickoff.
Step 2 — Connect Azure DevOps
Azure DevOps integration is the backbone of the Skalp AI model: all tickets, Pull Requests and deployments flow through your repo. This guarantees you stay in full control of the code and the production merge.
Create the Azure DevOps PAT
In Azure DevOps → User Settings → Personal Access Tokens. Select scopes: Work Items (Read & Write), Code (Read), Build (Read). Recommended duration: 1 year with scheduled rotation.
Enter the PAT in Skalp
In your Skalp AI dashboard → Settings → Integrations → Azure DevOps. Paste the organization URL (https://dev.azure.com/your-org), project name, PAT. Click Test connection.
Select the target repository
Skalp AI lists available repositories. Select the one containing your D365 F&O code (extensions, models, X++ classes). This repo will receive generated Pull Requests.
Configure the webhook
Skalp AI auto-configures an inbound webhook on your Azure DevOps project to receive PR status updates (merged, declined, requalified) and trigger pay-per-result billing.
Step 3 — Submit your first ticket
For the kickoff ticket, choose a low-risk topic: a table extension, an event handler, or a custom SSRS report. The goal is to calibrate the flow, not to test on a production-critical case.
Describe the business need
In 5-10 lines: which D365 screen is involved, which business rule to add, expected behavior on success and on error. No 50-page spec required.
Specify the technical context
D365 module (Finance, SCM, Project, HR…), One Version platform version, target model where the extension will be added. Skalp AI generates a Microsoft-compliant extension in THAT model.
Submit the ticket
Submission via the Skalp AI form or directly from Azure DevOps Boards. You receive a ticket reference and a lead time estimate (24 h, 48 h or 72 h depending on complexity).
Wait for the Pull Request
Standard 48 business-hour lead time. You receive a notification (email + optional Teams) when the Pull Request is opened on your Azure DevOps repo with generated code, SysTest tests, and documentation.
Step 4 — Validate the Pull Request
Validation stays 100% on your side. You apply your usual criteria (code review, CI tests, XppBP / FxCop gating) before merging to production. If the PR fails your review, it is not billed.
Review the code
Your architect or D365 lead opens the PR on Azure DevOps. The code is commented, naming conventions follow your standards (analyzed from your repo), tests are present.
Run the CI pipeline
If your Azure DevOps pipeline is configured (XppBP build + automated SysTest tests), it runs on the PR branch. Everything must pass green before merge.
Test in UAT environment
Optional but recommended: deploy the PR on a Tier-2 (UAT) environment via LCS for functional validation by 1-2 reference business users.
Merge or request revision
If all OK: merge to the release branch. If adjustments needed, comment on the PR; Skalp AI produces a revision within 24 h, up to 2-3 iterations with no surcharge.
Step 5 — Understand billing
Skalp AI bills €200 ex-VAT (20% VAT applies in France) per ticket actually merged on your Azure DevOps repo. As long as a ticket is not merged, it is not billed. As long as a ticket is in revision (your comments pending), it is not billed.
Billing is monthly, at end of calendar month. You receive a detailed invoice: Azure DevOps ticket reference, D365 module, merge date, €200 amount. Payment by SEPA bank transfer at 30 days end-of-month.
No volume commitment, no deposit, no minimum retainer. A month with no resolved tickets = zero invoice. A month with 50 resolved tickets = €10,000 ex-VAT.
For requalified or dropped topics (beyond SLA, scope not covered, review refusal after 3 iterations), no billing. You carry zero failure risk.
Frequently asked questions
How long does the full setup take?
Between 30 minutes and 2 hours, depending on your Azure DevOps maturity. If you already have a Git repo with your D365 code, a PAT, and a lead able to review PRs, count 30 minutes. If you're starting on Azure DevOps, plan a few hours of initial setup (covered by /docs/devops).
Do I need to stop my current AMS to start?
No. Most clients start with a 2-3 month parallel run: the current AMS continues on production-critical matters, and Skalp AI takes new developments. At the annual AMS contract term, you renegotiate down or terminate based on measured results.
How many tickets can I submit per month?
There is no cap on the Skalp AI side. The real limit is your IT-side validation capacity. An in-house D365 lead comfortably steers 20-40 tickets/month (200-400/year). Beyond, plan a second profile or split functional vs technical.
Which D365 F&O modules are covered?
Finance (General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets), Supply Chain (Inventory, Master Planning, Warehouse, Transportation), Project Operations, Production Control, Retail (Commerce HQ, Modern POS), HR / Payroll, Sales & Marketing. For Commerce e-commerce and Dual-Write CE↔F&O, see /docs/devops for specific configuration.
What if I don't have Azure DevOps but GitHub or GitLab?
Skalp AI officially supports Azure DevOps Repos due to native LCS integration. GitHub Enterprise and GitLab self-hosted are supported in bridge mode with some limitations (no automatic LCS release pipeline). Specify your setup during onboarding for adaptation.
Ready to submit your first ticket?
30 minutes to start. No unresolved ticket is billed.
Join the waitlist