i fix the four systems that decide whether your pipeline number is real.

revenue operations is the connective tissue between marketing, sales, and finance. it is the layer that decides whether the number in the board deck means anything.

most revops engagements produce configuration. new fields, new workflows, a cleaner dashboard, a tidier pipeline view. that work is real, and it is not the outcome.

the outcome is narrower than that. a revops engagement is finished when three statements are true.

you can state your pipeline forecast, and say how accurate it has been.

you can say which spend produced which revenue, and defend the method.

a stage name means the same thing in Q1 and Q4, to marketing and to sales.

if those are not true, you did not buy revenue operations consulting. you bought CRM administration with a better title.

i separate the two because i have been on the receiving end. at MacroFab i owned marketing and complete revenue operations together. that is normally three executive roles. that is where i learned what separates a system that reports from one that forecasts.

every revops problem i have seen decomposes into four systems. the order matters. fix three of them on a broken object model and you get a confident wrong answer.

the object model comes first because everything downstream inherits it.

say a lifecycle stage means one thing to marketing and another to sales. your attribution model is averaging two definitions. the output will be precise and wrong.

attribution comes second because the forecast depends on it. you cannot forecast pipeline contribution from a channel you cannot measure.

the forecast comes third because it is the test. a forecast is the only revops artifact that grades itself. it either matched reality or it did not. the gap measures whether the first two layers work.

i built a multi-touch attribution engine at MacroFab in that order. CRM event logs, marketing automation touchpoints, and paid spend into one pipeline model. it held 92% forecast accuracy across $200M in marketing-sourced pipeline for three years.

that number is not a boast about modeling. it is the evidence that the object model underneath it was correct.

more on the parts. [marketing attribution](/insights/b2b-marketing-attribution). [pipeline forecasting](/insights/pipeline-forecasting-b2b). [why MQLs mislead](/insights/why-we-dont-measure-mqls).

the four systems are platform-agnostic. the failure modes are not.

HubSpot for SaaS breaks in predictable places. lifecycle stage is one property with no enforced progression. a workflow sets it backwards and nobody notices. deal stages get added faster than they get defined. the attribution reports are good. they are only as good as the source tracking under them. that is where the defect lives. HubSpot revops work is mostly lifecycle discipline and clean UTM plus source governance.

Salesforce revops breaks differently. the object model is more expressive, so it accumulates more debt. lead-to-contact conversion loses attribution unless it is explicitly carried. opportunity stage probability gets used as a forecast and it is not one. campaign influence is powerful and almost always misconfigured.

i implemented Salesforce and Marketo at Keithley Instruments. i have run both stacks since. i do not have a preferred platform. i have a preferred object model, and i make the platform express it.

CRM consulting services that start from the platform get platform-shaped answers. start from the revenue question instead.

more: [HubSpot marketing attribution](/insights/hubspot-marketing-attribution).

read-only first. i connect to the CRM, ads, and analytics with no write access. then i look.

week one is evidence. i pull eight quarters of forecast versus actual. then attribution output and stage history. the gap between belief and data is the whole engagement in miniature.

week one also ships something. the first useful fix goes live in week one. a 30-day discovery phase is how this work loses the room.

everything is written down. a revops system that lives in one head is not a system.

B2B SaaS between $5M and $50M ARR, usually with one of three symptoms.

the forecast misses and nobody can say why. the board asks which spend worked and the answer takes three days to assemble. or sales and marketing report different pipeline numbers from the same CRM.

it does not fit a company that wants ongoing CRM administration. that is a real need and it is a different hire. i install the system and hand it over.

not sure the constraint is revops? start with the [growth diagnostic](/growth-diagnostic). it ranks the real blocker across demand, attribution, pipeline, and operations first.

need a senior owner too? that is [marketing leadership](/marketing-leader).