How I work with clients
I work in four engagement shapes. Each has a fixed scope, a clear outcome, and an honest commitment, so you know what you're buying before the first call.
If none of these fit, send me the situation: contact@dynamicspro.de.
99 published checks against an existing Dynamics 365 or Power Platform estate — and a report that names what it couldn't check.
Who it's for
Teams running an estate that's slowing down, accumulating tech debt, or about to scale. And anyone who inherited one they didn't build.
Format
Fixed-scope diagnostic, 2–3 weeks
What you get
99 checks across ten domains: transport integrity, security, data and auditing, automation, runtime health, capacity, customisation quality, adoption, tenant governance, delivery practice. Findings ranked by severity and by effort in person-days, capped at ten actions for the first 30 days. Every check that couldn't run is named, with the reason.
What I need from you
One read-only admin account, one environment. That covers 79 of the 99 checks. Nothing installed, nothing written.
Deliverable
Written report, decision-ready slide set, 90-minute walkthrough. You keep the raw measurement.
1 - Architecture & Health Review
The deployment maturity most teams skip — and the tooling to keep it after I leave.
Who it's for
Teams whose deployments are manual, unpredictable, or held together by one person who knows the order to click things in.
Format
Implementation + knowledge transfer, 4–8 weeks
What you get
One solution per work item, a five-pipeline Azure DevOps scaffold, plugin DLL injection, dependency analysis and a build environment. Then your team runs it, not me.
And the tool I built for it
The Solution Administration Console, installed in your environment. It answers in seconds what currently costs your team an afternoon: what the failed import was actually missing (Import History), which flows arrived as drafts (Process Comparer), which variable has no value in production (Env Config), who really holds that role (Role Analyzer), what's in any table in any environment (OData Browser). Twenty-one workspaces across the release cycle and the running estate. It's how I do this work — your team keeps it.
Deliverable
Working pipelines, documented patterns, the Console installed and configured, and an onboarding session.
2 - ALM & DevOps Setup
Fractional architecture leadership for in-flight programs.
For: In-flight Dynamics 365 programs that need senior architecture leadership without a full-time hire.
Format: Fractional engagement, fixed monthly hours.
Duration: Minimum 3 months, typically 6.
Commitment: 2–4 days per month (negotiable).
Includes: Architecture decisions & ADR ownership, design review of solutions, flows, and integrations, risk & dependency surfacing across workstreams, hands-on with the hard problems.
Price: On request.
3 - Architecture Lead
4 - Workshop & Coaching
Level up your architects, leads, or whole team on the topics that matter most.
For: Architects, team leads, or whole teams who want to build internal capability in Power Platform ALM, Dynamics 365 architecture patterns, or Azure DevOps for Dataverse.
Format: On-site or remote workshop.
Duration: 1–3 days, depending on track.
Deliverables: Trained team + reusable patterns workbook.
Price: On request.
Available workshop tracks
Power Platform ALM Foundation (2 days) — Per-Work-Item solutions, the 5-pipeline ADO pattern, plugin injection into unpacked Dataverse repos, solution dependency hygiene.
Dataverse Solution Layering Deep-Dive (1 day) — Managed vs. unmanaged strategy, the build-environment pattern, cross-publisher dependency detection.
Production-Grade Power Automate (1 day) — Heartbeat/watchdog flows, try-catch-scope error handling, monitoring & alerting baseline.
Dynamics 365 Field Service Architecture (1–2 days) — Offline profiles, Schedule Board for multi-day bookings, Work Order day-to-minute conversion.
Custom curriculum — Tailored to your stack and your team's specific gaps.
Not sure which one fits?
Book a 30-minute architecture call and we figure out the shape together. If none of the four fit, I'll tell you. If something matches, we scope the engagement on the next call.