Pipeline reviews without the prep: a fantasy that's getting less fantastical

It's Sunday, 9:14pm. Dana, a RevOps manager at a company you'd recognize, is building the deck for tomorrow's pipeline review. She is doing this on Sunday night for the same reason she does it every Sunday night: the review is Monday at 9, the data has to be pulled fresh or the VP will catch a stale number, and pulling it fresh means tonight.

The ritual has steps. Export the pipeline. Cross-check the big deals against what the AEs said in Friday's standup, because the CRM and the AEs have an openly hostile relationship with each other. Message two reps who will not answer until 8:40 tomorrow. Rebuild the slide where the forecast bridges to the number, because a deal moved stages after Thursday's snapshot. Add the slide the CRO asked for last week, comparing this quarter's pace to last quarter's, which requires a second export and twenty minutes of spreadsheet archaeology. Dana is good at this. It takes her two and a half hours instead of the four it takes her counterpart at her last company. It is also, she would tell you after one drink, the single stupidest recurring use of her time, because every fact in the deck existed on Friday. Her whole Sunday evening is spent moving facts from where they live to where they'll be looked at.

Then Monday at 9, the actual review happens, and here's the darkly funny part: the first forty minutes are spent reading the deck to each other. Deal by deal, an AE narrates what the slide already says, occasionally correcting it, which invalidates the slide Dana built last night. The last twenty minutes, the only twenty that matter, hold the real conversation: the three deals that are genuinely in trouble, the one the team disagrees about, the resourcing call the VP needs to make. Everyone leaves saying the meeting ran long. The meeting didn't run long. The meeting was an hour of status wrapped around twenty minutes of judgment, and the status part had no reason to exist.

The version without the Sunday

Now run the counterfactual, because it's no longer hypothetical. Some revenue teams already work roughly like this.

The pipeline picture isn't assembled weekly. It's simply current, because agents keep it that way as their standing job. One reconciles the CRM against the actual activity, the emails, the meetings held or skipped, the proposal opened or ignored, and when the record and reality disagree, it asks the AE directly, midweek, in the channel where the AE lives: "This deal shows closing Friday but there's been no contact in twelve days. Still real?" The answer, whatever it is, updates the picture. The two reps who never answer Dana on Sunday answer this, because it's one question at a time, in context, rather than a Sunday-night interrogation about seven deals.

By Monday morning nobody built a deck. The current state of the pipeline, with the deltas since last week highlighted and the anomalies flagged, is just there, the same picture for everyone, assembled by agents overnight with links to the underlying evidence. The forecast bridge exists because it always exists. The pace-versus-last-quarter comparison the CRO wanted is a standing view, not a Sunday project.

And the meeting changes shape, which is the part people don't anticipate. When nobody needs to narrate status, the review starts at minute one with the three deals that matter. The team spends the hour on judgment: is the champion at Deal B actually a champion, do we pull the SE into Deal C, do we walk from the one that's been "closing next month" for three months. Attendance drops, pleasantly, because the people who only ever came to absorb status now just read the picture. What's left in the room are the people with decisions to make.

Dana, in this version, isn't unemployed. She's the person who designed the rules the agents run: what counts as an anomaly, when an agent asks an AE versus flags a manager, which numbers require human sign-off because compensation touches them. When the VP asks a question nobody anticipated, Dana is the one who can actually chase it during the meeting instead of promising a follow-up deck by Thursday. Her Sunday nights belong to her. Her Mondays got harder in the good way: the easy hour of reading slides aloud is gone, replaced by an hour of arguments she has to referee with data.

What actually stands between here and there

The honest obstacles aren't technical, or not mostly. The picture the agents maintain is only as good as the team's willingness to let reality into the system. A sales culture where AEs sandbag, where the real forecast lives in the manager's gut and the CRM is theater, will get a beautifully current picture of a fiction. The teams making this work had to have an awkward conversation first: the record is about to become the truth, which means the truth has to go in the record. Some teams aren't ready for that conversation, and no agent fixes it for them.

There's also a subtler adjustment. The Sunday deck, for all its stupidity, was a rhythm. Weekly prep forced a weekly reckoning. When the picture is always current, teams have to deliberately preserve the reckoning, the moment where humans stop and exercise judgment on the pipeline, or the always-on data becomes wallpaper nobody looks at hard. The meeting survives. It just finally becomes what it was always pretending to be.

The fantasy in this piece's title was never really "no prep." It was an hour of smart people arguing about the deals that matter, informed by a picture nobody had to build the night before. That's not a fantasy anymore. It's a design choice, and somewhere, a competitor of yours has already made it. Dana's Sunday, meanwhile, is spoken for either way. The only question is by whom.