The promise
We’re a Microsoft partner — and independent of your implementation partner. We don’t sell licences, take referral fees, or have a statement of work to defend, so nothing shapes the review except what we find. We apply the same Success by Design review structure Microsoft’s FastTrack team uses, led by ex-FastTrack Solution Architects.
You’ll get a comprehensive report that clearly shows:
- What’s working well
- What’s risky or missing
- What must be fixed immediately before go-live
- Best-practice guidance + a practical remediation plan
- A rollout strategy you can execute with confidence
This mirrors the intent of Microsoft’s Solution Blueprint Review workshop: validate high-level scope/design concepts and identify risks early.
What you get
Solution Blueprint Review Report (PDF + playback session)
- Executive summary
- Risk heatmap (RAG) across workstreams
- Top 10 “stop-the-line” issues
- Decisions & assumptions log. What must be agreed
- Remediation backlog. What must be fixed in the next 2-6 weeks
- Go-live readiness gates. The definition of “Ready”
- Partner accountability checklist. The definition of “Done”
What clients typically uncover in this review:
- unclear scope boundaries
- late customisation debt
- missing non-functional requirements
- performance surprises
- data migration assumptions not reconciled
- cutover risk
- testing strategy gaps
- “UAT becomes SIT” chaos
What we review
We review your programme through the fundamentals that typically decide whether D365 projects succeed.
- Scope & solution concept. What’s in/out, fit-to-standard vs custom, key design choices.
- Finance foundations. Ledger setup, dimensions, intercompany, controls, close process.
- Operational design (Supply Chain/Project operations as applicable). Master data, inventory model, warehouse processes, planning assumptions, project operations deployment option.
- Integrations & application architecture. Interfaces, data ownership, failure handling, monitoring, performance.
- Data migration strategy. Quality, cutover approach, reconciliation, historical data principles.
- Security & compliance. Roles, SoD, auditability, regulatory requirements.
- ALM, regression testing & release strategy. Environments, branching, regression, One Version readiness, deployment discipline.
- Testing strategy. SIT/UAT scope, regression approach, test data, defect process, readiness criteria.
- Reporting strategy. Financial statements, management reporting, data sources, Power BI model approach, reconciliation.
- Go-live readiness & operating model. Cutover plan, hypercare model, support ownership, KPIs, training/adoption.
How the engagement works
- Kick-off meeting (60–90 mins). Confirm scope, timeline, and gather existing artefacts.
- Discovery workshops (2–4 sessions). We run structured review sessions with your team and partner.
- Assessment & synthesis. We validate design logic, identify gaps, and create the risk picture.
- Report + playback. You get the report, plus a working session to align on priorities and next actions.
Strategy add-on (rollout plan you can execute)
If you want this included (recommended), we’ll also deliver:
- Wave strategy. We help you design your rollout strategy.
- Governance model. Roles, decision rights, escalation paths.
- Partner accountability checklist. What “done” means.
Why not just use Microsoft FastTrack?
FastTrack is excellent — its review structure is the backbone of ours, and our reviewers are ex-FastTrack Solution Architects. But it has two structural limits. It’s available only to customers who meet a minimum annual Dynamics 365 spend and are attached to a qualified implementation partner. And it’s delivered jointly with that partner — it will flag architectural risk, but it isn’t positioned to give you an independent view of your partner’s own delivery.
Dr Dynamics is the cost-effective independent assurance option when you:
- Don’t meet FastTrack eligibility (or don’t want to wait for it)
- Want an independent second opinion on what your partner is doing
- Need a clear risk report before the project becomes “too late to change”
- Want external pressure that saves you from a painful missed go-live
Ideal timing: before design sign-off / before build accelerates / 8–16 weeks pre-go-live / before the next rollout wave.
Who this is for
- CFO / Finance Director who needs confidence in controls + close + compliance
- Programme leadership who needs an objective view of risks and readiness
- IT/Architecture leads who want integration/data/testing reality checks
- Companies preparing for an ERP implementation or a rollout wave
- Teams seeing scope drift, customisation debt, or go-live uncertainty