Zach Wright

The test Wright proposes is to pull the top accounts, open the source behind each one, check its date, and ask whether it relates to the problem being sold.

• The count that holds up matters more than an accuracy claim.
• Wright's rule is that no account should enter a queue without a reason someone can open and check.

In one post, Wright suggests pulling the top 10 accounts, clicking through to the source, checking the date, and counting how many reasons still hold up. In another, Wright asks people to pull the next 20 accounts and write down why this company, why this week, and where that came from.

Read original · Original 2 · Original 3

With a chat window, the seller still reads the answer, checks CRM, pastes into Slack or a sequencer, and updates fields by hand.

• Agentic GTM connects to the systems sellers already use and runs the checklist end to end: research, score, route, and notify.
• People keep the decisions to pursue, pass, or escalate.

Wright says an SDR process should be dissected end to end, including inbound qualification, outbound targeting, and AE handoff. Anywhere a seller digs through CRM, rebuilds research, or rewrites cold emails and call notes by hand is a place to automate agentically, while humans still decide who to work, who to skip, and when to hand off.

Read original · Original 2

Coverage looks good, but timing is random, and early touches burn accounts that might have been ready later.

• The list worth working is smaller: companies in the TAM showing the specific problem the seller solves right now.
• Wright would rather measure opportunities caught while the problem was still open than how much of the TAM was touched.

Wright contrasts a full-market export with a smaller list built from public evidence, with the source and date attached, so sellers and agents work accounts that are ready instead of all of them.

Read original

At many companies, Wright says, the honest answer is nobody: every rep has a version, and every AI sales agent has whatever its prompt says.

• RevOps and Sales Ops people are quietly taking on this job, sometimes called GTM AI Ops.
• Much of the work is writing the standard down: what is the reason for this account, where did it come from, and how old can it be before it stops counting.

Wright frames the job as choosing agents, connecting them, deciding what they are allowed to send, and checking whether pipeline actually improved. The written standard covers the reason, its source, and its age limit.

Read original · Original 2

Managed outbound is presented as the turnkey completion: Syft AI finds companies with a dated reason to engage, acts on them every week, and alerts the team in Slack with the company, problem, reason, and thread when a prospect is ready to meet. Wright also says teams can inspect the process in Claude through MCP.

Wright describes a customer, an AI sales agent company, whose agents acted on every company Syft surfaced with a dated reason to engage and saw record pipeline in their first month. That is a single customer anecdote, not independent performance data.

Read original · Original 2

It gives a newcomer a concrete test rather than a product claim.

Wright asks vendors to explain why an account is ranked first, then open the evidence.

• A number on a list, such as an 87, does not tell a salesperson what to say; an AI sales agent given the same number has to guess at a reason to reach out.
• The proposed test is simple: pull the top 10 accounts, click through to the source, check the date, and ask whether it relates to the problem being sold.
• The count that holds up matters more than an accuracy claim.

For brands planning a campaign

A webinar can use this as a live audience exercise: ask SDR leaders to audit a handful of accounts and compare how many have a dated, relevant reason. That makes the case for evidence-backed account selection without relying on a slide about model accuracy.

Wright argues that many AI-for-sales pilots feel busy but produce thin outreach because teams bought a chat window, not a workflow.

• Chat-window AI makes research faster, but the seller still reads the answer, checks CRM, pastes into Slack or a sequencer, and updates fields by hand.
• Agentic GTM connects to the systems sellers already use and runs the checklist end to end: research, score, route, and notify.
• Humans keep the decisions to pursue, pass, or escalate.

For brands planning a campaign

This gives a webinar a clear teaching frame: map the SDR workflow step by step, then show where a chat tool stops and an agentic system continues. It also sets up a useful audience question: which parts of the process still end with a person copying text between tools?

Wright describes managed outbound as weekly action on companies Syft AI finds, not simply sending more messages.

• The team sees a Slack channel; when a prospect is ready to meet, the team is pinged with the company, the problem the prospect is working on, the dated reason for outreach, and the thread.
• The team can also inspect the process in Claude through MCP: which accounts are being worked, why each made the list, and what has been sent.
• Wright says most teams get agentic GTM 90% built and stop, and an unfinished workflow produces the same pipeline as no workflow.

For brands planning a campaign

A webinar can show the handoff moment rather than only the sourcing step: what context arrives, who acts, and how the team checks the work. This is useful for SDR leaders who need to see how an agentic system fits around human closers.

Wright argues that teams still export the whole market, enrich it, and sequence every logo as if all accounts are ready now.

• Coverage looks good, but timing is random, and early touches burn accounts that might have been ready later.
• The working list should be smaller: companies in the TAM showing the specific problem the seller solves right now.
• Wright says Syft AI finds that list from public evidence with the source and date attached, and recommends measuring opportunities caught while the problem was still open rather than how much of the TAM was touched.

For brands planning a campaign

This is a strong contrarian hook for a webinar aimed at SDR leaders: stop measuring coverage and start measuring timing. It can support a segment on how to define a working list and how to avoid spending accounts before they are ready.

Wright says that at most companies nobody owns the answer to what counts as a good reason to reach out.

• Every rep has a version, and every AI sales agent has whatever its prompt says.
• RevOps and Sales Ops people are quietly taking on the job, sometimes called GTM AI Ops: choosing agents, connecting them, deciding what they can send, and checking whether pipeline improved.
• Much of the work is writing the standard down: what is the reason for this account, where did it come from, and how old can it be before it stops counting?

For brands planning a campaign

This points to a webinar audience beyond SDR managers: RevOps and sales ops leaders who own the rules for AI-assisted outreach. A practical segment could ask teams to draft a one-page evidence standard covering reason, source, and age limit.

Wright asks how many of 50 new accounts in an AI sales agent's queue would come with a reason someone could open and check.

• The test is to pull the next 20 accounts and write down why this company, why this week, and where that came from.
• Wright says many answers will come back as a title match or a funding round from months ago.
• Every step from first touch to follow-up inherits that starting point, so starting from a guess means the agent writes a good email about a guess.

For brands planning a campaign

This can become a short self-assessment for webinar attendees: run the 20-account test before changing tools. It makes the problem concrete and gives SDR leaders a way to judge whether their current agent has enough context to support outreach.

Chat-window AI makes research faster, but the seller still reads the answer, checks CRM, pastes into Slack or a sequencer, and updates fields by hand.

• Agentic GTM connects to the systems sellers already use and runs the checklist end to end: research, score, route, and notify.
• Humans keep pursue, pass, and escalate.
• In an SDR context, Zach Wright says to dissect inbound qualification, outbound targeting, and AE handoff, then automate the places where sellers dig through CRM, rebuild research, or rewrite cold emails and call notes.

Process dissection: walk the SDR motion end to end, identify manual bottlenecks, and separate agent work from human decisions.

For brands planning a campaign

A webinar can open with this split and use a simple SDR workflow map to show where handoffs break. That gives sales-tech buyers a practical way to judge whether a tool finishes work or only speeds up a step.

Examples: Source 1 · Source 2 · Source 3

A number on a list does not tell a rep what to say, and an AI sales agent given only a score has to guess at a reason to reach out.

• The proposed test is concrete: pull the top 10 accounts, click through to the source, check the date, and ask whether it relates to the problem being sold.
• A related test asks people to pull the next 20 accounts and write down why this company, why this week, and where that came from.
• Zach Wright's rule is that no account enters a queue without a reason someone can open and check.

Afternoon audit: sample accounts, open each source, check its date, and count how many reasons hold up.

For brands planning a campaign

The webinar can run a live account audit or give attendees a short checklist they can apply to their own pipeline. This turns the session into a working exercise rather than a product pitch.

Examples: Source 1 · Source 2 · Source 3

Coverage looks good, but timing is random, and early touches burn accounts that might have been ready later.

• The list worth working is smaller: companies in the TAM showing the specific problem the company solves right now.
• The measurement should shift from how much of the TAM was touched to how many opportunities were caught while the problem was still open.

For brands planning a campaign

A webinar segment can contrast market coverage with account timing. It gives SDR leaders a way to discuss list quality and weekly focus without relying on follower counts or volume metrics.

Examples: Source 1

Managed outbound is presented as the turnkey completion: Syft AI finds companies with a dated reason to engage, acts on them every week, and alerts the team in Slack with the company, problem, reason, and thread when a prospect is ready to meet.

• Zach Wright also says teams can see the process in Claude through MCP.
• One customer anecdote describes record pipeline in the first month after its AI sales agents acted on every company Syft surfaced.

The record-pipeline claim comes from a single customer example in Zach Wright's post and is not supported by independent performance data in the supplied material.

For brands planning a campaign

The webinar can include a build-versus-run segment and ask where SDR teams stall between pilot and weekly operation. The customer anecdote should be labeled as one company's reported result, not independent proof.

Examples: Source 1 · Source 2

At many companies the honest answer is nobody: every rep has a version, and every AI sales agent has whatever its prompt says.

• RevOps and Sales Ops people are quietly picking up this job, sometimes called GTM AI Ops.
• The work is largely writing the standard down: what is the reason for this account, where did it come from, and how old can it be before it stops counting.
• A related post frames managing up as protecting sellers from bureaucracy and removing manual bottlenecks.

For brands planning a campaign

A webinar aimed at SDR leaders can include a governance checklist covering ownership, evidence source, and freshness rules. That gives the audience a concrete takeaway for controlling agent behavior before scaling outreach.

Examples: Source 1 · Source 2

Examples include auditing the top 10 accounts, checking the next 20 accounts in a queue, and asking how much of an AE's week goes to research.

• Some posts are event promotion, such as the RevGenius Revolt 2026 Demo Day session on context for AI agents and workflows.
• Others use a customer review as a short proof point.
• The style is compact and operational rather than abstract.

The supplied material contains short LinkedIn posts and no full webinar recording or long-form talk transcript, so Zach Wright's depth in a live presentation format is not demonstrated here.

For brands planning a campaign

A thought-leadership webinar should be built as a working session with an audit, a checklist, and time for hard questions.

• A broad AI keynote would not match the format shown in the posts.
• The brief should also decide how product mentions and event promotion are handled.

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

The posts describe AI-assisted B2B prospecting and managed outbound but do not state a job title or ownership stake.

View example

2026 Demo Day, a RevOps event, to show how Syft AI finds companies with evidence of why now and pipes that into a stack. This is a speaking appearance, not a disclosed sponsorship.

View example

This is a speaking appearance, not a disclosed sponsorship.

View example

Arvind Seshan frames the shift from a Salesforce Sales Cloud product and keynote perspective, with enterprise CRM context and named products such as Hunter and Momentum. Zach Wright stays closer to account-level evidence tests and managed outbound at Syft AI.

Read original · Original 2

Both warn against automating work without deciding what should change.

David Brock writes for sales leadership and performance, using workshops and questions such as what to stop and whether teams are building judgment or replacing it. Zach Wright focuses more narrowly on account selection, dated evidence, and GTM workflow ownership.

Read original · Original 2

David Turewicz describes consulting and agency workflows built around Claude, Prospeo, and sequencers. Zach Wright's posts center on Syft AI's account evidence and managed outbound offer.

Read original · Original 2

The supplied posts present a Sales Cloud keynote and the Hunter outbound sales agent in first-person terms, covering a system that understands customer context, takes action alongside sellers, and puts Salesforce skills inside Claude. That suits a webinar for SDR leaders who need to understand how agentic outbound fits a larger CRM and sales-platform roadmap, especially where the sponsor sells into Salesforce-centric teams.

The tradeoff is distance from the SDR's weekly working detail.

• The posts are keynote and product-launch material; they do not show the account-level audit exercises, evidence standards, or SDR process teardown found in Zach Wright's posts.
• A sponsor that wants attendees to leave with a repeatable queue-audit worksheet would need to add that material.
• The posts also make the Salesforce connection explicit, so a sponsor competing with Salesforce or Sales Cloud should treat the session as a conflict review rather than a neutral thought-leadership booking.

Examples: Source 1 · Source 2

The supplied posts argue that saving seller time has not improved win rates or cycle times, that automating research and call prep can remove the work where judgment develops, and that teams should first ask what to stop. A workshop format around “Sh*t we have to stop” and measuring judgment rather than activity would fit an audience of sales leaders and RevOps people who are skeptical of another agentic-AI pitch.

The tradeoff is less concrete agentic-AI implementation.

• The posts give a strong diagnostic and leadership argument, but they do not lay out how an AI sales agent is connected, governed, or checked against account evidence.
• A sponsor wanting a live demonstration of an agentic SDR workflow would need to supply that layer.
• The supplied material also includes a book recommendation rather than a full account of David Brock's own operating playbook, so the session should be sold on the stated themes, not on an unverified methodology.

Examples: Source 1 · Source 2

The supplied posts show a specific method: load context, run a second Claude session to check the first, verify selected points by hand, and use a lean Claude plus Prospeo stack to test a new ICP or offer in about two minutes before sending the list to a sequencer or CRM. That fits a webinar for RevOps and sales ops practitioners who want to see the working habits behind agentic execution, not just the case for it.

The tradeoff is a narrower strategic frame.

• The posts are about tooling and quality control in client work; they do not address SDR team management, account prioritization at the queue level, or the buyer-facing argument for agentic GTM in the way Zach Wright's posts do.
• A sponsor seeking a category-level thought-leadership keynote would get more tactical detail than executive narrative.
• The supplied material also does not show live webinar delivery or audience composition, so those remain checks before booking.

Examples: Source 1 · Source 2