Alex Jones

Product companies are efficient at making what they sell, they argue, while sellers are rewarded for activity itself.

• Calls to accounts that will never buy, sequences to contacts the CRM got wrong, and record updates nobody acts on all pass as work.
• The replacement framing is “efficient activity with the least amount of waste possible.”
• Jones puts the responsibility on sales leaders, who now have widely available data, research, and automation, and says they should fund the backend systems that give sellers an edge.
• The prescription is blunt: drop bloated go-to-market subscriptions, buy Clay and Claude, connect the rest of the tools, and engineer the systems rather than manage the pile.

In one post, Jones asks leaders to name one thing their reps do every week that they would cut tomorrow if they were honest about it. They call that waste a silent cost that never shows up as a line item.

Jones says they repeated “activity drives results” at kickoffs and quarterly reviews for most of their career.

• They still believe in the ethos, but now argue that the slogan celebrates waste, especially after AI made it cheap to generate activity at scale.
• Their own mantra has changed.

Read original · Original 2

GTM engineering builds capabilities that did not exist before, such as routing a lead through three enrichment providers, scoring it against an ideal customer profile in real time, and automatically delivering it to a rep with full context.

• Jones says most companies stretch RevOps into engineering work: a Salesforce administrator who built one complex workflow is asked to architect the whole lead-routing system, while an operations manager who knows Excel becomes the de facto data engineer.
• The result is that innovation happens in quarters instead of weeks.
• Both functions matter, they say, and neither replaces the other.
• Poor data quality pushed through AI tools just produces bad routing decisions and flawed forecasts faster, making ownership of data standards more important, not less.

Jones recommends roughly two to three RevOps people for every GTM engineer. They describe the factory as needing more people to run it than to build new machines, while crediting GTM engineers with prototyping in days and shipping dozens of automations in six months.

Read original · Original 2 · Original 3

Small businesses, in their view, have an advantage because large organizations are too big to move as fast as AI now allows.

• The biggest constraint they name is fear: the technology is easier to use than people assume and does more than they expect.
• Jones positions their firm as “the harness for your GTM tech,” connecting AI systems and building next-generation infrastructure to speed up sales in what they call the agentic era.
• They argue that a company’s sales engine—sellers, marketers, and operations—cannot be allowed to stall.

Jones writes about attending the first Claude SMB Trainer Workshop, sponsored by Anthropic, with Matt Batterson.

• They describe prepackaged Claude plugins for small businesses as turning tasks that took days into tasks that take minutes.
• They say future workshops on the Claude small-business package will be free.

Read original · Original 2 · Original 3

Their case rests less on row counts than on what a single system makes possible: acting on first-party and third-party data together, including CRM records, call scripts, tech stack, and intent signals.

• Before Clay’s Audiences feature, tables were capped at 50,000 rows, so a million-record CRM had to be split across twenty or more tables and stitched back together by hand—undercutting the point of the tool.
• Jones also argues that Clay is useful precisely when CRM data is imperfect, because it draws on material the CRM never held.
• Clean CRM data, they add, would produce even better results.

Jones’s example is loss reasons.

• Clay reads call transcripts and finds the real reason behind each sales call.
• Teams cannot read every transcript themselves, they point out, so data that never reached the CRM can still be recovered and used.

Read original · Original 2 · Original 3

They say this is the kind of system their firm builds, that teams commonly stop halfway, and that the upfront work is worthwhile.

Jones uses the seven steps as a checklist readers can compare against their own process, and identifies enrichment as the step that turns a name and an email into something a rep can act on.

Read original · Original 2

They concluded that few companies could copy it because the work and skill required are hard.

• The elements they single out are running the revenue function like a product team, getting the data model right first, and being willing to pivot the motion and the stack afterwards.
• Jones frames the broader point as “GTM Alpha”: every revenue team needs its own competitive edge, that edge changes over time, and a leader’s job is to keep the playbook, systems, and training from going stale.
• They note that most companies and leaders do not want to face that reality, and that most CEOs would not let their revenue team pivot at all.

Jones describes XBOW spending the first six months building a standard tech stack, then pivoting to a product-development motion and cutting the stack in half in the process.

• Niroshan Rajadurai, Justin Miller, and Bruno Chester Leardine built the system described in the source material.
• Jones offered to send their own analysis document to anyone who asked.

Read original

In cybersecurity, that means event tactics, staying friendly with competitors and adjacent vendors, and promoting partners publicly.

• They argue that helping others when you can produces returns, and that the best part of the cybersecurity world is its sense of community.
• The commercial version is marketplace co-sell: Jones’s posts promote investing in co-sell infrastructure and training, streamlining procurement through private offers, and making it easier for customers to spend committed cloud budget on security products.

Jones’s event advice includes where the best buyers gather during the CISO Summit, which restaurant is where deals get done, playing blackjack with customers as bonding time, and a morning workout as a low-key way to be around executives.

• They also warn that late nights in Vegas rarely improve careers.
• On the marketplace side, they cite an AWS Marketplace CRO Fellowship in New York and a continuous threat exposure management session with NetSPI’s own CISOs.

Read original · Original 2 · Original 3 · Original 4 · Original 5

Alex Jones argues that RevOps and GTM engineering are different jobs.

• RevOps keeps current systems running: monitoring dashboards, cleaning data and training teams on process.
• GTM engineering builds new capabilities, such as routing a lead through several enrichment providers, scoring it against an ideal customer profile in real time and delivering it to a rep with full context.
• Most companies stretch RevOps people into engineering work, slowing innovation from weeks to quarters: the Salesforce administrator who built one workflow is asked to architect the whole lead-routing system.
• Jones says successful teams run roughly two to three RevOps people for every GTM engineer.
• They also warn that poor data quality is amplified by AI tools, making clear ownership of data standards more important, not less.

For brands planning a campaign

For a brief on redesigning revenue operations, this post lays out the argument and staffing ratio for a talk or advisory session, not just a generic overview of automation.

Jones compares B2B selling to a manufacturing line where 97 percent of material went unused.

• Product companies tend to be efficient at making what they sell, while sellers are rewarded for activity itself, such as more calls and another round on the phone.
• Jones says the long-standing mantra, 'activity drives results,' celebrated that waste.
• They now frame the goal as the most activity possible with the least wasted effort.
• The practical recommendation: sales leaders should fund GTM engineering so sellers get good data, research and automation.
• Jones names Clay and Claude specifically, and urges companies to cut bloated subscriptions and start engineering their systems.

For brands planning a campaign

A useful opening argument for an advisory session on cutting wasted selling effort: it pairs a memorable diagnosis with concrete tool choices for a leadership team to debate.

Jones breaks inbound qualification into seven stages: connecting every lead source so submissions land in one place in real time; enriching each record from a single email address while keeping forms short; turning that enrichment into seniority, company size, tech stack and buying signals; scoring the lead against ideal-customer criteria; routing it to the right rep with an alert; generating personalized follow-up before the rep logs in; and sending the lead to the CRM to trigger the right sequence.

• Most teams build only half of this, Jones notes, and the upfront work pays off.
• Their post says this is the kind of system the firm builds with Clay.

For brands planning a campaign

A ready-made anatomy of an automated inbound pipeline for a session host to discuss step by step with a revenue team as a concrete deliverable, not just a concept.

Writing about a public breakdown of XBOW's revenue system, Jones says the company’s level of detail was surprising, then concludes few competitors could copy its approach because the work and skills required are hard to replicate.

• Jones highlights how XBOW ran revenue like a product team, spent the first six months building a standard tech stack, then pivoted to a product-development motion and cut the stack in half, starting by getting the data model right.
• They connect this to 'GTM Alpha,' the idea that every revenue team needs its own evolving competitive edge, and say they turned the article into a document with their own analysis.

For brands planning a campaign

A secondhand case study Jones already knows well, useful for a talk that needs a real example of a product-team approach to revenue and a company that cut its stack rather than added to it.

Jones predicts that within two years most employees, executives and owners will not be able to imagine work without AI, comparing it to losing a phone.

• They report attending the first Claude SMB Trainer Workshop sponsored by Anthropic with a colleague, and describe small businesses as having an advantage because large organizations are too big to move as fast as AI allows.
• Jones lists fear as the biggest constraint and describes prepackaged Claude plugins for small businesses that replace work taking days with work taking minutes.
• The firm acts as 'the harness for your GTM tech,' connecting AI systems and building infrastructure to accelerate sales.
• Jones also mentions plans for free workshops.

For brands planning a campaign

This shows Jones can speak credibly about AI-native GTM adoption and Anthropic's small-business tooling, and is willing to run training sessions as well as advisory engagements.

Jones gives eight practical tips for selling at BlackHat: where the best buyers gather; which restaurant is where deals get done; why midday drinking is acceptable only if the customer starts it; playing blackjack with customers as bonding time; morning workouts as a low-key way to be around executives; and why late nights in Vegas rarely improve careers. Jones notes it is the first BlackHat they have missed in eight years and says the best part of cybersecurity is its sense of community, urging readers to help competitors and adjacent vendors when they can.

For brands planning a campaign

Jones has a conference-savvy, community-minded presence in cybersecurity go-to-market, making them a fit to host or speak for an event audience rather than serve only as a systems advisor.

RevOps keeps current systems running by monitoring dashboards, cleaning data, and training teams on process changes.

• GTM engineering builds new capabilities, prototyping processes in days and shipping automations while RevOps ensures they follow governance standards.
• Jones recommends a 2:1 or 3:1 RevOps-to-GTM-Engineering ratio and warns that stretching RevOps into engineering work creates a bottleneck, slowing innovation from weeks to quarters.

Jones frames the split as 'manage the factory' versus 'build the machines.' Concrete examples include opportunity stage criteria and forecasting consistency for RevOps, and routing a lead through three enrichment providers and scoring it against ICP in real time for GTM engineering.

Jones notes that both functions are critical and neither can replace the other.

For brands planning a campaign

A B2B SaaS company redesigning its revenue operations can engage Alex Jones on org structure, role boundaries, build-versus-run responsibilities, and the ratio of operations to engineering headcount.

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

In the AI era, dials to accounts that will never buy, sequences to contacts the CRM got wrong three job changes ago, and hours spent updating records nobody acts on are waste that never shows up as a line item. The replacement is 'efficient activity with the least amount of waste possible,' with precision as the goal.

Jones asks leaders to identify one weekly rep activity they would cut tomorrow and points to backend GTM engineering functions as a way to give sellers a competitive edge.

For brands planning a campaign

Sales leaders can engage on rep productivity, pipeline quality, and reducing low-value work through data, research, and automation.

Examples: Source 1 · Source 2

They describe the current period as a generational change, compare dependence on AI to losing a cell phone, and say SMBs have an advantage over large organizations that are too big to move as fast as AI allows. They represented FastForward at the first-ever Claude SMB Trainer Workshop sponsored by Anthropic and plan free future workshops on getting started with the Claude SMB package.

Jones cites Claude SMB plugin packages and Cowork as prepackaged skills that turn days of work into minutes, and describes FastForward as 'the harness for your GTM tech.'

Jones names fear as the biggest constraint holding people back and says the technology is easier to use than many assume.

For brands planning a campaign

Brands evaluating AI adoption in sales and marketing can engage on AI-native GTM infrastructure, change management, and building revenue systems around AI rather than adding tools.

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

Unifying first-party and third-party data lets teams act on CRM, call scripts, tech stack, and intent signals in one place.

Jones gives a concrete example: Clay reads call transcripts to find real loss reasons absent from CRM records. They say the bigger deal is not row count but what a unified data layer allows.

Jones acknowledges that CRM data is often incomplete but argues Clay improves results even more when CRM data is clean.

For brands planning a campaign

Brands considering Clay adoption or GTM data consolidation can engage on data architecture, tool stack decisions, and Clay integration.

Examples: Source 1 · Source 2 · Source 3

They say most teams build only half the pipeline and that FastForward builds this system with Clay.

The seven steps form a concrete checklist brands can test against their current process.

Jones notes that the upfront work is real but '100% worth it.'

For brands planning a campaign

A B2B SaaS company redesigning lead handling can engage on the full pipeline from form to sequenced follow-up and where teams commonly stop short.

Examples: Source 1 · Source 2

They also share practical sales advice for cybersecurity events like BlackHat, including where to meet CISOs, how to use the Four Seasons lobby and the Veranda restaurant, and the value of the cybersecurity community. They say this is the first time in eight years they will not be at BlackHat.

Jones describes specific BlackHat tactics: attending the CISO Summit lobby on Tuesday, booking Veranda tables for prospects and customers, and wearing a company shirt at the Mandalay Bay gym in the morning.

Jones warns that late nights in Vegas rarely improve careers and can wreck the next day.

For brands planning a campaign

Cybersecurity vendors and marketplace teams can engage on co-sell infrastructure, marketplace procurement, and event-based sales plays.

Examples: Source 1 · Source 2 · Source 3

They note that XBOW ran GTM like a product team, spent the first six months building a standard tech stack, then pivoted to a product-development motion and cut the tech stack in half. Jones created a doc explaining and analyzing the system and offered it via DM.

Jones emphasizes getting the data model right before building and notes that most CEOs are not willing to let their revenue team pivot.

Jones was initially shocked that XBOW shared this publicly but concluded few companies are willing to do the work or have the skillset to replicate it.

For brands planning a campaign

Brands can engage Jones to analyze their own GTM system or learn from XBOW's approach to data models and tech stack reduction.

Examples: Source 1

They describe the experience without judgment and emphasize that creating luck means putting yourself out there. They also highlight cybersecurity partner relationships, calling out ENDUIR Cyber as a top and favorite partner.

Jones notes that SMBs signed long-term contracts after the first call, while massive enterprise organizations demanded free POCs—a contrast in how different buyer types engage.

For brands planning a campaign

Brands evaluating how Jones works with partners can look at their emphasis on trust, reciprocity, and long-term relationships.

Examples: Source 1 · Source 2

FastForward sells GTM engineering and sales/RevOps automation, including Clay integration and inbound lead qualification built on Clay.

View example

One says “how NetSPI continues to scale our relationship with AWS Marketplace” and “we’re doubling down on NetSPI’s Marketplace investment”; the other says “at NetSPI we have been helping organizations implement CTEM frameworks” and refers to “our CISO”.

• The posts read as earlier work but give no end date.
• Ask for dates before treating NetSPI as a current role.

View example

Jones also says FastForward helps clients with Clay integration. Ask whether any commercial terms exist between Jones or FastForward and Clay.

View example

They praise the Claude SMB plugin packages and say FastForward will run free workshops on getting started with them, with paid setup available. Ask whether Jones or FastForward has sponsorship or other commercial terms with Anthropic.

View example

The post presents ENDUIR as a FastForward partner. Ask about the commercial terms of the partnership.

View example

They also write about NetSPI’s listing and participation in the ISV Accelerate Program. Ask whether Jones has a direct commercial relationship with AWS if that affects a campaign decision.

View example

Ask whether Jones has a commercial relationship with XBOW if that affects a campaign decision.

View example

They argue that deal assets should draw on CRM context, not generic templates.

Stays close to the deal and buying committee, tracking each micro-pitch and its supporting materials rather than the org-level divide between RevOps and GTM engineering or the specific tooling stack.

Read original · Original 2

They also argue that writing a precise spec is becoming the core technical work once an agent can handle implementation.

Frames the shift as an organisational and career question, weighing two models for where AI leadership sits and what it reports to rather than advocating a particular stack or posture.

Read original · Original 2

Writes about application security and offensive-security research, not revenue operations or GTM systems.

Read original · Original 2

Their post on XBOW describes a BDR team moved under RevOps and reframed as "agent managers" who QA agent output, handle the steps that still need a human, and have career paths into Sales, RevOps, CS, and GTM engineering.

• Jones's Clarify post lays out enterprise selling as a run of "micro-pitches" — VP of Sales, then RevOps, then security, then legal, then frontline managers — each needing its own asset built from CRM context rather than a re-logoed template.
• Buyers asking what happens to the rep and XDR job, or seeking a buying-committee asset list, get more from this than from a headcount ratio.

Jones's posts offer reported case analysis and product commentary, not described work designing a client's revenue system.

• One post states a commercial relationship directly: Clarify is named as a sponsor of The Signal.
• Expect a briefing built on other companies' published setups; ask what Jones has built or advised themselves, and for a staffing ratio and run-versus-build split, which they address only briefly.

Examples: Source 1 · Source 2

Her post frames the live choice between an existing RevOps leader becoming AI-native and owning the operating model, AI transformation, and builder teams, versus a separate GTM AI leader emerging alongside RevOps.

• She asks which model is winning.
• She pairs that with labour-market evidence from RevOps leadership roles she tracked — 19 of 23 explicitly mention AI or automation, 20 of 23 call for technical architecture or integration — and the 2019-to-2026 shift from "learn SQL, build every automation yourself" to "learn to write a spec an agent can build from," including failure modes and guardrails to anticipate.
• Leadership teams deciding where to place the AI mandate and how to write specs an agent can build from will find more here than in Jones's material.

Her post leaves the organisational question open, so the session would bring a framework and live options rather than a settled recommendation; Jones states a staffing rule.

• The role counts come from a small, self-collected sample, and the Clay workflow they describe is in alpha and flagged as needing review before publishing.
• The post carries a Clay partner designation, so confirm the commercial relationship before booking.

Examples: Source 1 · Source 2

One post argues that AI output must be reviewed by people who understand the domain, using a court filing with AI-generated fake citations as the failure case and warning that unreviewed AI-generated code is still reviewed — by malicious actors instead.

• A second describes his current research interest in guiding security agents with fingerprinting so they target likely weaknesses efficiently instead of wandering low-probability attack paths.
• Buyers whose revenue redesign also touches application security, AI governance, or the human-in-the-loop controls around shipped automation should weigh him seriously.

Jones does not write about RevOps or GTM engineering structure.

• Their material covers legal review, application security, and AI-driven pentesting.
• One post places them in a research role at Microsoft, pointing to research work rather than client advisory.
• For a talk on the RevOps-to-GTM ratio and system ownership, Jones is the weakest of the three; they are the strongest if the talk also needs a security-governance dimension.

Examples: Source 1 · Source 2