๐ค Hybrid autonomy is the production default for teams that are actually moving pipeline, not just testing agents.
As a serial CRO who has built and exited multiple companies where the sales motion had to survive diligence, I have watched pure agent plays stall the moment judgment is required. The wins come from keeping humans on the high-judgment AE work and letting agents handle research, first drafts, sequencing, and CRM hygiene.
โก The split is simple. Agents clear the noise and prepare the conversation. Humans decide the close, the exception, and the relationship. Teams that try to automate the judgment layer usually end up with more activity and less revenue.
The ones seeing results treat this as an operating model, not a pilot. The agent is on the rails. The AE is still accountable for the outcome.
๐ฏ That is the stack that scales without breaking the forecast.
Everything else is still an experiment that has not met a real quota.
๐ฅ TL;DR legends: Hybrid autonomy keeps humans on high-judgment AE work and agents on research, drafts, sequencing, and CRM hygiene. That is the production default for teams that are actually seeing results.
#HybridAutonomy #AISales #RevOps #SalesTech #GTM #EnterpriseSales #Pipeline #HumanInTheLoop #AgenticAI #B2BSales #ForecastAccuracy #RevenueSystems
๐ Clay-style waterfall enrichment is becoming the default data layer for teams that actually run agents at volume.
As a serial CRO who has built and exited multiple companies where the sales motion had to be clean enough for buyers to underwrite, I have watched single-provider lists quietly kill more marketing campaigns than bad copy ever did. Coverage gaps, stale titles, missing (or even worse - bad) emails compound quickly once an agent is in the loop.
โก Waterfall enrichment pulls from multiple sources in sequence so the agent or rep only acts on records that clear a coverage threshold. Claygents then sit on top of that clean layer and can research, qualify, and sequence without the usual data debt.
The difference shows up in reply rates and in how much manual cleanup the team still has to do. Multi-source data does NOT remove the need for a tight ICP. It removes the excuse that the list was the problem.
๐ฏ Teams that get paid treat enrichment as infrastructure, not a one-time export. The agent is only as good as the records it is allowed to touch.
โ๏ธ Levels of success are not equal. Some teams do it better, this is one of the ways how.
Spraying from a single vendor and hoping the match rate holds is so 2000 & late.
๐ธ TL;DR legends: Clay-style waterfall enrichment and Claygents give agents and reps clean, high-coverage data instead of single-provider lists. That is the layer that keeps autonomous outbound from scaling noise.
#Clay #WaterfallEnrichment #Claygents #GTM #RevOps #SalesTech #DataEnrichment #Outbound #AISales #Pipeline #EnterpriseSales #B2BSales โ at Ridgefield, CT
๐ค Made with AI
๐ Revenue intelligence is moving from dashboards that explain what already happened to systems that act on the deal while it is still alive.
As a serial CRO who has built and exited multiple companies where the sales motion itself was half of the diligence, I have seen both versions. The old tools told you a deal was at risk. The new ones update the CRM, flag the gap, and push the next action before the day ends.
๐ฅ Gong still leads on conversation intelligence. Clari plus Salesloft is pushing end-to-end orchestration after the merger. Salesforce Agentforce is embedding the same pattern inside the CRM so the agent can fill fields, score risk, and trigger plays without a separate login.
The difference that matters is whether the system only surfaces insight or whether it can execute the next step under your rules. Insight alone does not move pipeline. Execution does.
๐ฏ Teams that get paid are the ones treating revenue intelligence as an operating system, not a reporting layer. The score and the autofill are useful only if they change what the rep does today.
Everything else is a better chart of the same missed forecast.
๐ฅ TL;DR legends: Revenue intelligence is shifting from insight to autonomous execution. The tools that win are the ones that update the CRM, score risk, and trigger next actions while the deal is still open.
#RevenueIntelligence #RevOps #SalesTech #Gong #Clari #Agentforce #Pipeline #DealRisk #ForecastAccuracy #EnterpriseSales #GTM #B2BSales โ at Ridgefield, CT
๐ค Made with AI
๐ Agentic AI SDRs are now selecting 22% of new prospects and touching 37% of outreach, according to research. Median teams already credit AI for 30% of new outbound opportunities.
As a serial CRO who has built and exited multiple companies where the sales motion itself was half of what buyers underwrote, I have watched this shift up close. The volume is real. The quality is not automatic and my Agentic AI sourced numbers personally are higher, much higher.
๐ฅ Agentic AI tools can research, sequence, and book. They move fast when the ICP and the first messaging are already tight.
When the foundation is loose, they just scale noise. Reply rates were already collapsing before most of these agents launched. AI did not create that problem. It amplified it.
๐ฏ The teams getting paid are the ones treating agents as high-volume researchers and first-touch engines while humans still own the high-judgment moments. That split is the only version I have seen produce underwritable pipeline that scales; and I can tell you first hand that it scales far past the industry numbers in this post.
Everything else is a demo that looks good until the next board meeting.
๐ธ TL;DR legends: Agentic AI SDRs can now generate real outbound volume, but only the teams with tight ICPs and clean handoffs turn that volume into pipeline a CRO can scale it a buyer can underwrite.
#AgenticAI #SalesTech #Outbound #GTM #RevOps #AISales #SalesLeadership #Pipeline #EnterpriseSales #B2BSales โ at Ridgefield, CT
๐ค Made with AI
๐ Building a scalable revenue system means the motion can keep running and does not live only in the an employee's head. That's how you scale sales along with creating real value for a company.
๐ค Duo Copilot tracks the buying signals you choose, surfaces the right people, and prepares the outreach while the rep stays in control. The diagnosis and the next step sit in the same view.
๐ That is the difference between another tool adding to your tool sprawl and an agent based platform that actually shortens time between signal and action. Agents handle the volume. Humans still own the high-judgment AE work that closes enterprise deals.
๐ The best part is that all your reps can use the same sequences, alter them to make them their own, or generate new ones after learning from the best of the best. That is scale. That is value.
๐ธ TL;DR legends: Duo Copilot keeps sellers and agents on one shared plan so signal diagnosis becomes live next-best action the same day. It's done during the start-up phase and at scale.
@amplemarket
Grab a free trial here: grow.amplemarket.com/o7y8ql
#Amplemarket #DuoCopilot #AgenticSales #Outbound #SalesAI #GTM #RevOps #ad
๐ค Made with AI
๐ Agentic playbooks put sellers and agents on the same plan. Diagnosis after the call stops being a note that waits until Monday.
๐ค The shared plan surfaces the next-best action while the conversation is still fresh. The agent executes the sequence or the follow-up without a handoff delay.
๐ Reps stay in control of the high-touch moments. The system handles the coordination so nothing slips between the call and the next step.
โก This is how teams move from reactive CRM hygiene to live revenue motion. The plan is the system. The agents run it.
๐ธ TL;DR legends: Agentic playbooks keep sellers and agents on one shared plan so post-call diagnosis becomes live next-best action the same day.
#AgenticAI #SalesPlaybooks #GTM #RevOps #SalesEnablement #Outbound #RevenueSystems #SalesAI
๐ค Made with AI
โ๏ธ SDR, marketing ops, and RevOps seats are collapsing into fewer agent-supported roles while the CRO still owns the outcome.
๐ค Agents now run most of the volume work that used to require a full team. The remaining humans edit, direct, and close the pieces that still need judgment.
๐๏ธ The operating model that survives is the one a buyer can underwrite without the founder still sitting in every motion. LNZ designs that structure so the revenue engine keeps running after the exit.
๐ธ TL;DR legends: GTM functions are collapsing into fewer agent-supported seats, but the CRO still owns the result and the system has to stay underwritable for a new owner.
#GTM #RevOps #CRO #AIAgents #SalesLeadership #EnterpriseSales #RevenueOperations #ExitReady #MandA #HumanAI #Founders #Advisory
๐ Gartner says AI agents will outnumber sellers 10 to 1 by 2028, yet fewer than 40 percent of those sellers will report any productivity gain.
โ๏ธ The gap is not the agents. It is the data foundation, the automation layer, and the user experience they have to run on. Quick bolt-ons leave the same broken process underneath and just add more digital noise.
๐ง Sales leaders who overhaul those three pieces are predicted to be five times more likely to see real ROI. Everyone else gets more agents and the same results.
๐ธ TL;DR legends: Agents will outnumber sellers 10 to 1 by 2028, but fewer than 40 percent of sellers will feel the gain unless the data, automation, and UX underneath them are rebuilt first.
#AISales #Gartner #RevOps #SalesLeadership #GTM #EnterpriseSales #AIAgents #Productivity #CRO #RevenueOperations #SalesTech #AINative
Lawrence Lanzilli retweeted
The real test is whether those agents can write back into the CRM under the same rules the rest of the motion uses. Most teams still lose the signal at the handoff. The answer is No.. you need a GTM OS. Grok is the best IMO but class is right there with it.
๐ง I am seeing the GTM engineer versus RevOps debate play out inside firms right now. Both sides are protecting the same data layer and neither owns the full outcome.
๐ค AI already handles most of the sourcing, enrichment, and routine validation that used to justify two seats. The remaining work is judgment on schema changes, buyer-signal quality, and whether the motion is actually producing underwritable revenue.
๐ ๏ธ That is why I treat GTM and RevOps as one combined position. One person who owns the contract, the data that feeds it, and the revenue result it has to deliver.
๐ธ TL;DR legends: The GTM engineer versus RevOps split is outdated once AI does the bulk of the work. One combined GTM RevOps seat owns the data layer and the revenue outcome.
#RevOps #GTM #DataLayer #SalesOps #AINative #RevenueOperations #EnterpriseSales #B2B #CRM #GTMEngineering #CRO #SalesLeadership
๐ Gartner says AI agents in sales will outnumber sellers 10 to 1 by 2028. Fewer than 40 percent of those sellers will report any productivity gain from them.
โ๏ธ The gap is not the agents. It is the data, the automation layer, and the user experience the agents have to run on. Quick bolt-ons leave the same broken process underneath.
๐ง Chief sales officers who overhaul those three pieces are predicted to be five times more likely to see real ROI. The rest will have more agents and the same results.
๐ธ TL;DR legends: Agents will outnumber sellers 10 to 1 by 2028, but fewer than 40 percent of sellers will feel the gain unless the data, automation, and UX underneath them are rebuilt first.
#AISales #Gartner #RevOps #SalesLeadership #GTM #EnterpriseSales #AIAgents #Productivity #CRO #RevenueOperations #SalesTech #AINative
๐ As a serial sales leader, I've watched the difference between running the existing motion and actually redesigning it. The sales leaders who treat AI as a bolt-on tool keep adding people to an old process. The ones who redesign the motion put the system first.
๐ ๏ธ The work is no longer coaching more reps through the same sequence. It is rebuilding how research, sequencing, and decision rules live in the platform so a smaller team can produce cleaner pipeline.
๐ AI becomes the operating system, not another dashboard. The sales leader who leads that redesign owns the outcome instead of managing around the gaps in the old motion.
๐ธ TL;DR legends: sales leaders who redesign the motion with AI as the system, not a bolt-on, build leaner teams and revenue a buyer can underwrite.
#CRO #SalesLeader. #GTM #AI #RevenueOperations #SalesLeadership #EnterpriseSales #RevOps #AINative
๐ The GTM engineer role barely existed two years ago. By 2027 it is expected to rank among the highest-paid individual contributor functions in sales.
๐ Job postings for the title grew more than 200 percent year over year. Median compensation already sits between $130K and $160K, with senior and staff-level roles at AI-native companies clearing $220K to $250K plus equity.
๐ ๏ธ The work is not configuration. It is building the data, automation, and AI workflows that turn strategy into repeatable pipeline. Python, SQL, APIs, and systems thinking separate the high end of the market from the rest.
๐ฐ Companies are paying because one strong GTM engineer can replace or multiply the output of several traditional ops or SDR seats. The leverage shows up in conversion, speed, and cost of pipeline, not in headcount.
๐ฎ Talent that can design and own the technical revenue system is still scarce. That scarcity is what pushes the role toward the top of the compensation table as more teams try to operationalize AI at scale.
๐ธ TL;DR legends: GTM engineers are moving from niche hires to some of the best-paid sales functions because they build the systems that make the rest of the team productive.
๐ท๏ธ @Clay @Apolloio @amplemarket @Salesforce @HubSpot @RevOpsDaily
#GTMEngineer #GTM #RevOps #SalesLeadership #AISales #RevenueOperations #Hiring #CRO #EnterpriseSales #TechSales
๐ค Made with AI
Lawrence Lanzilli retweeted
Dan Patrick believes Larry Bird at his best was better than LeBron James.
โLarry Bird at his best was better than LeBron James. And we truly believe that.โ
Birdโs shooting, basketball IQ, clutch gene, and competitive fire made him one of the most feared players of his era. He didnโt need elite athleticism to dominate. He outsmarted defenders, delivered in the biggest moments, and made greatness look effortless.
LeBron has his own incredible legacy, but prime Larry Bird is a different kind of conversation.
Do you agree with Dan Patrick? Was Larry Legend at his peak better than LeBron?
Via: Dan Patrick Show
๐ง Most AI in revenue teams still lives with one person. A custom prompt, a laptop left open, a Slack thread only they understand. The output never reaches the rest of the team in a form they can trust.
โ๏ธ Operationalizing it means the work runs whether anyone remembers to ask. Call prep, deal risk, forecast notes, and next actions happen from a shared record instead of from whoever still has the login.
๐ก A context layer is what makes that possible. CRM, calls, email, calendar, and Slack get resolved into one current customer picture. Agents read the same facts instead of inventing them from partial data.
๐ Audit trails and permissions keep it deployable. Without them, an agent that touches buyer-facing content or deal data stays a demo. With them, the output can be reviewed, corrected, and reused across the team.
๐ Teams that get past the one-person stage are the ones starting to show commercial results. BCG found AI-advanced organizations are twice as likely to report conversion gains and more likely to post double-digit revenue growth.
๐บ TL;DR legends: AI stays stuck with one person until you give the whole team a shared, current, auditable context layer they can actually trust and act on.
๐ท๏ธ @BCG @ClearskiesAI @Salesforce @HubSpot @Gongio @Forrester @RevOpsDaily
.
#AISales #RevOps #GTM #AIAgents #RevenueOperations #CRO #SalesLeadership #ContextLayer #AgenticAI #EnterpriseSales โ at Ridgefield, CT
๐ค Made with AI
Lawrence Lanzilli retweeted
๐ซ A multi-channel sequence on an unqualified list is just spam with more inboxes.
๐ As a CRO who has built and rebuilt GTM engines through multiple exits, I have watched teams add LinkedIn, email, and dialer steps before they had an ICP or a real buying window. Volume went up. Meetings that close did not.
๐ฏ Confirm fit and intent first. Then the sequence can run across channels without training the market to ignore you.
๐ ๏ธ That is the stack we put in at LNZ Ventures. Research, score, then sequence. Not the other way around.
๐บ TL;DR legends:
Channels do not create pipeline. A confirmed ICP and a live signal do. Sequence only after both are true.
How many of this weekโs sends would survive that filter?
@lnzventures
#GTM #Outbound #SalesStrategy #RevOps #ICP #Founders #CRO โ at New York, NY
๐ง I use a four-layer CRO AI framework that will be useful to share. It starts with revenue signal and then decides what an agent can see versus what it is allowed to act on.
๐ก 1) Revenue Signal is the data the agent is cleared to observe. CRM activity, email threads, call transcripts, and other approved sources.
๐ค 2) Revenue Decision is what the agent interprets or recommends from that signal. Lead prioritization, pipeline risk, and forecast estimates.
โก 1) Revenue Action is the limited set of moves the agent may execute on its own. Record updates, opportunity routing, and follow-up preparation.
๐ 3) Revenue Governance sits above all three. Permissions, audit trails, escalation rules, and approval checkpoints keep the system inside the boundaries a CRO sets.
๐ง Cockroach Labs built its own AI system in-house so these layers stayed under one architecture instead of being stitched together later. Landbase takes the same idea further by deploying specialized GTM agents across SDR, AE, marketing, and RevOps so each role only acts on the signal it is cleared for.
๐ When the four layers are explicit, agents stop guessing. The signal tells them what matters. The decision layer tells them what it means. The action layer tells them what they may do. Governance keeps every step auditable. The result is cleaner handoffs and fewer agents touching data they cannot underwrite.
โ๏ธ In-house systems and role-specific agents both work when the layers are defined first. Without that order, the agents just accelerate the old process.
๐บ TL;DR legends: The four-layer CRO AI framework (Revenue Signal, Decision, Action, and Governance) is what makes in-house builds and specialized GTM agents actually useful instead of noisy.
#AISales #CRO #GTM #RevOps #AIAgents #SalesLeadership #RevenueOperations #EnterpriseSales #AIInfrastructure #AgenticAI #RevenueSystems #Marketing
๐ฎ I knew AI would change revenue work. I did not expect the shift to land this hard or this useful across sales, marketing, and RevOps at the same time.
๐๏ธ Forrester is right that AI is pulling RevOps from coordinator into operating-system architect. The same pressure is hitting sales and marketing. The teams that treat the stack as infrastructure instead of a pile of tools are the ones seeing the coordination work disappear and the judgment work stay.
๐ป A computer science background with years of technical architecture, coupled with complex consultative sales experience, make the difference clearer. You see where the data has to live, which agents can act, and which steps still need a person before the process breaks. That view keeps the system coherent instead of letting every function bolt on its own layer.
๐ The result is not more activity. It is cleaner handoffs, better forecasts, and marketing that feeds sales with something a buyer can actually underwrite. The change is larger than most of us planned for, and the upside is real when the architecture is right.
๐ป TL;DR legends: AI is forcing sales, marketing, and RevOps to run as one operating system. The technical architecture view makes it possible to design that system instead of just reacting to it.
#AISales #RevOps #GTM #MarketingAutomation #SalesLeadership #AIAgents #RevenueOperations #TechArchitecture #CRO #EnterpriseSales โ at Ridgefield, CT
๐ค Made with AI
๐ Full autonomy is not the same as results. Hybrid AI plus human outbound is showing 8 to 15 percent reply rates while fully autonomous AI SDRs sit at 1 to 3 percent.
๐ ElevenLabs moved its outbound share of pipeline from 5 percent to 30 percent by tightening the system around the tools instead of adding more agents. Megaโs AI growth engine took SMBs from zero to 10 million in revenue in 10 months by replacing agency work with automated execution that still had clear ownership.
โ๏ธ The pattern across both is the same. The agent or platform handles volume and research. Humans still set the rules, review the edge cases, and own the outcome. That combination is what turns activity into pipeline.
๐ When the system is designed first, the same team covers more ground without the failure rate that pure autonomy keeps producing.
๐ฅ TL;DR legends: Hybrid AI and human outbound is outperforming full autonomy on reply rates. The companies seeing real pipeline gains are the ones that put systems and ownership around the agents instead of expecting the tools to run alone.
#AISales #Outbound #GTM #RevOps #LeadGeneration #AIAgents #B2BSales #RevenueGrowth โ at Ridgefield, CT
๐ค Made with AI








