Search creators⌘K
  1. Home
  2. Creators
  3. Brendan Short

Brendan Short

Brendan Short writes about B2B sales, enterprise deal enablement, and how AI is changing revenue operations and sales roles.

40.5K followersEnterprise salesSales enablementAI in salesRevenue operationsBased on 9 posts · latest Oct 2026
LinkedIn

At a glance

Brendan Short is useful for explaining enterprise micro-pitches and where AI fits in sales workflows.

Best for

B2B SaaS brand or talk for revenue leaders on enterprise sales and AI adoption.

Not for

Volume-first outbound campaigns measured mainly by follower reach and paid post engagement.

Key takeaways

  • Enterprise deals run as dozens of micro-pitches, not one pitch.
  • XBOW's BDR team becomes agent managers when agents do outreach.
  • Practitioners say cold calling, buyer relationships, and market knowledge may stay human.

Check first: Confirm audience composition, sponsor conflicts, and independence before agreeing to work.

Main ideas
Enterprise deals are a series of small pitches, each needing its own material · AI sales tools should cut touchpoints, not multiply them · When agents do the outreach, the BDR job becomes managing agents
Audience
40,470 LinkedIn followers · 3 posts in 4 days (28 September – 1 October 2026) Publishing in the reviewed sample
Read first
Enterprise sales means dozens of micro-pitches, not one
Ways to work together
Sponsored placement in The Signal (disclosed example)
Sources for this section

What they are known for

Brendan Short writes about B2B sales, enterprise deals, and how AI is reshaping revenue teams.

  • Their posts connect big shifts to the work sellers actually do: tailoring materials for each person in a buying committee, changing BDR roles as agents take on more workflow, and preserving human connection and market knowledge where they matter.
  • Their work is useful for sales and RevOps readers weighing what to automate—and what still depends on people and deal context.

Short makes AI-and-sales trends tangible through specific operating examples.

  • In one post, an enterprise deal becomes a sequence of micro-pitches: a VP of Sales, RevOps, security, legal, and frontline managers each need materials suited to their questions.
  • In another, an AI-heavy revenue operation shifts BDRs from research and copywriting toward checking agent output and managing workflows.
  • A third gathers operators’ views on what may endure, including cold calling, buyer relationships, and sellers’ market knowledge.
  • Together, these examples offer a practical lens on balancing automation with buyer-specific support and human judgment.
  • One post discusses a Clarify product launch and identifies Clarify as a sponsor of The Signal.
Sources for this section

Ideas and priorities

Brendan Short writes about enterprise selling and what AI changes in revenue teams.

Read more

Their recurring position is that big deals are won through a long series of small, stakeholder-specific pitches rather than one presentation; AI sales tools should be judged by whether they help buyers move through that process, not by how much more outreach they generate; and as agents take over research and outreach, the sales development role shifts toward managing and checking that work. Short also asks practitioners what they think stays human in selling and publishes their answers alongside their own.

Enterprise deals are a series of small pitches, each needing its own material

Short argues that enterprise sales is not one pitch but dozens spread over months.

Read more

They call each one a “micro-pitch” that should build on the last.

  • The work is not only persuading a single buyer; it is moving through the people who each have a say.
  • In their account, the deal passes from the VP of Sales to RevOps, then security, then legal, then frontline managers, and back to the VP of Sales with whatever the round turned up, while the seller keeps the whole buying committee warm.
  • Because each audience is different, every step needs its own asset, built on the latest deal context rather than a reused template.

Short names the sequence and the asset for each stop: a 1:1 landing page for the VP of Sales, a deck for RevOps, a security and trust document, a legal redline, a designed thank-you note to the buying committee, and a deal room to manage the process end to end.

Read original

AI sales tools should cut touchpoints, not multiply them

Short distinguishes most “AI for sales” products, which they describe as driving more sequences, more calls, and more top-of-funnel activity, from tools that build sales material from what is already recorded on the deal.

Read more

Their argument is that a CRM already holds the context a pitch needs, so assets can reflect what a specific buyer actually asked for instead of presenting a generic document with a new logo. They judge a tool by whether it helps the buyer process the decision more easily, favoring fewer, higher-quality touchpoints over more contact.

Short walks through Clarify’s Artifacts launch, where an agent builds decks and documents inside the CRM from past calls, emails, and notes.

  • A RevOps deck, for example, can address what RevOps raised on the last call.
  • They state in the same post that Clarify sponsors their newsletter, The Signal, so the endorsement and the vendor’s launch message travel together.

Read original

When agents do the outreach, the BDR job becomes managing agents

Short argues that AI-native revenue teams redesign sales roles rather than delete them.

Read more

Their example is a company that moved its BDR team under RevOps and described the role as “agent managers.”

  • In their account, those BDRs are the humans in the loop: they quality-check what the systems generate, handle steps that still need a person, and have career paths into sales, RevOps, customer success, and GTM engineering.
  • Short sees this as the direction of the combined sales-development role across AI-native revenue organizations, though they call the example extreme because the internal systems are unusually sophisticated.

XBOW, the former GitHub Copilot team, runs revenue like a product org, with sprints and in-house tools built with Claude Code.

  • Short describes an internal system that sends each seller their most urgent opportunities every morning with one action to take, runs every call through eight agents for coaching, and turns dense security findings into language a seller can carry to a CISO.
  • With that much work automated, they conclude, the BDR job involves less research and copywriting and more managing the workflows that do them.

Read original

Short collects practitioners’ views on what stays human in selling

Short asked GTM operators a single question: in the AI era, what is one thing in your role that is not changing?

Read more

The answers they gathered and published reflect the operators’ views, not their own claims.

  • They include cold calling; buyers wanting to buy from a salesperson when signing a large check; human-to-human interaction becoming more valuable; hiring more SDRs rather than fewer; account executives carrying more accounts and higher quotas once the jobs to be done are split up; sales reps being closest to the market; RevOps operationalizing the tacit knowledge sellers hold; leaving straightforward declarative work alone; and cold calling still reaching executives such as CIOs, who are more likely to answer a phone call than an email.
  • Short closes the roundup by saying they are bullish on humans in the AI era.

The post follows a simple formula: one question, short quoted replies from operators named as a group, and a one-line position at the end. It is the clearest statement in the corpus of what Short expects automation to leave untouched.

This sits in tension with Short’s other two posts, which describe agents absorbing research, copywriting, and outreach. They frame the position as bullish on humans, not as a reversal: automation takes the work around the seller, while human contact remains at the point where a buyer commits.

Read original

Sources for this section

Start with their work

Enterprise sales means dozens of micro-pitches, not one

What does a long enterprise deal require from a seller?

Read more

This post maps the buying committee and the materials each step needs.

Brendan Short argues that enterprise sales involves dozens of micro-pitches over months, each building on the last.

  • Their example sequence moves from the VP of Sales to RevOps, then security, legal, frontline managers, and back to the VP of Sales, keeping the buying committee warm.
  • Each mini-pitch needs its own materials: a 1:1 landing page, a deck for RevOps, a security and trust document, a legal redline, a designed thank-you note, and a deal room.
  • The post introduces Clarify's Artifacts launch, which builds decks and documents inside the CRM using deal context such as past calls, emails, and notes.
  • They contrast this with most AI for sales tools, which chase more volume, and frame Artifacts as a way to create fewer, higher-quality touchpoints that help buyers process.
  • The post discloses that Clarify is a sponsor of The Signal.

For brands planning a campaign

For a talk or workshop on enterprise sales enablement and AI adoption, this post offers a ready-made framework: map each buying-committee step to a specific asset, then show how CRM-grounded AI can generate those assets. It also discloses a sponsored relationship, which buyers should distinguish from an independent recommendation.

XBOW's BDR team becomes agent managers

What happens to sales development roles when AI agents handle research and outreach?

Read more

This post offers a concrete model from a company that built its own revenue system.

Brendan Short describes XBOW moving its BDR team under RevOps and renaming the role agent managers.

  • In this model, BDRs are the humans in the loop: they QA agent outputs, handle tasks that still need a human touch, and have career paths into Sales, RevOps, CS, and GTM Engineering.
  • Short notes that XBOW is the former GitHub Copilot team, started three years earlier, and already a $1B+ company.
  • It runs its revenue org like a product org, with sprints, in-house tools, and work built with Claude Code.
  • Its internal system sends each seller the most urgent opportunities every morning with one action to take, runs every call through eight agents for coaching, and turns dense security findings into language a seller can take to a CISO.
  • They call it an extreme example and argue that the BDR job changes when the system does so much work: less research and copywriting, more management of the workflows that handle those tasks.

For brands planning a campaign

Use this as a case study for an AI-native revenue operations discussion: it shows how AI adoption changes role definitions, not just tooling. It can anchor a workshop segment on what sales development becomes when agents handle research and outreach.

What isn't changing in the AI-era sales playbook

Which sales fundamentals do experienced GTM operators expect to matter as AI changes the playbook?

Read more

This post collects their answers.

Brendan Short asks GTM operators to name one thing in their role that is NOT changing in the AI era, then lists their answers: cold calling; looking people in the eye and buying from a salesperson when they are cutting a big check; human-to-human interactions becoming more valuable; hiring more SDRs, not fewer; AEs having more accounts and higher quotas because jobs to be done are split; human connection; sales reps knowing the market better than anyone else; sellers holding the pulse of their industry while RevOps operationalizes that tacit knowledge; declarative work remaining declarative; and cold calling working with all personas, including a CIO who is more likely to pick up a phone call than reply to an email. They close by saying they are bullish on humans in the AI era.

For brands planning a campaign

This post offers a counterweight for an AI adoption workshop: pair automation and agent workflows with the human activities buyers and sellers still value. It can prompt discussion about which parts of a sales role to protect, automate, or redefine.

Sources for this section

Topics and approach

Posts cited for each topic
How the argument is packaged3
Enterprise deals run on a series of micro-pitches1
AI sales tooling should reduce touchpoints, not multiply them1
AI-native revenue teams change what a BDR does1
The parts of selling Short expects to stay human1

Enterprise deals run on a series of micro-pitches

Short argues that enterprise sales is not a single pitch but dozens of smaller ones spread over months, each aimed at a different person in the buying committee: the VP of Sales, then RevOps, then security, then legal, then frontline managers, then back to the VP with whatever the round turned up.

Read more

Each pitch needs material built on the latest deal context — a one-to-one landing page for the VP, a RevOps deck, a security and trust document, a legal redline, a designed thank-you note to the committee, and a deal room to hold the process together.

Names a specific artifact for each stage instead of describing the buying committee in the abstract.

For brands planning a campaign

This gives a workshop or talk a concrete spine: the stakeholder sequence and the asset for each step. A brand selling enablement, deal rooms, or proposal software can build a session around this list rather than general talk about longer sales cycles.

Examples: Source 1

AI sales tooling should reduce touchpoints, not multiply them

In the same post, Short separates most \"AI for sales\" products, which Short describes as pushing more sequences, more calls, and more top-of-funnel activity, from Clarify's Artifacts release, which builds decks and documents inside the CRM from call, email, and note context.

Read more

Short's example: a RevOps deck that reflects what RevOps actually asked on the last call rather than a template with a new logo. Short's stated position is fewer, higher-quality touchpoints aimed at helping buyers process, and Short points out that Clarify sponsors the newsletter.

The post is written around a paid partnership, so the endorsement and the vendor's launch message appear together; a reader should weigh it as sponsored commentary.

For brands planning a campaign

Useful for positioning a product against volume-based AI outreach, and as a model of sponsored commentary with the relationship stated up front. A brand considering a similar piece should expect a named product, a mechanism-level explanation, and disclosure in the same text.

Examples: Source 1

AI-native revenue teams change what a BDR does

Short walks through XBOW moving its BDR team under RevOps and describing the role as \"agent managers.\" In Short's account, those BDRs are the humans in the loop: they quality-check what the systems generate, handle steps that still need a person, and have career paths into sales, RevOps, customer success, and GTM engineering.

Read more

Short notes the company is the former GitHub Copilot team, started three years ago, is valued at over $1B, and runs revenue like a product org with sprints and in-house tools.

  • Short describes internal systems that send each seller their most urgent opportunities every morning with one action, run every call through eight coaching agents, and translate dense security findings into language a seller can take to a CISO.
  • Short's conclusion: less research and copywriting, more managing the systems that do those things.

For brands planning a campaign

A concrete case for the thesis that sales roles are being redesigned around agents rather than removed. A brand selling to revenue or RevOps leaders can use it as a reference example in a session on how teams assign responsibility, grounding the argument in one named company's operating model rather than broad statistics.

Examples: Source 1

The parts of selling Short expects to stay human

Short asked GTM operators one question: in the AI era, what is one thing in your role that is not changing?

Read more

The answers: cold calling; buyers wanting to buy from a salesperson when they are signing a large check; human-to-human interaction becoming more valuable; hiring more SDRs, not fewer; account executives carrying more accounts and higher quotas once the jobs to be done are split up; sales reps being closest to the market; RevOps operationalizing what sellers know tacitly; straightforward declarative work being left alone; and cold calling still working with executives such as CIOs, who are more likely to pick up the phone than reply to an email.

One open question for a group of practitioners, short quoted answers, and a one-line closing position.

Set against the AI-driven change in Short's other posts, this frames the argument as bullish on humans rather than a reversal of the automation argument.

For brands planning a campaign

This is the counterweight in the corpus, useful for an audience wary of AI-driven change messaging: a brand can use it to argue that new tooling should remove work around the seller rather than replace the seller's contact with buyers.

Examples: Source 1

How the argument is packaged

Across the three posts, the pattern is a single thesis with named specifics: a bulleted list of artifacts or roles, one company or product as the worked example, and a closing line that states the position.

Read more

Two of the three posts are standalone arguments; one poses a question to a group of practitioners and publishes their replies as a roundup. The product post carries an explicit sponsorship note, and the company post points readers to a longer writeup off LinkedIn.

For brands planning a campaign

A brand planning a co-authored piece or sponsored slot should expect a specific argument with named artifacts, tools, and people, not general thought leadership. The newsletter or off-platform writeup holds the deeper material, so campaigns should extend beyond the social post.

Examples: Source 1 · Source 2 · Source 3

Sources for this section

Brands and businesses

Brendan Short's posts mention one commercial relationship: Clarify, which they identify as a sponsor of The Signal in a launch post about Clarify's Artifacts product.

Read more

They also feature XBOW's revenue-team setup and link to a deeper write-up hosted at TheSignal.club. The posts don't mention ownership, employment, client, affiliate, or investment relationships.

Clarify

Sponsor

Short announced Clarify's Artifacts launch and said Clarify sponsors The Signal, the outlet represented in the post.

Read more

They said they were grateful for the partnership and shared a signup link. The post explains that enterprise deals need separate assets for each stakeholder in a buying committee, which is what Artifacts builds.

Original disclosure

Clarify is a sponsor of The Signal. I'm grateful for their partnership, and stoked to watch them continue to ship products as they build out the autonomous CRM.

View example

XBOW

Mention

Short described how XBOW moved its BDR team under RevOps and reframed the role as "agent managers," including details of XBOW's internal GTM system and a link to a fuller write-up at TheSignal.club.

Read more

View example

Sources for this section

Topics and similar creators

Brendan Short writes about how enterprise deals are actually bought and what AI changes in revenue teams.

Read more

Start with the post on micro-pitches — their account of a deal moving from the VP of Sales to RevOps to security to legal to frontline managers, and the specific asset each stop needs — because it sets up the rest of their thinking.

  • From there, the post on XBOW moving its BDR team under RevOps shows how they treat roles rather than just tools, describing sales development as human review of what agents produce.
  • The roundup of GTM operators on what is not changing in selling is the counterweight: they collect practitioners' answers and close by saying they are bullish on humans in the AI era.
  • Their product commentary on Clarify's Artifacts runs with a stated sponsorship of The Signal, their newsletter, so the endorsement and the vendor's launch message arrive together.
  • Readers who want the deeper write-ups will find that several posts point off LinkedIn to a newsletter or a longer company writeup.
Enterprise sales Sales enablement AI in sales Revenue operations GTM engineering Sales development (BDR) Buying committee navigation Practitioner roundups Sponsored commentary B2B revenue leaders

Alex Jones

Both write about AI-native revenue organisations and treat the sales engine — executives, sellers, marketers, and RevOps — as the part of a company that has to be rebuilt around agents.

Read more

Both make the argument through a named product or company rather than general claims about AI.

Jones writes mainly about small and mid-sized businesses adopting AI, and frames Jones's own firm as the harness connecting their GTM systems. Short works from the enterprise deal side, breaking a long sales cycle into stakeholder-by-stakeholder pitches, and their product commentary is sponsored.

Read original · Original 2

Olivier Roth

Both treat the CRM as the place where sales process should be enforced rather than a dashboard reps ignore.

Read more

Roth argues for putting the relationship check inside the stage transition so it becomes unavoidable; Short argues each stakeholder pitch needs its own material and a deal room to hold the process together.

Roth's material is about relationship intelligence and warm introductions — who can reach or unblock an account — while Short's is about the sequence of pitches a deal passes through and the assets each one needs.

Read original · Original 2

Ray Kelly

Both are practitioners who argue from a concrete example that AI output needs a person in the loop who understands the domain.

Read more

Kelly frames reviewers as the ones who can spot what is wrong rather than what looks right; Short describes BDRs as the humans checking what agent systems generate.

Kelly writes about application security and AI-driven pentesting, where unreviewed output shows up as a breach; Short's subject is revenue work, where the cost of a bad touchpoint is a stalled deal.

Read original · Original 2

Sources for this section

Audience

The LinkedIn account had about 40,470 followers on 8 October 2026, a large practitioner following in the B2B sales and revenue-operations niche.

Read more

Posts focus on enterprise deal cycles, AI-native revenue teams and the changing BDR/XDR role, making the account a potential fit for a LinkedIn-based talk or workshop.

  • But the sample does not establish whether followers include enterprise sales leaders, RevOps buyers or the executive audience for a sales-enablement workshop.
  • Before a campaign targeting a specific buyer audience, request recent reach and engagement data for comparable topics (enterprise sales enablement, AI adoption in GTM, micro-pitches), along with any audience survey or platform demographic data covering job function, seniority and geography.

LinkedIn followers

40,470

LinkedIn profile of the account that published the reviewed posts · 2026-10-08

Publishing in the reviewed sample

3 posts in 4 days (28 September – 1 October 2026)

Publication dates of the three reviewed LinkedIn posts · 2026-10-08

Sources for this section

Partnership options

The posts describe one partnership: Clarify is named as a sponsor of The Signal, and Short says they are grateful for the partnership while Clarify builds out its product.

Read more

The example is an early-stage B2B software product in the sales and revenue-operations space, introduced through a short written endorsement rather than a display ad. Ask Short directly about available formats, deliverables, and pricing; terms would need to be negotiated individually.

Sponsored placement in The Signal (disclosed example)

Buyer requirement

Clarify is named as a sponsor of The Signal, and the post links to TheSignal.club for more detail. To assess a sponsorship, ask Short directly about placement, length, frequency, deliverables, scheduling, and cost.

Sources for this section

Campaign fit

A campaign to shortlist

Strong fit for a talk or workshop, with two limits to manage.

Read more

Brief

A B2B SaaS company selling enterprise sales enablement and AI adoption support wants a creator-led talk or workshop. The session should help revenue leaders apply micro-pitch thinking to enterprise deals and decide where AI belongs in GTM workflows.

Reasons

  • Short's 28 September post supplies a ready framework: enterprise deals run as dozens of micro-pitches across the buying committee, and each step needs its own asset — a 1:1 landing page for the VP of Sales, a RevOps deck, a security and trust document, a legal redline, a designed thank-you note, and a deal room. That maps directly to a session on enterprise sales enablement.
  • The 30 September post makes the AI adoption case: XBOW moved BDRs under RevOps and calls them agent managers who QA agent output and own workflows, with internal systems that surface urgent opportunities and coach calls. This is specific enough to anchor a segment on AI-native revenue operations without relying on generic AI claims.
  • The 1 October roundup supplies the human counterweight: cold calling, buyer trust, and seller market knowledge. A workshop can pair automation with the work that should stay human.

Limits

Audience composition is unverified. The account had about 40,470 followers as of 8 October 2026, but the posts provide no breakdown by job function, seniority, company size, industry, or geography. Ask for audience data or confirm the mix through registrations before booking.

The only documented commercial relationship is a sponsored placement in The Signal by Clarify. Treat it as a disclosure precedent, not proof they will endorse any vendor. Agree on independence, disclosure, and whether the product can be named.

Next step

Ask for a session outline that starts with the micro-pitch map, adds the XBOW agent-manager case, and closes with a buyer filter for where AI should and should not replace seller contact. Confirm any existing sponsor conflicts before booking.

When to choose a specialist

Poor fit.

Read more

Brief

An AI outbound vendor wants Short to front a performance-style campaign promising more sequences, more calls, and higher top-of-funnel volume, with success measured mainly by follower reach and paid post engagement.

Reasons

  • Short's 28 September post explicitly contrasts most AI for sales tools, which push more sequences, more calls, and more top-of-funnel, with a different approach: fewer, higher-quality touchpoints that help buyers process. Asking them to sell volume-first outreach puts the campaign at odds with their stated argument.
  • The posts show a sponsored placement in The Signal, disclosed inside the post. They do not specify a rate card, placement terms, or performance-ad offer. Ask Short to confirm whether they offer guaranteed reach or conversion-style creative before negotiating.
  • The only available audience metric is about 40,470 LinkedIn followers, observed 8 October 2026. The posts provide no engagement data, so ask for it before using the account to forecast performance.
  • The sponsor example, Clarify, is an early-stage B2B software product in the sales and revenue-operations space, introduced through a written endorsement. That does not establish that Short will run high-volume advertising for any AI sales tool.

Alternative

If the vendor wants to work with Short, the workable option is a disclosed, argument-led sponsorship or session on reducing buyer friction, not a reach-based performance campaign.

A worked campaign example
Angle

Run the workshop as a buying-committee walkthrough, not a product demo.

Brief

A B2B SaaS enablement brand books Short for a 45-minute workshop plus a written follow-up for revenue leaders.

Deliverables

A one-page micro-pitch map, a short worksheet for each committee stop, and a recording or written recap. The brand can add its own enablement product only after the framework is on the table, with disclosure if the session is sponsored.

Evidence and gaps

The three posts center on this angle. Before the event, confirm the audience mix, ask for any audience data beyond the follower count, and agree in writing how the Clarify sponsorship example is handled so the session does not look like an undisclosed vendor pitch. If the brand needs proven performance metrics, the posts do not provide them.

Structure

Open with the claim: enterprise sales is dozens of micro-pitches over months, each building on the last.

Walk through the committee sequence from the 28 September post: VP of Sales, RevOps, security, legal, frontline managers, back to the VP.

For each stop, name the asset: 1:1 landing page, RevOps deck, security and trust document, legal redline, designed thank-you note, deal room.

Then bring in the 30 September XBOW case: BDRs as agent managers, humans QAing agent output, sellers receiving urgent opportunities each morning with one action, calls reviewed by coaching agents, security findings translated for a CISO.

Close with the 1 October counterweight: cold calling, buyer trust at high contract values, and seller market knowledge. Give attendees a filter: automate research, asset assembly, and routing; protect the human contact that carries a large check.

Title

Worked campaign angle: the micro-pitch workshop

Sources for this section

Who else to consider

Alex Jones

Choose Alex Jones for a B2B SaaS campaign aimed at making an SMB or midmarket revenue team AI-native in practice: adopting Claude Cowork, using prepackaged SMB plugins, or building a GTM technology harness rather than walking an enterprise buying committee through a deal.

Read more

The posts show firsthand workshop observations, a claim that AI-native operation will become a requirement, and an explicit FastForward offer to train or set up Claude for SMBs. For a session demonstrating AI adoption and lower overhead, Jones is closer to the operational work than Short's deal-navigation framing.

The tradeoff is narrower enterprise-deal specificity: the posts do not show micro-pitch sequencing, buying-committee asset maps, or enterprise sales-enablement case work.

  • They center on FastForward's commercial harness and Claude SMB packages, so brands should distinguish workshop content from service promotion.
  • A sales-enablement brand seeking a tested enterprise revenue framework should ask Jones to substantiate it.

Examples: Source 1 · Source 2

Ray Kelly

Choose Ray Kelly when the need shifts from revenue operations to AI adoption in security and application development, especially review accountability for AI-generated work, AI-assisted pentesting, or grounding AI in environmental evidence to reduce wasted effort and false positives.

Read more

The posts discuss a legal filing with AI-generated fake citations, the need for domain-expert review before shipping AI output, and a research approach that fingerprints targets before testing. For a security-focused session or a workshop on AI governance, Kelly offers direct technical detail that Short's posts do not.

The tradeoff is a different buyer task.

  • Kelly's posts do not cover enterprise sales cycles, buying committees, pipeline enablement, or revenue operations, so Kelly is not a substitute for the micro-pitch workshop.
  • The posts also contain Microsoft research context and cybersecurity claims that a sales-enablement brand should validate with Kelly.

Examples: Source 1 · Source 2

Olivier Roth

Choose Olivier Roth when the campaign need turns on relationship intelligence and warm paths into accounts: mapping who can introduce the team, building that check into a stage transition, or connecting network data to CRM agents.

Read more

The posts describe a growth leader who enriched roughly 10,000 contacts with company details and used relationship paths to book meetings and revive stalled deals, plus a network-augmented CRM walkthrough with Clarify agents that surface warm paths and draft intro requests. For a workshop on multi-threading and go-to-network motions, Roth's material is closer to the pipeline problem than Short's micro-pitch assets.

The tradeoff is that Roth's posts center on CRM and relationship-data workflows, not the full sequence of buyer-facing assets across legal, security, and frontline management that defines Short's micro-pitch framework. Both posts also promote Clarify and The Swarm, so a brand already working with Short's Clarify sponsorship should manage overlap and disclosure.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Creator campaign brief: reusable template

Completed example: enterprise sales enablement workshop

Completed example: reject a volume-first performance campaign

Sources for this section

Research methodology

  • Brendan Short's three LinkedIn posts cover enterprise deals as a sequence of micro-pitches to a buying committee, an AI-heavy revenue team that moved its BDRs under RevOps, and a roundup of GTM operators on what is not changing in selling.
  • The posts do not show publication dates, so they cannot be placed in time and no development over time is claimed.
  • The posts do not provide earlier posts, a longer post archive, or audience detail beyond an observed LinkedIn follower count of about 40,470 on 8 October 2026; recurring ideas and any shift in Short's positions therefore rest on these three posts, and a wider corpus would be needed to confirm they hold across the whole body of work.

Brands they talk about