How do you report broken lead routing when sales on Outreach and leadership only reviews forecast accuracy monthly on Dynamics 365 in 2027?

The Tuesday morning that nobody escalated

Picture a 40-rep sales org. Marketing runs demand gen, SDRs and AEs live in Outreach all day, and Dynamics 365 is the CRM of record where opportunities, forecast categories, and close dates live. Leadership — the CRO, the VP Sales, the CFO's FP&A partner — meets once a month for a forecast accuracy review. They look at commit vs. actual, category slippage, and coverage ratio. Nobody in that room has ever opened a lead assignment rule.

On a Tuesday in week two of the quarter, an assignment rule silently stops firing for one lead source. Maybe a picklist value changed on the web form, maybe a territory owner went inactive, maybe an integration user's license lapsed and the sync started writing leads with a null owner. The leads still arrive. They land in a queue nobody watches. Outreach never gets a prospect record for them because the sync is scoped to owned leads. Reps do not complain, because from a rep's seat, nothing happened — you cannot miss a lead you never saw.

Three weeks later, the monthly forecast accuracy review happens. Pipeline created that month is down. The VP Sales attributes it to a soft market and a light webinar. FP&A notes that new-logo commit was 12% below plan. Nobody says "routing." The root cause — roughly 220 leads that sat with no owner and no first touch — is invisible because it never generated a symptom in any artifact leadership actually reads. By the time it surfaces, those leads are 30 to 60 days cold, and the recovery conversion is a fraction of what a same-day touch would have delivered.

This is the structural problem you are being asked to solve. It is not "how do I fix routing." It is: how do you make a weekly, operational failure legible inside a monthly, financial review cadence, run by people whose only lens is forecast accuracy. The answer is not to demand a new meeting. Leadership already told you what they care about. Your job in RevOps is to build the bridge from routing telemetry to the forecast number, so that the failure shows up as a line in the review they already run rather than a complaint they have to be persuaded to care about.

Three constraints shape everything that follows. First, your evidence has to come from systems leadership already trusts — Dynamics 365 for pipeline and forecast, Outreach for activity — not from a spreadsheet you maintain by hand. Second, the unit of the report has to be dollars and forecast variance, not lead counts and SLA percentages. Third, you get one slide and about four minutes in the monthly review. Everything else you build is scaffolding to make that slide true.

How the mechanism actually works: from a null owner to a forecast miss

The causal chain from a broken routing rule to a forecast miss is longer than most people assume, and understanding each link is what lets you quantify it instead of asserting it.

Link one: the lead lands and the assignment rule evaluates. In Dynamics 365, a lead is created by a form handler, a list import, an integration, or manual entry. An assignment rule or Power Automate flow evaluates criteria — territory, company size, product interest, lead source — and stamps an owner. A break here means the owner field stays as the integration user, an inactive user, or a default queue. The lead record exists and looks perfectly normal in a list view. Nothing errors.

Link two: the Outreach sync scopes on owner. Most Dynamics 365–Outreach integrations sync prospects based on owner assignment or on membership in a view that filters by owner. If the owner never resolves to a real seller, the lead either never becomes an Outreach prospect or becomes one with no assigned user, meaning no sequence enrollment. This is the amplifier: a routing failure in the CRM becomes an activity failure in the engagement platform, which means there is no email, no call task, no first touch.

Link three: time-to-first-touch stretches. Speed-to-lead research is one of the few areas of sales operations with genuinely well-replicated findings — the classic Harvard Business Review "Short Life of Online Sales Leads" work and the subsequent lead-response studies consistently show contact and qualification rates fall off sharply once response time moves from minutes to hours to days. You do not need to cite a precise multiplier to make the argument. Directionally, a lead touched the same hour converts materially better than the same lead touched a week later, and the decay is steepest in the first 24 hours.

Link four: fewer leads convert to opportunity. Lower contact rate means lower meeting rate means fewer opportunities created. The effect lands in the *pipeline creation* number for that period.

Link five: pipeline creation shortfall becomes a forecast miss one to two quarters later. This is the link that makes routing a forecast-accuracy problem rather than a marketing problem. If your average sales cycle is 60 to 120 days, pipeline you failed to create in month one is revenue you cannot close in month three or four. Leadership sees the shortfall long after the causal event, at which point the diagnosis defaults to "market" or "rep execution."

The reporting implication of this chain is precise: you must instrument link three (time-to-first-touch) as the leading indicator, and connect it arithmetically to link five (forecast variance) as the number leadership acts on. Everything between them is your model.

The three instruments you need. First, a routing exception view in Dynamics 365: leads created in the last 30 days where owner is null, owner is inactive, owner equals the integration account, or the lead is in an unworked queue. Second, a first-touch clock: the difference between lead creation timestamp and the earliest logged Outreach activity — email sent, call, or meeting booked — for that lead. If your Outreach connector writes activities back to Dynamics 365, this is a calculated column; if not, you pull it from Outreach reporting or the Outreach API and join on email or prospect ID. Third, a conversion baseline by first-touch bucket, computed on your own historical data, which is what converts counts into dollars.

Real numbers: what to instrument and what "bad" looks like

Vague claims get dismissed in a forecast review. Concrete, self-derived numbers do not. Here is what to measure and the ranges that generally distinguish healthy from broken — with the caveat that your baseline is the only benchmark that matters in the room, so compute every figure below on your own data before you present it.

Time-to-first-touch (TTFT). Measured from lead creation to first logged Outreach activity. Report it as a distribution, never an average — averages hide the tail that is actually killing you. Track the median, the 90th percentile, and the percentage over 24 hours. In a healthy inbound motion with working routing and enforced sequences, median TTFT for high-intent inbound is commonly measured in minutes to a few hours, and the share exceeding 24 hours stays small. When routing breaks, the median may barely move — because most leads still route fine — while the 90th percentile blows out to days and the over-24-hour share climbs. That divergence between median and P90 is itself the tell, and it is the single most useful chart you can put in front of leadership.

Unrouted and unworked counts. Two separate numbers. *Unrouted*: leads with no valid seller owner. *Unworked*: leads with a valid owner but zero Outreach activity after N hours. They have different fixes — the first is a rules or integration defect, the second is a capacity, enablement, or sequence-enrollment problem. Reporting them as one blob invites the response "so is this an ops problem or a rep problem," which stalls the conversation. Track each weekly, as a raw count and as a percentage of leads created that week.

Sequence enrollment rate. Of leads routed to a seller, what share get enrolled in an Outreach sequence within 24 hours? A gap between "routed" and "enrolled" localizes the failure to the sync or to rep behavior rather than to the assignment rules. If enrollment rate is high but TTFT is still long, your sequences are starting with a long first-step delay — a settings problem, not a routing problem, and worth knowing before you accuse the wrong system.

Lead-to-opportunity conversion by TTFT bucket. This is the calculation that turns operations into finance. Pull 6 to 12 months of Dynamics 365 leads with a computed TTFT, bucket them — under 1 hour, 1 to 8 hours, 8 to 24 hours, 1 to 3 days, 3 or more days, never touched — and compute for each bucket the conversion to opportunity and, where volume allows, to closed-won. Nearly every org that runs this finds a monotonic decline. Do not borrow someone else's decay curve; yours is more persuasive and it is unarguable because it is their own data.

At-risk pipeline, the headline number. The arithmetic:

*At-risk pipeline = (leads in degraded TTFT buckets) × (baseline conversion rate of the fast bucket − observed conversion rate of the degraded bucket) × (average opportunity value)*

Worked example with placeholder figures you would replace with your own: 220 leads never touched in a month; your fast-bucket conversion is 14% and your never-touched conversion is 2%; your average new-business opportunity is \$28,000. That is 220 × 0.12 × \$28,000 ≈ \$739,000 of pipeline that did not get created. Apply your historical win rate — say 22% — and it is roughly \$163,000 of bookings, landing one to two quarters out depending on cycle length. Now express it as forecast variance: if the affected quarter's commit is \$4M, that is about 4% of commit, which is often the same order of magnitude as the miss leadership is already trying to explain.

Coverage-ratio impact. Leadership tracks pipeline coverage. If you carry 3.5x coverage and the routing gap removed \$739,000 from a \$14M pipeline against a \$4M target, coverage falls from 3.5x to about 3.3x. That single sentence lands harder in a forecast meeting than any SLA chart, because coverage is already on their slide.

Detection latency. Track how long a routing break existed before anyone noticed. If your answer is "three weeks, and we found it because pipeline looked light," that is your argument for weekly monitoring, stated as a number rather than an opinion.

Recovery yield. When you re-route and re-sequence stale leads, measure what you actually recover. Recovered leads convert well below fresh ones — expect a meaningful fraction of the original rate, not parity. Reporting honest recovery yield builds far more credibility than claiming you saved the full amount, and it strengthens the case for prevention over cleanup.

Suggested thresholds to propose. Unrouted leads: under 1% of weekly volume; over 3% is an incident. Share of high-intent inbound with TTFT over 24 hours: under 5%; over 15% is an incident. P90 TTFT for high-intent inbound: single-digit hours. Detection latency for any routing break: under 7 days. Get leadership to ratify these once, in the monthly review, and every subsequent report becomes a simple pass/fail against a standard they approved rather than a fresh argument.

Trade-offs: how much reporting machinery to build, and where to put it

There are four viable reporting postures here, and picking the wrong one is the most common way this effort dies.

Option A — the manual weekly pull. One saved Dynamics 365 advanced-find view for unrouted leads, one Outreach report for activity, joined in a spreadsheet every Monday morning. Cost: roughly 30 to 60 minutes a week. Advantage: you can start this week, with zero admin approvals, and you will know within two weeks whether the problem is real and how big it is. Disadvantage: it is a spreadsheet, which means it is fragile, unauditable, and personally dependent on you. Use it as a two-to-four-week diagnostic to earn the right to build something durable — never as the permanent answer, and never as the artifact leadership sees. Present its *conclusions*, not the sheet.

Option B — native Dynamics 365 views plus a dashboard. Calculated columns for TTFT and a routing-exception flag, a couple of system views, and a Dynamics 365 dashboard. Cost: a few days of admin work plus a customization request. Advantage: it lives inside the system of record, so numbers cannot be accused of being "your spreadsheet math," and any leader can click into it. Disadvantage: calculated columns on activity relationships have real limits in Dynamics 365, and you may need a rollup or a scheduled flow to materialize the first-touch timestamp onto the lead. This is the right default for most mid-market teams.

Option C — Power BI with both sources joined. Dynamics 365 via the standard connector, Outreach via API export or your warehouse. Cost: a couple of weeks including data-source approvals, plus ongoing ownership. Advantage: this is where the conversion-by-TTFT-bucket analysis and the dollar model actually belong, and it slots straight into the monthly review deck. Disadvantage: another asset to own, and if the Outreach connection breaks, your routing monitor breaks silently — which is exactly the failure mode you are trying to eliminate, so build a freshness check into the report itself and show the data-as-of timestamp on every page.

Option D — proactive alerting via Power Automate. A scheduled flow that queries for routing exceptions and posts to a Teams channel or emails the ops owner when thresholds trip. Cost: low once the query exists. Advantage: cuts detection latency from weeks to hours, which is the single biggest lever on total damage. Disadvantage: alert fatigue is a genuine risk. Alert on *threshold breaches*, not on individual leads, and start with a deliberately quiet threshold so the first alerts anyone sees are real.

The cadence trade-off is separate from the tooling trade-off. You will be tempted to ask leadership for a weekly routing review. Do not. They told you their cadence is monthly and their lens is forecast accuracy — arguing with that spends credibility on the wrong fight. Run the weekly cadence at the operator level, where the fix actually happens, and let the monthly review consume the rolled-up dollar impact and the trend line. The monthly slide answers three questions and nothing else: how many leads were affected, what that is worth in pipeline and bookings, and what percentage of this period's forecast variance it explains. If routing was clean, that slide says "clean" in one line and you move on — which is what earns you the four minutes next month.

The build-versus-borrow trade-off. Some teams reach for a dedicated routing tool with built-in SLA monitoring. That can be right if routing logic itself is the bottleneck. But it does not solve your stated problem, which is a *reporting* and *translation* problem across three audiences and two systems. A new tool adds a third data surface leadership does not read. Fix the measurement and the narrative first; the tooling decision gets much easier once you have three months of TTFT and conversion-by-bucket data to size it against.

Pitfalls that sink this report, and how to avoid each

Reporting SLA compliance instead of dollars. "We hit 87% on our 4-hour touch SLA" means nothing to a CFO. It has no unit they manage. Always carry the number through to pipeline and bookings, and state the forecast-variance percentage explicitly. The SLA chart is your backup slide, not your headline.

Presenting averages. Mean TTFT is the single most misleading metric in this entire domain, because routing failures produce a fat tail, not a shifted center. A handful of leads sitting for 30 days barely moves a mean computed over thousands. Report median, P90, and percent-over-threshold. If you show only one number, show percent-over-24-hours.

Letting it read as an accusation. If the monthly review hears "sales is not working their leads," you have started a fight and lost the room. Separate unrouted from unworked in every artifact, and lead with unrouted — the systems failure — because it is the part nobody can be defensive about. Frame unworked as a capacity question, not a diligence question, and bring the capacity math with you.

Building the report on a fragile join. If your TTFT depends on the Outreach connector writing activities back to Dynamics 365, and that connector quietly stops, your monitor will report perfect health while the underlying situation is worst-case. Instrument the monitor itself: show the count of activities synced in the last 24 hours and the data-as-of timestamp on every page. A monitoring system with no liveness check is worse than none, because it manufactures false confidence.

Boiling the ocean on backfill. The instinct is to compute TTFT for all historical leads and fix every stale one. Do not. Scope the diagnostic to the last 90 days and to your highest-value sources — demo requests, pricing-page submissions, contact-sales — where conversion is high enough that the dollar math is unambiguous. A tight, defensible \$700K number beats a sprawling \$4M number full of low-intent content downloads that nobody believes.

Ignoring the reverse case. Verify your detection query stays quiet on a known-good week. If you cannot show a period where the report correctly said "clean," leadership will reasonably suspect it always says "broken." Run it against a historical window you know was healthy and show the flat line. This one step does more for the report's credibility than any amount of additional metrics.

Fixing quietly and never reporting. RevOps teams routinely repair routing breaks the same day and say nothing, then wonder why nobody funds the monitoring work. Log every incident — date, source affected, lead count, duration, estimated dollar impact, fix — in a durable record in Dynamics 365 or your ops wiki. Six months of that log is the entire business case for whatever you want to build next, and it converts invisible firefighting into a visible track record.

Over-claiming recovery. When you re-route 220 stale leads, do not report the full \$739,000 as recovered. Report what actually converted. Under-claiming once buys you more trust than the number ever would have.

Missing the ownership question. Before the monthly review, know who owns the fix — the Dynamics 365 admin for assignment rules, the Outreach admin for sequence enrollment, RevOps for the model and the monitor. If leadership asks "who is fixing this" and the answer is a shrug, the finding gets tabled. Bring one named owner and a date.

Skipping the ratification step. The highest-leverage four minutes you will spend is getting leadership to approve the thresholds once, in writing, in a monthly review. After that, you are reporting against their standard, not arguing for your own, and the conversation shifts permanently from "is this a problem" to "are we inside the number."

Related questions

What if the Outreach connector does not write activities back to Dynamics 365?

Pull first-touch timestamps from the Outreach API or its reporting exports and join on email address or prospect ID in Power BI. Less elegant, equally valid. Note the join method on the report so nobody relitigates the numbers later.

How do I get time to build this when routing keeps breaking?

Run Option A — the manual weekly pull — for two to four weeks. Present the dollar figure once in the monthly review. A credible six-figure at-risk number is the fastest way to convert firefighting time into funded build time.

Should this go to the CRO or the VP Marketing?

Both, but lead with whoever owns the forecast. The at-risk-pipeline framing is a forecast-accuracy story, so it belongs to the forecast owner. Copy marketing, since lead source and form configuration are usually where the break originates.

What if leadership says routing is a sales problem, not an ops problem?

Show the unrouted count separately from the unworked count. Unrouted leads had no owner and no Outreach prospect — no rep could have worked them. That distinction ends the debate in one slide without naming anyone.

How long before the fix shows up in forecast accuracy?

One to two sales cycles. If your cycle is 60 to 90 days, expect pipeline creation to improve within weeks but forecast accuracy to reflect it a quarter later. Say this out loud when you present, so nobody expects next month's number to move.

FAQ

What single metric should I lead with in the monthly forecast review?

At-risk pipeline in dollars, expressed as a percentage of the period's forecast variance. Everything else — TTFT distribution, unrouted counts, sequence enrollment rate — is supporting evidence you keep on a backup slide. Leadership manages dollars and variance; give them the finding in their own unit and the operational detail only if asked.

How do I calculate at-risk pipeline without inventing numbers?

Use only your own Dynamics 365 history. Bucket the last 6 to 12 months of leads by time-to-first-touch, compute actual lead-to-opportunity conversion for each bucket, then multiply the count of degraded-bucket leads by the conversion gap and by your average opportunity value. Every input is a query result, not an assumption, which is why it survives scrutiny.

Is weekly monitoring worth it if leadership only meets monthly?

Yes, and the two cadences serve different purposes. Weekly monitoring is for detection and repair by the operator; the monthly review is for reporting rolled-up impact to leadership. Detection latency is the biggest single driver of total damage — catching a break in three days instead of three weeks cuts the affected lead volume by roughly 80%.

How do I separate a routing failure from reps simply not working their leads?

Split the population. Unrouted leads have no valid seller owner and typically no Outreach prospect record — a systems failure. Unworked leads have a valid owner and zero activity after your threshold — a capacity, enablement, or enrollment issue. Report them as two separate lines in every artifact and never merge them into a single number.

What is the fastest way to detect a routing break going forward?

A scheduled Power Automate flow that queries Dynamics 365 for leads created in the last 24 hours with a null, inactive, or integration-user owner, and posts to a Teams channel when the count crosses a threshold. Alert on threshold breaches rather than individual records, and set the threshold conservatively so the first alerts people see are unambiguously real.

Should I ask leadership to add a weekly routing review to their calendar?

No. They set a monthly cadence around forecast accuracy; arguing the cadence spends credibility you need for the finding itself. Run weekly at the operator level and bring one rolled-up slide monthly. Ask instead for one thing they can grant in the meeting: ratified thresholds, so future reports are pass/fail against their own standard.

Sources

• https://hbr.org/2011/03/the-short-life-of-online-sales-leads
• https://learn.microsoft.com/en-us/dynamics365/sales/forecast-accuracy
• https://learn.microsoft.com/en-us/dynamics365/sales/create-manage-leads
• https://learn.microsoft.com/en-us/power-automate/getting-started
• https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-to-dynamics-365
• https://developers.outreach.io/api/reference/
• https://support.outreach.io/hc/en-us
• https://www.gartner.com/en/sales/topics/sales-forecasting

Related on PULSE

• How do you report broken lead routing when no dedicated RevOps hire yet and leadership only reviews forecast accuracy monthly on Dynamics 365 ?
• How do you report broken lead routing when parent-company rollup reporting and leadership only reviews forecast accuracy monthly on Dynamics 365 ?
• How do you report call recordings not tied to opps when sales on Outreach and leadership only reviews forecast accuracy monthly on Dynamics 365 ?
• How do you report call recordings not tied to opps when no dedicated RevOps hire yet and leadership only reviews forecast accuracy monthly on Dynamics 365 ?
• How do you report call recordings not tied to opps when parent-company rollup reporting and leadership only reviews forecast accuracy monthly on Dynamics 365 ?