RevOps function build

Building a revenue operations function from nothing.

No ops function existed. The forecast was rebuilt in a spreadsheet every week by whoever had time, and two dashboards answered the same question differently.

+18 ptsOf forecast accuracy
1Definition per metric, written down and owned
0Weekly spreadsheet rebuilds after handover
SalesforcePower BIArcGIS

Nobody was being careless. There was simply no owner.

Stage definitions varied by rep. Conversion history did not exist, so the forecast had a feeling behind it rather than a method. Every definition had drifted to wherever the last person left it.

The reporting was rebuilt from the agreed definitions rather than patched, because a patched report carries its old assumptions invisibly.

A stage needs a condition, not an opinion."Had a meaningful conversation" is not one. "Confirmed budget and named the approver" is.
Method, not feeling.Conversion history by stage gave the forecast something to stand on.

What changed

18 points of accuracyMeasured against actuals over two quarters.
One definition per metricField, filter, date basis and owner, written down.
The rebuild stoppedNo more weekly spreadsheet, because the report is trusted.

If this sounds familiar

Three things are true in almost every system we open. If two are true for you, the same work applies.

The forecast is rebuilt by handCount the hours. It is usually more than anyone thinks.
Two reps would stage the same deal differentlyThen conversion rates measure optimism.
Nobody owns the definitionsSo they drift, quietly, until the numbers stop agreeing.

More of the work

Every engagement, with the number it moved.

Questions

Could you do this for us?

Probably. Every engagement starts with the free diagnostic, which tells both of us whether the same pattern is present in your systems and what it is costing.

What would it cost?

Work like this sits inside the $2,000 a month retainer, up to 15 hours a week, or Kaypo included. The diagnostic that scopes it costs nothing.

How long does it take?

It depends on the state of the systems, which is what the diagnostic establishes. Nothing is quoted before somebody has read them.

Related services

Where this sits, and what it costs to fix.

Find what is broken, freeTick what is true and see what we would doReporting and forecastWhy the forecast is wrongThe metrics that matterWhat everything costs

Let us look under the hood.

Read-only access to your systems, and a written report you keep either way.

Start the free diagnostic

Let's chat.

Thirty minutes. Tell us what you are working on and we will tell you on the call whether we can help.

Add your name and a work email so we know who we are talking to.

Thank you!

We will reach out to you shortly. If you have not heard from us by tomorrow, email hello@sapwood.io.

While you wait, keep reading