Rebuilding Revenue Operations on Dynamics 365 With a Six-Month ROI Deadline

Why do revenue operations rebuilds miss a six-month ROI deadline?

Because the funding case lists every problem at once, and the programme tries to fix them at once. Quoting, commission, pipeline hygiene, forecasting, lead routing, dashboards, Copilot and an ERP change all start in the first month, each with its own workshop series. Every workstream depends on data the others are still changing, sellers are asked to change how they quote and how they are paid in the same quarter, and at month five there is a lot of activity and nothing that can be measured against a baseline.

The fix is not more capacity. It is an order in which each stage stabilises what the next one depends on, and a single pilot outcome chosen before any build starts.

• Pay and quoting changed together with process: sellers distrust the system the moment their commission looks wrong.
• Automation built on unstable data: flows and routing encode rules the data cannot yet support, then fail quietly.
• Dashboards designed before definitions: every report is argued about because "closed won" means three things.
• No baseline: the ROI gate arrives and nobody measured the before state, so no after state can prove anything.
• An ERP migration on the same calendar: the integration target moves while the CRM side is being built.

In what order should pay, quoting, data and automation be fixed?

Sequentially, with a gate between stages. Stages can overlap by a few weeks for preparation, but the build and the change for users should not. The timeline below is a shape, not a promise; the real durations depend on scope, the number of sellers and the state of the data.

How do you get reps out of Word quotes without buying a CPQ product?

For most B2B sellers who quote list price plus discounts, Dynamics 365 Sales plus a thin Power Platform layer is enough, and it replaces the Word document rather than automating it. The detailed build-versus-buy analysis, audit controls and phased cutover off a quoting spreadsheet are covered in our quote-to-cash from spreadsheets guide, and pricing rules such as order-level tiers are in the volume discounts and complex pricing guide. What matters under an ROI deadline is the minimum that gets reps off Word.

• A governed product catalogue and price lists, maintained by a pricing role rather than by whoever last edited the Word file.
• Quote lines on the quote record, so totals and discounts are calculated by the platform and reportable.
• Quote templates built as Word document templates against the quote, so the layout reps are used to survives while the content comes from governed data.
• PDF generation either from the platform where your Sales version and configuration support it, or through a Power Automate flow that populates the Word template, converts it to PDF and attaches it to the quote.
• A discount approval flow above a threshold, with the approver and decision written back to the quote.
• The old Word templates withdrawn on a set date for the pilot team, so parallel quoting does not become permanent.

When does a CPQ purchase or a custom build make more sense?

When the price is computed from a configuration model rather than looked up and discounted, when product compatibility rules are genuinely complex, or when many external partners quote. In those cases a configure-price-quote product, or a custom quoting application, can be justified, but it rarely fits inside a six-month ROI gate alongside everything else, so it is usually a stage-two decision.

We recommend the right solution - whether that's Microsoft Dynamics 365, Power Platform, or a custom-built CRM. Some businesses need the Microsoft ecosystem. Others need full control without licensing. We deliver both. If per-user licensing across every seller and approver does not fit, a custom CRM on React, Node.js, PostgreSQL or .NET can own quoting and commission inputs with no per-user licence, and the same sequencing applies.

How do you make commission calculable from CRM data?

Dynamics 365 Sales is not a commission engine, and it does not need to be. It needs to hold every input a commission plan uses, defined once, so the calculation can be run from CRM data by whatever performs it: a finance model, a reporting layer or a dedicated commission tool. Payroll keeps paying throughout. The first proof is reconciling a closed period: the CRM inputs, run through the plan rules, reproduce what was actually paid, and every difference is explained.

If the rebuild also changes stages or ownership, time those changes to a commission period boundary; the sales process redesign guide covers how to do that without breaking commission mid-quarter.

Which workstreams should you pause so one ROI pilot lands in six months?

Pausing is a leadership decision, not a delivery decision, and it has to be written down or paused work restarts through side doors. The table is a typical starting point; your list depends on what the funding case promised.

How do you define an ROI pilot that can be proven inside six months?

Choose one outcome the business already cares about, that the rebuild directly changes, and that can be measured before and after with data you trust. We do not supply ROI figures; the numbers come from your own baseline and your own finance team. What we do is make sure the measurement is designed before the build, so the gate is a reading rather than a debate.

• Pick an outcome in the pay and quoting stage, such as time from request to sent quote, quotes needing rework, discount leakage against policy, or hours finance spends reconciling commission.
• Measure the baseline for the pilot team before anything changes, with the method written down so the after measurement uses the same one.
• Keep the pilot population small and representative: one team or region, with a comparable team continuing as before where possible.
• Agree with finance how the measured change will be valued in the ROI case, before seeing the result.
• Report monthly on the same measure, including when it is not moving, so the gate holds no surprises.

What is the risk of a legacy ERP migration running alongside, and what if it becomes a fire drill?

It is usually the largest single risk to the deadline, because quotes become orders and orders must land in an ERP that is itself changing. Solzet does not implement or migrate the ERP; we build the CRM side and the integration, and work with the team or vendor that owns the ERP. The integration patterns for ERPs without a proper API, such as staging tables, file drops, acknowledgement and reconciliation, are covered in the quote-to-cash guide.

• Fix the integration contract early: the order fields, keys and acknowledgement the CRM sends and receives, agreed with the ERP team independently of which ERP is live.
• Design for both systems for a period: the contract is implemented against the legacy ERP first, then the new one, with the CRM side unchanged.
• Keep a file-based fallback that finance can import manually, so a delayed ERP cutover does not stop quoting.
• When the ERP migration turns into a fire drill, freeze CRM scope to the pilot, stop any CRM change that touches order hand-off, keep quoting live in Dynamics 365 and route orders through the fallback with daily reconciliation.
• Record the ERP delay separately in the ROI reporting, so the pilot outcome is judged on what the CRM rebuild controls.

What does Solzet deliver in a revenue operations rebuild, and what does it not?

Senior consultants and full-stack developers with 8+ years of Dynamics 365 Customer Engagement and Power Platform delivery run the sequencing and baseline work, and build the Sales configuration, pricing and approval layer, quote templates and document flows, commission input model, data cleanup and integration. Implementation scope is described on our Dynamics 365 Sales page, and flows on the Power Automate page.

• Delivered: Dynamics 365 Sales, Power Automate, Dataverse data work, PCF controls where configuration runs out, reporting inputs and integration to your ERP and finance systems.
• Not delivered: implementation or migration of Dynamics 365 Finance, Business Central, NAV, Finance and Operations or any ERP, payroll processing, or commission plan design as HR or legal advice.
• Not promised: a return figure. The pilot is designed so your own baseline and finance team can prove or disprove it.
• If an existing build is already failing, a health check before the rebuild is usually the faster route.