Microsoft Dynamics 365 · Advisory
As a Microsoft Partner we advise SMB and mid-market companies on Microsoft Dynamics 365 and Dynamics CRM before money flows in the wrong direction. The most expensive implementation is the one where a wrong module mix, overly generous licensing, or an unclear migration concept has to be repaired afterward — we get ahead of that, with an advisory that actually makes decisions. Microsoft CRM advisory with 20+ years of practice since CRM 3.0.
30 days free
We set up the trial tenant in 48 hours, train your key users (2 hours), hold weekly office hours with the architect, and prototype your target use case. After 30 days you receive an architecture recommendation — you decide on adoption or shutdown.
Topic landscape
Six questions that come up at the start of almost every Microsoft Dynamics 365 or Dynamics CRM project — and on which the later implementation is decided.
Is Sales alone enough? Do you also need Customer Service — or just Customer Insights Journeys for a marketing team of three? We check which of the six CE modules actually create value and which only generate license costs.
Who needs a full-user license, who is fine with Team Member, where do Device licenses fit? In a typical 80-person sales force, 20–35% license savings are possible without losing functionality. Tool: our License Cost Calculator.
Big bang or iterative? Which modules first? Which integrations to ERP, marketing tool, BI? We build a 6- to 18-month roadmap with clear milestones, budget corridors, and dependencies — no PowerPoint fairy tale.
Standard with customization or your own Power Apps overlay? Microsoft Copilot or your own AI agent? Per use case, we check where Microsoft standard is enough, where Power Platform is the right answer, and where custom software (see Independent Engineering) would make more sense.
From Salesforce, NAV/Navision, an old on-prem CRM, or Excel spreadsheets. Which data is worth migrating, which is deliberately not? We calculate effort and risks — before anyone promises "everything just works".
100 licenses must become 100 users — otherwise all the technical brilliance was for nothing. Already in the advisory phase, we plan the training and adoption concept, rather than gluing it on after go-live.
Three advisory formats
Which format fits depends on where you are today — before selection, in the middle of a project proposal, or with a running implementation you want reviewed.
30 minutes by phone or video call. You speak, we listen, classify, and tell you honestly whether Microsoft Dynamics 365 makes sense in your situation — or not.
One day, on-site or remote. With your 3–6 most important stakeholders. At the end: a written solution proposal with module choice, license calculation, and roadmap sketch.
3 to 5 days. For running Microsoft Dynamics 365 implementations, larger migration plans, or projects that need a second pair of eyes.
Honestly
There are situations where we politely refer you elsewhere — because an arades advisory wouldn't be worth your money.
When Salesforce is the right answer. Highly complex sales processes with mature partner ecosystems, an already deployed CPQ like Salesforce CPQ, international account hierarchies with thousands of custom fields — in such constellations, Salesforce is often the more honest choice. We will tell you that. We know Microsoft Dynamics 365 very well, but we also know its limits.
When a standard tool is enough. A four-person sales team that is currently happy with Pipedrive or HubSpot Free usually doesn't need a Microsoft Dynamics 365 implementation. A migration to D365 is then more symbolic politics than business value.
When the requirements call for a niche tool. Pharma CRM with healthcare compliance? A tool like Veeva is superior there. Auction software for auctioneers? An industry specialist covers that better. We name the right vendor and step back.
When there is no internal owner. Microsoft Dynamics 365 is not a tool you "hand over to IT" and forget. Without a business-side person who takes responsibility for the system in the company — data quality, process logic, adoption — every implementation will fail. We say that before contract signing, not afterward.
When the budget doesn't match the expectation. Rolling out a 200-person sales organization with complex lead-to-cash logic in 12 weeks is not realistic. We'd rather not build than start a failing project.
How a workshop runs
Two weeks before the workshop, a 30-minute call to align on the agenda. We ask you for existing materials — process diagrams, Excel lists, old CRM exports. From those we build a concrete workshop agenda, not a generic template.
9 a.m. to 5 p.m., on-site or remote, with 3–6 of your most important stakeholders (sales, IT, management). Structured: current state, target picture, module mapping, license choice, roadmap sketch. With two breaks and lunch — no slide marathons.
Within 5 business days you receive a result document: a 10–15 page solution proposal, an Excel license calculation, a roadmap sketch. Plus a 30-minute follow-up call to clarify open questions.
Qualification
We don't advise from slides — we advise from more than 20 years of Microsoft practice. Since Microsoft CRM 3.0 (2005), we have been building CRM and ERP implementations through every platform shift, release-wave rebrand, and license-model change. We know a lot that the Microsoft documentation does not cover — from projects we have actually run.
Service matrix
A Microsoft Dynamics 365 advisory rarely runs as a monolithic project. It typically spans three clearly separable phases, each with its own deliverables and cost corridor — usually calculated as a percentage of annual license volume.
| Phase | Typical duration | Deliverables | Cost range (% of annual license volume) |
|---|---|---|---|
| Discovery & architecture | 2–4 weeks | Solution blueprint (15–25 p.), license calculation, roadmap sketch, risk register | 5–15 % |
| Implementation (accompanying advisory) | 3–12 months | Sprint reviews, architecture decisions, quality gates, change requests | 80–200 % |
| Optimization & follow-up advisory | ongoing, quarterly | License audit, performance reviews, release-wave assessment, adoption checks | 10–25 % per year |
The percentages are orientation corridors from real SMB and mid-market projects. Day rates on request. Specific fixed prices follow after the 30-minute discovery, or at the latest at the end of the architecture phase.
Industry focus
We are not industry specialists in the narrow sense — we are generalists for SMB and the mid-market. Three industry clusters appear most often in our advisory practice, each with typical use cases.
Advisory snippets from real SMB projects
Short excerpts from typical advisory phases over the last 24 months. Industry and size remain visible; all identifying details have been deliberately removed.
Machinery · 140 users
Starting point. Existing Dynamics 365 Sales implementation with a high full-user ratio, slow performance, low adoption in field sales.
Solution. 4-day architecture review with license audit, plug-in analysis, and custom-field inventory. Recommendation: move 38% of full users to Team Member, archive 12 unused custom entities, plug-in refactoring in wave 2.
Result. 31% license savings in the first renewal cycle, measurably better list performance, and field-sales adoption rising from 41% to 78% over 6 months.
IT service provider · 65 users
Starting point. The HubSpot estate hits its limits on project steering and time-sheet integration. Microsoft licenses already in place.
Solution. 1-day strategy workshop, then a 3-day architecture spike covering Sales, Project Operations, and Customer Insights Journeys. Migration concept out of HubSpot. License calculation with a mix of full-user and Team Member licenses.
Result. Written solution proposal with a 12-month roadmap. Investment framework plus licenses can be calculated. Project started after a 6-week advisory phase.
Industry association · 28 users
Starting point. Member management in an old on-prem tool. Event registrations via a separate form solution. Duplicate data storage, manual invoicing.
Solution. Strategy workshop with the office and the board. Architecture sketch for Dynamics 365 Sales as the member database, Customer Insights Journeys for events, Power Pages for self-service.
Result. Solution proposal with non-profit licensing (substantial discount). 6-month implementation plan. Transitioned into an arades implementation after a 4-week advisory phase.
Further reading
From the first sprint to go-live. A four-phase approach with discovery, build, migration, and hypercare. Typically 3–6 months for SMB, 6–12 months for mid-market.
Three rollout packages (quick-start, mid-market, plus), a four-phase model, and TCO transparency with three calculation examples.
Migration from Salesforce, SAP CRM, HubSpot, on-prem CRM, and four further source systems. Four-phase model, six selection criteria, fixed-price migration packages.
API-to-API, iPaaS, ETL, custom connectors, webhooks, direct database. Ten typical mid-market scenarios, from ERP connection through telephony and DMS to Datev / Lexware. Fixed-price integration packages.
Turning 50 licenses into 50 users. Role-specific curricula, online-live, on-site, and on-demand videos. Includes Microsoft certification preparation.
After go-live. Response under 4 hours, direct escalation path to Microsoft. Pay-per-hour, Application Care, or Strategic Care.
Calculate yourself what your Microsoft Dynamics 365 licenses would cost with the right mix of full-user, Team Member, and Device licenses.
Full-user, Team Member, Device licenses, add-ons. CSP model, yearly renewal logic. Transparent calculation before the Microsoft order process.
When the advisory turns into custom code: five programming models in Dynamics 365, explained in a structured way — Dataverse plug-ins in C#, the JavaScript client API, Power Fx, AL for Business Central, and PCF controls. With packages and six typical programming mistakes.
Sales module with lead, opportunity, and account management. Forecasting, pipeline steering, Outlook and Teams integration.
Service and support platform with case management, knowledge base, omnichannel, and SLA steering.
Field operations steering for maintenance and service jobs. Route optimization, spare-parts management, mobile app.
Frequently asked questions
The discovery conversation (30 minutes) is free. A strategy workshop (1 day, on-site or remote) is calculated jointly. An architecture review over 3–5 days is offered as a fixed-price range, depending on module depth and number of stakeholders.
Sales, Customer Service, Field Service, Project Operations, Customer Insights Journeys (Customer Engagement), and Business Central (SMB ERP). For the Finance & Operations apps Finance, Supply Chain Management, Commerce, and Human Resources we refer to specialized F&O partners from our network — see also our D365 ERP knowledge area.
Yes. If Salesforce, HubSpot, or an industry-specific CRM is the better answer, we say so in the discovery conversation. We are a Microsoft Partner — but we don't sell implementations to clients whose requirements fit better elsewhere. More on this in our architecture-and-strategy offering under Advisory & Architecture.
For an SMB implementation 2–4 weeks: one discovery conversation, one workshop, a written solution proposal with license calculation. For mid-market projects with multiple modules or ERP integration 4–8 weeks with an architecture review.
Yes, that's our second pillar. If your question spans beyond Microsoft (build vs. buy, EU sovereignty, open-source alternatives), see Advisory & Architecture in Independent Engineering.
After the discovery conversation you speak with the same people who will also build the system for you. No account-manager layer, no handover to an offshore team. We work in teams of 2 to 6 people — the decision-makers are technically deep in the topic.
Yes. An architecture review (3–5 days) examines a running Microsoft Dynamics 365 implementation for weaknesses, license optimizations, and migration risks. You receive a report with prioritized recommendations — even if the implementation came from a different partner.
The discovery conversation is timeboxed at 30 minutes. A strategy workshop runs for one day (on-site or remote). An architecture review covers 3–5 days spread across 2–3 calendar weeks. The full advisory phase up to decision readiness takes 2–4 weeks for SMB plans, and 4–8 weeks for mid-market multi-module projects.
Discovery conversation: free of charge. Strategy workshop (1 day incl. preparation and follow-up): fixed price. Architecture review (3–5 days): fixed-price range, depending on module depth and stakeholder count. If you move into implementation, the workshop investment is credited against the project budget. Day rate on request.
For on-prem CRM estates (CRM 2011/2013/2015/2016, Dynamics 365 on-premises) we clarify three points in the architecture review: which customizations are cloud-capable, which must be rebuilt, and which data is worth migrating. Microsoft does not offer an automatic lift-and-shift — a deliberate re-design step is standard and is calculated with a clear effort estimate. More on execution in the implementation overview.
Yes. We advise holding structures, franchise networks, and groups with multiple legal entities on tenant strategy: one tenant with business-unit separation, multiple tenants with data replication, or hybrid models. We use our productized intercompany solution for this. The choice depends on compliance requirements, reporting needs, and license optimization.
Yes, that is one of our advisory focus areas. We map accounts, items, document flow, and customer master between CE and ERP. For Business Central (SMB ERP) we cover advisory and implementation ourselves. For Finance & Operations we work with specialized F&O partners from our network and handle the CE side plus the integration. Background in the D365 ERP knowledge area.
Effectively the same thing. With Wave 2017, Microsoft renamed the product Microsoft Dynamics CRM to Microsoft Dynamics 365 Customer Engagement — today split into Sales, Customer Service, Field Service, Customer Insights Journeys, and Project Operations. If you are searching for a Dynamics CRM advisory or a Microsoft CRM advisory, you usually mean these CE apps. We cover both naming worlds and carry out migrations from on-prem CRM 2011/2013/2015/2016 or Dynamics 365 on-premises into the cloud.
In the strategy workshop or architecture review we clarify three questions: which entities are worth migrating (accounts, contacts, open opportunities, historical activities), what data quality they bring with them, and which are deliberately not migrated. We calculate the effort for ETL, mapping, and validation as a fixed price and plan a test migration before the real one. Source systems from our practice: Salesforce, HubSpot, SugarCRM, Microsoft Dynamics CRM on-premises, NAV/Navision, Excel.
Yes, that is a mandatory part of our strategy workshops. A Microsoft Dynamics 365 implementation rarely fails on the technology, but almost always on missing adoption. We plan role-specific training curricula, key-user programs, and accompanying office hours already in the advisory phase — not only after go-live. Details in the training and adoption concept.
GDPR-compliant tenant configuration, EU data residency, NIS2 requirements for affected companies, Microsoft Purview for data classification, Conditional Access and MFA for Dynamics 365 users. For industries with elevated requirements (finance, health, critical infrastructure) we extend the architecture review with a security add-on.
Yes. Under the label Advisory & Architecture in Independent Engineering we run vendor-independent CRM strategy workshops — with an honest comparison between Microsoft Dynamics 365, Salesforce, HubSpot, and industry-specific solutions. Module and license decisions come only after that.
30 min · free · no obligation
Tell us about your plan. We listen, classify, and give you an honest first assessment — whether Microsoft Dynamics 365 fits, which modules make sense, and what a realistic investment range would be.
Accompanying services
Engineering projects rarely stand alone — license logic, architecture clarification, quality gates, knowledge transfer, and follow-up operations usually run in parallel. Here are the most common accompanying services we add via Discovery Spike, sprint fixed price, or Application Care contracts.
Before · Architecture
Before implementation begins: tenant structure, data model, security concept, integration mapping. The result is an architecture document any engineering team can build on — including one other than us.
Read more →
Before · CSP
Which license bundles for which users, which add-on SKUs are required, where you are over- or under-licensed. Sourced as a Microsoft Licensing Partner — with the option to use CSP purely as control without margin maximization.
Read more →
During · Quality gate
An independent second opinion during a running implementation project — whether we run it ourselves or another partner does. CMMI-based quality gates, risk reviews, fixed price per gate.
Read more →
During · Adoption
Not the classic two-day workshop that's forgotten a week later — but a dynamic learning program over 4–6 weeks with initial training, application phases, and follow-up sessions. Training matrix across roles and topics.
Read more →
After · Operations
After go-live: a predictable Application Care contract with a monthly flat fee, SLA-based. Includes releases, hotfixes, enhancements, tenant hardening — and continuous guidance rather than ticket-only response.
Read more →
After · Knowledge
When the original developers are gone, the predecessor partner is no longer reachable, or documentation is outdated — reverse engineering of the existing solution with a documented result: code map, data model, customization inventory.
Read more →
