Jose Aleman

Ten million dollars of net-new revenue divided by a one-million-dollar quota produces ten hires, and the board approves it.

• The operational friction the model leaves out is what causes the miss: ramp curves that do not match the real sales cycle, headcount added without more pipeline supply, reps added without front-line managers to inspect deals, and territories carved out of patches that existing producers built.
• Their recommendation is that operations show leadership the exact friction required to deliver the target and name the likely miss before the year begins, rather than explaining it six months later as an execution problem.

The worked scenario: the company needs $10M in net-new revenue, each rep carries a $1M quota, so it hires ten reps.

• If the historical sales cycle is five months, a plan assuming a new rep is fully productive in 90 days is mathematically impossible.
• A cost that rarely appears in the model is the effect on reps already producing: they hand over accounts and pipeline to new hires, then return to a smaller patch and a harder path to the same quota.

Read original

Deals slip and markets turn, and a board can plan around a miss it saw coming.

• What it cannot absorb is finding out the same day the operations team does.
• Their sharper claim about incentives: a risk process that depends on a rep flipping a status field is always about a month behind, because no rep marks their own number at risk while there is still a chance.
• The alternative is to read behavior rather than sentiment, and attach an inspection or escalation rule to each signal instead of a score.

Each signal comes with an action.

• A close date pushed twice in one month leaves Commit until a manager has actually spoken with the buyer about timeline.
• A late-stage opportunity with nothing on the calendar gets inspected that day.
• A buyer who replied same-day, then goes nine days silent and no-shows a sync, is not having a slow week—a decision is being made without you, and it calls for executive outreach.
• Two weeks from close with legal that has not seen paper is not closing in two weeks.

Read original

The spreadsheet was not the mistake; the order was.

• Having guessed and been challenged, the leader reached for data to defend the guess, so the numbers read as backfill.
• Conversion data is how a diagnosis gets made, not what gets presented.
• Executives want to know where the money is stuck and what is being done about it, in that form.

Two rewrites.

• Instead of reading out that discovery-to-evaluation conversion dropped in EMEA, say there is qualification drift in EMEA, weak pipeline is advancing because exit criteria are subjective, and MEDDIC gates are being hardcoded into the CRM this week.
• Instead of using the word velocity about time-in-stage in security and legal review, say enterprise deals are stalling at contracting, two approval steps duplicate each other, and both are being cut.
• The dashboard goes in the appendix and opens the moment someone asks how you know.

Read original

Marketing announces a large increase in marketing-qualified leads and expects a positive reaction; the CFO answers with the balance sheet.

• Defending the lead number sounds like protecting a department rather than confronting the P&L, and dismissing it undermines the team that generated the demand.
• Their third response connects the two and answers the three questions boards actually ask: what growth cost, how long until that spend is recovered, and what changes as a result.
• In this framing, RevOps is neither on marketing's side nor finance's side, but responsible for making everyone look at the same economic reality.

A 30% increase in MQLs is met by a CFO pointing to CAC payback stretched to 22 months.

• The scripted reply: volume was strong in mid-market, higher acquisition costs in that segment pushed payback to 22 months, and next quarter spend moves toward the channels and segments with a better balance between growth and capital efficiency.
• Aleman adds that the board does not need a tour of the lead-scoring model or a count of webinars attended.

Read original

The deeper diagnosis is about ownership: CPQ was built by one team to control what reps can sell, the comp plan by another to shape what reps want to sell.

• When the two disagree about what a good deal looks like, reps find the gap between them every time.
• This matters more as quoting gets automated, they argue, because once a system can assemble a quote, the compensation plan becomes the steering wheel—the thing that tells the system which deals are worth writing.

A rep discounts to close, the quote clears approval because the tool and its rules said it was fine, and three months later the commission statement is lower than modeled because the discount moved the margin the rate was tied to. Nobody connected the two decisions; in Aleman's framing, the system was never built to.

Read original

The post explains why a plan that adds up on a spreadsheet can still miss its number, and shows the method: take the finance model and identify the operational friction it left out.

Aleman walks through a Q4 planning meeting that looks flawless on paper: the company needs $10M in net-new revenue, each rep carries a $1M quota, so it hires ten reps.

• Six months later, it misses by 30%.
• The post argues that the miss was built into the plan, not caused by poor selling, and identifies the forces the finance model ignores.
• A five-month sales cycle makes a 90-day ramp impossible.
• Doubling headcount without adding pipeline just slices the same deals into smaller pieces.
• Adding reps without a front-line manager undermines deal inspection and win rates.
• Aleman also describes a cost rarely included in a hiring model: new reps need territories and accounts, often taken from reps who were already producing.
• Top performers return to smaller patches and start to see their success as a penalty.
• The closing point defines the roles: leadership sets the aggressive target, while operations shows the friction required to deliver it and flags the miss before the year starts.

For brands planning a campaign

The clearest single piece for a RevOps planning talk. It offers a concrete, repeatable demonstration: rebuilding a headcount plan with ramp curves, pipeline supply and manager ratios, rather than giving general advice about forecast discipline.

Newcomers get a sharper definition here than from most descriptions of the job: not making the number, but removing surprise.

Aleman distinguishes between two kinds of bad quarter.

• Deals slip and markets turn; that is survivable.
• What is not survivable is a committed deal dying in week four and nobody noticing until week eleven.
• The post argues that incentives help explain why: the CRM is the last place a rep will admit a deal is dying, because flagging their own number as at-risk while there is still a chance can look like giving up.
• A risk process that depends on a rep changing a status field is therefore always a month behind.
• Aleman’s alternative is to read behavior, not sentiment.
• A close date pushed twice in one month comes out of Commit until a manager has spoken with the buyer about timing.
• A late-stage opportunity with nothing on the calendar gets inspected that day.
• A buyer who replied same-day and then goes silent for nine days is not having a slow week — a decision is being made elsewhere, and it needs executive outreach.
• Two weeks from close with legal yet to see the paper is not closing in two weeks.

For brands planning a campaign

Strong material for a session on pipeline risk signals. The behavior-based checks make a practical checklist for the audience, and the framing gives the speaker a clear, quotable thesis.

It is useful for anyone with the right numbers who still watches the room switch off.

A RevOps leader is asked in a management review why the sales cycle is stretching.

• They answer that the team needs to push harder, get challenged, then open a spreadsheet of stage-by-stage conversion and velocity figures.
• Aleman says the spreadsheet was not the mistake; the order was.
• After guessing and being challenged, the leader reached for data to defend the guess, so the numbers read as backfill.
• The distinction is between using conversion data to find where money is stuck and presenting it as the answer.
• Executives are not doing pipeline math in their heads; they want to know what is stuck and what is being done about it.
• The post rewrites two examples in those terms.
• Instead of saying discovery-to-evaluation conversion dropped in EMEA, say there is qualification drift in EMEA, weak pipeline is advancing because exit criteria are subjective, and MEDDIC gates are being hardcoded into the CRM this week.
• Instead of talking about velocity, or time-in-stage, in security and legal review, say enterprise deals are stalling at contracting, two approval steps duplicate each other, and both are being cut.
• The dashboard goes in the appendix and comes out when someone asks how you know.

For brands planning a campaign

Useful for a talk or workshop on executive communication. The before-and-after rewrite gives the speaker a live demonstration the audience can copy.

Aleman describes a management review where a marketing or operations leader announces a 30% increase in MQLs and pauses for a positive reaction.

• The CFO points to the balance sheet: CAC payback has stretched to 22 months.
• The post focuses on the trap for the RevOps person in the room.
• Defending the MQL number can sound like protecting a department rather than confronting the P&L.
• Dismissing it undermines the demand-generation team.
• Aleman offers a third response, written out as dialogue: volume was strong in mid-market, higher acquisition costs in that segment stretched CAC payback to 22 months, and next quarter spend moves toward channels and segments with a better balance between growth and capital efficiency.
• The board does not need a tour of the lead-scoring model or a count of webinars attended.
• It needs three things: what growth cost, how long until that spend is recovered, and what changes as a result.

For brands planning a campaign

A strong source for a session on marketing-finance alignment or how RevOps earns credibility with a CFO. The scripted response works as an example audiences can adapt to their own numbers.

It is the set’s most specific piece on margin leaking out of quote-to-cash.

Aleman describes a familiar sequence: a rep discounts to close a deal, the quote clears approval because the tool and its rules permit it, and three months later the rep opens a commission statement lower than modeled because the discount changed the margin the commission rate was tied to.

• Nobody connected the two decisions and, in Aleman’s framing, the system was never built to.
• The underlying diagnosis is that CPQ was built by one team to control what reps can sell, while the comp plan was built by another to shape what reps want to sell.
• When the two disagree about what a good deal looks like, reps find the gap between them.
• Aleman then considers how this changes as quoting gets automated: once an agent can assemble a quote, the compensation plan becomes the steering wheel, telling the system which deals are worth writing.
• The post ends with a conference session announcement for a talk on CPQ and sales compensation.

For brands planning a campaign

The most technical item here and the best anchor for a quote-to-cash or compensation-design session. It also covers the person’s speaking activity and the AI-quoting angle a conference organiser could build a panel around.

The leader guessed at a cause—that the team needed to push harder before quarter end—was challenged, then reached for stage-by-stage conversion and velocity numbers to defend the guess, making the numbers read as backfill.

• The alternative is to name the problem and the fix in the same breath: qualification drift in EMEA because exit criteria are subjective, with MEDDIC gates being hardcoded into the CRM that week.
• Conversion data is how the diagnosis gets made, not what gets presented; the chart sits in the appendix until someone asks how you know.

The same moment is rewritten twice: what the leader said and what they should have said. The difference in framing is visible rather than asserted.

For brands planning a campaign

A session or written piece on executive communication for revenue teams has a ready structure: walk through a real review, then rebuild the answer. Forecasting, CRM, or BI tools can sponsor it without the topic collapsing into a product pitch, because the argument is about sequence and framing, not a dashboard.

Examples: Source 1

A risk model that depends on a rep changing a status field is therefore permanently a month behind reality.

• The post substitutes observable signals for self-report: a close date pushed twice in one month, a late-stage opportunity with nothing on the calendar, a buyer who replied same-day going nine days silent and no-showing a sync, and two weeks to close with legal not yet on paper.
• Each signal carries an inspection or escalation rule, such as pulling the deal out of Commit until a manager has talked to the buyer about timeline.

Aleman draws the boundary explicitly: this does not make the number happen. Markets turn, and competitors win deals that should have been won. What RevOps owns is the absence of surprise.

For brands planning a campaign

A vendor selling pipeline inspection, forecasting, or sales-engagement software can sponsor a talk built on the signals the audience can inspect. The strongest angle is the shift from self-reported deal health to behavior, giving the audience something concrete to change the week after the session.

Examples: Source 1

If the model assumes a new rep is fully productive in 90 days but the sales cycle is five months, the ramp curve is mathematically impossible.

• If headcount doubles without more inbound or outbound capacity, the same pipeline is sliced into smaller pieces and nobody hits quota.
• If front-line managers are not added, deal inspection dies and win rates drop.
• A cost that rarely makes it into the model is the effect on reps who were already producing: new reps need territories, accounts, and pipeline, often taken from the people who built them, so a strong performer returns to a smaller patch and a harder path to the same quota.
• The recommendation is for operations to show leadership the exact friction required to deliver the target and call the miss before the year begins.

For brands planning a campaign

Planning, territory design, and revenue capacity vendors have a specific, testable argument to sponsor. The post also supports a workshop format, since it lays out numbers a room can redo against its own cycle length, ramp assumptions, and patch history.

Examples: Source 1

Jose Aleman traces the leak between them with a worked scenario: a rep discounts to close, the quote clears approval because the tool and the rules said it was fine, and three months later the commission comes in lower than modeled because the discount moved the margin the rate was tied to.

• Nobody connected the two decisions, and the systems were never built to.
• CPQ was built by one team to control what reps can sell, the comp plan by another to shape what reps want to sell, and when the two disagree, reps find the gap every time.
• The post also argues that as quoting becomes automated, the compensation plan becomes the steering wheel—the thing that tells the system which deals are worth writing.

The post doubles as an event promotion, pointing readers to a Dreamforce session on CPQ and sales compensation.

For brands planning a campaign

This is the posts’ clearest commercial intersection, suited to vendors bridging quote-to-cash and incentive compensation. Aleman also uses the channel to promote a conference session, which matters for campaigns built around event-adjacent content rather than standalone posts.

Examples: Source 1

Defending the MQL number sounds like protecting a department, while dismissing it undermines the go-to-market team that generated the demand, so neither response works.

• The suggested phrasing connects the two: strong mid-market volume this quarter, higher acquisition costs in that segment, and next quarter's spend reallocated toward channels and segments with a better balance between growth and capital efficiency.
• The board questions are how much growth cost, how long it takes to recover the investment, and what is changing as a result.
• RevOps is framed as neither on Marketing's side nor Finance's side, but responsible for making everyone look at the same economic reality.

For brands planning a campaign

A brand with spend-allocation, attribution, or marketing-efficiency products can use the MQL-versus-payback framing as a session hook. The post supplies an executive-ready script rather than another metric definition.

Examples: Source 1

An operational situation—a management review, a board conversation, a Q4 hiring plan, a commission statement, or a deal that has gone quiet—runs to the moment where the standard response stops working.

• The writer then names a response to substitute, written as something a person could say or do on Monday.
• The prose uses numbers, quoted phrases, and explicit escalation rules rather than general principles.
• One of the five promotes a conference session.

For brands planning a campaign

The format suits a talk or workshop that takes a room through the same scenario-and-substitute structure, with a sponsoring brand providing the situation and the argument resting on operational detail. The five posts are short text pieces; ask for long-form, video, or transcript samples if the campaign needs those formats.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

View example

Both describe plans locked because the team ran out of time, not because anyone proved them right. Both prefer a tool that refuses to answer over one that answers confidently on bad data.

Mahmood writes as someone building and promoting a planning product, keeping the argument at the data and tooling layer: stale account data, guessed capacity numbers and assumptions nobody agreed to. Aleman focuses on the human mechanics — what reps do when territory shrinks and how an answer lands in a boardroom — without pitching a product.

Read original · Original 2

Spira's diagnostic approach resembles Aleman's: name the sequencing or ownership fault rather than the surface symptom, then offer a concrete test, such as handing a candidate your stage definitions and asking which they would delete.

Spira writes in a numbered, question-led format under a recurring series heading and ties the governance argument to a named vendor's product for version control and approval history. The subjects differ too: Spira covers CRM architecture and the order of the first RevOps hires, while Aleman covers planning arithmetic, board framing and the gap between quoting rules and commission plans.

Read original · Original 2

Roth writes from a sales leadership perspective in a comic narrative register, using the post to recruit and name the people doing the hiring. Aleman writes in a more clinical, diagnostic register, focused on operations and board reporting, and closes with what to say or change rather than an invitation to apply.

Read original · Original 2

The posts walk through discovering a quota gap, territory imbalance, and capacity shortfall in Q3, then argue that planning tools should show their math and say when data cannot support an answer. That makes Mahmood a tighter fit than Aleman for a session on sales-planning model design or evaluating planning software.

The posts focus on sales planning and a creator's own planning tool, not pipeline-risk signals or the CPQ-and-compensation leak.

• Ask Aleman to add forecast-risk diagnosis and quote-to-cash alignment if those are essential to the session.
• Because the posts are product-adjacent, separate the session from the tool to avoid a vendor pitch.

Examples: Source 1 · Source 2

The posts argue that a signed deal should be reconstructable—which quote was final, who approved the discount, when terms changed, and whether the CRM matches the contract—and that the first RevOps hire must own definitions, architecture, and process before measurement. For a company whose forecast pain comes from ungoverned deal changes, audit-trail gaps, or a wrongly sequenced RevOps build, Spira is more directly useful than Aleman on pipeline-risk signals and CPQ-comp alignment.

These posts do not address live pipeline-risk diagnosis or matching CPQ to comp.

• One is tied to a specific deal-governance product; the other argues for a particular hiring sequence.
• A talk on forecast accuracy and sales-comp plan design would need substantial new material.
• Aleman's posts, by contrast, give the pipeline-risk triggers and discount-to-commission example this alternative lacks.

Examples: Source 1 · Source 2

The posts describe a comp plan built without sales input that led A-players to leave, and a deal-size turnaround that cut sub-$5K deals from forecast, added MEDDICC-based structure, focused on top accounts, and shifted upmarket. For a need centered on sales-comp change management, rep retention, or deal-size strategy, Roth is a better choice than Aleman for the diagnostic and quote-to-cash angle.

These posts lack the behavior-based pipeline-risk checks and CPQ-approval-to-commission mismatch in Jose Aleman's posts.

• One mixes a hiring promotion and jokes with the lesson, so a talk would need tighter structure.
• For a session focused on diagnosing pipeline risk and aligning CPQ with sales compensation, this alternative offers adjacent sales-management experience but less of the requested operational detail.

Examples: Source 1 · Source 2