Hassan Mahmood works on sales planning and revenue operations. Mahmood's writing focuses on territory, quota, capacity, and compensation planning, including how AI can help teams test scenarios while tracing recommendations back to their data and assumptions. Mahmood says they have spent fifteen years working with sales planning teams and helped build Voiant Sales Intelligence.
Hassan Mahmood is most useful for practitioner-led content on traceable AI-assisted territory, quota, capacity, and compensation planning.
Best for
Enterprise sales-planning or compensation software running webinars or co-authored assets for planning, sales ops, and RevOps leaders.
Not for
Frontline SDR enablement, sponsored post reach plays, or mixed individual-contributor AI sales keynotes.
Key takeaways
A confident wrong AI answer is worse than no answer when data cannot support it.
Planning breaks because files do not agree, not because the plan is wrong.
Reconciliation eats the work revenue operations teams were hired to do.
Check first: Confirm audience job titles, seniority, industry, company size, geography, and campaign-specific results before committing.
Main ideas
A confident wrong answer is worse than no answer · Planning breaks because the files don't agree, not because the plan is wrong · The connected model sits on top of existing planning platforms; it doesn't replace them
Hassan Mahmood writes about the decisions behind sales planning and revenue operations: how to set territories, quotas, capacity and compensation, and how to test changes without losing sight of the data and assumptions behind them.
They argue that a polished AI answer is not enough if its inputs cannot support the recommendation.
They also wrote The 90-Day Planning Cycle, a short book about why annual sales planning can take six months and how to complete it in ninety days.
Mahmood makes the costs of planning friction tangible.
They describe teams spending weeks reconciling territory, pipeline and compensation files, then avoiding useful “what if” questions because each change triggers days of rework.
Their proposed alternative is analysis that connects territory, quota, headcount, compensation and forecasts—and shows how each number was reached, or says when the data cannot support an answer.
That emphasis also shapes their advice for RevOps: disputes and reconciliation consume time that could go to account strategy.
Their work is useful to sales-planning and RevOps readers who want to understand not only what a plan recommends, but whether its assumptions can be examined and challenged.
Hassan Mahmood writes about sales planning and revenue operations.
Read more
Their posts argue that most planning failure is a data-integrity failure dressed up as a forecasting problem.
Territory, pipeline, compensation and headcount sit in separate files that disagree, so a smart team spends weeks reconciling versions by hand, then locks a plan because the clock ran out, not because anyone proved it right.
The numbers that matter — a quota gap, a territory imbalance, a capacity shortfall — tend to surface in the third quarter, when they can no longer be fixed.
Mahmood's answer is a connected model with traceable math and a stated preference for no answer over a confident wrong one.
Shorter posts add a diagnostic for judging whether a plan will land on time and describe how revenue operations teams lose their days to reconciliation.
Mahmood names Voiant Sales Intelligence as a product they helped build and positions it as a layer above established planning platforms, not a replacement for them.
A confident wrong answer is worse than no answer
Hassan Mahmood argues that AI planning tools have made the wrong part easy.
Read more
Ask a tool to rebalance territories or move quota and it will answer in seconds with a clean recommendation and a chart, without mentioning that the underlying account data is six months old, half the rep capacity numbers came from someone's spreadsheet guess, or the plan rests on assumptions nobody agreed to.
The plan then ships because it looks finished.
Mahmood would rather receive no answer than a confident wrong one, because no answer sends someone to check the data.
The design rule they say they built Voiant around follows from that: show how each number was calculated, let users trace a recommendation back to its inputs, and have the system say when the data cannot support an answer.
Mahmood states both sides of a tension: AI makes analysis take minutes instead of weeks, but also makes unsupported answers spread quickly.
Their constraint is not less AI, but rules about what it is allowed to conclude, drawn from years of doing the work by hand.
A tool rebalances territories in seconds and returns a recommendation with a chart attached.
Two quarters later, attainment is down, a strong rep is fielding calls from recruiters, and someone in finance asks where the number came from.
Nobody can say.
The post closes by asking whether readers could trace every number in their last scenario back to its source.
Planning breaks because the files don't agree, not because the plan is wrong
Hassan Mahmood describes an annual ritual they have watched as a consultant and built models for themselves.
Read more
In October, one person exports territories from the planning tool, someone else pulls pipeline from the CRM, and finance sends a compensation file with different rep names from the other two.
A capable, expensive team then spends about six weeks lining up those files by hand, arguing over which version is current and rebuilding the model every time leadership asks a new question.
Because each what-if question costs roughly three days of rework, people stop asking.
The plan gets locked because the team ran out of time, not because anyone proved it was right.
Mahmood proposes a thinking layer that holds territory, quota, headcount, compensation and forecast in one model, so a change in one shows up in the others.
The goal is to plan in weeks and answer a scenario that same afternoon, with the math visible.
The image accompanying the post marks three numbers in orange on sample data: a quota gap, a territory imbalance and a capacity shortfall.
Each is the kind of figure leadership learns about in the third quarter, when it is already too late to fix.
A rep gets a number their territory could never support, misses, leaves, and the miss is recorded as a performance problem.
The connected model sits on top of existing planning platforms; it doesn't replace them
A practical boundary runs through Hassan Mahmood's product writing.
Read more
They say plainly that they are not trying to replace platforms such as Pigment, Anaplan or Varicent: those platforms are where a plan should live, and their team has spent years implementing them.
What those platforms don't provide out of the box, in Mahmood's account, is a layer that reasons across all of them at once, so a change to territory, quota, headcount, compensation or forecast propagates through the rest instead of forcing a rebuild.
The claim is deliberately narrow: the argument is about where the analysis happens, not which system of record a company should run.
The post lists four product goals: plan in weeks rather than spend a full quarter reconciling files; get a same-afternoon answer to a what-if with the math shown; keep a forecast where every number traces back to a decision someone can accept or reject; and have the system admit when the data cannot support an answer. The fourth goal echoes the rule in the post about AI tools that answer too readily.
A planning team's arguments in October predict whether the plan lands in January
Hassan Mahmood offers a diagnostic for the first week of October.
Read more
It is about what people argue over, not which tools they use.
If the argument is over whose account list is right or which version of the Excel file is current, the plan usually lands late.
If the argument is about the market and the assumptions behind the numbers, or which accounts deserve more coverage, Mahmood reads that as a sign of a mature organisation and expects the plan to arrive on time.
The diagnostic is aimed at sales planning, sales operations and revenue operations people whose fiscal year starts in January.
It reframes planning quality as a question of where a team's attention goes.
Hassan Mahmood asks readers where they are in their planning and, in the same post, names a short book, The 90-Day Planning Cycle. They describe it as a book about why annual sales planning takes most companies six months and how to set territories, quotas and compensation plans in ninety days.
Reconciliation eats the work revenue operations teams were hired to do
Hassan Mahmood describes revenue operations teams' day-to-day as reactive work that is genuinely necessary but moves nothing forward: disputes, territory fights, quota adjustments and chasing why one system doesn't match another.
Read more
The work people took the job for — account strategy, working out the right ratio of addressable market to rep, spotting greenfield accounts outside the CRM — does not happen because reconciliation leaves no time.
Mahmood's uncomfortable point is that the tools and techniques to change this already exist.
What is missing is a decision to trade one kind of work for the other.
That puts the obstacle in management's hands, not the software market — a different claim from the product posts, but one that sits alongside them.
The post lists what revenue operations teams do all day: disputes, territory fights, quota adjustments and cross-system mismatches, all reactive and necessary. It also lists what they have stopped doing: account strategy, TAM-to-rep ratios and finding greenfield accounts outside the CRM.
Hassan Mahmood’s central claim about AI and sales planning is simple: an answer is not the same as a defensible answer.
Read more
It is also the clearest statement of the design rule they say they built their product around.
Hassan walks through a specific failure mode.
An AI tool asked to rebalance territories or move quota returns a polished recommendation with a chart, but never mentions that the account data is six months old, half the capacity numbers are spreadsheet guesses, or the plan rests on assumptions nobody agreed to.
The plan goes out because it looks finished.
Two quarters later, attainment is down, a strong rep is fielding recruiter calls, and nobody in finance can say where the number came from.
Hassan would rather get no answer than a confident wrong one, because no answer sends someone to check the data.
They say Voiant Sales Intelligence was built to show how each number was calculated, trace recommendations back to their inputs, and say when the data cannot support an answer.
The post ends by asking readers whether they could trace every number in their last scenario back to its source.
For brands planning a campaign
The traceability argument is the strongest hook for a webinar or written collaboration with a sales planning software company. A session framed around one real scenario, worked through live with the question "can every number be traced back," matches the claim Hassan is already making rather than bolting a product pitch onto generic AI-in-sales content.
This is the fullest account of the problem Hassan addresses and the clearest look at how they position their product alongside large planning platforms.
Read more
Read it before the shorter posts.
The post details an annual planning ritual.
In October, one person exports territories from the planning tool, someone else pulls pipeline from the CRM, and finance sends a comp file with different rep names from the other two.
A capable, expensive team then spends six weeks matching files by hand, arguing over which version is right, and rebuilding the model each time leadership asks a new question.
Because each what-if costs three days of rework, people stop asking, and the plan gets locked because the team has run out of time—not because anyone has proved it is right.
The year plays out as a quota gap, a territory imbalance, and a capacity shortfall that surface in Q3.
Hassan says they have seen this as a consultant and built those models themselves.
They position Voiant as a thinking layer across territory, quota, headcount, comp, and forecast on one model, and explicitly say they are not trying to replace platforms like Pigment, Anaplan, or Varicent, where they say a plan should live.
The post notes that the numbers in the image are sample data.
For brands planning a campaign
Useful for a co-existence message rather than a replacement pitch: a planning vendor can position itself alongside the platforms its prospects already use. The October-to-January countdown offers a natural seasonal slot for a session on why plans are locked by the calendar rather than by evidence.
The shortest version of Hassan’s diagnostic method, and the post where they name their book.
Read more
If you only have two minutes, this one tells you who they are talking to.
Hassan’s test is what the planning team is arguing about.
If the argument is over whose account list is right or which Excel file is current, the plan usually lands late.
If it is about the market, the assumptions behind the numbers, or which accounts deserve more coverage, Hassan sees a mature organisation and expects the plan to land on time.
They address sales planning, sales operations, and RevOps teams whose fiscal year starts in January, and close by asking where readers are in their planning.
Hassan also says they wrote “a short book, The 90-Day Planning Cycle,” about why annual sales planning takes most companies six months and how to set territories, quotas, and comp plans in ninety days.
For brands planning a campaign
The diagnostic lends itself to audience participation: ask attendees what their team is arguing about and work from their answers.
The book is a natural supporting asset, but the post does not name a separate publisher or catalogue record.
The clearest picture of the team Hassan addresses and what they think the job should be.
Read more
Read it to decide whether your audience is the subject of their work.
Hassan describes revenue operations as a cycle of reactive but necessary work that does not move the business forward: disputes, territory fights, quota adjustments, and chasing down mismatches between systems.
The work people took the job for—account strategy, finding the right ratio of addressable market to rep, and spotting greenfield accounts outside the CRM—does not happen because reconciliation takes all their time.
Hassan’s conclusion: the tools and techniques already exist; the obstacle is a decision nobody has made to trade one kind of work for the other.
For brands planning a campaign
This points to a decision-level session, not a tooling demo. Build on the trade-off between reconciliation and proactive account strategy—the question a buyer must answer before a planning product matters.
How Mahmood makes the case: narrated failure modes and a direct handoff4
Territory, quota, capacity and comp planned in one connected model1
AI should refuse to answer when the data can’t support it1
The annual planning countdown: six months versus ninety days1
RevOps time lost to reconciliation instead of strategy1
Territory, quota, capacity and comp planned in one connected model
Hassan Mahmood argues that sales planning breaks when territory data, pipeline, headcount, compensation and forecast sit in separate files that don’t match: rep names differ in the comp export, and the model gets rebuilt whenever leadership asks a new question.
Read more
They say teams spend six weeks manually reconciling the files, then lock a plan because time ran out, not because anyone proved it right.
Mahmood positions Voiant Sales Intelligence as a thinking layer across these systems, so changes in one area show up in the others.
The goal: plan in weeks and get a same-afternoon answer to a scenario, with the math shown.
Mahmood illustrates the problem with sample data: three flagged numbers representing a quota gap, a territory imbalance and a capacity shortfall, plus a story about how those numbers surface too late in Q3 to fix.
Mahmood says they are not trying to replace platforms such as Pigment, Anaplan or Varicent, and that their team has implemented them. Avoid “replace your planning stack” framing; it conflicts with their stated position.
For brands planning a campaign
Pitch connected planning across territory, quota and comp on a single model, not another point tool. Show the reconciliation step disappearing and a “what if” answered without a rebuild.
AI should refuse to answer when the data can’t support it
Mahmood argues that every AI planning tool will produce an answer, but a confident wrong answer is worse than none.
Read more
A polished recommendation with a chart can hide six-month-old account data and capacity numbers that were someone’s best guess.
In the failure they describe, the plan goes out because it looks finished; reps get new territories, attainment falls two quarters later, and nobody can say where the number came from.
Mahmood says Voiant was designed to flag when the data can’t support an answer, with each number traceable to its inputs and rules for what may be concluded drawn from years of manual work.
For brands planning a campaign
A content collaboration on AI governance for planning fits Mahmood’s public argument: how to constrain what a model can conclude and audit a planning recommendation. It gives a software partner a credible, non-salesy angle.
The annual planning countdown: six months versus ninety days
Hassan Mahmood offers a diagnostic to use by the first week of October: ask what the team is arguing about.
Read more
Disputes over whose account list is right or which spreadsheet version is current predict a late plan; debates about market assumptions and which accounts deserve more coverage predict an on-time plan. Mahmood connects this to “The 90-Day Planning Cycle,” a short book they wrote about why annual sales planning takes most companies six months and how to set territories, quotas and comp plans in ninety days.
Mahmood turns the observation into a public self-test for sales planning, sales ops and RevOps leaders whose fiscal year starts in January, offering the book in exchange for a direct message or comment.
Before promoting the book, ask Mahmood for a description of its contents; the post references it but gives only their description of its subject.
For brands planning a campaign
A clear seasonal hook: a webinar or content series built around the October-to-January planning countdown, opening with the “what is your team arguing about” diagnostic and working through a compressed planning calendar.
RevOps time lost to reconciliation instead of strategy
Hassan Mahmood says RevOps teams spend their days on territory fights, quota adjustments and chasing mismatches between systems: all reactive, all necessary, none of it moving the business forward.
Read more
Account strategy, TAM-to-rep ratios and spotting greenfield accounts outside the CRM don’t get done because reconciliation uses up the time. Mahmood says the tools and techniques to change this already exist; the missing piece is a decision to trade one kind of work for the other.
For brands planning a campaign
This frames the buyer’s problem in terms of time allocation. A joint asset that quantifies hours spent reconciling systems, or shows how to reallocate that time, would fit Mahmood’s argument and give sales planning and RevOps leaders a reason to attend.
How Mahmood makes the case: narrated failure modes and a direct handoff
Across the posts, the recurring structure is a concrete failure story, not a feature list: a rep gets a number their territory could never support, misses, leaves, and the result is called a performance problem; or a plan ships looking finished and attainment drops two quarters later.
Read more
Mahmood names the roles and timing, gives a short set of design requirements, then closes with a direct ask: send a DM, comment below, or describe how you handle the problem today. The prose is plain and specific, anchored by sample data or an annotated image.
Problem narrative, cost of the status quo, approach or product, then a direct reader action. All four posts reviewed follow this structure.
For brands planning a campaign
Plan for a story-led format with one clear reader action. Build a webinar around a single failure scenario the audience recognises, not a feature tour, and give Hassan Mahmood a concrete question to put to the audience.
The four posts detail one business relationship: Hassan Mahmood writes that they and their team built Voiant Sales Intelligence, a sales planning product that checks territory, quota, headcount, comp, and forecast in one model.
Read more
They position it alongside established enterprise planning platforms — Anaplan, Pigment, and Varicent — noting that those platforms are where plans should live and that their team has spent years implementing them. The posts also refer to a short book Mahmood wrote, The 90-Day Planning Cycle, on setting territories, quotas, and comp plans in ninety days.
Voiant Sales Intelligence
Owned business
Mahmood writes that they and their team built Voiant Sales Intelligence over several months, and says they are proud of the product.
Read more
They present it to sales planning and RevOps leaders and invite readers to request a demo by direct message. The posts do not specify their formal title or company structure; ask them to clarify before scoping a deal.
Hassan Mahmood writes about why sales plans fail in the handoff between the planning tool, the CRM file and the finance file, and what a connected planning model should do instead.
Read more
Start with the October planning countdown for the diagnostic: what a team argues about predicts whether the plan lands.
Then read the post on file reconciliation for the fullest account of the problem, followed by the AI caveat about refusing to answer when the data cannot support it and the shorter post on RevOps teams losing their days to disputes.
The work is for sales planning, sales ops and RevOps readers, and anyone evaluating AI-assisted territory, quota, compensation and forecast work.
For adjacent reading, Jose Aleman, Jake Dunlap and Marcus Chan are the closest comparators.
Jose Aleman also writes LinkedIn posts for sales and revenue operations leaders about why capacity plans and forecasts fail when operational friction is left out of the model.
Read more
The posts use concrete failure scenarios — hiring ten reps and missing the quarter, or a Commit deal dying unnoticed — and argue that the operational team must surface the miss before the year begins. That is the same reader and the same habit of tracing a bad outcome back to a planning assumption.
Hassan Mahmood focuses on data integrity and a connected territory, quota and headcount compensation model with traceable math; Jose Aleman focuses on the hiring math itself: ramp curves, pipeline slicing and reading deal behavior rather than sentiment to avoid board surprises.
Jake Dunlap writes for revenue and RevOps leaders about structural causes of failure, using portfolio-scale analogies and a blunt rule about incentives.
Read more
Both argue that plans and tool stacks will not change until someone owns the outcome and the math is visible.
Hassan Mahmood stays inside sales planning across territory, quota, comp and forecast; Jake Dunlap focuses on private-equity portfolio commercial leadership risk and tool sprawl, arguing that no new tool should be approved without saying what it replaces and that shrinking the stack needs to sit in someone's paycheck.
Marcus Chan writes LinkedIn posts for sales leaders that turn failures into teachable stories and end with a direct change in behavior.
Read more
Both use concrete scenes — a rep given an unsupportable number or a top performer humiliated in a team meeting — to show how a management decision produces a downstream result.
Hassan Mahmood analyzes planning systems, reconciliation work and AI traceability for sales planning and RevOps; Marcus Chan coaches frontline sales management and deal strategy, including how to prepare a champion for a CFO conversation and how a manager should handle a missed number.
For a webinar or content collaboration on AI-assisted territory, quota, and compensation planning, the available audience information is thin and LinkedIn-only.
Read more
Hassan Mahmood's LinkedIn profile showed 4,532 followers on 8 October 2026, and the four posts ran from 21 September to 5 October 2026.
That is a small base for an activation that depends on registration volume, so treat this as a content collaboration or a pilot, and ask for campaign-specific results before committing to it as a reach play.
The subject matter speaks to a specific professional reader—sales planning, sales ops, and RevOps people who deal with territory disputes, quota changes, comp, and CRM reconciliation—and the posts address that reader directly, with open questions and invitations to DM.
The posts do not identify followers' roles or workplaces.
Ask for LinkedIn analytics covering follower job titles, seniority, industry, company size, and geography over the last 6–12 months, plus reach, reactions, comments, and DM or lead volume on the four planning posts above, and registration or attendance numbers from any comparable webinar or gated content.
Whether readers act on the 90-day planning cycle book offered in the 5 October post would be the closest available proxy for a webinar conversion.
Hassan Mahmood’s four posts include no sponsor policy, rate card, media kit, or partner disclosure.
Read more
They present them as a practitioner and vendor, promoting Voiant Sales Intelligence, a sales planning product they say their team built, and offering their short book, The 90-Day Planning Cycle, to readers who ask.
These are their own offers, not third-party sponsorships, so they don’t show what a paid collaboration might include or how they handle disclosure.
The only contact route in the posts is a direct LinkedIn message: one invites enterprise sales planning and RevOps leaders to DM about Voiant’s Sales Intelligence AI; another asks readers to DM or comment to receive the book.
Before committing budget, ask whether they accept sponsored posts, webinar or event participation, and co-authored content, and request written rates and disclosure terms.
Need: an enterprise sales-planning and compensation software company wants a practitioner-led webinar plus one co-authored written asset on AI-assisted territory, quota and comp planning, aimed at sales planning, sales ops and RevOps leaders whose fiscal year starts in January.
Read more
Decision: accept, with reach expectations set low and commercial terms agreed in writing first.
The case rests on topical overlap, not audience size.
Hassan Mahmood's posts already make an argument for this exact subject.
One says an AI planning tool may return a clean recommendation with a chart attached while hiding account data that is six months old, capacity numbers that were someone's spreadsheet guess, and assumptions nobody agreed to.
They would rather get no answer than a confident wrong one.
That traceability rule — show the math, refuse when the data cannot support an answer — is a natural spine for a vendor session and their stated position, not a campaign script.
Another post lays out the buyer problem: territories exported from one tool, pipeline pulled from a CRM, a finance comp file with different rep names, six weeks of hand-matching, and a plan locked because the team ran out of time.
A third offers the seasonal hook, the October-to-January countdown, and a diagnostic a webinar host can run live: ask what the team is arguing about.
A fourth frames the payoff as a trade between reconciliation and account strategy work.
They also state a boundary that helps a planning vendor: they are not trying to replace platforms such as Pigment, Anaplan or Varicent, and their team has implemented them.
A co-existence or thinking-layer framing fits their public position; a replace-your-stack pitch does not.
Before committing, negotiate the deliverable, fee, disclosure wording and any exclusivity directly and in writing; no partnership or sponsorship details, rate card, media kit, deliverable list or disclosure practice are published in the posts.
The measured audience is LinkedIn-only: 4,532 followers on the profile observed 8 October 2026, with no follower seniority, industry, geography or company-size data, and no per-post reach, reaction, comment or lead figures.
Treat this as a content collaboration or pilot whose value is credibility and topic match, not registration volume; ask for registration or attendance numbers from a comparable session before setting targets.
They promote Voiant Sales Intelligence, a product their team built, so agree how an adjacent or competing product will be handled on air.
When to choose a specialist
Need: a sales-engagement or frontline SDR enablement brand wants a sponsored post series and a registration push with targets based on follower count and impressions, plus a general 'AI in sales' keynote for a mixed individual-contributor audience.
Read more
Decision: decline in this form.
The audience is the mismatch.
Hassan Mahmood writes for enterprise sales planning, sales ops and RevOps people dealing with territory disputes, quota changes, compensation files and CRM reconciliation.
Their content is diagnostic and story-led — a rep gets a number the territory could never support, misses, leaves, and it gets called a performance problem — rather than the fast, individual-motivation format a frontline SDR campaign usually runs on.
Their posts address leaders who own a plan, not individual reps buying a prospecting tool.
The reach target is unsupported.
The only measured figure is 4,532 LinkedIn followers, with no engagement or reach data behind it and no audience demographics to show those followers are the target buyer.
Targets or pricing based on audience size would rely on a claim the available figures cannot support.
The format compounds the mismatch.
Their posts publish no sponsor policy, rate card, media kit or partner disclosure practice, so there is nothing to price or schedule against; they also do not say how a paid arrangement would be disclosed.
They promote their own sales-planning product and book.
A campaign for a competing product, or one asking a keynote to stay generic, would conflict with the work they already publish.
This could work if the audience shifted to sales planning and RevOps leaders, the deliverable became one anchored scenario walkthrough instead of a volume post series, and success were measured by qualified conversations rather than impressions.
Settle the written scope and rate, disclosure language, and how the adjacent product will be represented before proceeding.
A worked campaign example
Campaign angle: 'Where did that number come from?' — a 45-minute practitioner webinar plus one co-authored article and one short traceability checklist, built entirely from arguments Hassan Mahmood already makes publicly.
Format.
Open with the diagnostic from their October countdown post: what is your team arguing about right now — whose account list is right, or the assumptions behind the numbers?
Use the answers as the session's running material.
Then walk through one scenario end to end: a territory rebalance or quota shift, the recommendation the tool returns, and the questions underneath it — how old is the account data, whose best guess were the capacity numbers, and which assumptions did anyone actually agree to?
Close with their rule from a post: every number should show its math, and the system should say the data cannot support an answer when that is true.
End with their call to action: describe how you handle this today, or send a message to continue the conversation.
Why it works with this creator.
The failure narrative comes from their own writing: three flagged numbers representing a quota gap, a territory imbalance and a capacity shortfall that leaders discover in the third quarter, by which point it is too late.
The payoff comes from their RevOps post: the trade between reconciliation work and the account strategy, TAM-to-rep ratio and greenfield work people took the job for.
The seasonal hook is theirs: the first week of October as the point when a January plan is already predictable.
Deliverables and division of work.
One 45-minute live session, co-hosted with a named counterpart from the brand; one co-authored written piece on auditable planning scenarios, published on the brand's site and promoted from Hassan Mahmood's LinkedIn; one short checklist the audience can use on their own plan without the article.
They bring the scenario and diagnostic; the brand brings the platform context and follow-up route.
Constraints to hold.
Keep the platform-coexistence line intact: they are not replacing Pigment, Anaplan or Varicent, and their team has implemented them.
The session should sit alongside the buyer's existing planning stack, not against it.
Agree in writing on deliverables, fee and disclosure; no rate card or sponsor policy is published in the posts.
Agree how their product, Voiant Sales Intelligence, will be handled on air.
Measurement and the honest ceiling.
Judge the pilot on registrations from the named planning and RevOps audience, attendance rate, and qualified follow-up conversations, not impressions.
The only measured audience figure available is 4,532 LinkedIn followers observed 8 October 2026, with no engagement or registration data.
Treat the first run as a pilot and ask for comparable webinar numbers before scaling.
If it works, the natural extension is a short series following the planning calendar from October through January, using the second and third posts as episode hooks.
Details that affect this plan.
The four posts have no publication dates, so treat them as a set rather than a dated progression.
The book named in one post, The 90-Day Planning Cycle, is not available here; confirm it before treating it as a finished reference.
The posts include no video, transcript or article-length work, so the proposed format rests on written posts alone.
Ask how readers act on invitations to message or comment before setting response targets.
Choose Jose Aleman instead when the session's core problem is forecast risk and capacity math, not the planning model itself.
Read more
The two posts address the gap between headcount and revenue capacity: hiring ten reps does not add ten quotas because ramp curves, pipeline dilution and manager span change the arithmetic, and existing reps often lose accounts to fund new hires.
The second post offers a behavior-based early-warning routine for deals that are dying while the CRM still shows them as Commit.
This is a sharper fit if the vendor's audience cares more about catching a miss before the quarter closes than about building the territory or comp plan.
A session built on this material would focus on inspection and friction: what the finance model ignores, which risk signals a rep will never volunteer, and how RevOps owns the absence of surprise.
The tradeoff is that neither post covers territory design, quota setting or compensation mechanics as the vendor's product does.
Aleman focuses on what happens after the plan is built: capacity assumptions, ramp, pipeline allocation and deal inspection.
The session would spend less time inside the planning tool and more on the operating consequences a planning leader has to defend to the board.
Hassan Mahmood's posts sit closer to the planning subject itself; Aleman's focus is the execution risk around it.
Choose Jake Dunlap instead when the buyer wants to discuss organizational risk around commercial leadership and tool governance, not the mechanics of territory and quota planning.
Read more
One post describes a portfolio of companies where every growth thesis depends on one VP of Sales or CRO hire, with 18 to 24 months of lost growth before a bad hire is caught and replaced.
It proposes a shared bench of senior GTM operators as a hedge.
The other argues that tool sprawl will not shrink until someone's compensation depends on shrinking it, that teams use maybe 30% of what they already own, and that keeping pace with platform releases is a standing function rather than an audit.
For a planning software vendor whose main sales objection is 'we already have a stack and nobody owns it,' that second argument is directly useful.
The tradeoff is distance from the vendor's core subject.
Dunlap's work focuses on portfolio-level hiring risk and tool portfolio management.
It does not cover territory modeling, quota allocation, comp plan design or the file-reconciliation cycle described in Hassan Mahmood's posts.
A webinar built mainly on Dunlap's material would need the vendor to supply the planning-specific scenario.
The audience may also skew toward investors, PE operating partners and GTM operators rather than the sales planning and RevOps practitioners targeted by a session about planning-specific scenarios.
Choose Marcus Chan instead when the campaign's goal is to improve how sales managers coach deal execution, not how a planning team sets territories, quotas or comp.
Read more
One post recounts a sales leadership mistake: publicly humiliating a strong performer and losing them.
The lesson is that reps quit managers, not companies.
The other walks through teaching a champion to sell internally, including role-play questions to ask before sending negotiated pricing to an economic buyer.
If the vendor's webinar targets sales managers who have to make a plan land with a team, this material offers a live-coaching angle and a concrete scenario about the CFO conversation that a planning tool cannot model on its own.
The tradeoff is the buyer task itself.
Chan's posts focus on manager behavior and champion enablement, not territory, quota or compensation planning.
The session would be a sales leadership conversation with a planning vendor as sponsor, rather than a practitioner-led planning session.
The audience is frontline sales managers and reps, narrower than the enterprise sales planning and RevOps leaders for a planning-focused session.
Hassan Mahmood's posts already cover the planning-specific problems and the AI traceability argument, so Chan represents a different purchase decision, not a substitute for the same one.
Four LinkedIn posts by Hassan Mahmood cover AI-assisted planning and the case for traceable numbers, the annual cycle that starts with territories sent from one system and a compensation file from another, the October checkpoint for judging whether a January plan will land on time, and how revenue operations teams lose their days to disputes and reconciliation.
The posts name Voiant Sales Intelligence, a planning product Hassan says they and their team built, and a short book, The 90-Day Planning Cycle, described in one post; the post does not describe the book's contents, so it is treated as a lead rather than a summarised source.
The posts carry no publication dates, so they are presented as a set of positions rather than a dated progression.
No video, transcript, article-length work, sponsor policy, rate card or audience-demographic data is published in the posts here.
The only measured audience figure is a LinkedIn follower count of 4,532 observed on 8 October 2026.
For adjacent reading, the discovery section compares Hassan Mahmood with Jose Aleman, Jake Dunlap and Marcus Chan.
