u/Narrow_Ad6149

burned a quarter once "fixing" an sql-to-opp rate that tanked. dashboards, enablement, the whole circus. nothing moved. turned out the rate didn't even tank, the reps had just started backfilling the stage on fridays so their forecast looked clean going into the weekend. no bottleneck. I spent three months optimizing a data-entry habit.

haven't trusted a conversion rate at face value since. The data you diagnose off is only as honest as it is hard to game, and stage conversion is the easiest thing in the whole crm to game. reps sandbag. they skip discovery and jump straight to verbal when a deal's hot. they sit on a stage so their cycle time doesn't blow up. so when someone goes "our sql-to-opp is the constraint" my first move isn't fix it, it's go prove the rate is even real first.

what i actually trust now is whatever nobody has a reason to fake. calendar invites. signed contract dates. won/lost bucketed by close-date cohort. money actually in the bank. there's zero upside to fudging a calendar invite so that's about as close to ground truth as this job gets. anything a rep or an admin can quietly retune on a tuesday — stage rates, lead scores, "engagement," whatever fires an mql this month — that's a hypothesis until the hard signals back it up, not a finding.

the test is dumb but it's saved me more than once: if the "constraint" only shows up in the gameable data and vanishes the second you look at the un-fakeable stuff, it's not a constraint. it's a reporting bug in a constraint costume. go fix the report and leave the funnel alone.

and the sneaky one nobody brings up: account matching. dupes and subsidiary splits will straight up hallucinate a coverage gap for you. one logo living in three salesforce records looks identical to a pipeline hole right until you dedupe and it just evaporates. lost stupid amounts of time to that before i learned to check it first.

Anyway, how messy is everyone's actually. do you split trust-it data from verify-it data before you go diagnosing or is that a luxury and you're just cleaning as you go and hoping the numbers aren't quietly lying to you

Something that took me too long to internalize. Sharing in case it saves someone a quarter.

Most RevOps teams get asked to fix everything at once. Pipeline's light, win rate slipped, the sales cycle crept up, NRR is soft, pricing feels off. So we build dashboards for all of it and chip away at all of it. And the number barely moves.

Theory of Constraints (it's from manufacturing, but it maps cleanly onto a revenue engine) says throughput is set by exactly one bottleneck at a time. Relieve a stage that isn't the constraint and nothing happens downstream, because the real bottleneck just absorbs the slack. You can pour leads into the top all day, but if win rate is the binding constraint, that pipeline piles up against the same wall.

The method I've landed on:

1. Lay the engine out as a sequence of rates. Lead to MQL to SQL to opp to win to onboarded to retained to expanded, with volume and conversion at each stage, plus ACV and cycle length. Rough numbers are fine. You're looking for the shape, not auditing the data.
2. Find the stage furthest below benchmark, weighted by how much revenue flows through it. A 10-point miss on a stage all your revenue crosses beats a 30-point miss on a sliver.
3. Confirm it's actually binding. The test most diagnoses skip: if you fixed this stage tomorrow and changed nothing else, would ARR actually move, or would the next stage just cap it? If relieving it only shifts the bottleneck one step downstream and nets nothing, it wasn't the constraint.
4. Put a number on it. Recoverable revenue is roughly gap-to-benchmark x volume x ACV, carried through retention. That tells you how much it's worth fixing, and it's the number leadership actually reacts to.
5. Then, and only then, sequence the work. Fix the one. A new constraint emerges somewhere else. Repeat.

The hard part was never the math. It's the discipline to NOT work the other four stages while you fix the one that's binding, and to defend that focus when every QBR wants you to boil the ocean.

Curious how others run this. Do you formally name a single binding constraint each quarter, or do you keep parallel workstreams across the funnel? And if you single-thread it, how do you keep leadership bought in when the other metrics are visibly ugly?