WE BUILT 'PLAN TO COMPLETE' BECAUSE 94% OF FORECASTS AREN'T FULLY TRUSTED.
- Robbie Burnell
- 2 days ago
- 4 min read
Updated: 20 hours ago
There is a number that should embarrass every revenue leader in professional services: 94% of services forecasts are not fully trusted by the people who rely on them. This isn’t about inaccuracy or lateness, simply a lack of trust.
That gap is more significant than organizations care to admit, because running on untrusted forecasts doesn't go ignored. It has to be worked around, with Sales protecting their number and Delivery building in buffers, then Finance layering on its own assumptions.
If everyone is running a shadow model of reality, and no one's model matches anyone else's, by the time a deal closes the handoff is already a negotiation.
At Precursive, we built “Plan to Complete” because we got tired of hearing that happen.
THE PROBLEM ISN'T SALESFORCE. IT'S WHAT SALESFORCE CAN'T SEE.
Salesforce is good at what it was built for, namely (not solely) beyond the staples of a CRM it is for tracking where a deal is in a sales motion. Probability scores, stage gates and close dates are all Sales signals, built from genuine Sales conversations and often validated by healthy Sales judgment.
Unless you’re a Precursive user, what Salesforce has never had is a Delivery signal.
Does the Services team have capacity to start this engagement on the expected close date? Is the resource profile this deal needs already committed to something else? If this deal closes and three others close in the same week, what happens? Salesforce doesn't know and frankly that is by design - it’s a Sales tool.
The result of all this is a forecast that's commercially confident yet operationally blind. The consequences can be significant; Sales will get penalized for missing revenue and Delivery gets blamed for not being ready. The root cause? Two sides of the business which have never shared a real-time view of what's possible, are invisible to the other.
A widely cited study found that 68% of companies say they can't trust their sales forecasts. We think that figure is higher in professional services, where the gap between "we think this deal will close" and "we have a plan to deliver it" is structural, not just a process failure.
WHAT 'PLAN TO COMPLETE' ACTUALLY DOES.
Plan to Complete is our answer to that structural gap.
When a deal reaches a certain probability threshold in Salesforce, “Plan to Complete” creates a delivery-side commitment in Precursive: a proposed resourcing plan, a timeline, a set of milestones that Delivery can validate against actual capacity. The result is a signal that Sales and Delivery share, in real time, about whether the forecast is achievable, not just closeable.
This changes the nature of the forecast conversation. Instead of "Sales thinks this closes in Q3" vs. "Delivery finds out in Q4," you get a shared view: "This deal closes in Q3, and here is our plan to deliver it. Delivery has confirmed the resource. The forecast is trusted because both sides of the business stand behind it."
It sounds simple, but it is surprisingly uncommon.
WHAT MOST FORECASTS SHOW | WHAT 'PLAN TO COMPLETE' ADDS |
Deal probability (Sales view) | Delivery confidence (resource & capacity view) |
Expected close date | Confirmed start date and onboarding plan |
Revenue value | Delivery feasibility at that revenue value |
Sales stage | Delivery stage (pre-engaged, resourced, scheduled) |
CRM pipeline view | Unified Sales + Delivery pipeline view |
The model doesn't replace sales judgment, it extends it and amplifies it so Delivery doesn’t ever veto deals, or discover issues on start date, but instead confirming what they can deliver ahead of time, so the number Sales is voicing is the number the business can actually hit.
THE NEW LAYER: ASKING CLAUDE (MCP CONNECTORS)
We also recently launched an MCP connector for Precursive, which connects Claude, Anthropic's AI, directly to your Precursive and Salesforce data.
What that means in practice: instead of switching between two systems to answer a question like "what's our delivery confidence on the Q3 pipeline?", you can ask Claude directly, in natural language, and get an answer that draws on both. Which deals have a “Plan to Complete” in place. Where Delivery has flagged a resourcing risk. Which opportunities are forecast-ready and which are still operationally blind. Get the answer in seconds.
This isn't a reporting feature. It's a shift in how fast a leadership team can move from question to decision. When a CFO asks "can we trust our number?", the answer shouldn't take three meetings and a spreadsheet. It should take a prompt.
Plan to Complete makes the underlying data trustworthy. The MCP connector makes it accessible. Together, they're how we think forecasting should work in a modern services business.
WHY WE BUILT THIS NOW.
The honest answer is that the tools to do this have existed for a while. The will to change the process hasn't always been there.
For a long time, professional services organizations accepted the gap between Sales and Delivery as a fact of life. The handoff was messy, the forecast was imperfect, and the business moved on. What's changed is that customers no longer accept a messy handoff. They experience it directly, as a delayed start, a resource who wasn't expecting them, an onboarding that felt reactive rather than planned.
The forecast problem has become a customer experience problem and that's harder to ignore.
Plan to Complete exists because we believe the services businesses that win over the next few years will be the ones that close the loop between what Sales promises and what Delivery delivers, not after the fact but before the ink is dry.
If you feel like your forecast isn't trustworthy, it might not be a data quality problem, but rather a structural one…and it's solvable.
Comments