Tahnee Perry shares practical advice on using AI tools and connected work systems for B2B marketing, sales, and go-to-market operations, including pipeline analysis, content production, and workflow design.
Tahnee Perry is most useful for practical AI workflows in B2B marketing, sales, and go-to-market operations.
Best for
A B2B SaaS company seeking AI-assisted pipeline, outbound, or content operations workshops or advisory.
Not for
A direct-to-consumer wellness or consumer app sponsored post aimed at US consumers aged 18-34.
Key takeaways
AI underperforms when isolated from tools and systems teams already use.
Split AI work into stages, each with one bounded job.
A five-step agent method can recover qualified leads that disappear between systems.
Check first: Confirm whether they offer paid advisory or workshops, and request rates and terms.
Main ideas
AI underperforms because it runs in isolation from the tools a team already uses · Split AI work into stages, with one bounded job each · Build a verification step and have one model review another's work
Tahnee Perry writes about making AI useful in B2B marketing, sales, and go-to-market work.
They focus less on prompts in isolation than on workflows: connecting tools to business systems, assigning clear tasks, and getting outputs into places where teams can use them.
Their posts offer practical ideas for content production, pipeline planning, lead recovery, and choosing between AI tools.
Perry turns broad AI ambitions into workable processes.
In a lead-recovery framework, the sequence starts by manually tracing one buyer journey, then establishes a stable source of truth, gives agents bounded jobs, and checks their results against approved examples.
The value lies in the attention to verification and the handoff to people who can fix underlying sales and operations problems—not just in using agents.
The same systems perspective shapes their content-production process: call transcripts, search data, a calendar, and notes feed several content formats. Perry also explains why ambitious processes often fail: one prompt is asked to do too much, planning is skipped, or the output has nowhere useful to go (common pitfalls).
For pipeline planning, they describe a scoring model that weighs channels, recommends a focus, and translates it into actions and measures.
A separate ChatGPT-versus-Claude comparison suggests giving tools different jobs and having one review the other; its task-by-task preferences reflect marketers’ views, not a universal ranking.
Their work is most useful to readers exploring practical AI operations and the steps, checks, and business connections needed to make a process usable.
Tahnee Perry writes about putting AI to work inside B2B marketing and go-to-market operations.
Read more
The through-line in the posts is that most AI failures are integration failures rather than prompt failures.
AI has to connect to the systems a team already uses, break into staged jobs instead of one long prompt, undergo checks against approved examples, and serve a decision—which channel to fund, which leads to recover—rather than only produce drafted text.
Their priorities are focus and subtraction: pick one channel for 90 days, name the things to stop doing, and make sure the output lands somewhere a person actually looks.
AI underperforms because it runs in isolation from the tools a team already uses
Perry's central diagnosis is that teams get little from AI not because the models are weak but because AI has no access to the working context: what's in the CRM, what last week's numbers were, what a colleague put in a campaign plan.
Read more
The proposed fix is one step: connect the AI platform to the tools the team already uses.
Then manual exports and copy-paste stop being part of the job.
The same reasoning appears in the go-to-market failure list, where an output that doesn't land in a CRM, a document or an inbox someone checks is described as dying, regardless of how good it is.
A content production workflow where every call is transcribed automatically by Granola, then Claude pulls the transcript along with SEMrush data, the content calendar and notes, and produces a summary, a LinkedIn post, a newsletter hook, an SEO-optimized landing page and a deck update, with no manual copying between tools.
Split AI work into stages, with one bounded job each
Perry argues that a single prompt trying to research, write and format is fragile by design.
Read more
The fix is to break the work into stages, with a planning layer in front.
That layer decides which tools to use and what the workflow must produce, for whom and when—questions teams skip when they jump straight to prompting.
The pipeline-recovery method applies the same principle at the agent level: rather than one general agent, they describe several narrow ones, each with a defined task.
In this account, bounded jobs make agents dependable; vague instructions produce a different answer every time.
The three-agent architecture described for pipeline recovery: one agent pulls the daily list of qualified leads, one reconstructs each lead's journey across every system, and one drafts the recovery message for sales.
Build a verification step and have one model review another's work
A recurring quality-control theme: check AI output rather than trusting the first pass.
Read more
In the pipeline method, Perry describes adding a step that compares agent output against approved examples and reruns anything that fails, because agents are expected to be inconsistent initially.
The tool-selection post makes a related argument at the model level: give each AI tool a job, then ask one to review the other's output, because one tool may be better than another at a given task.
Perry attributes this approach to a named practitioner.
The ten-task preference list presented as what marketers say they prefer: ChatGPT for campaigns, offers and angles, and for social calendars and repurposing; Claude for blogs, newsletters and thought leadership, and for spreadsheets, SQL and lightweight code; both for positioning, customer interviews, competitive research and project planning.
Use AI to make the focus decision, not just write the copy
Perry pushes AI past drafting into allocation: which channel deserves the next 90 days.
Read more
The model described reads pipeline history, scores the channels still producing pipeline, picks one and builds a week-by-week plan.
It also names three things to stop doing so the team has capacity, plus three leading indicators to check weekly.
The position behind it: volume outbound is dead, and precision still works.
They report running the model against their own business, where the recommendation was to shut down two channels currently being paid for and rebuild referrals from scratch.
A Claude scoring model that reads the last 90 days of pipeline data, closed-won sources, reply rates and meeting volume; scores five channels from 1 to 5; and returns one channel, three sentences of reasoning, 30-day phases with three actions per week, three cuts and three weekly leading indicators.
A small team of agents can find pipeline leaks in days
The most detailed argument in these posts treats existing revenue as recoverable.
Read more
Waiting for a RevOps function to trace every broken sequence takes weeks; a small team of agents can investigate in a day.
Perry insists on first reconstructing one lost lead's every touchpoint by hand—across forms, automated emails, sales activity and chat logs—so the leak is visible before an agent is taught to find it.
They also call for fixing the source of truth first: a daily snapshot of qualified leads that never reached a meeting, rather than a live CRM report that changes under you and produces a different version of the past on every run.
The repair is cross-functional by design, with sales contacting affected prospects while RevOps corrects sequences, routing and ownership rules.
The results in the post come from a Zapier practitioner, not Perry's own engagement.
An account of a Codex agent recovering more than $100,000 in Zapier's pipeline. Perry credits the same method to Angela Ferrante at Zapier, where it dropped weekly pipeline leakage from the high six figures to the thousands.
A shift from picking tools to designing the system around them
Read together, the posts move from task-level tool advice toward workflow architecture.
Read more
The earlier argument splits jobs between ChatGPT and Claude, with a preference list for each task.
The later arguments treat tool choice as the easy part and locate failure in the absence of a planning layer, staged prompts, bounded agent jobs and a destination for the output.
The tension is worth noting: the tool-comparison post is comfortable with a both-tools answer for many tasks, while the workflow posts argue that deciding which tool to use is worthless if the surrounding process is undecided.
The same ten-task comparison that sends blogs and newsletters to Claude and campaigns to ChatGPT sits alongside a claim that competitive intelligence and outbound pipelines built in Claude break without a planning layer and a home for the output. Perry explored this in a session with Johan Abadie from SalesIntel.io.
This is the clearest example of Perry turning AI from a writing assistant into a pipeline decision tool.
Read more
It answers a practical question: how can an AI system recommend a focused channel plan instead of generic marketing advice?
Perry describes a prompt that asks Claude to read 90 days of pipeline data and score five channels — referrals, thought leadership and paid, account-based, events, and signal outreach — from 1 to 5.
It recommends one channel to focus on for 90 days, with a week-by-week plan of three actions per week, three things to stop doing, and three leading indicators to track weekly.
Running the prompt on Perry’s own business led it to recommend shutting down two paid channels and rebuilding referrals from scratch.
For brands planning a campaign
A B2B SaaS team tackling pipeline leakage or AI-assisted GTM could use this prompt structure in a workshop: load real pipeline data, score current channels, and compare the model’s recommendation with the team’s plan.
The post shows a practical division of labor between two major AI tools rather than treating one as universally better.
Read more
Newcomers can see how Perry approaches tool fit and quality control in everyday marketing work.
Perry presents Charlie Treadwell’s approach: give each AI tool a job, then ask one to review the other’s output. The post lists ten marketing tasks and the tools marketers say they prefer for each: campaigns and offers to ChatGPT; blogs, newsletters, and thought leadership to Claude; brand positioning, customer interviews, competitive research, and project planning to both; CSVs, Excel formulas, SQL, and lightweight code to Claude.
For brands planning a campaign
Useful for teams deciding where each AI tool fits in a GTM process and setting up a review step where one model checks another’s output before it reaches a CRM, doc, or inbox.
This post explains Perry’s core operating argument: connect AI to work systems instead of moving data by hand.
Read more
It shows why AI adoption stalls and what changes when those connections are live.
Perry describes a content production process: Granola transcribes every call; Claude pulls in the transcript, SEMrush data, a content calendar, and notes; then it creates a summary, a LinkedIn post, a newsletter hook, an SEO-optimized landing page, and a deck update.
Most teams cannot do this, the post says, because their AI runs in isolation, without access to the CRM, last week’s numbers, or a colleague’s input.
The fix is to connect the AI platform to the tools the team already uses.
Claude has native connectors for 400+ platforms, while ChatGPT offers similar access through its App library.
For brands planning a campaign
Use this as the basis for a content operations audit: map where call transcripts, SEO data, calendars, and briefs live, then identify manual transfers or copy-paste steps that could be removed by connecting the AI platform to those systems.
This is Perry’s most detailed example of AI and pipeline work, and the best entry point for teams dealing with leads disappearing between CRM, sales activity, and automation systems.
Read more
It lays out the method, team roles, and verification step.
Perry outlines a five-step method for finding and recovering qualified leads that disappear between systems: rebuild one buyer journey by hand; name a source of truth, such as a daily snapshot of qualified leads that never reached a meeting; build agents with bounded jobs — one pulls the daily list, one reconstructs the journey, one drafts the recovery message; verify against approved examples; and turn the diagnosis into a cross-functional fix.
A Codex agent recovered more than $100,000 in Zapier’s pipeline, the post says.
The same method helped Angela Ferrante at Zapier reduce weekly pipeline leakage from the high six figures to the thousands.
For brands planning a campaign
A B2B SaaS company focused on pipeline leakage could use this five-step method in a workshop or advisory engagement: rebuild one lost buyer journey, define a snapshot source of truth, assign bounded agent jobs, and check against approved examples before scaling to more leads.
This post diagnoses the problems behind Perry’s other process examples.
Read more
It helps readers understand why an AI process might impress in a demo but fail on a revenue team.
Perry names three failure modes in Claude GTM processes: a single long prompt that tries to research, write, and format is fragile by design; there is no planning layer to decide which tools to use, what the process must produce, for whom, and when; and the output has no home if it does not land in a CRM, a doc, or an inbox someone checks. On August 19, Perry covered these topics with Johan Abadie from SalesIntel.io, walking through competitive intelligence and outbound prospecting pipelines built in Claude.
For brands planning a campaign
Use this as a readiness checklist before a GTM automation build: break long prompts into stages, define the planning layer and output destination, and ensure the final artifact reaches a system the sales or marketing team already uses.
Finding pipeline leaks with small teams of bounded AI agents
Tahnee Perry’s most detailed post here lays out a five-step method for recovering qualified leads that disappear between systems: rebuild one buyer journey by hand across the stack (forms, automated emails, sales activity and chat logs) to see the leak directly; name a stable source of truth, such as a daily snapshot of qualified leads that never reached a meeting, rather than a live CRM report that changes under you; give each agent one bounded job, with one pulling the daily list, one reconstructing the journey and one drafting a recovery message for sales; add a verification step that reruns anything failing an approved-example check; and turn the diagnosis into a cross-functional fix, with sales contacting affected prospects and RevOps repairing sequences, routing and ownership rules.
Read more
They credit Angela Ferrante at Zapier with dropping weekly pipeline leakage from the high six figures to the thousands using the same method.
Bounded agent jobs, a daily snapshot as the source of truth, and a verification pass against approved examples, after one buyer journey is rebuilt manually.
For brands planning a campaign
The strongest single piece for a pipeline-leakage brief. A workshop or advisory engagement could use the five steps as its working agenda, though the supporting results come from a named practitioner story rather than Tahnee Perry’s own engagement data.
Scoring and choosing pipeline channels with Claude
Tahnee Perry describes building Claude a scoring model for a client pipeline.
Read more
The model reads the last 90 days of pipeline data, closed-won sources, reply rates and meeting volume, and falls back to three questions if nothing is connected.
It scores five channels still filling pipeline in 2026 on a 1-5 scale: referrals, thought leadership plus paid, account-based, events and signal outreach.
It then picks one channel to focus on for 90 days, with reasoning in three sentences; lays out 30-day phases with three actions per week and named artifacts; and lists three things to stop doing plus three leading indicators to track weekly.
The post says the model advised shutting down two channels they were paying for and rebuilding referrals from scratch.
A staged prompt that moves from inputs to channel score to a single pick, a 30-day plan and explicit cuts.
For brands planning a campaign
Directly usable in a workshop on channel focus and AI-assisted planning, with the cuts-plus-leading-indicators structure giving a brand concrete outputs to test. The prompt is available through a comment-to-receive link but is not included in the post; ask for it to reproduce the model.
Connecting AI platforms to the tools a team already uses
Tahnee Perry describes going from five tabs to one window for content production: Granola transcribes every call automatically, then Claude pulls the transcript along with SEMrush data, the content calendar and notes, and produces a summary, a LinkedIn post, a newsletter hook, an SEO-optimized landing page and a deck update, with no manual exports or copy-paste.
Read more
They say most teams cannot do this because their AI runs in isolation, unaware of CRM contents, last week’s numbers or a colleague’s campaign requirements. The fix is to connect the AI platform to existing work tools, using native connectors from Claude or an app library from ChatGPT.
Connect the AI platform to the tools the team already uses so data moves without manual steps.
Names specific tools, including Granola and SEMrush, helping a brand judge how directly the setup would transfer to its own stack.
For brands planning a campaign
Useful evidence for a content-operations engagement. A brand can test the claim that connectivity, not prompting, is the bottleneck; ask to see the connected setup working, not just a description.
Splitting work between ChatGPT and Claude, then cross-reviewing output
Tahnee Perry recommends giving each AI tool a job and then asking one to review the other’s output, an approach attributed to Charlie Treadwell, because sometimes one tool is simply better than the other.
Read more
The post carries a ten-item preference list from marketers: ChatGPT for campaigns, offers and angles and for social calendars and repurposing; Claude for blogs, newsletters and thought leadership and for CSVs, Excel formulas, SQL and lightweight code; both for brand positioning and messaging, customer interviews and CRM notes, competitive research and battlecards, project planning and requirements, and visual generation.
Assign one tool per job and add a cross-review step between the two models.
For brands planning a campaign
Gives a brand a ready way to frame tool selection in an AI-workflow engagement and shows how Tahnee Perry draws on named practitioners’ experience, not only first-person claims. The list reflects what marketers say they prefer; test it against your own needs rather than treating it as a benchmark.
Tahnee Perry names three failure modes for Claude workflows in go-to-market work.
Read more
First, one long prompt trying to research, write and format is fragile by design and should be broken into stages.
Second, teams lack a planning layer, jumping to prompting before deciding which tools to use and what the workflow must produce, for whom and when.
Third, output has no home, so it dies unless it lands in a CRM, a document or an inbox someone actually checks.
The post promotes a session with Johan Abadie from SalesIntel.io covering competitive intelligence and outbound prospecting pipelines built in Claude.
Staged prompts, an explicit planning layer and a defined destination for every output.
For brands planning a campaign
A compact diagnostic a brand can apply to its own automations before a workshop; the three failure modes map cleanly onto workshop exercises. The post promotes a commercial event, not a published account of workflow results, so ask for evidence from the session.
The posts name several products and companies as part of Tahnee Perry's working toolkit and case studies.
Read more
Anthropic's Claude and OpenAI's ChatGPT and Codex recur as tools they build with and write about. Granola and Semrush appear as inputs to the content pipeline they describe, Zapier features as a case-study subject, SalesIntel.io as a webinar co-presenter, and the AI at Work newsletter as a destination for fuller breakdowns.
Anthropic (Claude)
Mention
Claude is the tool Perry writes about most: a pipeline-scoring prompt built for a client (a prompt that reads 90 days of pipeline data and picks one channel to focus on for 90 days), a side-by-side comparison of ChatGPT and Claude for marketing and GTM tasks, Claude as the connector pulling transcripts, SEMrush data, and calendar notes into content production, and three reasons Claude GTM workflows break ahead of a webinar.
SEMrush data is one of the inputs Claude pulls when producing a summary, a LinkedIn post, a newsletter hook, an SEO-optimized landing page, and a deck update.
The post tells the story of an agent method applied to Zapier's pipeline, attributed to Angela Ferrante at Zapier, and says Perry learned the steps directly from Ferrante.
Read more
Ask Perry to clarify any commercial relationship with Zapier.
Perry co-presented a webinar on August 19 with Johan Abadie from SalesIntel.io, covering competitive intelligence and outbound prospecting pipelines built in Claude.
Perry directs readers to the AI at Work newsletter for full breakdowns of the ChatGPT-versus-Claude comparison and the five-tabs-to-one-window content pipeline.
Tahnee Perry's posts read as a working notebook for connecting AI tools to the systems a B2B team already uses: its CRM, content calendar, call transcripts and pipeline history.
Read more
Start with the five-step pipeline-recovery method, the most concrete method in their posts, then read the channel-scoring model and two posts on workflow design for the reasoning behind it: staged prompts, bounded agent jobs, a verification pass and a defined destination for every output.
The through-line is focus and subtraction: pick one channel, name what to stop doing, and check that the result lands somewhere a person actually looks.
Tool choice matters less to Perry than the surrounding process, so treat the ChatGPT-versus-Claude preference list as a starting point for testing, not a settled verdict.
Works the same territory: go-to-market systems that combine outbound, content, paid ads and revenue operations.
Read more
Posts teach by naming the layers in order and explaining how each changes the result. The argument that copy sits on top of four structural layers, and that teams fix the wrong layer when a campaign stalls, echoes Perry's diagnosis of AI workflows failing for structural rather than prompt-related reasons.
Vacca writes about agency campaign work, naming clients and performance numbers, and treats outbound as one part of a five-part GTM stack built largely in third-party tools.
Perry focuses on the inside of a team's workflow: connecting its existing CRM, calendar and transcripts, then splitting work into bounded agent jobs.
The only quantified result in their posts is credited to a practitioner at another company, so ask for results from Perry's own engagements.
Writes about revenue operations and what AI changes in it, using a single idea to reframe a familiar practice.
Read more
For example, they use Jevons Paradox to argue that cheaper RevOps work expands demand for it rather than shrinking it, and describe win-loss analysis shifting from a quarterly retrospective to a live feedback loop. This echoes Perry's account of agents finding pipeline leakage in a day instead of weeks.
Sundar's posts recount other companies' operations, such as a sales development organisation rebuilt from 30–40 people to 400-plus, largely at the level of process and handoffs. Perry's posts offer methods readers can run — prompts, agent roles and verification steps — with tool-level detail such as connector setup and staged prompts.
Covers AI adoption in B2B marketing from an advisory angle, testing new models as they land and telling readers which changes are worth acting on.
Read more
They also write about how buyers now form opinions before reaching a website. The shared concern is practical: what a marketing team should do differently this week, rather than what a model release announcement says.
Morris concentrates on model releases and measurement under zero-click search, where attribution shows only the last interaction in a longer journey.
Perry focuses on workflow and pipeline: which channel to fund for 90 days, how to find qualified leads that disappear between systems, and where AI output should land.
Morris's posts draw on client sessions and downloadable analysis; Perry's offer reusable method steps.
Tahnee Perry suits a B2B SaaS campaign about pipeline leakage and AI-assisted go-to-market work when the buyer wants practitioner-facing material rather than broad consumer reach.
Read more
Five LinkedIn posts dated June 10 – September 16, 2026, cover a pipeline-leakage investigation method, a Claude scoring model for channel choice, a content-production process built on transcripts and connectors, a comparison of ChatGPT and Claude by job type, and a diagnosis of why Claude GTM processes break.
The posts target people who run pipeline, outbound, and content operations.
The only measured audience figure provided is the LinkedIn profile follower count: 15,817 followers, observed October 10, 2026.
The posts include engagement prompts (“Comment PIPELINE,” “Repost so other marketers can steal the cheatsheet,” registration links), but do not report who replied, how many people replied, or their roles.
For buyers, the content signals an audience of B2B marketing, sales, and revenue-operations practitioners who own pipeline, outbound, and content production.
Its instructional, implementation-heavy material—a five-step agent method, three-agent architecture, and 30-day phased plan—suits a campaign aimed at people already working inside a CRM and marketing stack.
Posts reference named tools and platforms (Claude, ChatGPT, Zapier, Granola, SEMrush) and one named practitioner's results, consistent with an audience evaluating AI tooling and processes.
The account has a mid-sized LinkedIn following, but follower count alone does not establish sponsored-post delivery or performance on a particular topic or format.
Selected examples include the August 19, 2026 post describing Angela Ferrante's pipeline-leakage work at Zapier and the June 10, 2026 post describing the five-tabs-to-one-window content process.
They illustrate the practitioner content offered to the audience.
Before committing, ask for recent performance data on comparable topics, depth, and formats—the pipeline-leakage and AI-related posts are the closest comparison points—and for audience survey results or another documented source covering job function, seniority, geography, and company size.
LinkedIn followers
15,817
Tahnee Perry LinkedIn profile follower count · 2026-10-10
Tahnee Perry's five posts offer practical guidance on AI-assisted marketing and go-to-market workflows, but document no partnership, sponsorship, or paid-collaboration formats.
Read more
They mention no media kit, rate card, audience demographic package, or sponsorship policy.
The posts direct readers to a newsletter called AI at Work and, in one case, a registration link for an August 19 session with Johan Abadie of SalesIntel.io.
Neither is presented as a commercial offer or buyer inquiry route.
Perry's posts do not say whether they accept sponsorships; ask directly about availability and terms before planning a paid engagement.
They do show the kind of work a brand could ask about: step-by-step breakdowns of pipeline recovery, AI prompt and workflow design, and tool-connection setups.
Perry also cites practitioners by name when describing methods, including Angela Ferrante's pipeline leakage work at Zapier and Charlie Treadwell's practice of having one AI tool review another's output.
A worked example or live walkthrough may suit a campaign better than a packaged sponsorship slot, though the posts do not document either as a product.
Brief A: A B2B SaaS company wants to reduce pipeline leakage and build AI-assisted go-to-market workflows, and is considering a workshop or advisory engagement.
Read more
This is a strong fit.
The posts target people who run pipeline, outbound, and content operations, with implementation-heavy material rather than general commentary: the five-step Agent Investigation Method for recovering qualified leads that disappear between systems; a Claude scoring model for choosing one pipeline channel for 90 days; three failure modes in Claude GTM workflows; a content-production workflow built on call transcripts and tool connectors; and a practical division of labor between ChatGPT and Claude followed by cross-review.
That material maps directly onto the brief.
A workshop or advisory engagement is a more plausible commercial shape than a sponsored awareness placement: the strongest fit is instructional method, not packaged sponsorship inventory.
Tahnee Perry's posts do not mention a media kit, rate card, sponsor policy, or disclosed sponsorship example.
Ask whether they offer paid advisory or workshop engagements and request current rates and terms before scoping.
The posts report one measured figure, a LinkedIn follower count of 15,817 observed October 10, 2026, but no demographic breakdown or per-post performance data.
The $100,000+ pipeline-recovery result and the drop from high six figures to thousands are attributed to Angela Ferrante at Zapier, not to Perry's own client engagements.
The full prompt, framework, and five verification questions sit behind comment or link calls to action and are not included.
The fit is clear enough for a scoping conversation; ask for recent comparable results before proceeding.
When to choose a specialist
Brief B: A direct-to-consumer wellness or consumer app brand wants a paid sponsored-post package aimed at US consumers aged 18–34 on Instagram or TikTok, with demographic reach guarantees, a rate card, and examples of similar consumer sponsorships.
Read more
This is a poor fit based on Tahnee Perry's posts.
All five posts are B2B LinkedIn material about pipeline leakage, AI-assisted GTM workflows, content operations, and tool selection.
They show no consumer lifestyle content, short-form video, visual product campaigns, or consumer audience work.
The posts provide no location, age, gender, employer, job function, seniority, or company-size breakdown, and no delivery benchmark for any post.
The only measured audience figure is a LinkedIn follower count of 15,817, which does not establish whether the audience includes US consumers aged 18–34 or how a sponsored post would perform.
Tahnee Perry's posts mention no media kit, rate card, sponsorship policy, or disclosed sponsorship example.
Before treating this as a viable paid placement, ask them for platform demographic exports, recent per-post performance on comparable topics and formats, examples of prior consumer campaigns, and their commercial policy.
Without that information, the brief should not proceed.
A worked campaign example
Worked campaign angle for Brief A: a Pipeline Leakage Recovery Workshop plus AI GTM Workflow Diagnostic, run as an advisory engagement.
Objective: help the B2B SaaS revenue team find where qualified leads are disappearing and leave with a working AI-assisted process, not a generic slide deck.
Audience: revenue operations, sales operations, marketing operations, and sales leaders who own pipeline routing, sequences, and automation.
Proposed format: a two-session workshop with a written playbook and a next-step brief.
This is an inferred advisory shape; Tahnee Perry's posts document no sponsorship or workshop package, so confirm availability, terms, and rates directly before contracting.
Pre-work: the client pulls 90 days of pipeline data, closed-won sources, reply rates, and meeting volume, and selects one qualified lead that never reached a meeting.
The client also gathers that lead's touchpoints across forms, automated emails, sales activity, and chat logs so the leak can be seen directly.
Session one: use the three failure modes as a diagnostic — one long prompt doing everything, no planning layer, and no home for the output.
Then rebuild one buyer journey by hand, name a stable source of truth such as a daily snapshot of qualified leads that never reached a meeting, and run or adapt the channel scoring model to pick one channel focus for 90 days with cuts and weekly leading indicators.
Session two: design three bounded agent jobs — one pulls the daily list, one reconstructs the journey across systems, and one drafts the recovery message for sales.
Add a verification step that reruns outputs against approved examples, and map the cross-functional fix: sales contacts affected prospects while RevOps repairs sequences, routing, and ownership rules.
If the client also wants content production in scope, extend the workflow with transcript capture, connector-based data pulls, and a cross-review step where one AI tool checks another's output.
Deliverables: one reconstructed buyer journey, a defined source of truth, three bounded agent job specs, an approved-example verification checklist, a cross-functional fix list, a 90-day channel focus plan, and a written playbook.
Success measures: the team can repeat the leak investigation without the workshop lead, each agent job produces a bounded and reviewable output, failed outputs are rerun, and the final recovery action lands in a CRM, document, or inbox someone checks.
Buyer note: the Zapier result belongs to Angela Ferrante, not to Perry's own engagement record; the full prompt and framework behind the posts are not included.
Ask for recent comparable results and confirm current rates, availability, and workshop terms directly.
Choose Mohan Sundar over Tahnee Perry when the need is to rebuild the revenue operations and sales development system rather than recover a specific leak with an AI-assisted workflow.
Read more
The posts show RevOps leadership framing: a Jevons Paradox argument that AI expands RevOps demand because continuous win-loss analysis becomes possible, and a Rippling case covering SDR-to-AE handoff design, AI checks on Gong recordings against rules of engagement, inbound-to-outbound rep training, and quota and promotion measures. For a B2B SaaS company whose pipeline leakage comes from poor routing, ownership, handoff rules, or outbound org design, that operating-model perspective is more directly useful than their prompt-level workflow examples.
The tradeoff is a weaker fit for a hands-on workshop on AI-assisted GTM workflows.
Tahnee Perry's posts stop at case summaries and management decisions; they do not describe the prompt structure, agent job design, source-of-truth setup, verification checklist, or cross-functional repair sequence.
A buyer who wants the team to leave with a repeatable AI pipeline-leak process should ask for that method or plan to source it elsewhere.
Choose Alex Vacca when the need is to buy or benchmark a full outbound and GTM engine rather than learn a creator's internal method.
Read more
The posts set out a five-part GTM model and a five-layer campaign diagnostic: AI search visibility, signal-based outbound, founder and employee content, paid ads, and RevOps on top; then sending foundation, market mapping, signal stacking, channel coordination, and reply and revenue measures.
They name concrete tools such as Clay, Prospeo.io, Instantly.ai, Apify, lemlist, RB2B, HubSpot, and Salesforce, and quote results including 6x reply lifts from signal-stacked campaigns and AirOps pipeline.
For a B2B SaaS company that wants an operating partner to build and run the outbound system, or a diagnostic that reads campaign failure from the bottom layer up, this is a closer fit than a workshop on internal AI workflows.
The tradeoff is commercial shape and control.
The posts read as agency service marketing: the buyer gets a team to build and run the engine, not a reusable in-house advisory method.
Tahnee Perry is a better fit for a workshop or advisory engagement; Alex Vacca is a stronger choice for outsourced execution, but a weaker one if the goal is to leave the client team with bounded agent jobs and a repeatable process.
The posts also sell the agency's own results, so buyers should separate pitch claims from auditable implementation evidence.
Choose Rupert Morris when the need is AI tool adoption and marketing discovery rather than pipeline leak recovery.
Read more
The posts test two major model releases and recommend handing one repetitive team process to AI with real templates and data, and analyze the zero-click era, where more than 68% of Google searches ended without a click and attribution no longer follows a neat linear path. For a B2B SaaS company whose problem is how buyers find and judge the brand before they reach the site, or how to start using new models inside existing client work, this offers a complementary marketing-leadership view.
The tradeoff is narrower operational depth for the stated need.
Tahnee Perry's posts do not show an agent architecture, a buyer-journey reconstruction, a source-of-truth method, or a cross-functional repair sequence.
They are more useful for shaping the discovery and adoption case than for fixing pipeline leakage inside CRM, routing, and sequence systems.
A buyer choosing Rupert Morris for this need should ask for an operations specialist to be involved or confirm that a broader marketing advisory scope will suffice.
Tahnee Perry's five LinkedIn posts cover an AI-assisted pipeline scoring model, task-by-task preferences between ChatGPT and Claude, a content production process built on call transcripts and tool connectors, a five-step method for recovering qualified leads that disappear between systems, and three failure modes in Claude go-to-market processes.
No publication dates are given for the posts; one refers to a joint session held on August 19 with Johan Abadie from SalesIntel.io.
The posts do not include the prompts, frameworks, the five verification questions, or newsletter material placed behind comment or link calls to action, so those items are gaps rather than supporting detail.
The pipeline figures cited in the posts — more than $100,000 recovered and a drop from high six figures to the thousands — are attributed to Angela Ferrante at Zapier, not to Perry's own engagements.
The LinkedIn follower count shown on October 10, 2026 was 15,817; Perry's posts here do not provide a demographic breakdown, per-post performance data, media kit, rate card, or sponsorship terms.
Comparisons with similar creators rest on posts from those creators, not on a complete account of Perry's body of work.
