Reports rebuilt by hand
Skilled people reconciling three systems every quarter. Productivity lost, at senior rates.
Revenue Operations
One customer, three systems, and a forecast rebuilt by hand.
RevOps owns the stages, the CRM and the forecast, rarely the rule each one rests on. The cost sits where a tool was added and the definition under it was never agreed.
From the seat
Every team trusts its own report.
In a company like this, the head of RevOps spends the last week of the quarter rebuilding the board report by hand, because the CRM, the billing system and the customer success tool each count the same customer differently. A forecasting tool was bought in spring. It now holds a fourth version of the pipeline. A field that was required at stage three is required by nobody, and when the dashboard built on it broke, the dashboard was rebuilt and the rule was not.
The system works. It works around the gaps, and the people in RevOps close them each week by hand. The money goes into the work that keeps the system looking right.
The levers
The system runs on five rules, written down or not.
A tool can hold a rule; it cannot make one. Where the rule was never agreed, the gap is closed by whoever is reconciling the numbers that week.
- 01
Stage definitions and the data model
A pipeline stage is a promise about what has happened to a deal; the data model says how customers, contracts and people are recorded so the promise can be checked. Where one stage means three things, every report built on it is an argument and every forecast is a guess with a number on it. The cost lands on whoever has to make the three agree, and it gets filed as CRM hygiene, as though the data were at fault.
What we check: the written definition of each stage, who may move a deal into it, and how often the CRM, billing and customer success systems disagree on the same customer.
- 02
Reporting and the forecast process
The forecast is the one report the whole company acts on, and it should be a process: who submits, on what evidence, how it is challenged and what the record shows afterwards. Where it is a Monday call that walks the same deals, the output is confidence, not forecast accuracy. The hours spent at quarter end are the symptom; the missing process is the cause.
What we check: forecast against actual by quarter and by manager, and how many hours went into producing each one.
- 03
The tech stack against the process
Each tool was bought to solve a problem that had an owner at the time. Over the years the stack comes to hold the same customer in several places, and licences for what nobody opens. Where the process was never agreed, the next tool adds another copy, and the cost is the licence plus the hours spent keeping the copies in step.
What we check: every tool against the step it serves, the users who opened it last month, and the data that lives in more than one of them.
- 04
CRM hygiene and who owns it
CRM hygiene is the name given to the gap after the fact: fields empty, stages stale, the same account entered twice. Behind each is a rule nobody set, a field nobody owns and a seller with no reason to fill it. A clean-up campaign treats the symptom; the field is empty again by the next quarter, and the hours to clean it are paid again too.
What we check: the fields required at each stage, how many of them are filled on the deals that closed last quarter, and who is held to each one.
- 05
The data shared between CRM, billing and customer success
The CRM says what was sold, billing says what was invoiced, and customer success says whether the customer will stay. Where the three are never reconciled by rule, one customer carries three contract values and two renewal dates, and net revenue retention is whichever system was opened first. The hours to reconcile them sit at quarter end; the decisions taken on the unreconciled numbers sit everywhere else.
What we check: one quarter's customers counted in each of the three systems, where they differ, and which figure the board saw.
What it costs
Paid in hours, by every team that touches the system.
None of these appears on an invoice. Each is counted anyway, in hours at the rate of the person doing it, and most of the total is time.
Tools that do not pay back
Licences across the stack for software that holds another copy of the data, renewed because nobody owns the decision to stop.
Decisions on a number nobody trusts
Hiring, spend and the board's own plan held back or taken late on a forecast that is argued every Monday and missed every quarter.
The work that never starts
Improvements RevOps never has the quarter for: the stage that would mean one thing, the forecast that would hold, never built.
The evidence
The system as it runs, measured in other companies.
Four published figures, each with its source and sample, and vendor surveys named as such. Your own figure sits in the records RevOps reconciles every quarter end.
- 01
76%
The share of CRM users and administrators who said "less than half of their organization's CRM data is accurate and complete"; in the same survey, 37% reported losing revenue as a direct result of poor data.
Validity, The State of CRM Data Management in 2025, 602 CRM users and administrators in the US, UK and Australia, vendor survey, 10 July 2025
- 02
40%
By the sellers' own account, 40% of their time goes on selling, meetings with customers and prospecting together, and 60% on work that is not: quotes, planning, data entry and training.
Salesforce, State of Sales, seventh edition, 4,050 sales professionals in 22 countries, surveyed August to September 2025, vendor survey, p. 8, 2026
- 03
Eight tools
The standalone tools in the average sales team that does not run on one platform, two thirds of the teams surveyed; 42% of reps say too many tools overwhelm them. Each is a licence, and a copy of the customer to keep in step.
Salesforce, State of Sales, seventh edition, 4,050 sales professionals, vendor survey, p. 16, 2026
- 04
50%, and 45%
Sellers overwhelmed by the technology their job needs, and what it costs them: "50% are overwhelmed by the amount of technology needed. Overwhelmed sellers are 45% less likely to attain quota."
Gartner, survey of 1,026 B2B sellers, January to March 2024, press release 16 September 2024
As the company grows
A new system at every stage, and a new copy of the customer.
At each stage the company adds a tool before it agrees the rule the tool needs. The copies of the customer multiply, and the reconciliation follows them.
Where to start
The Diagnosis is the RevOps audit, done in two months.
Diagnosis
€15,000 flat · two months from the day we get access
Stage definitions, the forecast record, the stack and the data in each system, taken from interviews with RevOps, each team lead, finance and the people who enter the data, and from the systems themselves. You end with where the hours go, what they cost in your own payroll figures, and which rule to write first. The rules are then settled in Operation with RevOps and each team lead: €50,000 more within 30 days of the Diagnosis briefing, or €65,000 with it included.
Book a strategy callDetails →One team's leak, or the system's? Compare all six functions →
FAQ
Before you buy the next tool.
Is this a CRM project?
No. A CRM holds the system; it does not decide it. We read where the stage definitions, handoffs and owners disagree, price what that costs, and fix the rules before any tool in the stack is changed.
What happens to our RevOps team?
It does the work with us, and what is fixed stays with it. Where there is no RevOps function yet, Build writes the commercial system down first, so there is something for the function to run.
Where are territories, quota and the annual plan read?
On the GTM Strategy page, with the CEO and the CRO. This page reads the system that carries the plan: the stages, the forecast, the stack and the data. The Diagnosis reads both, whichever seat you start from.
We are small. Is RevOps too early?
Not if your revenue recurs. Stage definitions and a forecast process can be written before the team that runs them exists, and that is cheaper than rewriting them later.
Get started
A single stage definition shows how the system is run.
Pick one stage of your pipeline and we ask who defines it, who uses it and where the reports disagree. If the system holds, the call ends early.