The Decision Foundation Audit: Agree on the Numbers, Then Clean Up What Feeds Them

Decision first: don’t add another required field, stage gate, or dashboard until you’ve agreed what the numbers mean and cleaned up the HubSpot properties that feed them. That’s what a Decision Foundation Audit does. It has two equal halves. Top-down, your leadership team agrees on the definitions and the process. Bottom-up, every material HubSpot property gets an honest outcome. Skip either half and you lock today’s confusion into tomorrow’s process.

The problem: numbers that disagree

You walk into the leadership meeting with a pipeline number. Finance has a different one. CS has its own view of renewals. Nobody is lying. Each team is reading the same CRM through a different definition, and the records have slowly drifted away from how your process is supposed to run.

That’s CRM drift. It’s why your leadership team can’t fully trust the numbers.

The usual reflex is to tighten: more required fields, harder stage gates, a new dashboard. Those feel decisive. But they enforce definitions nobody agreed on. You get green fill rates and the same argument on Friday.

Filled isn’t the same as true.

Half one: agree on the definitions (top-down)

Start with the decisions, not the fields.

1. Name the numbers you defend. Usually new pipeline, conversion by stage, forecast commit, renewal or churn rate, and expansion. Keep the list short.
2. Write down what each one means. What counts, what doesn’t, and which date it uses. Who owns the definition when teams disagree?
3. Write down the process behind it. What has to be true for a deal to move stages? What has to happen before a customer is “onboarded”? Sales often has written exit criteria. Post-sales onboarding rarely does.

This is a leadership job. Your CEO, COO, and CRO own the meaning. RevOps runs the system but shouldn’t have to invent definitions alone.

Half two: clean up the properties (bottom-up)

This half is not an afterthought. Definitions on a slide do nothing if the properties underneath still say something else.

For every property that feeds one of those numbers, pick one outcome:

Two patterns show up often. A “renewal date” property that really holds the next billing date. And a nurture stage that becomes a parking lot. Nurture works better as closed-lost with a required date and note, so it stays visible without inflating pipeline.

Material means “if this field is wrong, a leadership decision gets worse.” Usage isn’t the test. A rarely filled field can matter more than a busy one.

Then, and only then, enforce

Once both halves are done, gates and required fields protect something real. Before that, they protect confusion.

A simple order:

• Agree on the numbers and their definitions.
• Clean up every property that feeds them.
• Add enforcement where leadership will stand behind the rule.
• Keep watching for drift, because process and records separate again over time.

What you have when it’s done

• A short, written list of the numbers your leadership team uses, with agreed definitions and owners
• Written process steps, including post-sales exit criteria
• An outcome for every material property, with Pending items named to people and Blocked items named to decisions
• A clear line between what must be true in the record and what a report can calculate

Buoy does not build your reports. Your team uses the trusted data in the tools you already have.

How Buoy helps

The Buoy Audit is a one-time engagement, done with you, not handed to you. Buoy’s team works with your leaders: we start from the numbers your leadership team uses, agree on how each is defined, then clean up the HubSpot properties behind them. You keep the documentation and Included Access to the workspace. Validation flags drift on the record.

Let's chat and we’ll start from the numbers your leadership team uses.

FAQ

What is a Decision Foundation Audit?

A two-part audit. Top-down, leadership agrees on what each number means and the process behind it. Bottom-up, every HubSpot property feeding those numbers is kept, deleted, turned into a rule, marked pending, or marked blocked.

Why not just add required fields?

Required fields raise fill rates, not truth. If nobody agreed what a field means, enforcing it just locks in placeholders.

Is this a data-quality cleanup?

It includes cleanup, as one of two equal halves. But it starts from the decisions you defend, not from unused-property counts.

Who owns it?

Leadership owns the definitions. Team heads defend their parts of the process. RevOps implements the property outcomes.