Josh Wetzel writes about how sales and go-to-market teams can use AI to redesign revenue operations, with a focus on clean data, clear ownership, and workflows that produce measurable results.
Josh Wetzel writes about how sales and go-to-market teams can put AI to work in revenue operations.
Their central point is that adding AI tools is not the same as improving results: teams need clean data, clear ownership, and processes that already work.
Their examples range from meeting preparation and pipeline reporting to lead scoring and call coaching.
Follow their work for practical accounts of what operators are building, what it takes to make those systems useful, and where AI projects can fail.
Wetzel connects broad arguments about AI and go-to-market strategy to specific operating choices.
They put data and process before applications, distinguish personal AI use from team-wide workflows, and ask whether a system improves a real business outcome.
Their operator-dinner posts make that test tangible: one describes a lead-scoring system updated against actual revenue, while another contrasts reported production savings with a large enterprise investment that had no quantifiable board-level return.
They also note that agents can automate a working playbook but cannot repair a broken one.
These concrete examples and cautions help readers separate operational progress from AI hype.
Josh Wetzel writes about how revenue teams should rebuild around AI, returning to one argument: adoption is not the problem; operating-model maturity is.
Read more
Across five LinkedIn posts drawn from Pavilion operator dinners, a SaaStr AI CRO Summit, a meetup at Lovable's San Francisco offices, and a Pavilion AI Pulse survey of 244 GTM operators, they return to the same sequence—clean data first, then process, then systems, then application—and the same warning: agentic tools amplify a playbook rather than repair a broken one. The posts combine survey figures with specific numbers reported from operator rooms, and Wetzel says directly that building this kind of operating model is the work they want next.
AI adoption is broad, but operating-model maturity isn't
The recurring claim: nearly everyone now uses AI, but hardly anyone has reorganized around it.
Read more
Josh Wetzel cites the Pavilion AI Pulse Survey of 244 GTM operators: 95% use AI regularly, the average self-rated maturity score is 6 out of 10, 46% name missing strategy or ownership as the top blocker, and 38% point to data quality and integration issues.
Only 30% have moved beyond individual productivity to team-level systems.
In one post, they pair these findings with ICONIQ's State of GTM report, which puts AI-enabled sales teams at a 17-point revenue growth advantage and AI-native companies converting trials and proofs of concept at roughly twice the rate of others.
The conclusion: the gap between leaders and laggards is measurable, widening and structural—not a matter of tool access.
The split is between Phase 1, personal AI fluency, which is described as largely solved, and Phase 2, agentic workflows that move pipeline, win rates and net revenue retention, where the real advantage is built. Most teams, in this account, are running Phase 1 plays and expecting Phase 2 results.
Josh Wetzel's refrain: AI does not fix a data problem; it exposes one.
Read more
The sequence is Data, then Process, then Systems, then Application, with most teams starting at the last step.
Operators seeing durable returns do the unglamorous work first: clean the data layer, map how the revenue motion actually runs, and decide what to optimize before automating anything.
As a later post puts it, AI scales what is already there; if it's broken, speed only moves you faster in the wrong direction.
A day across three stops: the SaaStr AI CRO Summit, an AI-in-GTM meetup hosted with Pavilion at Lovable's San Francisco offices, and a smaller Pavilion operator dinner.
Every vendor demo at the summit assumed clean data and a CRM that served as the source of truth; in Josh Wetzel's account, most teams have neither.
Agents handle the internal work; humans own the customer
This is the operating model in one line.
Read more
Josh Wetzel says the go-to-market playbook they spent 20+ years building is obsolete.
The replacement moves meeting prep, enrichment, pipeline reporting and workflow automation into the background, so field staff arrive at conversations with full context and without CRM hygiene work.
The supporting figures: 88% of GTM teams already use AI for call intelligence and meeting prep, and 57% have workflow automation running.
What's missing is someone willing to build the operating model around existing infrastructure.
They also note AI being used to define candidate assessment rubrics and reduce screening bias.
Josh Wetzel describes building with Claude Code and Cowork and comparing notes with operators running live experiments in real organizations. They say directly that implementing this operating model is the job they want next, and ask anyone building this kind of GTM org to get in touch.
The framing shifts from a market gap to a personal next step: the post that identifies the missing owner for AI strategy also positions Josh Wetzel to fill that role.
Agentic tools amplify a playbook that already works — they don't fix a broken one
The sharpest gut check: agentic tools automate a playbook that already works, while AI feeding AI without real data underneath compounds errors rather than results.
Read more
Josh Wetzel singles out deliberately unspectacular builds, judged by maintained accuracy and low operating overhead rather than demo value.
The highest-return build in one operator room was a lead scoring system that reconciles marketing and sales signals weekly, refines itself monthly against actual revenue and takes about an hour a week to run—with no dashboard and no demo day. Two other examples: an agent that recommends content experiments and a second agent built to run the one selected; and call coaching agents whose feedback goes to the manager rather than the rep, because coached feedback read as development while direct feedback read as surveillance.
Much of the published material synthesizes discussions in small rooms rather than analyst reports.
Read more
Josh Wetzel hosts and co-hosts Pavilion operator dinners, then recaps them as numbered takeaways, attributed figures, and thanks to named hosts, sponsors and attendees. The recurring contrast: vendor pitches assume a trustworthy CRM, while operators building in production describe real tradeoffs and disagreements.
The posts mention a Pavilion SF operator dinner co-hosted with Leela Gill, a chapter dinner sponsored by Dust, and a Pavilion and Lovable meet-and-greet. One recap closes by asking readers what their own team has actually shipped with agentic AI and inviting replies in the comments.
Put a number on AI: tokens against headcount, weeks against weeks
Josh Wetzel's posts offer specific production figures, not just directional claims, and credit their sources.
Read more
They consistently compare an AI result with the cost or cycle time it replaces, presenting failures in the same frame as successes.
Contract processing fell from four weeks to one week, while alert correlation replaced three full-time employees at $18K in tokens against $450K in headcount.
On the failure side, one large enterprise reported $50M invested and 200 use cases tested with no quantifiable ROI for its board; the post attributes this to infrastructure limits rather than AI limits.
One outbound approach described in the room reached a 76% response rate and 41% executive meetings against a 1.5% baseline.
These room figures are reported as heard, not as verified benchmarks; the enterprise is not named.
Two questions still open: governance and build versus buy
Josh Wetzel treats governance and build-versus-buy as live questions, not settled positions.
Read more
On governance, distributed access is fine during experimentation, but once teams start rebuilding the CRM in their spare time, an operating model becomes necessary.
Tiered approaches already running in some teams are flagged as worth understanding.
On build versus buy, the stated rule is to build when a capability is core to differentiation and the team has the technical depth; otherwise, stop burning tokens on reinvention.
Both questions are still sharpening in real time, consistent with the view that the field remains in an experimentation phase.
One operator room concluded that the winners aren't those with the biggest budgets, but those who know what problem they're solving before picking a tool or approach.
Start here for the argument that runs through everything else Josh Wetzel writes.
Read more
It answers the question newcomers usually ask first: if nearly every go-to-market team now uses AI, why are results still so uneven?
A recap of one day across three stops: a SaaStr AI CRO Summit, an AI-in-GTM meetup at the Lovable SF offices, and a smaller Pavilion operator dinner.
The central claim: vendor demos assume clean data and a trustworthy CRM, and most companies have neither.
Josh Wetzel cites a Pavilion AI Pulse survey of 244 GTM operators: 95% use AI regularly, the average self-rated maturity score is 6 out of 10, 46% name missing strategy or ownership as the top blocker, and 38% point to data quality and integration.
The post argues for tackling Data, then Process, then Systems, then Application, though most teams start at the last step.
For brands planning a campaign
Useful as the sequencing argument in a hiring brief. It makes the case for putting data-layer cleanup and a named owner ahead of tool purchases in the first weeks, with concrete benchmarks to frame a 30-60-90 plan rather than generic AI enthusiasm.
This is the shortest statement of the distinction Wetzel keeps returning to: using AI personally versus rebuilding how a revenue team operates.
Read more
Read it to understand what they count as real progress.
The post separates adoption from operating maturity.
It reports the same 95% regular-use and 6-out-of-10 maturity figures, adds that only 30% of teams have moved beyond individual productivity into team-level systems, and cites ICONIQ's State of GTM report for a 17-point revenue growth advantage for AI-enabled sales teams and roughly double the trial and proof-of-concept conversion rate at AI-native companies.
It divides the work into Phase 1, personal AI fluency, largely solved, and Phase 2, agentic workflows that move pipeline, win rates, and net revenue retention.
For brands planning a campaign
Gives leaders a ready-made milestone structure. A brief can ask specifically for Phase 2 evidence: two or three workflows systematized across a team, rather than used ad hoc by whoever figured them out first.
Read this for the operating model in one line: agents handle the internal work, humans own the customer.
Read more
It is the clearest account of which jobs Wetzel would automate first.
The post argues that winning teams are redesigning the operating model rather than adding headcount to solve pipeline problems.
It names the internal work that should run in the background: meeting prep, enrichment, pipeline reporting, and automation, so field staff arrive at conversations with context and without CRM hygiene work.
Supporting figures: 88% of GTM teams already use AI for call intelligence and meeting prep, 57% have automation running, and the number one blocker is that 46% of teams have no clear owner or strategy.
Wetzel also notes building with Claude Code and Cowork and comparing notes with other operators.
For brands planning a campaign
Directly relevant to a hiring brief about redesigning a revenue operating model. The named workflows offer a shortlist of candidates for the first 90 days, while the ownership statistic supports making one person accountable before scaling anything.
Read it to see the standard Wetzel applies when judging an AI project, including the unglamorous ones.
Notes from a Pavilion SF chapter operator dinner where every attendee had built something with AI.
The highest-return build in the room was a lead scoring system that reconciles marketing and sales signals weekly, refines monthly against actual revenue, runs in about an hour a week, and has no dashboard.
Call coaching agents worked better when feedback went to the manager rather than the rep: coaching reads as development, while direct feedback reads as surveillance.
One builder had an agent recommend content experiments and a second agent run the chosen one.
The sharpest point: agentic tools automate a playbook that already works; they do not fix a broken one.
AI feeding AI without real data underneath compounds errors.
For brands planning a campaign
A practical screen for first workflows. It favours quiet, compounding systems with a weekly rhythm over demo-day projects, and calls for data-backed triggers rather than generic personalization.
This post gives the most specific side-by-side numbers on working and failing deployments.
Read more
Read it for the contrast between in-production savings and a very large write-off.
A recap of a Pavilion SF operator dinner co-hosted with Leela Gill, focused on AI return on investment rather than hype.
Reported production results: contract processing cut from four weeks to one week, and alert correlation replacing three full-time employees at $18,000 in tokens against $450,000 in headcount.
On outbound, one approach in the room reportedly reached a 76% response rate and 41% executive meetings against a 1.5% baseline.
On the failure side, one large enterprise invested $50 million, tested 200 use cases, and showed the board no quantifiable ROI; the post attributes this to infrastructure limits rather than AI limits.
The post also raises build versus buy, with a rule that teams should build only when something is core to differentiation and they have the technical depth, and governance as the next hard problem once access is distributed.
For brands planning a campaign
Gives a build-versus-buy test and cost framing for a campaign brief: quantify token or infrastructure spend against the headcount or cycle time it replaces, and assign an owner for governance and access control as workflows spread.
AI adoption is broad, but operating-model maturity lags3
Data before automation3
Convening operators is the research method3
Humans own the customer; agents take the internal work2
Agentic AI amplifies a playbook that already works1
Open questions: governance and build versus buy1
AI adoption is broad, but operating-model maturity lags
Across several posts, Josh Wetzel returns to one finding from Pavilion's AI Pulse Survey of 244 GTM operators: roughly 95% use AI regularly, self-rated maturity averages 6 out of 10, 46% say no clear strategy or owner is the main blocker, and 38% point to data quality and integration.
Read more
In one post, they pair that with ICONIQ's State of GTM report, which puts AI-enabled sales teams at a 17-point revenue growth advantage and AI-native companies converting trials and proofs of concept at nearly twice the rate of others.
The argument is consistent: the constraint is not access to tools, but how the revenue organization is set up around them.
In another post, they call the gap between leaders and laggards measurable and accelerating.
For brands planning a campaign
A brand hiring for a revenue-operating-model rebuild should expect Josh Wetzel to start with an ownership map and maturity baseline, not a tool rollout, and to judge progress by whether workflows move from individual use into team-level systems.
Josh Wetzel's most repeated point is that AI does not fix a data problem; it exposes one.
Read more
They lay out a sequence — Data, then Process, then Systems, then Application — and say most teams start at step four, buying and automating before the underlying data layer and GTM motions are sound.
They credit operators who see durable ROI with doing the unglamorous work first: cleaning data, mapping how the revenue motion actually runs, and deciding what to optimize before automating anything.
In a later post, they spell out the consequence: AI scales what is already there, so if it is broken, speed only moves you faster in the wrong direction.
The Data to Process to Systems to Application sequence serves as a diagnostic: it locates where a team sits and what needs repair before agent work begins.
For brands planning a campaign
Expect an engagement to start with data and motion mapping, not agent development. Specify the data audit and process map as deliverables before systems are built.
Agentic AI amplifies a playbook that already works
Josh Wetzel's sharpest gut check: agentic tools automate a playbook that already works; they do not fix a broken one.
Read more
AI feeding AI without real data underneath compounds errors, not results.
The builds they single out are deliberately unspectacular.
The highest-ROI example from one operator dinner was a lead scoring system that reconciles marketing and sales signals weekly, refines itself monthly against real revenue, and takes about an hour a week to run — no dashboard, no demo day, just quietly compounding accuracy.
They also describe agents that recommend content experiments, followed by a second agent that runs the selected experiment, and hyper-specific data-driven triggers rather than generic personalization.
Wetzel ranks builds by maintained accuracy and low operating overhead, not demo value—a useful filter for deciding which workflows deserve automation.
The call-coaching example departs from common practice: feedback goes to the manager rather than the rep, because direct feedback felt like surveillance while coached feedback felt like development.
For brands planning a campaign
For campaigns involving scoring, coaching, or outbound triggers, Wetzel offers a clear view on where feedback should land and what high ROI looks like: small, weekly, and sustained rather than shipped and abandoned.
Humans own the customer; agents take the internal work
In a post declaring the go-to-market playbook they spent 20+ years building obsolete, Josh Wetzel lays out the redesigned model: agents handle internal work and humans own the customer.
Read more
Meeting prep, enrichment, pipeline reporting, and workflow automation run in the background, so field team members arrive at conversations with full context, no manual preparation, and no CRM hygiene tax on their week.
They cite survey figures showing the infrastructure already exists — 88% of GTM teams using AI for call intelligence and meeting prep, 57% with workflow automation running — and say what is missing is someone willing to build the operating model around it.
They also note AI helping define candidate assessment rubrics and reduce screening bias.
Wetzel says directly that implementing this operating model is the work they want next, and describes building with Claude Code and Cowork and comparing notes with operators running live experiments.
For brands planning a campaign
This closely matches the stated hiring need: a leader to redesign the revenue operating model around agentic AI.
Wetzel is openly seeking that work, which helps on timing.
Be specific about ownership, data access, and which workflows come first.
Much of Wetzel's published material is event recap: co-hosting a Pavilion SF Operator Dinner, hosting chapter dinners, attending the SaaStr AI CRO Summit, and joining a Pavilion and Lovable meet-and-greet in the same day.
Read more
The posts synthesize conversations in small rooms through named takeaways, attributed quotes and numbers, and explicit thanks to hosts, sponsors, and attendees.
A recurring contrast: vendor demos assume clean data and a CRM that is a source of truth, while operators building in production describe tradeoffs and disagreements.
Across three stops in one day, they report the same theme surfacing.
Wetzel's posts use peer operators who have shipped something as the basis for numbered takeaways, rather than relying on vendor or analyst claims.
For brands planning a campaign
Wetzel appears to check recommendations against primary operator conversations rather than published case studies. Roundtables, dinners, and event-based content fit how they already work and produce material.
Wetzel's posts give specific figures, not just directional claims.
Read more
Examples include contract processing cut from four weeks to one week; alert correlation replacing three FTEs at $18K in tokens against $450K in headcount; an outbound rebuild described in one room as reaching a 76% response rate and 41% executive meetings against a 1.5% baseline; and an enterprise with $50M invested across 200 tested use cases and no quantifiable ROI for the board. Posts credit the sources of figures, including the Pavilion AI Pulse Survey, ICONIQ, named co-hosts, and named sponsors.
The $50M and 200-use-case enterprise failure is reported as something heard in a room, with no company named, so it reads as an anecdote rather than a verified benchmark.
For brands planning a campaign
Wetzel offers quotable, specific benchmarks for campaign copy. Confirm sourced figures before republishing and treat figures gathered in the room as anecdotal.
On governance, they argue that distributed access is fine during experimentation, but once teams start rebuilding the CRM in their spare time, an operating model is required.
They point to tiered approaches some teams are running as worth understanding.
On build versus buy, their stated rule is to build when the capability is core to differentiation and the team has the technical depth; otherwise, stop burning tokens on reinvention.
They frame both as questions sharpening in real time, consistent with their observation that the field is still in an experimentation phase.
For brands planning a campaign
Wetzel presents these topics as unsettled, so a brief can ask for a governance model as an exploratory deliverable rather than assume a ready-made framework.
The posts document Josh Wetzel's involvement with the Pavilion operator community and two brands connected to its San Francisco dinners: Dust, named as a sponsor, and Terret, credited as host.
Read more
They also show them at a Pavilion and Lovable meet-and-greet at Lovable's offices.
Pavilion
Disclosed partnership
Wetzel hosts and co-hosts Pavilion's San Francisco Operator Dinners and uses Pavilion's AI Pulse Survey (244 GTM operators, April 2026) to frame their posts on AI in go-to-market.
Read more
Ask whether they have a formal commercial relationship with Pavilion.
Original disclosure
Last night I had the pleasure of co-hosting the Pavilion SF Operator Dinner alongside Leela Gill
After the SaaStr AI CRO Summit, Wetzel attended a Pavilion and Lovable meet-and-greet at Lovable's San Francisco offices, described as a room of operators building revenue engines with AI.
Read more
Ask whether they have a commercial relationship with Lovable.
Josh Wetzel writes about how revenue teams should rebuild around AI, drawing on field notes from rooms full of operators rather than analyst reports.
Read more
Start with the operator dinner and meetup recaps, where they collect what people building in production reported, then move to the survey-based posts.
The recurring argument: adoption is near-universal, but operating-model maturity lags, and the constraint is ownership and data, not tools.
For the practical payoff, follow the data-before-automation thread and the Phase 1 versus Phase 2 distinction, then read the numbers from operator rooms: contract processing cut from four weeks to one week, alert correlation replacing three full-time hires at a small fraction of headcount cost, and an enterprise that spent $50M across 200 tested use cases with nothing to show its board.
To assess their less-settled positions on governance and build-versus-buy, ask how those decisions are developing.
Both argue that adding headcount to a shaky revenue system buys noise rather than growth.
Read more
Greg Spence makes the case that hiring more salespeople will not fix a broken sales model, and lays out an order of operations: go-to-market strategy, account management standards, enablement, forecasting governance, and CRM architecture all come before hiring. That first-person operating argument echoes Josh Wetzel's descriptions of putting data before automation and rebuilding the revenue operating model.
Greg Spence writes prescriptive frameworks drawn from a career spanning CPG manufacturing, retail, SaaS, digital media, industrial services, automotive, HVAC, and commercial signage.
The focus stays on sales infrastructure and cross-industry transfer.
Josh Wetzel's material centers on convening peer operators and on AI and agentic workflows, with production figures and survey data reported from the rooms where they were discussed.
Both treat senior operator gatherings as places where working answers take shape.
Read more
David Appel recaps a go-to-market leadership salon with 160-plus leaders and reaches conclusions similar to those Josh Wetzel reports from Pavilion dinners: buyers are compressing their decision process, the data layer and guardrails need fixing before scaling agents, and teams should train their people the way they train their agents. Both also observe that AI is lifting middling performers, not just top ones.
David Appel's most recent material ranges well beyond revenue teams into finance and investor territory, covering IPO conferences, systems of action, predictability, and performance-based pricing for CFO audiences, and settles the build-versus-buy question firmly on buying. Josh Wetzel stays closer to go-to-market execution, keeps build versus buy open, and frames the change as agents taking internal work while humans own the customer.
Both argue that AI should be built into the operating model rather than used ad hoc, and back that case with concrete operator numbers.
Read more
Shalin Jain describes reaching $20M in revenue with only four reps by building AI agents to mine support and success calls for expansion opportunities and collapsing forecasting and intelligence tools into one AI-native CRM. Josh Wetzel makes a similar case when describing quietly compounding lead scoring and workflow automation replacing manual effort.
Shalin Jain writes as a bootstrapped SaaS founder about rebuilding one company and its product, and speaks at conferences about what AI-native means for a business. Josh Wetzel writes as a revenue leader synthesizing what many operators are shipping, drawing on dinners, meetups, and survey data rather than a single product or company.
Josh Wetzel's LinkedIn profile reports about 9,995 followers as of 8 October 2026.
Read more
Five posts from 8 May to 14 August 2026 focus on GTM operating models, AI adoption survey results and recaps of invitation-only Pavilion operator dinners.
Selected examples include the 8 May dinner recap, with named participants, and the 14 August recap, which credits Dust as sponsor and lists attendees by name.
The subject matter points to an audience of sales, revenue operations and go-to-market practitioners, making the content a stronger fit for credibility-focused placements aimed at sales and RevOps decision-makers than for reaching non-specialist buyers.
The profile provides no follower demographics or post engagement counts.
Before committing, ask for recent post engagement numbers and audience survey data on job function, seniority and company size; platform demographic data covers geography, age and gender, but not employer or seniority.
LinkedIn followers
9995
LinkedIn profile record with this research · 2026-10-08
The five posts show Josh Wetzel hosting and convening Pavilion San Francisco operator dinners, not offering sponsorships or partnerships through their own channels.
Read more
They thank event sponsors—one post credits Dust as a dinner sponsor—and invite people who hold operator seats to direct-message them for an invitation to upcoming dinners.
This is an event-attendance route tied to a Pavilion chapter, not a media kit, rate card, sponsored-content offer, or partnership inquiry process.
The posts do not describe sponsored posts, newsletter placements, speaking fees, affiliate arrangements, or other bookable formats, and do not say whether they accept sponsorships.
Brands considering a paid partnership should ask directly about available formats, pricing, and availability.
A B2B software company selling revenue data infrastructure, CRM hygiene tooling, or workflow automation wants a practitioner voice for a co-created thought-leadership and event series aimed at sales, revenue operations, and go-to-market leaders at mid-market and enterprise software companies.
Read more
The brief calls for expert commentary, roundtable hosting, and follow-up analysis—not a scripted product demo.
This is a close match.
The subject matter is already Josh Wetzel’s beat: the gap between broad AI adoption and lagging operating-model maturity; the argument that AI exposes a data problem rather than fixing it; and the sequence of data, then process, then systems, then application.
A vendor in this space gets a spokesperson whose stated positions support the product category without needing to be written for them.
The posts also offer quotable, specific numbers for a campaign: contract processing cut from four weeks to one week; alert correlation replacing three full-time roles at $18,000 in tokens against $450,000 in headcount; a lead scoring system that runs about an hour a week; and an outbound rebuild reported at a 76% response rate and 41% executive meetings against a 1.5% baseline.
Each figure is attributed to a room or a survey, so re-check it before republication.
Format fit is unusually strong for event-led work.
Wetzel convenes the exact audience a revenue vendor wants in the room: Pavilion San Francisco operator dinners, chapter dinners, the SaaStr AI CRO Summit, and a Pavilion and Lovable meet-and-greet on the same day.
Their writing method—synthesizing small rooms into numbered takeaways—maps directly onto a sponsored dinner, moderated roundtable, or post-event analysis.
Hosting and writing up the room is closer to their existing work than a standard sponsored post.
Two points need confirmation before a decision.
Ask directly about format, pricing, and availability; the posts do not specify them.
The audience evidence is also limited: five posts point to practitioner readers, and Wetzel has roughly 9,995 LinkedIn followers, but the posts provide no engagement counts or job-title, seniority, or company-size data.
Ask for those figures before underwriting a campaign against a guaranteed number of qualified readers.
When to choose a specialist
A consumer-facing brand or a general-purpose AI assistant marketed to non-specialist buyers wants follower-count-led reach, a fixed impression target, and a scripted demonstration for a general audience.
Read more
The mismatch is audience, format, and available information.
Josh Wetzel’s posts target people already running revenue teams, covering survey findings, production deployments, and invitation-only operator dinners.
They offer no evidence of reach into general or consumer readerships, or job-function, seniority, company-size, geography, or engagement data.
There is also no documented sponsorship format, rate card, affiliate arrangement, or sponsored-content offer.
Ask directly about booking, rates, and audience data before planning a campaign that depends on them.
The content style compounds the problem.
The published work synthesizes rooms and surveys, attributing numbers to the Pavilion AI Pulse Survey, ICONIQ, named co-hosts, and named sponsors.
A campaign requiring a scripted product claim or generic personalization message would clash with Wetzel’s stated positions: agentic tools automate a playbook that already works rather than fixing a broken one; AI feeding AI without real data underneath compounds errors; and the strongest use cases are hyper-specific, data-driven triggers rather than generic personalization.
A campaign seeking unqualified product assertions would either be watered down or visibly conflict with their published arguments.
A hiring or advisory engagement that requires someone to build from scratch without ownership or access to the data layer is also a weak fit.
Across the posts, the consistent message is to start with data cleanup, motion mapping, and an accountable owner; the leading blocker is the 46% of teams with no clear strategy or owner.
An engagement that skips that sequence and asks for agents first asks for the exact pattern Wetzel warns against.
A worked campaign example
Campaign angle for the strong-fit campaign: a co-hosted operator session followed by a published analysis series.
Concept: “What the room actually shipped.”
A revenue-data or workflow vendor sponsors a small, invitation-only operator dinner for sales and RevOps leaders in one metro.
Josh Wetzel co-hosts and moderates; the outputs are a short post-event analysis and two follow-on pieces built from the discussion.
The angle mirrors a format that already works here: a recap of a Pavilion SF operator dinner that ranks builds by maintained accuracy and low operating overhead rather than demo value, and singles out the unglamorous winner—a lead scoring system that reconciles marketing and sales signals weekly and takes about an hour a week to run.
The first deliverable is the seat-level plan, not the content.
Frame the topic—the data-to-process-to-systems-to-application sequence—as a question rather than a pitch: which workflows have attendees moved from individual use into team-level systems, and what did they have to fix first?
The framing can draw on arguments already published: fewer than a third of teams have moved past individual productivity, the top blocker is the absence of a clear owner or strategy, and AI scales whatever is already there.
The second deliverable is the post-event analysis, structured as numbered takeaways in the style of the existing dinner recaps, with each claim attributed to a named attendee, a survey, or an unattributed room observation. The third is a short practice piece on one named workflow, using the build-versus-buy test Wetzel already states: build when the capability is core to differentiation and the team has technical depth; otherwise, stop burning tokens on reinvention.
Sequencing and measurement: hold the dinner first, publish the analysis within two weeks while the material is fresh, then publish the workflow piece as the lead-in to the next session.
Measure named attendees who take a follow-up meeting, shares inside attendee companies, and how often the framing language appears in prospect conversations—not raw impressions.
Before contracting, confirm whether a paid co-hosted format is available, its pricing and disclosure terms, and whether the engagement can include a data-quality or governance topic.
The posts raise governance as an open question, not a settled framework, so ask what position Wetzel can support rather than assuming one is ready-made.
For a hiring brief, the same information supports a 30-60-90 plan based on Wetzel’s stated sequence: weeks 1 to 4, name one accountable owner and audit the data layer and revenue motions; weeks 5 to 8, systematize two or three workflows that already work, such as meeting prep, enrichment, or pipeline reporting, rather than launching pilots; weeks 9 to 12, prove those workflows run at team level and set the governance model for access as they spread. Treat the survey figures as framing, not benchmarks for the reader’s own company.
Choose Greg Spence when the decision is to rebuild a broken sales operating system before scaling, and the buyer wants evidence of that work rather than AI-specific experience.
Read more
The two posts argue that adding headcount to a shaky model creates noise and payroll rather than predictable growth.
They lay out a sequence buyers can check against their own plans: clarify go-to-market strategy before writing job descriptions, set strategic account management standards, build sales enablement before ramp pressure, establish forecasting and KPI governance so pipeline means the same thing to everyone, and make CRM architecture usable.
They also describe building and scaling national sales organizations four times and taking C-Suite Network from zero to 11 business development representatives with playbooks, proprietary tools, compensation matched to strategy, AI-based data analysis, and stable leadership alignment.
A second post makes the cross-industry case, citing CPG, retail, SaaS, digital media, industrial services, automotive, HVAC, and commercial signage.
It says applying the same operating principles in enterprise commercial signage drove roughly a 30% increase in operational cadence and revenue 26% beyond the annual quota.
For a buyer focused on agentic AI, the tradeoff is clear: neither post is about agentic AI.
AI appears once, as AI-based data analysis within a wider sales-infrastructure rebuild.
Buyers working out who should own AI, how to map the data layer, or how to systematize agent-driven workflows will find the sequencing argument useful, but there’s no first-person account of doing that work.
The two posts take a general operating-principles approach and name no AI deployment.
Choose Greg Spence for a sales-system and enablement rebuild, not as a demonstrated agentic-AI operating-model choice.
Choose David Appel when the decision is to work with someone who convenes senior go-to-market leaders and frames problems in terms of data, governance, and business models rather than rep-level tactics.
Read more
The posts describe the 60th Go-to-Market Leadership Salon with more than 160 senior leaders and report the room's positions: the build-versus-buy debate is settled toward buying platforms and building only what is uniquely yours; AI is raising the floor so middle performers move up; and companies that scaled agents before fixing scattered and unqueryable data now have siloed agents fighting over conflicting information.
The same post lays out three practices for teams: know the buyer's decision process and attack where it is collapsing, train people the way agents are trained, and get data and governance right before scaling agents.
A second post, from a run of investment-bank conferences and the NYSE IPO Summit, extends the argument to company strategy: own a proprietary data moat, prioritize predictability over growth rate, and expect seat-based pricing to be displaced by outcome-based pricing as AI does the work.
The tradeoff is a lack of direct implementation detail.
These posts recap observations from salons and investor conferences, offering a useful frame for leadership audiences, but focus on what groups of leaders are saying rather than showing a single company's workflows being rebuilt, with named steps and results.
Buyers who need someone to work inside their own stack and systematize two or three workflows will get a strong strategic frame but less implementation detail.
Governance is raised as an open problem, not a settled method, so a campaign or engagement promising a ready-made governance model would go beyond what these posts support.
Ask David Appel for audience composition and commercial terms before making a buying decision that depends on them.
Choose Shalin Jain to learn from an operator who rebuilt their own software company's operating model with a small team, rather than someone who talks about the sector generally.
Read more
The posts are first-person: they describe building HappyFox to $20M in annual recurring revenue with only four reps, bootstrapped and profitable with under 100 people and no venture funding over 12-plus years, then rebuilding for an AI-native model.
The concrete examples are close to the work a buyer would fund: AI agents mining support and success calls for upsell opportunities so expansion discovery happens without manual effort; consolidating five forecasting and intelligence tools into one AI-native CRM to cut tool-switching fatigue; and an AI memory surfacing pricing objections that had been missed, described as a reason to stay a student of your own data.
The posts also frame the shift as an operating system reset rather than a product change, and name what a small team needs: frameworks, tools, and the questions to ask before starting a reset.
The tradeoff is scope and scale.
These posts describe one company's internal rebuild in customer support software, offering detail on a small, bootstrapped, product-led team but less on the enterprise go-to-market operating model a larger buyer may want to redesign.
The rep and tooling examples center on support and success signals and sales tooling consolidation, not outbound, pipeline governance, or a multi-layer revenue organization.
One of the two posts is primarily a conference announcement describing what will be shared at SaaStr London.
Ask Shalin Jain for audience data and commercial terms if those would affect your decision.
