I got three different answers.

Monday it was one model 5.0. Wednesday it was another frontier company. By Friday, the Wednesday answer was “so last quarter.” Let’s go back to the original frontier model company’s next version 5.5.

None of that advice was wrong. It just expired fast.

That’s the real signal. In a market this fickle, betting your GTM motion on one tool is the mistake.

Here’s what I noticed this week, and what I’m doing about it.

Bring your own harness

Every week there’s a new leaderboard. A new benchmark. A new “this changes everything.”

If you rebuild your workflows every time the leaderboard flips, you will never ship anything.

My takeaway: own the harness. Rent the model.

A harness is the operating layer around a model: the context it receives, the tools it can use, the memory it draws on, and the rules that guide the work.

I keep my core context in one place: my notes, brand voice, ICP definitions, and runbooks. Claude reads from it directly. I export the material for Gemini, OpenClaw, Hermes, Llama, GPT, and others.

The models change. My source of truth stays portable.

When the advice flips next Tuesday, I swap an engine. I don’t rebuild the car.

For a CRO, this is a data integrity question. For a founder, it’s capital efficiency. You paid to build that context once. Don’t pay again every time a vendor ships a press release.

Advice is fickle. Your context shouldn’t be.

LinkedIn split in two. That imposes a new discipline.

LinkedIn now gives me two feeds: For You and Network.

At first that felt like a small UI change. It isn’t. It’s two different jobs.

For You is for discovery. I use it to find people and ideas I don’t know yet. New voices. New operators. New angles on problems my clients have.

Network is for action. I use it to act on relationships I already chose. Existing connections. People I’ve met, worked with, or deliberately decided to follow.

Mix those up and you get noise. You scroll For You and call it relationship-building. You scroll Network and call it research. Neither happens.

This maps cleanly to the 4-layer motion. For You feeds the Signal layer. Network feeds Outreach. Separate the inputs and each layer gets cleaner.

The discipline: decide which job you’re doing before you open the app.

SF Tech Week: win it before you land

SF Tech Week is almost here.

For a week, the whole city comes alive. Technologists. Venture capital. Private equity. Startup founders. Engineers and builders. All of them steeped in the AI motion, spread across dozens of events hosted by dozens of companies.

That density is the opportunity. It’s also the trap. With that many rooms, you can stay busy all week and come home with nothing but a lanyard collection.

The ROI of a conference is decided before you get there. Here’s my pre-conference checklist. It works for any event, but it matters most at one this big.

Pick three outcomes. Not “network.” Three specific results. Two meetings with a named ICP. One partner conversation. One piece of content.

Choose your rooms, not just your events. Tech Week is a buffet. Pick the five or six sessions where your buyers and partners will actually be. Skip the rest without guilt.

Build the target list from the agenda. Hosts, speakers, and sponsors are published. That’s a free Signal layer. Research them now, not in the hallway.

Use both feeds. Search For You for people posting about Tech Week. Check Network for existing connections who’ll be in town. Warm first, cold second.

Pre-book the meetings. A message sent a week out beats a handshake in a crowded room.

Set up capture before you leave. I record sessions and conversations to transcripts so I can process them later instead of scribbling. Decide where the notes land before day one.

Schedule the follow-up now. Put a 48-hour follow-up block on your calendar before the week starts. The follow-up is where the pipeline actually gets built.

A conference isn’t an event. It’s a campaign with a venue.

Harvest season changes what buyers care about

It’s fall. Harvest season.

On the farm, this is when you stop planting and start bringing it in. Business works the same way.

The mindset of the people you sell to shifts right now. If your messaging doesn’t shift with it, you’ll sound like you’re talking to someone who left the room in June.

Here’s what I see changing:

CROs and VPs of Sales are closing, not exploring. Q4 is about landing the number. Anything that doesn’t help close this quarter gets pushed to January.

Finance is watching every dollar. Your buyer’s CFO and FP&A partners are reconciling the year. Remaining budget is either getting spent with purpose or getting clawed back.

Founders are planning 2027. The smart ones use Q4 to decide what next year’s motion looks like. Headcount plans. Tool consolidation. What to stop doing.

Everyone is tired. It’s been a long year. Short, specific, and useful beats long and clever.

So adjust. Talk about what closes now or what sets up next year. Skip the “let’s explore” pitch. Nobody is planting seeds in October.

If you’re one of those founders mapping 2027 right now, start with an honest read on where your motion stands today. I’ll point you to a quick way to get one at the end of this piece.

Launching gtmsos.ai

The new site is live at gtmsos.com. I bought the ai domain after the rebuild wrapped, and gtmsos.ai now 301-redirects to it until the domain migration phase.

But the domain isn’t the real launch. The architecture is.

GTMSOS now runs as a set of connected pieces. WordPress is the primary site CMS. Gamma runs a landing page factory on a ‘go’ subdomain. ScoreApp powers the GTM Assessment. Calendly handles booking. Substack carries the writing.

Five platforms. One brand.

The hardest part wasn’t any single platform. It was UX coherence. Making five tools, each with its own defaults, look and feel like one company. I wrote a design canon first: exact colors, three fonts, spacing on an 8px grid, banned colors, a rule for every corner radius, yada yada. Then every platform got measured against it.

The second big move was letting my AI chief of staff work inside WordPress directly. That runs through Novamira’s MCP server, which gives an agent real access to the site instead of me copying and pasting. The quest for this capability pulled me through lots of resistance.

That’s where the zigs and zags started.

Zig: the first login path failed. Repeated login attempts tripped a rate limit on the command-line route. The MCP connection worked immediately. I dropped the CLI and never looked back.

Zag: the old site had baggage. 41 pages. Only 4 linked from anywhere. The other 37 were leftovers from a previous business identity, still public. The browser tab still read “Productivity Blog.” The share image was a photo of me from 2017. Your website accumulates debt the same way your CRM does. Quietly. Until someone looks.

Zig: none of the fixes were live. After a long session of colors, fonts, spacing, and headings, everything looked great. On staging. The public site still showed the old version. Staging is where you practice. Production is where you get paid.

Zag: the platform fought back. GoDaddy’s managed WordPress was the problem. Cloudflare kept blocking my agent’s connection to the site. So I moved hosts mid-project, out of managed WordPress and into cPanel hosting. The Cloudflare blockage is no longer an issue. The price was new tools, a new staging copy, and a process I had to relearn from scratch.

Zig: direction is everything. Pushing staging to production is one button. Push it the wrong way and you wipe out your own work with the old site. That rule is now written in red in my runbook.

Zag: the post-launch surprises. After the first cutover, two things broke. Search engines were blocked, because a staging setting traveled with the data. And the site’s address came back as http instead of https. Fixing that took 733 replacements across the database. Neither was a disaster. Both would have been if nobody checked.

The fix for all of it: write the runbook while it’s fresh. I documented the process the same day, including the steps I wasn’t sure about. The next cutover will take a fraction of the time.

The agent did most of the heavy lifting. The judgment calls stayed mine. Which pages to retire. What the headline says. When to push the button.

That’s orchestration. The agent executes. The composer decides.

Clearing the field

Harvest isn’t only about bringing the crop in.

It’s also when you clear the field. You pull the old stalks, fix the fences, and decide what gets planted next season. Skip that step and next year’s crop grows up through last year’s debris.

That’s what my migrations are for.

The projects absorbing most of my time lately aren’t new builds. They’re migrations. One is done. The rest are on deck.

Done: managed WordPress to cPanel hosting at GoDaddy. More control, a real staging workflow, and direct access for my agents.

On deck: Neat to OneDrive or Dropbox for records. One less specialized subscription. Records live where everything else already lives.

On deck: Instantly to HeyReach. Rethinking the Outreach layer around where my buyers actually respond.

Evaluating: what replaces Trigify. HubSpot acquired Trigify. When a signal tool gets absorbed into a platform, you have to decide whether to follow it or rebuild the layer. Grok Bot from xAI has been a siren song lately, and so has MoltSets. I haven’t committed to either. But I’m curious, and my Signal layer is up for review.

None of these look hard on a slide. All of them are.

Each migration means new integrations. New data mappings. New processes. New failure points to test. My chief of staff agent has been busy mapping fields, rewiring automations, and catching what breaks.

So why do it?

Two reasons.

First, room. Every tool I retire makes space for something newer. New technology, new processes, and a new stack that gives me capabilities the old one couldn’t. You can’t plant the new crop in a full field.

Second, cost. Subscriptions creep. A tool you signed up for in 2024 renews quietly every year whether you use it or not. Fall is when budgets get set, so fall is when I audit every line. Cut what doesn’t earn its keep before it renews into next year.

And the tools are replaceable because the system isn’t tied to any one of them. That’s the same lesson as field note one. Own the harness. Rent the tools. When a vendor gets acquired, raises prices, or falls behind, you move in weeks instead of quarters.

This is how you scale revenue without headcount. Not by picking the perfect stack. By building a system that survives when the stack changes.

The thread through all six

Fickle model advice. A split feed. SF Tech Week. A season. A site. A field to clear.

Different topics. Same lesson.

The tools will keep changing. The system is what compounds.

Before you plan 2027

Harvest season is when you take stock. Most GTM leaders do it with a gut feel and a spreadsheet.

I built a five-minute diagnostic instead.

The GTM Readiness Assessment scores your motion across the four layers: Signal, Research, Outreach, and RevOps. It shows which layers are ready to carry next year’s number and which ones need clearing first.

No sales call. No pitch. Just a clear read on where you stand.

Take it before you lock next year’s plan.

Take the GTM Readiness Assessment

I write about AI Orchestration for GTM leaders every week. If this one landed, forward it to a founder who’s heading into SF Tech Week or planning 2027 right now. Thank you.

Not because I suddenly started using it more.

Because something in the system was configured differently than I thought.

That was the moment I stopped treating my agentic GTM stack like a finished product.

It isn’t one.

It’s a living operating system. And like the revenue engine it’s supposed to support, it needs maintenance, monitoring, governance, and someone accountable for keeping it healthy.

The audit nobody budgets for

Every founder, CRO, and VP of Sales I talk to seems interested in AI orchestration.

Far fewer are interested in maintaining it.

We like the story that agents reduce headcount, automate workflows, and give small teams more leverage.

We skip the other side of the equation.

Agents themselves need an owner.

They need health checks.

They need permissions.

They need cost controls.

They need recovery plans.

So I audited my own stack.

Here’s what I found.

Share

My permissions were too restrictive.

Early caution had turned into permanent policy. Several workflows couldn’t complete without me clicking through approval prompts.

I wasn’t governing access based on risk.

I was governing it based on fear.

I had MCP bloat.

Connectors had accumulated over time. Many had been installed for one experiment and never touched again.

Nothing was catastrophically wrong.

But every unused dependency increased complexity.

My system of record had become fragile.

One registry file had quietly grown with every event the system logged.

It was still working.

But one bad write could have turned a boring maintenance problem into a recovery project.

I had no system-health monitoring.

No dashboard.

No alerts.

No obvious signal that a workflow had failed.

I usually discovered the problem when I went looking for an output and it wasn’t there.

My model configuration wasn’t explicit.

A default setting was driving behavior and cost that I had never consciously chosen.

The important lesson wasn’t which model was selected.

It was that a critical operating assumption lived as a default instead of a decision.

Failed agent runs had no recovery path.

If a sequence crashed halfway through, I couldn’t resume from the point of failure.

The recovery plan was essentially:

Start over.

Hope it works.

My context layer was duplicating itself.

The same information existed in multiple systems in slightly different forms.

Nothing forced those versions to stay synchronized.

So they slowly drifted apart.

None of this showed up as one dramatic failure.

It showed up as friction.

A slow leak, not a burst pipe.

The maturity ladder underneath the mess

I’ve been comparing notes with other AI-native builders, and the same pattern keeps appearing.

One founder I follow, Amos at Swan, described an evolution that will sound familiar to anyone building an agentic company.

You start with local files.

Then come scripts.

Then specialized agents.

Then shared context.

Then multiple people and multiple agents begin depending on that context.

And suddenly what worked beautifully for one person becomes infrastructure.

Strip away the specific tools and you get a maturity ladder that almost every GTM team running agents will eventually climb.

Share

Stage 1: Manual AI

You use models and tools directly.

There isn’t much infrastructure debt because there isn’t much infrastructure.

The human is still the orchestration layer.

Stage 2: Agent sprawl

You automate more workflows.

Agents multiply.

Connectors accumulate.

Similar logic gets recreated in different places.

Permissions become inconsistent.

The system is becoming useful.

It’s also becoming harder to see.

Stage 3: Context collapse

This is where things get interesting.

Signal hands something to Research.

Research hands something to Outreach.

Outreach hands something to RevOps.

Those handoffs depend on shared context.

But nobody has been maintaining the context layer.

Registry files age.

Memories duplicate.

Definitions drift.

Different agents begin operating from different versions of reality.

The GTM system hasn’t stopped working.

It has stopped agreeing with itself.

Stage 4: Audit-driven maturity

Eventually you discover that orchestration alone isn’t enough.

Now you need observability.

Cost governance.

Explicit permissions.

Context management.

Recovery protocols.

Dependency reviews.

Someone has to operate the operating system.

Here’s the part worth sitting with:

The failures are the audit.

A blown budget tells you cost governance is immature.

A crashed run exposes your recovery architecture.

Connector bloat exposes dependency debt.

Conflicting context exposes weak information architecture.

You don’t necessarily need a consultant to tell you where your system is immature.

Your friction is already telling you.

The metric I’m still looking for

Amos uses ARR per employee as a forcing function.

It’s a useful idea because it asks whether the system is creating leverage instead of simply adding people.

GTM teams running agents need a similar forcing function.

I’m not convinced we’ve found the right one yet.

It might be:

Cost per completed workflow.

Or:

Successful runs as a percentage of total runs.

Or:

Human interventions required per automated workflow.

The important thing is to stop measuring AI activity and start measuring AI reliability and business output.

Token consumption isn’t an outcome.

Number of agents isn’t an outcome.

Number of automations isn’t an outcome.

Revenue created, time removed, decisions improved, and work completed are outcomes.

What changed once I looked

The audit didn’t fix anything.

It did something more useful first.

It turned seven vague anxieties into seven concrete operating decisions.

Permissions became policy instead of fear.

The MCP list got cut back to the connectors that were actually load-bearing.

The registry file got a rotation and archiving plan before it became a recovery problem.

Monitoring got added so a failed workflow becomes visible when it fails, not when someone notices the missing output.

Model choices became explicit configuration instead of hidden defaults.

Failed runs got a recovery path.

Share

And the context layer moved toward one source of truth, with other systems pointing back to it instead of quietly creating competing versions.

None of this is glamorous.

It’s plumbing.

But plumbing is what determines whether “AI orchestration” becomes infrastructure you can trust or a compelling demo that works until the day it doesn’t.

Run your own audit

If agents are operating anywhere inside your GTM system, ask seven questions:

1. What can each agent access, and why?

2. Which connectors are actually still necessary?

3. What system is the source of truth?

4. How quickly do you know when a workflow fails?

5. Are model choices explicit or inherited from defaults?

6. Can a failed run recover without starting over?

7. How many copies of the same context exist across your stack?

If you haven’t looked at those questions in the last 90 days, your AI stack probably contains more infrastructure debt than you think.

Mine did.

And that’s the larger lesson.

The first generation of agentic GTM was about proving that agents could do the work.

The next generation will be about proving that we can operate them reliably.

What’s the part of your own AI stack you’re least excited to audit?

Reply and tell me.

I’ll take the most common answer and dig into it next.

Leave a comment

A product manager. A marketer. A founder I talk with regularly. And a guy who flew from Germany to San Francisco on vacation, for the sole purpose of attending hackathons.

They shipped an AI campaign engine. Describe your product. Set a goal. Set a budget. Pick a geography.

It returned two campaign variants, ran synthetic A/B metrics, and delivered an analysis. Work that used to take two weeks and a real ten thousand dollar spend.

Then the jury gave its feedback.

They did not say the build was bad. They said this:

You didn’t present the problem. You didn’t share the value prop well enough.

He built the answer and lost on the question.

Thanks for reading my summer of 2026 point of view and making comments. I am listening to you with the intent to better understand what helps you as a founder move forward, remaining in the ‘eye of the AI storm’.

The line that explains the whole summer

That same founder told me something a few weeks later that I have not been able to put down.

He was describing why his first launch failed. Two clients, both stalled, nobody adopting.

He said: “We weren’t building for the customer. We were building for the investor.”

That is the founder condition in 2026, stated more honestly than most of us manage.

You are building for the room that funds you. Not the room that buys from you.

AI just made that mistake much cheaper to commit, and much more expensive to survive.

What I actually watched

I spent the last five weeks in rooms.

AMD at Moscone. AWS Launchpad and the AWS Builder AI Camp. (Open) ClawCamp and Claude Camp. A Cerebras launch. TailscaleUp. A Provectus-Anthropic workshop on agentic work. Roundtables, founder calls, hackathon debriefs.

The exposure for me was extraordinary. Inference providers serving forty trillion tokens a day. Context compression cutting token usage by eighty-three percent. Six hundred megawatts of new data center capacity. Agent memory graphs. A company brain.

Here is what almost none of it had on the agenda.

Distribution.

Very few rooms asked how any of this reaches a buyer.

Every room was selling capability

That is the pattern. Nearly every session, every booth, every demo.

Faster tokens. Cheaper inference. Longer context. Better agents. More capability.

Capability is real. Capability is also now table stakes.

Let me make it concrete.

This summer I built my son a five page booking site on Vercel. Coaching schedule, payments, appointments. One day. Nothing to host.

A couple years ago I would have charged a client five thousand dollars for that build.

The wall did not get lower. The wall came down.

When a wall comes down, everyone standing behind it becomes visible at the same moment. Visible, and suddenly identical.

That is your feed right now. Four hundred founders, all newly capable, all saying the same sentence about what they built.

Capability stopped being your differentiator the moment it became free. It became the noise.

And your capability window is closing faster than you think

On August 26, Marc Benioff and Dario Amodei sat down together to launch a joint product. The largest CRM on the planet, wired directly to a frontier lab.

Read that as a founder, not as a spectator.

Whatever capability you are currently differentiating on has a shelf life. The platform layer absorbs features. It always has. AI just compressed the absorption cycle from years to weeks.

You cannot win a race where your competitor’s roadmap ships as someone else’s default setting.

So stop racing on capability. Race on the thing platforms cannot absorb, which is knowing something specific and current about a specific buyer.

Share

The best idea I heard all month came from a networking talk

At the AWS Builder AI Camp, a LangChain engineer demoed eight agents triaging a service incident.

No central coordinator. No orchestrator telling anyone what to do.

The agents coordinated by leaving traces in a shared document. Each one read what had changed, decided whether it had something to contribute, and acted. Biologists call this stigmergy. Ants do it. It works at scale precisely because nobody is broadcasting.

I sat there thinking: that is the market.

Your buyers are not waiting for your announcement. They are leaving traces. Funding rounds. Job requisitions. Filings. A public complaint about the exact friction you remove.

Broadcasting is the old model, and the old model assumed attention was available. It is not available anymore.

Read the traces. Act on the ones that concern you. Stay quiet on the rest.

The only thing that still costs something

Proof of trigger.

Evidence that a specific buyer, at a specific moment, has a specific reason to move.

Not a claim about your product. A signal about their week.

That is the scarce asset, and it is scarce because it cannot be generated. It has to be observed.

Here is what that looks like inside the four layer AI Orchestration motion.

Signal. Stop buying lists. Start watching changes. One platform I build with targets profiles from job postings, social activity, and regulatory filings rather than from a static database. That is the direction of travel.

Research. Volume is a cost, not a virtue. Put a cheap model in front of your expensive one and let it discard the irrelevant before you pay for reasoning. And note this: most of your target accounts post rarely. They comment far more often. The comment layer is under-fished.

Outreach. Open with the trigger you saw. Name it. Date it. Source it. Then, and only then, name what you do. The order is not a stylistic choice. The order is the entire thing.

RevOps. This is the layer founders skip and buyers do not. More on that in a moment.

Three ways your signal dies

One. You lead with what you built.

Your buyer does not have a capability gap. They have a moment. Open with capability and you are one of four hundred capability claims competing for the same three seconds.

Two. You confuse volume with reach.

More posts. More sends. More sequences. AI made your output free, which means it made everyone’s output free. The feed did not expand to accommodate you. Your share of it shrank.

Three. You cannot name the trigger.

You do not know what changed in their world this week. So you sound speculative.

Speculative sounds like noise. Noise gets deleted.

How the good demos actually talked

At that same AWS session, an engineer walked through a supply chain deployment at a large pharmaceutical company.

He did not open with durable memory or virtual file systems, though the system has both.

He opened with this. Report generation went from twelve weeks to ten minutes. Eight million dollars saved a year.

Twelve weeks to ten minutes. That is a sentence a CFO repeats in a meeting you are not in.

Compare it to how most founders open. “We built an agentic platform with persistent context.”

Same technology. One of those sentences travels. The other one dies in the room it was spoken in.

Name the outcome. Let them ask how it works.

The layer that closes your deals, and you are ignoring it

Founders treat governance as the boring part. Buyers treat it as the buying part.

Gartner predicted that forty percent of enterprise applications would feature task-specific AI agents by 2026, up from less than five percent in 2025.

Now put that next to what security leaders are actually reporting. In the 2026 CISO AI Risk Report from Cybersecurity Insiders and Saviynt, seventy-one percent of organizations said they use AI tools that reach into core business systems like Salesforce and SAP. Only sixteen percent said they effectively govern that access.

Sit with that gap. Your buyer wants what you built and is not equipped to absorb it.

That is not a footnote. That is the objection that kills your deal in procurement, three weeks after your champion said yes.

The vendors in the room already know this. AWS spent a chunk of its builder session on the governance layer underneath its agent stack. Tailscale shipped secure credential injection so agents never touch a raw secret. The infrastructure companies are selling control, not just capability.

And here is the specific ask I keep hearing from executives, in almost the same words every time.

They want a red button.

A control that says stop before this burns my token budget. Predictable cost. A kill switch. Someone accountable for what the agent did and why.

If you cannot show cost containment, you are asking a buyer to sign an open ended invoice. No serious operator does that.

Build the guardrail into the offer. It is not a compliance cost. It is a closing tool.

Share

What this cost me to learn

I lost a deal this summer.

A VP of sales running a million dollar personal book. Opening a branch. He needed a prospector, and he told me so directly.

I knew the problem. I had done the job the system was supposed to do. I had the architecture spec’d and I could build it.

I still lost.

Not because the build was wrong. Because I opened with a picture instead of with his trigger, and the picture landed sideways before I ever got to explain it.

He still has the problem. That is the part that stings.

I made him do the translation work. Buyers do not do the translation work. They just stop replying.

What changed when I fixed the order

I stopped leading with capability. I started leading with the trigger.

Since then: two new engagements signed, both on this exact motion.

GTMSOS went from scattered pages to an actual system. The domain is live. Twelve child pages. A product architecture that holds together.

The 100 Leads Sprint got designed and built end to end with a development partner. Signal capture, model scoring, structured data, all wired.

And an invitation to speak at an AI engineering conference on GTM engineering signals, to a room that is mostly founders.

None of that happened because I got better at building.

It happened because I got better at being heard.

The close

Go back to the hackathon jury.

They were right, and they were right about something much bigger than that one product.

The build stopped being the hard part the moment a stranger from Germany could help ship a working product in two hours, on his vacation, with people he met that morning.

The hard part is the sentence before the demo. The one that proves you were paying attention to them.

Last month I wrote that the moat didn’t move, the buyer did.

Here is the follow on: The moat is gone. What is left is whether you can prove you were watching.

If you want to see what that looks like built out, I put the whole motion on one page. One hundred leads, sourced from live triggers instead of static lists, scored for relevance, and delivered with the trigger attached to every name so your first sentence writes itself.

Have a look when you have ten minutes: The First 100 Leads

No pitch attached. If the motion is useful and you build it yourself, that is a good outcome too.

Share

Next in this series: the same five weeks, read through a CRO’s forecast. Then through a VP of sales’ Monday morning.

Sources

Gartner, Gartner Predicts 40% of Enterprise Apps Will Feature Task-Specific AI Agents by 2026, Up from Less Than 5% in 2025

Cybersecurity Insiders and Saviynt, 2026 CISO AI Risk Report, January 2026, n=235 security leaders.

I spent two days at Advancing AI 2026. In the keynote hall, in the workshop rooms, and in the hallway conversations with the builders, investors, founders, and developers who actually ship this stuff. The thing that mattered most had almost nothing to do with gigawatts.

Patrick Moorhead, who has covered AMD for thirty years, titled his field note “Helios Ships, Venice Swings, And The Software Moat Narrows.” That third point is the whole game from the Go-to Market perspective. The moat was never the hardware. It was the porting cost, the years of rewriting and tuning it took to move a workload off the incumbent.

That cost is collapsing. And when a switching cost collapses, buyers get choice. When buyers get choice, orchestration decides the winner, not the spec sheet. That is a GTM story. It’s your story.

The moat you're defending is made of porting cost

Here’s the moment that stopped me. On stage, Philippe Tillet of OpenAI, the man who created Triton, described AI agents now writing optimized GPU kernels down to instruction scheduling in assembly, against an open compiler stack. Work he said would have been impossible in a closed one.

Vamsi Boppana, who runs AI at AMD, put a number on it. His team ran 14,000 models through an AI optimizer called Hyperloom in a single pass, something no human team could do by hand. And Anthropic’s story, retold all week, was one engineer wiring Claude to a rack over a weekend and coming back to a working performance graph.

Read that as an operator, not an engineer. The most defensible moat in tech, the reason customers stayed put for a decade, was integration labor. AI just turned integration labor into a weekend job.

So ask the uncomfortable question. What is your moat made of? If the answer is “the work it would take a customer to leave,” you’re defending a porting-cost moat. And porting cost is collapsing in your category too. It’s only a question of which quarter.

Tokenomics is the new pipeline math

Every serious room was really talking about one thing: the cost per unit of intelligence. AMD calls its edge “tokens per dollar.” Dan McNamara said AMD’s own IT team cut token costs 43% by routing each request to the right model on the right compute instead of sending everything to the frontier.

Then AT&T’s CTO Jeremy Legg made it real. Over a trillion tokens a month. More than a hundred GenAI models in production. Cache-aware routing cutting some AI costs by as much as 90%. He used the word I’d been waiting for a Fortune 50 operator to say out loud: moneyballing. Moneyballing token costs across a portfolio of open and closed models to hit the same outcome for a fraction of the spend. That’s not an infrastructure story. It’s a revenue-efficiency story in an infrastructure costume.

Here’s the translation. Tokens are becoming a cost of goods sold. The teams that measure, route, and compound their token economics will out-margin the teams that don’t, exactly like the teams that measured pipeline conversion buried the ones that guessed.

Tokenomics is the new pipeline math. If your RevOps function can’t see cost-per-outcome across your AI motion yet, that’s where your margin is leaking.

Subscribe now

The distributed stack is an orchestration problem

Watch how AMD framed the day and you’ll see your own operating model staring back. The pitch wasn’t one god-box. It was intelligence distributed across the data center, the enterprise server, the desk, and now the robot. Frontier model in the cloud, open model on-prem, a small model on a device beside you.

Jack Huynh showed personal AI running 300-billion-parameter models on a box that sits on a desk. In the workshops, I watched a small vision-language-action model drive a robot arm on a Ryzen board, and an open engine called Atom serve a coding agent locally with no data center in sight. Cisco’s Jeetu Patel said the line of the conference: “Humans click, but agents swarm.”

Sit with that. The old motion assumed a human at every step. The new one assumes hundreds of agents running around the clock across a distributed stack. That only creates value if something orchestrates it. Routes it. Governs it. Prices it.

This is the AI Orchestration thesis, and the four layers map cleanly. Signal is the router deciding what each request actually needs. Research is the context each agent pulls to make a good decision instead of a generic one. Outreach is the swarm doing the work at machine scale. RevOps is the control plane: the tokenomics governance, the observability, the guardrails. The thing Cisco literally shipped as “Cloud Control” so a leader can quarantine a runaway agent before it torches the budget.

This isn't theoretical, and it isn't only a hyperscaler game. On Claire Vo's How I AI, a solo builder named Alex Finn walked through the exact model running on his own desk. Five machines, five agents, a fleet dashboard he built himself, routing each task to the right local model and running the whole thing 24/7 without babysitting it. Signal, Outreach, and a control plane, operated by one person. And his sharpest line is the tokenomics punchline: unlimited local inference changes the use-case math in a way a $20 cloud subscription never can. One builder already lives in the world AMD spent two days describing.

AMD spent two days proving that in silicon. The lesson for GTM is identical. You don’t have a tooling problem. You have an orchestration problem.

The buyer already voted

Now rewind seven weeks. On June 2 I was at Microsoft Build, watching Satya Nadella lay out the same future from the buyer’s side of the table.

Microsoft didn’t pledge loyalty to a vendor. It bragged about choice. First-party silicon. Partner systems. The first cloud to stand up Nvidia’s Rubin. Deeper work with AMD. And its own Maia accelerator, which Microsoft said delivers 30% better tokens per dollar than the leading GPU, already validated on a frontier model and running Microsoft 365 Copilot. The biggest AI buyer on earth told its developers that silicon is now a portfolio decision, not a marriage.

Same with models. Foundry now lists more than 11,000 of them, and Satya said the model itself is becoming less of the differentiator. When a buyer has 11,000 interchangeable options, the moat isn’t the model. It’s the orchestration around it.

Even Jensen felt it. Beamed in from Taipei, the most powerful incumbent in the industry sold Nvidia not on lock-in but on tokens per dollar per watt, and on making token generation 30 times cheaper than the last generation. When the leader starts selling unit economics instead of switching cost, the moat is already gone. He just hasn’t said so.

That’s the demand signal. Now connect it to the supply side. Seven weeks later, Andrew Feldman and AMD answered that exact buyer. Cerebras took the one axis Nvidia still owned, ultra-low latency, and fused it with AMD’s throughput and memory into a single disaggregated solution. Five times the throughput while keeping the speed. On Cerebras Cloud this year.

That’s not two vendors making a chip. It’s two challengers composing a product to attack the incumbent’s last stronghold, aimed at a buyer who already said out loud it wants choice. June 2 was the buyer voting for a world without a moat. July 23 was the ecosystem shipping the product that world demands. Two months, thesis to purchase order.

The lesson most vendors will miss: in a choice-rich market, the winning play isn’t “do everything myself.” It’s “compose the best combination and let partners vouch for me.” If you’re still running a hero-seller, do-it-all, closed motion, you’re running Nvidia’s strategy in a market that just rewarded AMD’s.

What I took from the rooms

I didn’t go to San Francisco to admire hardware. I went to read the demand.

The builders and founders weren’t asking which chip is fastest. They were asking how to run more intelligence for less, everywhere, without hiring an army. That’s the scale-revenue-without-headcount question, asked by the people building the picks and shovels. The investors were circling the same thing from the other side: where does margin compound, who owns the orchestration layer, and who’s just reselling tokens.

And the developers in the workshops, wrist-deep in ROS 2 and inference engines, were quietly building the routing and control muscle every enterprise is about to need and almost none of them have. That gap is the opportunity. It’s the one I intend to lead into.

The move

Stop buying tools. Start composing the system. The next eighteen months belong to operators who treat AI as an orchestration layer with real unit economics, not a shelf of point solutions with a demo and a logo.

AMD just showed the industry what that looks like in silicon. It made the switch cheap, made the economics legible, and let the ecosystem sell for it. Run the same play in your go-to-market.

So here’s my question. If a customer could leave you as easily as an engineer now moves a workload off CUDA, what would actually make them stay? Reply and tell me. I read every response.

Subscribe now

I’ve spent the last few weeks in rooms where that sentence stops being a clever line and starts being a budget conversation.

By the way, thank you for reading my blog. Appreciate your engagement.

What the rooms actually sound like

Venture Dock in Palo Alto. Shack15 at the Ferry Building, in the same room as Author of “AI Leadership in the 4th Industrial Revolution”, Kent Kaufman, and Managing Partner at Human Ventures, Manoj Fernando, Apache Iceberg experts from Datadog, Databricks, TRM, and a dozen startups nobody has heard of yet.

"With intelligent robots the paradigm is shifted, and so we may see an acceleration in the ability of robots, and that's why physical AI is such a hot topic at the moment, is because we have not had the ability to have intelligent robots before, and that's a significant change." ~ Kent Kaufman

A session on marketing agents in production with Anthropic.

Workshops on high-ticket sales. Claude Code running outbound through Smartlead and GetLeads. This week, Advancing AI at Moscone.

Here is what struck me. The infrastructure conversation and the go-to-market conversation have stopped being separate conversations.

The people building the models and the people trying to hit a number are now describing the same problem in different vocabularies.

The Unbridled Part

Startup growth pain used to be a capacity problem. Not enough hands.

Now it’s a discernment problem. Too many things you could automate, and no principled way to decide which ones you should.

I sat with technical founders to pressure-test a developer product thesis. I sat with a sales AE to hear where the theory breaks against a real quota.

Same gap in both conversations. Everyone can build. Almost nobody has decided what winning looks like before they build it.

That’s the unbridled part. Not the technology. The absence of a governing question.

What I’m building, in the open

I’m designing a scalable agentic system with hot-swappable data sources. Concretely, it does this:

Reads intent signals. Scores ICP match. Enriches, dedupes, and curates account and contact data. Provides source attribution back to the systems of record. Compounds what it learns about preferences. And gates one segment of the interaction behind a human checkpoint.

That last one is the part people skip.

Notice the shape. Signal, then Research, then Outreach, then RevOps. That order is not decoration. Reverse it and you get a very fast machine producing very confident garbage.

The four questions I now run everything through

Before I automate anything, it has to survive four questions. If a workflow can’t clear all four, it’s a demo, not a system.

1. Does the agent learn from proprietary customer context?

Generic context produces generic output. My scoring model is only worth something because it’s absorbing signals from my accounts, my closed-won patterns, my disqualifications. The enrichment layer is a commodity. What I feed it is not.

2. Does the workflow improve with every completed cycle?

A workflow that performs identically on run 500 as it did on run 5 isn’t compounding. It’s just fast. The preference layer exists so that every human correction at the checkpoint gate becomes training data for the next cycle. That’s the difference between automation and leverage.

3. Does it create measurable customer value?

Not internal efficiency. Customer value. Did the buyer get a more relevant conversation? Did they waste less time? If the only metric that moved is “emails sent per rep,” you built a spam cannon with a nicer UI.

4. Would switching providers erase the advantage?

This is the brutal one. If swapping the underlying model or the data vendor deletes your moat, you never had a moat. You had a subscription. Source attribution and the accumulated preference layer are what survive a provider swap. The prompts are not.

Three disciplines that didn’t exist on the org chart 18 months ago

Watching adoption patterns across these rooms, a shape keeps repeating. Agent adoption is creating three new executive disciplines. Most people are filing them all under “governance,” which flattens something important.

Permission control. What is the agent allowed to touch, on whose behalf, and where does a human have to sign. Not a security checkbox. A design constraint that shapes the whole architecture.

Capacity economics. Inference has a unit cost. Multi-agent orchestration has a unit cost. The question “can we afford to run this 40,000 times a month” is now a strategy question, not an IT question.

Capacity economics. The only defensible proof that any of it worked.

If you can name who owns each of those three at your company, you’re ahead of most of the room.

Share

The economics finally moved

Here’s what changed, practically. Multi-agent orchestration became economically viable.

We’re moving on from one oversized assistant attempting everything. A single model doing signal detection, research synthesis, copywriting, and CRM hygiene was always a compromise. It was just the only affordable option.

Now you can compose specialists. Small teams can appear much bigger than they are.

But be honest about the other side of that. Your competitors have access to the same models, the same vendors, the same tutorials.

Which means the advantage is not the capability. It’s the speed of your compounding loop and the quality of your judgment about where humans stay in it.

The Honest Tension

I’ll name the pro and the con, because I don’t trust arguments that only have one side.

The pro: I can now run a go-to-market motion that would have required six people two years ago, and it gets sharper every week.

The con: the same abundance means my mistakes replicate at machine speed. A wrong ICP definition used to cost me a few bad meetings. Now it costs me 4,000 bad touches and a burned domain reputation.

Execution abundance is amplification. It amplifies whatever strategy you fed it.

Where this Leaves the Discipline

The new GTM discipline is not prompt engineering.

It’s three decisions, made deliberately, in this order:

Which work deserves automation. What outcome proves value. Where human judgment must remain.

That third one is where I see the most avoidance. Teams treat the human checkpoint as a temporary crutch to be removed once the model gets good enough.

I think that’s backwards. The checkpoint is where the proprietary learning enters the system. Remove it and you’ve optimized away the exact mechanism that makes you different from everyone running the same stack.

Build the loop. Guard the gate. Measure the customer, not the activity

What’s the one workflow you’ve automated that you can honestly say passes all four questions? Reply and tell me. I’ll share what I’m learning as this system goes from working to compounding.

Share

The first was a pitch event in Palo Alto. Sixteen early-stage startups. Half had revenue. Every single one had a real product. Almost none had a repeatable GTM motion.

The second was an AWS Builder meetup in San Francisco. SurrealDB was presenting their agent memory platform. Technically brilliant. At the Q&A, I asked the Co-founder Tobie, a straightforward question.

“Over the next twelve to twenty-four months, who are you actually targeting? Developers, AI-native startups, enterprise, database consolidation?”

The answer: all types of organizations. Startups, scale-ups, enterprises, defense, finance.

Honest answer. Expensive answer.

The Gap Mark Roberge Keeps Warning Founders About

Roberge, founding CRO at HubSpot, now Stage 2 Capital, draws a hard line between two things founders routinely conflate.

Product-market fit means customers find value. Go-to-market fit means you can deliver that value *repeatedly and profitably*, to the right people, through a motion someone else could run.

You can have the first without the second. Most of the founders I met in Palo Alto do. Great product. Real retention. No system.

And when they feel the pressure to fix that gap, most of them make the same move.

They go buy some GTM execution.

Three Ways Founders Try to Buy GTM

There are really only three options when a technical founder decides it’s time to build pipeline.

**Option 1: The Freelancer.** Fast to hire, cheap to start. They execute tasks. What they can’t do is think with you. There’s no ICP depth, no strategic judgment, no marketing intuition. And when they leave, everything they touched leaves with them.

**Option 2: The Agency.** Looks more serious. There’s an account manager, a pitch deck, a kickoff call with someone sharp. Then the handoff happens. The senior person disappears. Junior operators, running the same $15/hour playbook take over. You got two weeks of strategy and months of managed execution that isn’t connected to it.

**Option 3: The GTM Operator.** A strategic advisor who also executes. Same person, same brain, same accountability every week. They work on a limited number of clients because the work requires depth. They build systems, not just campaigns.

The difference isn’t style. It’s compounding.

Freelancers sell time. Agencies resell time. Operators build systems that compound.

Why the First Two Options Don’t Solve the Actual Problem

The Palo Alto founders aren’t failing at execution. They’re failing at *signal*.

Most of them have gone straight to Layer 3. They’re sending outreach. Writing sequences. Running ads. But it’s built on nothing. There’s no signal clarity, no research layer, no RevOps loop that learns from what works.

That’s the mistake. They bought execution before they built the engine underneath it.

When I think about what it actually takes to close the gap between product-market fit and go-to-market fit, I think in four layers:

**Layer 1: Signal.** Know who is ready to buy before you call them. Not a firmographic. A trigger event is something observable that tells you an account is in motion *right now*. A new hire. A funding round. A product launch. A regulatory shift.

**Layer 2: Research.** Show up knowing more than they expect. Not because your team Googled them that morning. Because a system built the picture before the conversation started.

**Layer 3: Outreach.** Messages that land because they’re built on real context. Specific. Timely. Not templated spray.

**Layer 4: RevOps.** The loop that makes the whole system learn. Every win. Every loss. Every shift in what “ready” looks like. This is Roberge’s speedometer. It’s the signal that tells you your GTM motion is working before churn tells you nine months later that it wasn’t.

A freelancer can execute Layer 3. An agency can manage Layer 3. Neither of them builds Layers 1, 2, and 4. And without those three, Layer 3 is just noise at scale.

What the Right Model Actually Produces

The GTM Operator model works because it doesn’t separate strategy from execution.

The same person who diagnoses your ICP writes the first sequence. The same person who sets up your RevOps loop reads the data when it comes back. The same brain that chose the trigger event in month one adjusts the signal criteria in month four because the market shifted.

That’s not a deliverable. That’s a compounding system.

The revenue formula is simple: R = N × C × V × M. New pipeline times close rate times deal value times retention. Every layer of the GTM engine touches at least two of those variables. A freelancer moves one lever once. An operator tunes the whole machine continuously.

The Question That Tells You Where You Are

Before you hire anyone or buy anything, answer this.

Can you name the trigger event that tells you an account is ready to buy?

Not an industry. Not a company size. A *trigger*. Something that happens in the world or inside a company that makes them ready now that they weren’t ready before.

If you can name it, you have the beginning of a signal layer. That’s where a real GTM motion starts.

If you can’t name it, no freelancer, no agency, and no AI tool is going to build it for you. That’s the operator conversation.

The product is real. The market is real.

The system is what’s missing. And the system has to be built, not bought by the hour.

*If you’re a founder or know one building this right now, I’d start with the trigger. What event makes your best customers ready? Hit share.*

Share

One of those numbers closes deals. The other fills a dashboard nobody trusts.

Here’s the operating truth most GTM teams won’t say out loud: 28 touches into silence isn’t persistence. It’s a signal you never earned the first hour.

The Research Has Already Happened

By the time your sequence fires, your buyer has done 80% of their research. They’ve been on podcasts, Reddit threads, YouTube, and AI queries. They’ve formed a view of you — or they haven’t.

You’re not the first voice in the room. You’re competing with the impression left by every hour of content they consumed before your name landed in their inbox.

Two patterns show up everywhere right now.

The founder with 200 leads and 3 conversions. The list isn’t cold. The brand isn’t warm enough. You’re asking for time you haven’t earned.

The CRO with SDRs at 120% of activity quota and 60% of pipeline target. Activity without presence is noise. You’re measuring the wrong variable.

Both problems look like a pipeline problem. Neither one is.

The 7-Hour Threshold

There’s a principle behind the highest-converting GTM programs I’ve seen. It’s not a sequence. It’s a threshold.

Seven hours of content consumption is a buying signal. More predictive than a form fill. More reliable than a demo request.

Think about it this way: you don’t trust a vendor after one email. You trust one after you’ve spent real time with their thinking. The same is true for your buyers.

Here’s how the framework maps across your GTM stack.

Signal: Stop tracking opens. Track hours.

Most teams run signals on intent to notice. The 7-hour principle runs signals on intent to trust.

Podcast listens. Video watch time. Workshop attendance. Newsletter engagement depth. When a prospect crosses a meaningful consumption threshold, that’s not just activity data. That’s a trust indicator. Build the infrastructure to see it.

Research: The 7 hours tell you more than the prospect does.

When Signal shows you someone has consumed 7 hours of your content, it also tells you which 7 hours. What topics. What formats. What questions they’re still carrying.

That’s not a lead record. That’s a buyer briefing. Use it to understand exactly what’s still unresolved before you make contact.

Outreach: The first touch should be earned, not claimed.

Outreach triggered by engagement depth converts because it’s contextual. You’re not interrupting. You’re showing up at the moment they’re ready.

That’s the difference between a 28-touch sequence and a single message that books the meeting. One assumes attention. The other earns it.

RevOps: Change the metric.

Not “how many touches did this deal receive?” Ask “how many hours of engagement happened before the first meeting?”

Engagement depth becomes a leading indicator of close probability. It belongs in your forecast model more than activity count does.

When Deals Stall Mid-Funnel

This is where the framework stops being theoretical and becomes operational.

If you’re a founder in a stalled deal:

You’re sending follow-up emails. Checking in. Giving them one more week. Nothing is moving.

Here’s what’s actually happening. They haven’t hit their 7-hour threshold yet. They’re still deciding if they trust you enough to champion this internally.

The fix isn’t more outreach. It’s delivering the next hour of content that advances their confidence. A recorded pitch. A workshop invite. A peer case study that answers the question they haven’t voiced yet.

The Signal layer tells you where they are. Outreach meets them there. That’s the founder-led sales motion that actually works. Not 28 more touches. A system that earns the remaining hours.

If you’re a CRO with a stalled mid-funnel:

Mid-funnel deals stall for three reasons: wrong ICP, wrong champion, or insufficient trust. Most teams treat all three with the same tool. A follow-up sequence.

The deals stalled on trust can’t be re-engaged with volume. They need depth.

Here’s the signal to build into your model: if a prospect is in Stage 2 pipeline and hasn’t logged 3+ hours of brand engagement, that’s not a pipeline problem. It’s a nurture problem wearing a pipeline costume.

Deals where buyers hit 7+ hours of engagement before discovery close faster, with fewer objections, at higher ACVs. That’s a forecast model worth trusting.

What This Looks Like in Practice

A bootstrapped ABM agency founder. One hundred programs built. $130M in pipeline sourced. Two people on the revenue team.

He doesn’t run 28-touch sequences. He runs a 7-hour stack: weekly podcast, weekly newsletter, monthly deep-dive webinar, quarterly in-depth workshop. By the time someone books a call, they’ve already decided. He sends a pre-recorded pitch so they don’t waste a meeting on the overview. Average sales cycle: 58 days, 28 of which are legal review.

That’s not an outlier. That’s what happens when you build a GTM system around earning trust instead of counting activity.

The pipeline fills differently. The conversations open differently. The close rate looks different too.

The Question Worth Asking

What’s your 7-hour stack?

Not your sequence. Not your cadence. Your stack. The body of content and experience that moves a skeptical buyer from “I’ve heard of them” to “I’m ready to talk.”

And do you know if your buyers are spending those hours with you — or with the competitor who figured this out first?

If you’re a CRO or founder and this pattern sounds like your pipeline right now, reply. I want to hear what your 7-hour stack looks like. Or why you don’t have one yet.

“Companies are great at educating on products. They suck at sales training. They really do. Most companies really do.”

That’s not a hot take from a Twitter thread.

That’s forty years of enterprise sales, delivered plainly, by someone who has lived every version of this problem.

I heard it this week. And it’s the most important thing a founder planning their first sales hire needs to hear right now.

Because you are about to make the same mistake.

You Don’t Have a Coverage Problem

You think you need a person to make the calls you can’t make.

That’s not wrong. But it’s the wrong diagnosis.

What you actually have is a motion problem.

The ICP is in your head. The deal stages shift when the week changes. The follow-up “system” is your inbox. The training plan is a product demo, a handshake, and a hope.

Adding a rep to that is not scale.

It’s delegation of chaos.

Salesforce's 2024 State of Sales report found that reps spend 70% of their time not selling. That number doesn't improve when there's no system for them to inherit. It gets worse.

What Forty Years in the Field Looks Like

The sales veteran I talked to this week has seen this pattern play out at the enterprise level. Repeatedly, across decades.

His company had two kinds of salespeople: the ones in their 50s and 60s who had been around forever, and the ones in their 20s who were sharp but green. Nothing in the middle.

The experienced reps carried institutional knowledge. None of it was written down. When they left, it left with them.

The younger reps knew the product cold. Nobody taught them how to sell it.

Marketing owned the training. Some managers were strong. Some weren’t. After enough turnover, he said, you had the blind leading the blind.

That’s not a hiring problem. That’s a system that was never built.

You’re not at the enterprise stage yet. But the seed of that failure is being planted right now, at your current stage, in the decision you’re about to make.

The Four-Layer Motion Your Hire Needs to Inherit

There’s a four-part GTM motion every sales organization runs, whether they know it or not.

Signal. Research. Outreach. RevOps.

Most founders have fragments of one layer when they post the job.

Here’s what the hire needs on day one:

Signal. A documented ICP. Not in your head. Who buys, who stalls, what triggers urgency, what disqualifies fast. Written. Searchable. Not a Slack thread.

Research. Account context that doesn’t require the founder to brief the rep before every call. Personas, stakeholder maps, conversation history. A system that holds memory so the rep doesn’t have to.

Outreach. A repeatable prospecting motion already running. Personalized at scale. Not five manual messages a day that only work when you send them.

And here’s where something shifted this week.

I was in North Beach San Francisco Wednesday. Not a conference. A confluence. Our cohort at HeyGen calls it “Infinitely Me”.

I watched a platform compress what used to require a full production team into a single motion. Training videos. Objection handling walkthroughs. Personalized prospecting clips. Product explainers. Internal comms. FAQs. 100+ languages.

One platform. One motion.

The excuse that you couldn’t afford to build a sales training and content system before the first hire just expired. I watched it die in real time.

RevOps. A pipeline your rep can trust. Deal stages that don’t move. A CRM with actual data in it. A forecast that isn’t your gut.

The rep doesn’t build this system. They run it.

If it doesn’t exist when they walk in, they spend their first 90 days constructing the runway while standing on it.

That’s your runway. Measured in dollars and months.

The Founders Who Win in 2026

They are not the ones who find the best first sales hire.

They are the ones who build the system before the hire arrives, and they are building it at machine speed.

Content motion. Signal layer. Outreach sequence. Operational foundation.

The rep they hire doesn’t inherit a blank whiteboard. They inherit momentum.

That is the difference between a 30-day ramp and a 90-day experiment.

Mark Roberge, who scaled HubSpot from zero to $100M as founding CRO, puts the undocumented ramp at four to six months. Most founders budget for three.

Before You Post the Job

I built a five-minute diagnostic for exactly this crossroads.

It maps which of the four layers are ready and which ones will cost you your first hire before they close a single deal.

No sales call. No pitch. Just clarity on where you actually stand.

Take GTM Readiness Assessment

Try it before you post the job.

The first sales hire fails 60 to 70 percent of the time.¹ The founder blames the hire. The hire is not most often the problem.

The problem is the founder built nothing for them to inherit.

The founder is the system. Their calendar is the pipeline.

The founder’s head holds the Ideal Customer Profile. In a mature sales organization, the ICP is a written document the whole team uses. It defines who buys, who stalls, who looks like a fit but isn’t, plus the disqualifiers, the urgency triggers, and the buyer-language tells.

In a founder-led organization, none of that is written down. The ICP is whatever the founder remembers in the moment.

The founder’s gut is the forecast. When the new sales rep arrives, they do not inherit a sales motion. They are inheriting the founder’s nervous system.

That’s not a job. That’s an impossible transplant.

The trap is not that the founder is in every deal. The trap is that the founder is the only system.

The Off-Ramp Has Five Stages

Stepping out of founder-led sales is not a switch. It is a runway.

Most founders try to skip from Stage 1 to Stage 4. That’s the failure mode.

Stage 1. The founder is the system. Everything in their head, their inbox, their calendar.

Stage 2. The founder documents the system. ICP, deal stages, win/loss patterns, message library, signal triggers. Written down and searchable.

Stage 3. The founder hands the system to a fractional operator. RevOps lead, fractional sales engineer, fractional content lead. They build the operating layer the next hire will inherit.

Stage 4. The first AE inherits a working system. They evolve it. They don’t rebuild it.

Stage 5. The sales team runs the system. The founder runs the company.

Each stage maps to a layer of AI Orchestration. Signal, Research, Outreach, RevOps.

By Stage 3, all four layers have been externalized from the founder’s head into the operating system. That externalization is the work. The hire comes after.

A Real Example

A Series A SaaS founder I worked with hit $2M ARR. She hired a Sales Executive out of a top-tier enterprise SaaS company.

Eight months later, the Sales Executive was gone. The founder blamed the hire. We looked at what was actually missing.

The signal-detection rituals lived in the founder’s head. The deal-stage definitions changed every Tuesday.

The forecast was the founder’s gut. The ICP was a Slack thread. The Sales Executive walked into a sales motion that did not exist outside the founder’s body.

We rebuilt. The founder spent ninety days documenting everything.

Then sixty days with a fractional RevOps lead building the operating layer. Pipeline definitions, signal triggers, message templates, forecast cadence.

Then the next sales hire arrived. Same caliber of person. Different result.

Ramped in sixty days. Qualified meetings held. Pipeline full. Hit quota in quarter three.

The founder didn’t hire better the second time. They built a runway the second time.

That’s the difference. Not the human. The system underneath the human.

What This Means for You

If you are at $1M to $5M ARR and thinking about your first sales hire, ask one question. What system am I handing them?

If the answer is your calendar, you are not ready to hire. You are ready to document. Then to externalize. Then to hire.

The off-ramp is sequential. Skip it and you waste eighteen months of runway and one good operator’s career.

The founders who scale aren’t the ones with the best first sales hire. They’re the ones who built the system before the hire arrived.

You are not trying to hire your way out of founder-led sales. You are trying to systematize your way out.

That is the job of a System Composer.

Founder-led sales is not a personality trait. It is a stage.

Every founder starts there. The ones who scale don’t hire their way out. They build their way out.

If you’re somewhere on the off-ramp and not sure what to externalize next, subscribe. Next Friday I’ll break down the fractional operator stack that runs Stage 3. Which role to add first, which to add last, and how to know when to graduate from each.

Share

Footnotes

1. Jason Lemkin, SaaStr. His surveys put the first VP of Sales failure rate near 70 percent within the first year. See The Top 10 Mistakes Founders Make When Hiring Their First Sales Team and Why First Time VPs of Sales Fail. ↩

With Mark Roberge at the GTM Leader Society Sales Leader Breakfast. April 29, 2026, San Francisco.

Yesterday was one of those days where I could feel two different parts of myself lighting up nearly at the same time.

The learner.

And the builder.

Not the imposter LinkedIn version of those words.

Not “lifelong learner” as a personality bumper sticker.

Not “builder” as a way to cosplay startup energy.

I mean the actual thing.

The part of me that wants to sit in a room, listen hard, absorb patterns, ask better questions, and understand how people who have done the thing actually think.

And the part of me that wants to take a messy, real-world problem and start sketching architecture on the back of a napkin until something useful begins to appear.

Yesterday I got both.

And I loved it.

Morning. The learner room.

I started the day at the GTM Leader Society, hosted at Kearney by AJ Gandhi, Madeline Wallace, and Scott Edmonds, for the book launch of Mark Roberge’s The Science of Scaling. The room was full of CROs and GTM operators.

You are not just “learning about AI.” You are not just “building with AI.” You are becoming the kind of person who can move between abstraction and execution.

Different room from what would come later in the day.

Different energy.

Same underlying question.

How do you take something that is working and scale it without breaking it?

Roberge’s argument runs straight through it.

Product-market fit. Then go-to-market fit. Then growth and moat.

Three sequenced stages.

Each one earned, not assumed.

Each one measured, not felt.

Roberge walking the room through “The GTM System.” A reminder that scale is not a vibe. It is an architecture.

The discussion had this lively Harvard Business School lecture feel to it.

Not passive.

Not fluffy.

Actual GTM operators debating concepts that matter:

What breaks as companies scale.

How revenue systems mature.

How CROs think about repeatability.

How leaders separate signal from noise.

How go-to-market stops being heroics and starts becoming science.

“The Science of Scaling.” A small wink from the universe. The entrepreneur Roberge profiles in his introduction is also named Doug.

I cracked it open right after the breakfast.

Roberge’s introduction profiles an entrepreneur. Coincidentally also named Doug.

I will take that as a sign to keep going.

Afternoon. The build room.

Then the day flipped.

I crossed town to a builder community event called the Agentic AI Ideation Challenge, hosted by the UiPath Community.

The Agentic AI Ideation Challenge. Hosted by UiPath Community in San Francisco. April 29, 2026.

The premise was simple. Take a real use case. Apply agentic AI thinking. Design something that could actually matter.

Not a toy.

Not another “AI assistant for your inbox.”

Not another wrapper pretending to be a company.

A real operating problem.

Our use case was a charity that needed help transitioning its development department and core case management functions into a more modern operating model.

I worked the problem with two engineers, Manu and Philip.

Three people. One whiteboard. A few hours.

Hack team. Manu, me, Philip. Three people, one whiteboard, a few hours, a real problem.

And immediately, the builder part of my brain went nuts.

Because this is where AI gets interesting.

Not when it writes another mediocre paragraph.

When it starts touching the actual nervous system of an organization.

Externally, we explored architecture for outward-facing workloads.

Listening agents monitoring social media feeds.

Sentiment indicators layered onto demographic and firmographic data.

Prediction patterns around future benefactors and donors.

Models that could help the organization understand who might give, why they might give, when they might give, and what signals suggested deeper alignment with the mission.

That’s not “automation.”

That’s organizational awareness.

Internally, the work was even more important.

Enhancing governance.

Improving security.

Designing better access controls.

Supporting rigorous, compliant case management.

Creating smoother volunteer onboarding workflows.

Building systems that could help people do sensitive human work with more clarity, consistency, and trust.

And because this was not some fantasy whiteboard exercise, we also had to think about how it would be tested.

Scalability.

Agentic AI Unit Economics.

Resilience.

Security.

The boring words that separate a demo from something that can actually survive contact with reality.

That is the builder high.

Taking ambiguity and forcing it into shape.

Taking a real human institution with constraints and history and risk and saying:

“Okay. What would actually make this better?”

Some of the Agentic Ideation Challenge crew. Builders, hosts, and the UiPath team that ran the room.

The two rooms were closer than they looked.

There is a quiet thread connecting the two events.

And I kept thinking about how rare it is to spend one day in both modes.

In one room, I was learning backward from pattern recognition.

In the other, I was building forward from first principles.

One part of the day was:

“Here are the patterns from people who have scaled. Understand the system.”

The other was:

“Here is a messy problem. Design the system.”

And the more I build, the more I realize those are not separate muscles.

They are the same muscle trained from opposite directions.

Naval Ravikant calls the builder side specific knowledge.

The kind that cannot be taught, only learned. Built up by following real curiosity into real work, then getting feedback from reality.

Roberge calls the learner side earned scale.

The kind that cannot be assumed, only proven. Built up by hitting metrics that say a system is ready for the next stage.

Two different vocabularies. Same instinct.

Both refuse the shortcut.

The learner makes the builder less reckless.

The builder makes the learner less theoretical.

The learner asks:

“What has already been proven?”

The builder asks:

“What can we make true now?”

The learner studies the map.

The builder walks into the fog.

The learner respects accumulated wisdom.

The builder knows wisdom does not matter until it survives implementation.

And honestly, I think this is the zone I want to live in.

Not just consuming.

Not just executing.

Both.

Learning enough to see the deeper pattern.

Building enough to earn the lesson.

Because the world does not need more people with opinions about AI.

It does not need more people summarizing trends.

It does not need more people standing on the sidelines saying “agentic workflows” like it is a magic spell.

It needs people who can sit with a charity’s operational pain and imagine a better system.

It needs people who can understand the science of scaling and still remember that every scaled system started as a fragile little experiment.

It needs people who can move between the seminar room and the build room.

Between theory and architecture.

Between curiosity and execution.

Between learning and shipping.

Yesterday reminded me that I am happiest when both parts are awake.

The learner in me wants to understand what is changing.

The builder in me wants to participate in the change.

And the best days are the ones where I get to do both.

I walked out with a complete rethink of how revenue operations has to function in the agentic era. Two days in San Francisco. Five signal themes. One consistent message underneath all of them.

The RevOps arc is not a department upgrade. It is a full operating system rebuild.

01. Pricing Is a Product Surface, Not a Launch Decision

The session title was How (Not) to F*ck Up Your Pricing. Nobody in the room laughed it off.

The premise landed like a two-by-four. Founders decide pricing at launch. Then they defend it for three years. In a seat-based world, that was defensible. In an AI-native, usage-based, outcome-priced world, it is a slow bleed.

Think of pricing like a React component. It has props. It has state. It needs a render function. You would not write it once and never refactor it. Pricing deserves the same engineering respect as your product code.

The practical implication: RevOps needs to own a pricing operating rhythm. Instrument every deal. Run willingness-to-pay interviews every quarter. Ship at least one pricing experiment per quarter. Govern it in a monthly GTM council with product, sales, finance, and CS in the room.

Founders who miss this will keep losing 20 to 40 percent of contract value without ever seeing where it went.

02. Payments Are a GTM Decision, Not a Back-Office Chore

Founders obsess over top-of-funnel. They hire growth marketers, rebuild landing pages, and chase every inbound signal.

Then a buyer clicks Buy and hits a payment flow that looks like it was built in 2014. That is where the bucket leaks.

The Beelieve session on integrated payments made the invisible visible. Declined cards, unsupported currencies, manual invoicing, and slow reconciliation are quietly taxing every growth motion. Involuntary churn caused by failed renewals does not show up in your pipeline report. It just disappears.

Payments are the plumbing of growth. You do not notice them when they work. You notice nothing else when they break.

The fix is structural. Measure the real funnel from first touch to cash collected, not just to signup. Assign RevOps accountability for the payments surface. Report payment health alongside pipeline health. These are the same number.

03. Effective Craziness Needs an Operating System Under It

Matt Hammel put a name to the thing every founder knows but few will admit.

He called it Effective Craziness. The emphasis belongs on the first word. Early-stage chaos is a stage, not a strategy. The founders who romanticize the scramble are the ones who stall between five and twenty million in ARR.

The Quote-to-Cash spine is what separates effective from just crazy. It is the operating system that runs under the founder’s energy. Without it, your AI works great in the demo. It breaks in production. Not because the model is wrong. Because the operational spine underneath it was never built to carry the weight.

Quote-to-Cash is the spine. RevOps is the kernel. The founder still writes the apps. That division of responsibility is what makes a company scalable rather than just fast.

Geoffrey Moore was in the room. His Crossing the Chasm framework still runs underneath every serious GTM conversation in this industry. What struck me in conversation with him was how cleanly the chasm concept maps onto the hybrid GTM challenge every founder now faces. Self-serve buyers live on one side. Enterprise buyers live on the other. RevOps is the bridge.

04. The Product-Led vs. Sales-Led Debate Is Over

The session Product-Led, Enterprise-Ready ended the argument that has consumed GTM strategy for a decade.

The winners are running both motions at the same time. Modern buyers want to try before they talk. Enterprise buyers still need a named AE, a security review, and a procurement partner. Category leaders now serve both audiences inside the same company without confusing either.

Product-Led is the front door. Sales-Led is the concierge. The concierge does not yell at you in the lobby. They meet you at the right floor.

RevOps is the layer that makes the whole building feel like one hotel.

The operational requirement: a shared ICP definition, product-qualified lead scoring feeding the CRM, clear rules of engagement for when sales gets involved, and a single revenue dashboard that shows pipeline from both motions in one number.

05. Compliance Is a Growth Feature for the Agentic Era

Founders love to call compliance a “later” problem.

Later tends to arrive on a Tuesday with a letter from a tax authority you did not know existed. The Beelieve session on tax compliance for the agentic era made the stakes impossible to ignore. When AI agents transact across borders, usage becomes a taxable event in dozens of jurisdictions simultaneously.

Compliance is the seatbelt of international growth. It slows nothing down when it works. It saves your life exactly once.

The practical play: map the taxable surface of your product before your next market launch. Assign a single owner for global tax compliance inside RevOps. Treat compliance health as an uptime metric on the same dashboard as pipeline health.

The Through Line: Five Pieces. One Revenue Arc.

Every session at Beelieve ’26 was solving the same problem from a different angle.

Pricing sets the value story. Payments collect the value. Quote-to-Cash operationalizes the value. Hybrid GTM expands the value. Compliance protects the value.

That is the full RevOps arc. Five pieces. One system. Every founder in that room needed all of it.

The companies that win in the next three years will not be the ones with the best product. They will be the ones who built a revenue operating system underneath their product before the operational debt became a board topic.

Key Takeaways

• Pricing is a living product surface. Treat it like an engineering discipline, not a launch event.

• Payments are a GTM asset. The funnel ends when cash is collected, not when the trial starts.

• Effective Craziness only scales when a Quote-to-Cash spine runs underneath it.

• Hybrid GTM is the new default. Product-Led and Sales-Led are coordinated motions, not competing religions.

• Compliance is infrastructure. Automate it early or retrofit it painfully after scale.

Now I realize the harder part is keeping the story intact as it passes through a buying group.

Most teams still sell like one good champion is enough. It is not. In 2026, even a mid-market deal touches product, finance, security, legal, RevOps, and executive judgment before it closes. The rep who wins is not the one with the best pitch. It is the one who can carry one coherent narrative across many voices.

That is what multi-threaded messaging actually means. And most teams are still getting it wrong.

The real product I’m selling

Here is the honest reframe. I am not selling “sales enablement” or “professional services” or “a SaaS platform.”

I am selling clarity to product. Speed to sales. Confidence to executives. Safety to legal and security. Adoption to customer success. Proof to finance. And political cover to the champion.

The buyer does not experience my offer as one thing. Each stakeholder experiences it as a different kind of risk reduction.

Same offer. Different stakes. Different thread.

Signal before messaging

Before I write better messaging, I need better signal.

A field sales engineer I respect put it this way: do not ask buyers what messaging they want. Watch how your best customers actually bought. Observe how champions build internal consensus. Look at what information people actually use when they decide.

Stated preference gives you opinions. Revealed preference gives you the message that survives the buying process.

This matters more right now than ever. At GTC recently, Nvidia and its ecosystem partners are accelerating the AI capability curve for every technical buyer in the room. Security leaders gathering at RSA in San Francisco are updating their vendor evaluation checklists in real time. Your buyers are not static. Their mental models are shifting fast. The message that resonated six months ago may not survive the scrutiny of a newly AI-informed product lead or a freshly alerted CISO evaluating a risk issue or a vendor review today.

Do not automate a broken sales motion. Understand it first.

The Five-stage Buyer Journey, compressed

Let me walk through the buying journey with one goal: show you who matters most at each stage and what they need to hear.

Stage 1 — Problem Awareness. A trigger fires. A missed number. A board question. A churn spike. At this stage I am not selling a solution. I am helping the buying team agree the problem is real. The CEO, CRO, and RevOps leader are most active. Tie the pain to lost revenue, delay, or structural risk. Not features.

Stage 2 — Problem Understanding. The buyer starts due diligence. Product, engineering, and sometimes compliance begin hovering. This is where education becomes a sales tool. The best multi-threaded messaging at this stage feels less like persuasion and more like a map.

Stage 3 — Solution Explanation. The buyer shifts from “what is wrong?” to “how could we fix it?” Every stakeholder has a different lens. Finance wants payback. Engineering wants integration clarity. Sales wants conversion lift. CS wants adoption speed. Security wants controls. This is the point where a five-slide narrative beats a forty-minute product rabbit hole.

Stage 4 — Vendor Evaluation. Finance, procurement, security, and legal arrive with full authority. This is where deals die quietly. The competitor is not always another vendor. Sometimes the competitor is internal caution.

Stage 5 — Decision Readiness. The buying group is close, but still needs political cover, timing, and internal consensus. Deals are not lost only on objections. They are lost in the gap between interest and internal readiness.

Three entry motions, same buying group

Whether you are running sales-led, product-led, or a partner co-sell, the buying committee does not change. What changes are when you enter and how much trust you start with.

In sales-led growth, multi-threading starts earlier because trust starts lower. In product-led growth, usage creates interest. It does not replace committee alignment. Too many PLG teams mistake product engagement for buying consensus. Finance, security, and leadership often arrive late and cold with real veto power.

In partner co-sell, you borrow credibility, but you also inherit agenda misalignment. A partner co-sell works best when the partner is not just opening the door, but reinforcing the same buying case each stakeholder needs to hear.

The CRO’s actual job

The CRO is not just managing reps. They are coordinating specialist-to-specialist credibility across both sides of the table.

Your CEO and CFO should map to their commercial leader. Your product consultant should map to their product lead. Your SE should map to their architect. Your security counterpart should meet theirs before the deal stalls in a questionnaire.

The modern CRO is part storyteller, part conductor, part diplomat. The job is not to push one message harder. It is to keep every critical thread in place.

How I equip the champion

The champion is not the closer. The champion is the translator.

My job is to make them look smart when I am not in the room. That means a simple narrative, not a feature deck. Objection language they can actually use. Clarity on who must say yes. A mutual action plan they can execute without me coaching every step.

A good champion is not someone who loves my pitch. A good champion is someone I have equipped to make the internal case.

Where multi-threaded deals break

I see a few patterns consistently. Messaging each persona differently but losing the core story in the process. Bringing security and legal in too late. Letting one enthusiastic stakeholder substitute for committee consensus. Over-automating before the motion is actually understood.

Add timing to the list. Conference weeks, fiscal resets, Q4 freezes, and board cycles all affect when buying groups can actually move. Knowing the operating weather is part of discipline.

The closing truth

Multi-threaded messaging is not seven different pitches.

It is one business case, translated across the real decision journey.

The old GTM model assumed a lead could become a deal if the rep worked hard enough. The modern model is different. A deal becomes real only when the buying group can move together. That is why this discipline matters. Not because buying committees are trendy. Because decisions are now social, technical, financial, and political at the same time.

That is the job. Own every thread.

Subscribe now

Which stakeholder unravels more deals in your world: finance, security, or indecision? Drop it in the comments.

He said the goal is to systematically break down audiences, choose the right data sources, decide when AI should be used versus other systems, and build differentiated tactics around that.

He talked about a future where systems ingest the full universe of customer conversations, detect why deals are won or lost, and trigger re-engagement automatically when the reason changes.

On Thursday in Oakland, I joined builders and we wired up agentic assistants in real time at The Penthouse Heist, a STAK Ventures hackathon. DigitalOcean and HLOS.ai gave us infrastructure. We dove into OpenClaw integrations and tools connected to messaging platforms inside of hours.

The energy in that room was real. The optimism was contagious.

Two different rooms. One shared lesson.

AI is not your foundation. It is a stress test of your foundation.

My takeaway? If your revenue forecast is fuzzy, your handoffs between persons or teams are messy, and your data model is weak, more AI will not fix the problem. It will scale the confusion faster. That is what Week 3 of this series is about. The Foundation Fix.

Signal #1: You are automating activity before you understand the audience

Kareem made a point that I keep turning over. He said Clay’s differentiator is not a gimmick feature. It is the discipline of learning to think about GTM systematically. Who is the audience? What data sources matter? When should AI be used and when should it not? He described his firm:

Clay is built to help companies remove every obstacle to growth by understanding who the customer is and how their products connect to different audiences over time.

What strikes me is how rare that clarity actually shows up in practice. Most teams I talk to want AI outreach before they can clearly define ICP by product, moment, pain, and trigger. They are automating on top of mush.

Jordan Crawford pushed back in that room, noting that founders often need to eat their vegetables first, meaning actually study customers before reaching for tools. Kareem agreed. His answer was not to reject AI but to build systems that ingest first-party and third-party signals and improve based on feedback.

This is not a tooling gap. It is an audience clarity gap, and AI makes it worse before it makes it better.

Signal #2: You have speed but no operating rhythm

The hackathon was exhilarating. Builders can now stand up capable agentic systems faster than most GTM leaders realize. But the thing I kept coming back to, watching team after team sprint through demos, is that speed without rhythm becomes what I call random acts of heroism. A brilliant push, a clever workaround, a result nobody can replicate next week. It’s like the Doctor of OpenClaw.

RevOps leaders do not get paid for horsepower alone. They get paid for lap times, repeatability, and staying on the track. The model I kept imagining to sketch in my notes that evening was straightforward: bound by physics of progress, a focus on outcomes, a repeatable daily rhythm, leading indicators instead of lagging ones, output goals that are visible before the quarter ends, and a disciplined routine that does not depend on who showed up inspired that morning.

In my personal rhythm, the morning is for proactive creation and prospecting. Midday is for validating assumptions and removing blockers. Evening is for settling decisions, learning, reflecting, and resetting. That is not glamorous. There are other time period cadences. But it is a personal example of what separates a GTM machine from a GTM moment.

Velocity without cadence is not scale. It is adrenaline.

Signal #3: Your system cannot learn from feedback

This is where Kareem’s product vision hit me hardest. He described Clay’s direction as moving toward systems that ingest the full universe of customer actions and conversations, understand why deals were won or lost, help teams find the right customers, and improve tactics through both human and automatic feedback loops. The specific example he gave was an agentic system that detects a lost-deal reason, watches when that reason changes in the market, and triggers re-engagement automatically.

That is a vivid picture. It is also completely out of reach if your CRM reason codes are garbage, your call data is trapped in a tool nobody reviews, your pipeline stages are cosmetic, and your signal model shifts every quarter based on who is running the forecast.

The best AI system in the world cannot learn from a GTM organization that does not know what good looks like.

The Foundation Fix Framework

Before you buy the next AI tool, score your GTM foundation against these five tests.

Audience truth. Can you define who buys, why they buy, when they buy, and what changed to make them ready? Not as a slide. As a working model your team uses.

Signal discipline. Do your first-party and third-party signals actually map to revenue decisions, or are they interesting data points with no clear action attached?

Operating rhythm. Do you run on a daily and weekly cadence with leading indicators and defined output goals, or do results depend on who had a great week?

Feedback loop. Can your system learn from wins, losses, objections, and timing shifts? Is that learning automatic, or does it require a quarterly offsite to surface it?

KPI integrity. Do your forecast, pipeline, conversion, and expansion metrics reflect reality? Or are they optimistic by default and explained away after the quarter closes?

Clay showed me what a GTM system looks like when it is built on all five of these. The hackathon showed me what happens when talented people have speed, tools, and energy but are building on top of an unclear model. Both rooms were full of smart people. The difference was foundation.

Before You Add More AI, Fix This

AI is not replacing the need for GTM foundations. It is making weak foundations impossible to hide.

The companies that win this cycle will not be the loudest about agents. They will be the clearest about audiences, rhythms, signals, and feedback. Better AI will help. Better foundations will compound.

If this helped you see your GTM system more clearly, subscribe to follow the full four-part series on AI sales orchestration.

Subscribe now

If you are building the operating layer beneath AI, my book 21 Keys to AI Orchestration gives you the management lens for doing it on purpose.

And if this piece reminded you of someone wrestling with forecast drift, pipeline mess, or AI overload, share it with them and tell me in the comments: which crack in the foundation shows up first in your business? Audience confusion, rhythm breakdown, or feedback failure?

Most CROs I talk to are facing the same pressure right now.

Grow revenue. With last year’s team.

Hiring is frozen. CAC is climbing. Sales cycles are longer. And the board still wants the number.

The constraint isn’t talent. It isn’t market. It’s capacity.

Here’s what I’ve come to believe: AI sales agents aren’t replacing sellers. They’re replacing the friction around selling. The admin. The research. The CRM updates. The endless prep work that burns 30 to 40 percent of a seller’s week.

Colin Behring said it best at a recent STAK Ventures event: “Agentic AI feels like the real movie. ChatGPT was just the trailer.”

The GTM teams that win in 2026 will treat AI agents the way smart companies already treat RevOps. As infrastructure, not as a pilot program.

The Efficiency Crisis Is Structural

This isn’t a temporary budget problem. It’s a structural shift in how revenue gets built.

Three things are true simultaneously right now:

Pipeline math is harder. Buyers are more skeptical, cycles are longer, and conversion rates are under pressure across the board.

CAC is climbing. More touches, more content, more tools. And the cost to acquire each customer keeps going up.

Headcount growth is constrained. Even companies with strong balance sheets are cautious about adding quota-carrying reps.

In Week 1 of this series, I wrote about System Authority. How GTM teams earn trust through signal and consistency. Week 2 is about what comes next: capacity and throughput.

Sales capacity is the new growth lever. And AI is the only way to expand it without expanding headcount.

What the STAK Panel Got Right

The STAK Ventures event brought together founders, operators, and investors who are building and deploying AI in real businesses. A few insights landed hard.

Colin Behring: The Productivity Explosion

Colin shared a real number. In just a few days, AI agents completed roughly 275 hours of work inside his organization. Not hypothetical. Not projected. Done.

That’s the equivalent of multiple full-time employees. In days.

For GTM, translate that into pipeline research, CRM hygiene, proposal generation, and reporting. These are the tasks eating your sellers alive. Agents reclaim that time and redirect it toward revenue.

Marcus Sawyerr: The Zero-Admin Company

Marcus has a simple mission: remove all the admin.

His OTT framework: Objective, Tasks, Tools is as clean as it gets. Start with the outcome you want. Then orchestrate agents to handle the repetitive work underneath it.

Salespeople should be focused on relationships, discovery, and negotiation. Everything else is a candidate for automation. Marcus is proving that’s not a fantasy. It’s operational now.

Edward Irby: Agents Are Only As Good As Their Tools

Edward made a point that every GTM leader needs to hear. Agents don’t operate in a vacuum. At You.com, the team invests heavily in search APIs, research APIs, content crawling, and evaluation frameworks, because the output quality of an agent depends entirely on what it’s connected to.

For revenue teams, that means your agents must be wired into your actual revenue stack: Salesforce, HubSpot, Gong, LinkedIn, enrichment tools. Agents become RevOps extensions. Disconnected agents become expensive experiments.

Hans Sandhu: Outcomes, Not Science Projects

Hans brought the business lens the room needed. Too many AI deployments inside companies are still science experiments. Interesting demos. No commercial impact.

For revenue teams, the outcome is simple: more pipeline, lower CAC, higher seller productivity. Every agent deployment should map back to one of those three. If it doesn’t, it’s a distraction.

The AI Sales Orchestration Framework

Most companies are deploying AI randomly. Winning companies are deploying AI orchestration.

This is the core thesis behind 21 Keys to AI Orchestration. It applies directly to GTM.

Here’s the four-layer framework I use with clients:

Layer 1: Signal Agents continuously monitor for buying intent. Hiring surges, funding rounds, product launches, regulatory shifts. The kind of real-time signal that used to require a full-time analyst. Now it’s automated and always on.

Layer 2: Research Agents build the account brief. Company analysis, competitor landscape, leadership profiles, financial signals. What used to take an SDR two to three hours per account now happens before the rep opens their laptop.

Layer 3: Outreach Agents draft personalized outreach. Like emails, LinkedIn messages, account hypotheses, all based on the signal and research layers. The seller edits and sends. Human judgment on top of machine throughput.

Layer 4: RevOps Agents update systems automatically. CRM entries, opportunity summaries, forecasting inputs. The administrative drag that kills seller momentum disappears.

A rep running this stack doesn’t perform like one rep. They perform like three. That’s not an exaggeration, but it’s basic capacity math.

Why This Changes the Equation for Founders and CROs

Historically, scaling revenue meant one thing: hire more people. More SDRs. More AEs. More RevOps headcount.

That model is breaking down. The question isn’t how many people do we need, but it’s how much revenue can each person produce?

AI orchestration changes the denominator. A team of five sellers, properly equipped, can perform like a team of fifteen. Hans Sandhu put it simply: the future isn’t SaaS alone. It’s outcome-driven AI systems.

For GTM leaders, that outcome is direct: more revenue per employee.

The Builders Advantage

At STAK Ventures, the room was full of builders. Founders, operators, investors who aren’t waiting to see how this plays out.

Marcus Sawyerr captured the moment well: reinvent what we thought wasn’t possible.

That’s exactly where GTM leaders stand right now.

The companies that win in 2026 won’t have the most salespeople. They’ll have the best sales orchestration systems.

Subscribe to GTMSoS for the full series. Pick up 21 Keys to AI Orchestration if you want the framework in depth. Week 3 is coming.

Post more. Show up more. Be more “visible.”

Wrong.

Authority is a system problem. And until you solve the system, you’re just adding noise to an already noisy world.

Here’s the truth about buyers and investors that they already know: they don’t reward loud. They reward certainty. Certainty doesn’t come from charisma. It comes from evidence, delivered consistently, inside a repeatable machine.

That machine is what I call System Authority.

This is Week 1 of the Search-First GTM Authority series, and it’s the part most founders and revenue leaders skip, because it feels like homework. But it’s the key part that works.

Authority Isn’t Vibes. It’s Reduced Uncertainty.

I was listening to one of the founders recently where someone described their goal as building “the most trustworthy brand in an untrustworthy space”, and that a culture of trust and transparency “facilitates velocity.”

That’s not marketing copy. That’s an operational insight.

When trust is high, everything accelerates: decisions, closes, partnerships, referrals, hiring. Even fundraising. Friction disappears when people feel safe choosing you.

So here’s my working definition:

System Authority is the set of artifacts and behaviors that make other people feel safe choosing you, at the exact moment they’re looking for help.

Search-first just means those artifacts are findable when someone is already searching for the answer you have.

What System Authority Is (and Isn’t)

Let me be direct about what this is NOT:

• Posting every day with no strategic spine

• “Thought leadership” that never becomes a process

• A personal brand with no receipts to back it up

System Authority IS:

• A documented GTM Operating System, how you actually win

• Proof that it works, why anyone should believe you

• A publishing engine that turns your system into searchable answers

This is why content alone fails. You can’t scale trust on fluff. The goal isn’t massive inbound on Day 1, it’s building a place people can find, where they learn to know, like, and trust you. That place becomes your trust-building machine.

The 4 Assets That Create System Authority

1. Your POV: Category and “Why Now”

One clean sentence. What you do, who you do it for, why it matters right now. No nine-word soup. No “AI-powered synergy.” One sharp claim that a buyer can repeat to their boss without you in the room.

2. Your Process: The Operating System

This is the missing piece for most GTM consultants and revenue leaders. They have opinions. They don’t have a system.

System Authority requires you to name and document: how you diagnose, how you prioritize, how you execute, how you measure. If your buyer can’t explain your methodology without you present, you don’t have a system yet. You have a conversation.

3. Your Proof: The Receipts

A founder I heard described the “perfect environment” for building authority as being at a conference where a credible operator publicly validated results in real time. That’s the point: third-party proof collapses doubt faster than anything you say about yourself.

Proof is numbers, case studies, before/after scenarios, repeatable patterns across clients, public references. If you have it, show it. If you don’t have it yet, your Week 1 job is to go get it.

4. Your Publishing Engine: Search-First Distribution

Search-first means you publish answers to questions your ICP is already asking, not top-of-funnel awareness plays, but high-intent searches:

• “GTM strategy for B2B SaaS”

• “sales operating system template”

• “how to find PMF without hiring a full team”

Your system drives the content topics. Not the other way around.

Investor Reality Check: What They’re Actually Optimizing For

I dug into the backgrounds of the investor panelists for this cohort. Here’s the translation:

Karen Sheffield (Pachamama Ventures): Climate tech with corporate demand and partnership potential as the scaling path. Not consumer vibes, provable B2B impact.

Chima Osuka (Suncoast Ventures): Early-stage healthcare, specifically “critical gaps” with real-world impact. Not sci-fi. Not someday. Now.

Yoon Choi (Muirwoods Ventures): Cross-border, mobility/automotive DNA. Long cycles, deep enterprise relationships.

Jason Miles (Amenti Capital Partners): Connected mobility and digital ecosystems. Founders who understand enterprise sales reality, not founders who think enterprise means “a bigger SMB.”

Radu Skutaru (VU Venture Partners): Global, multi-stage, multi-sector across Consumer, Enterprise, FinTech, Healthcare, and PropTech. Deal flow at scale with selectivity.

Danil Kislinskiy (GGW Ventures): Software-focused syndicate. Later-stage lean, late seed/Series A+ with an ARR bar. Not idea stage.

The common thread: investors aren’t buying cool products. They’re buying systems that turn risk into probability.

The Bottom Line

Week 1 of Search-First GTM Authority is not “post more.”

Week 1 is build a system worth finding.

That’s what we’re doing at GTM SoS.

→ Subscribe to get the rest of the series, including the templates that turn this into a machine.

Subscribe now

→ And if you want the system in a book, read my 21 Keys to AI Orchestration, built to help you turn strategy into repeatable execution, and to make sure when someone searches for the GTM answer you already have, they find you.

Doug Skinner is a GTM strategy and AI orchestration consultant with 40 years in enterprise technology. He works with VP Sales, Revenue Leaders, Founders, and CROs who are ready to stop adding AI tools and start building AI-driven GTM systems.

I wasn’t there to pitch. I was there to listen.

And what I heard underneath the startup energy and investor Q&A were five uncomfortable truths about GTM that most founders acknowledge but very few actually operationalize.

If you follow GTMSoS because you’re wrestling with how to build revenue motion that actually scales, this one’s for you.

Trend 1: Constraints Aren’t a Limitation. They’re the Cheat Code.

The founders moving fast in this environment are not the ones with the most resources.

They’re the ones who’ve decided what they won’t do.

Time. Money. Focus. Headcount. The founders I watched hold the room weren’t paralyzed by infinite options. They were liberated by finite ones.

Constraints force the only thing that matters early: clarity. And clarity is the precondition for any GTM motion worth running. You can’t orchestrate what you haven’t defined. This isn’t a philosophy, but an operating principle.

Trend 2: The Room Is the Product

Brian said something that made half the room laugh and the other half exhale:

“How many of you are founders? … How many of you are lost? You’re not alone.”

That’s the real value of proximity, being near people who have already paid the tuition you’re still paying.

For GTM leaders, this translates directly: the network you’re in shapes the intelligence you have access to. A strong VC or operator network doesn’t just give capital or introductions, it gives context. What “fundable” looks like right now. What customer acquisition motions are actually working. What’s theater and what’s signal.

If your peer group isn’t challenging your assumptions, you need a different room.

Trend 3: A Deck Is Not Conviction

AJ Thomas, one of the investors in the room said something I’ve been thinking about ever since:

“I look at four things. The first is humans, then opportunity, then product, then deal. What I look for is there a humility and audaciousness in the approach?”

She describes it as ‘Humbitiousness’ energy.

That’s a reminder a lot of revenue leaders need too.

A pitch deck is not conviction. Conviction sounds like:

“I’ve lived this problem. I know the wrong fast.”

It’s not polish. because it’s pattern recognition earned in the field.

In my GTM work with sales leaders, I see the same failure mode: teams mistake activity for insight. Cadences for conviction. CRM entries for customer understanding. The founders and sellers who win have specificity. They know their ICP’s exact pain, and they can name what they’ve tried that didn’t work.

Trend 4: AI Is Not a Feature. It’s the Environment.

This is where I want to push past the event recap and give you the straight take.

Danil Kislinsky put it plainly:

“Use AI to run your own diligence first. Interrogate your pitch the way an investor would. Ask the uncomfortable questions.”

That’s correct, but it’s the minimum viable use of AI.

What I see in my AI Orchestration work is that most sales and GTM teams are still treating AI as a productivity layer: faster emails, quicker research, cheaper content. That’s not orchestration. That’s automation cosplay.

The shift worth making: use AI to compress the feedback loop between GTM hypothesis and market signal. Not to produce more, rather to learn faster. Tighter positioning. Faster message testing. Sharper ICP validation. AI doesn’t replace the GTM motion. It accelerates the reps.

And macro context matters here: money is flooding into AI, and investors are openly worried it’s becoming overspend. The founders (and revenue leaders) who survive this cycle will be the ones who can answer:

“How do you create ROI with AI, without being a science project?”

That’s the question my “21 Keys to AI Orchestration” is built to answer. If you’re not already thinking in systems instead of tools, you’re behind.

Trend 5: GTM Means Give-to-Market First

The best conversations in the room weren’t about growth hacks. They were about distribution choices.

Community. Partnerships. Content with a point of view. Outbound with a thesis, not a template. Product-led motions that earn trust before they ask for conversion.

AJ reframed it cleanly: GTM doesn’t just mean “go-to-market.” It means give-to-market.

The room was shifting visibly away from “raise → hire → spray.” The motion that’s working right now is simpler and harder:

Get signal → run tight sprints → earn the right to scale.

That’s the GTM Tab-Killer motion I’m building and testing in public right now. Pick an ICP. Sharpen the message. Ship the motion. Talk to customers. Repeat. No theater. No spray.

Write Your Own Genre

Are VC-funded startups dead, or are they a mystical genre where too many founders are trying to write inside someone else’s, when they should be writing their own?

Currently, with AI hype and AI skepticism rising simultaneously, the founders who survive won’t be the ones with the prettiest deck. They’ll be the ones with:

• Constraints that force clarity

• Distribution choices, not spray

• Real customer pull

• A community that keeps them in the game

The journey is still what it’s always been: twists, obstacles, uphill grade. But it’s a hell of a trade if you want your aspirations realized.

Shoutout to Brian Sparkes and STAK Ventures for building a room that actually moves the needle, not just name tags.

Next issue: I’m running a live GTM sprint right now. Picking ICP, sharpening message, shipping motion, measuring signal. I’ll be sharing the reps in public here on GTMSoS. Subscribe if you want the unfiltered iteration log.

If you were at STAK on February 18th, drop a comment. I’d love to hear what hit you hardest.

Let me tell you the exact moment I learned “alignment” isn’t a soft skill.

A Founder leaned over to the CPO right before a board meeting and whispered:

“Slides 8-10 are too busy. Can we just present 8 with the OKRs?”

He wanted to announce a win: “We launched a new app for a segment.”

Instead, he had that sinking feeling:

We were going to miss the public launch.

And the sick part?

The team looked busy.

Kanban board glowing. Burndowns “healthy.” Sprint ceremonies tight. Cards flying out of the factory like we were printing outcomes.

But reality didn’t care.

Because go-to-market objectives weren’t pulled into the dev lifecycle early enough, so we weren’t shipping outcomes.

We were shipping motion.

The lie we tell ourselves: “We just need to move faster.”

Most teams say they want to “move faster.”

What they really mean is:

“We want fewer surprises.”

Here’s the missing translation layer:

• Builders reduce surprises by turning ambiguity into systems.

• Business leaders reduce surprises by turning systems into outcomes with constraints and a decision cadence.

One-liner that stings because it’s true:

The gap between “great engineering” and “great business” is rarely talent. It’s translation.

Now… here’s why the Iceberg ecosystem is such a good case study.

Because every one of the six speakers at a recent developer event showed me a different version of the same truth:

“Shipping outcomes” is mostly about making constraints explicit, then building the system so the business can actually sell and operate it.

AI Strategy Theater: the fastest way to waste a year

AI projects don’t die because “the model wasn’t good enough.”

They die because:

• the data is dirty

• ownership is unclear

• the workflow isn’t integrated

• nobody agrees what “done” means

So, leadership panics and does the modern ritual:

They buy another tool.

Congrats. You didn’t fix the system.

You upgraded your chaos into automation theater.

The Iceberg talks were basically six different ways of saying:

“Stop doing theater. Start doing physics.”

RisingWave “Ship the upside, name the dragons.”

If you want builder energy in one slide, it’s this:

RisingWave integrated Apache DataFusion as a batch query engine for Iceberg workloads and saw 5–10× query speedups without tuning (and ~24% average speedup across 22 queries) and then immediately hit memory constraints that forced spill-to-disk + planner work.

That’s the point I wish every GTM leader understood:

You don’t get “speed.”
You get speed + the new bottleneck.

And the best teams don’t hide the bottleneck.

They productize it.

OLake “Ingestion is not a feature. It’s the foundation.”

OLake’s talk was basically a public service announcement:

Iceberg doesn’t save you if your ingestion is garbage.

At terabyte scale, ingestion must be high-throughput, lightweight, scalable, support full load + incremental + CDC, and guarantee exactly-once behavior, while avoiding the small-files / bloated-metadata death spiral.

That maps directly to the “fewer surprises” thesis:

Bad ingestion creates surprise bills, surprise latency, surprise “why is the catalog on fire?”

Good ingestion is alignment, disguised as plumbing.

Ryft “Time travel is cute until snapshot retention bankrupts you.”

Iceberg snapshots enable time travel and rollback…

…but with streaming ingestion + frequent commits + compaction, you can generate thousands of snapshots per day, and retention becomes expensive fast.

Ryft’s capability: intelligent snapshot management using time-aware retention models, high-resolution snapshots for recent history, calendar-aligned restore points for long-term recovery, leveraging Iceberg’s tagging semantics so retention becomes predictable and operationally sustainable.

Translation to GTM outcomes:

If you can’t control operational cost and recovery posture, you don’t have a product.

You have a demo.

Datastrato (Apache Gravitino) “Iceberg REST is not production-ready until identity + governance exist.”

This was the most important “grown-up” talk in the set:

Iceberg REST Catalog helps decouple compute from storage, but production teams hit the wall on security and governance, especially in multi-tenant lakehouses.

Datastrato’s capability (via Gravitino): making Iceberg REST production-ready with authentication, fine-grained access control, auditing, and secure credential vending, and doing it in a way engines like Spark/Trino/Flink can connect without custom forks.

Translation to the main script:

This is what “done” looks like.

Not “it works on my laptop.”

It works with identity, policy, and accountability.

Dremio “The fastest way to stall shipping is making everyone fight over where data lives.”

Alex Merced framed the real bottleneck perfectly:

Projects slow down when data sits in silos. Teams need quick access to current data without complex pipelines, and federation + virtualization create a unified logical layer over disparate systems.

Dremio’s capability here: query federation + data virtualization over Iceberg (and beyond), reducing the cognitive load of “where is the data / what can I access,” so more of the org can use the same data without a religious war over tools.

Translation to alignment:

If every roadmap item requires a bespoke data movement project first, you’re not “moving fast.”

You’re cosplaying as a product team while doing ETL therapy.

VeloDB (Apache Doris) “Stop rebuilding silos for AI. Use hybrid retrieval on shared data.”

Kevin Shen hit a problem almost everyone is recreating right now:

We adopted lakehouses to share data… and then for AI we revert to old behavior: copy data into a new system, worry later, and recreate silos.

VeloDB’s capability (via Apache Doris): serving diverse query patterns by combining high-performance SQL analytics + full-text search + vector search (hybrid search), plus query acceleration and materialized views on open Iceberg data to make analytics and retrieval cheaper and faster.

Translation to the “AI Strategy Theater” section:

If your RAG system needs a second copy of your truth, you’re not building intelligence.

You’re building lag, cost, and inconsistency.

So, what’s the throughline?

Each speaker attacked a different “surprise generator” that kills shipping:

• Performance surprises → RisingWave (DataFusion-powered Iceberg analytics)

• Ingestion/correctness surprises → OLake (Iceberg-native CDC + exactly-once + scale)

• Retention/cost surprises → Ryft (time-aware snapshot management)

• Security/governance surprises → Datastrato/Gravitino (identity-aware Iceberg REST)

• Access/silo surprises → Dremio (federation + virtualization over open formats)

• AI freshness + retrieval surprises → VeloDB/Doris (hybrid search on shared lakehouse data)

Which brings us back to the original thesis:

Most teams don’t need more motivation.

They need fewer surprises.

And fewer surprises come from systems that encode constraints, not decks that promise vibes.

Closing

If you’re a founder or product leader and your “AI strategy” currently feels like:

• more tools

• more meetings

• more Slack threads

• and the same shipping pain…

You’re not alone. You’re just in AI Strategy Theater.

I write about how to close gaps by aligning engineering reality with GTM outcomes without turning your company into a bureaucracy.

Subscribe now

If that’s your world, subscribe so you don’t miss the next post.

If you’re a Vice President of Sales in 2026, you’re battling physics, not feelings.
91% of sales orgs missed their targets last year. Forecasts are falling apart. Pipelines are decaying. CRM data is rotting faster than reps can update it. Reps are burning out, culture is fraying, and every board conversation now begins with:
“Why can’t we predict anything?”

What we’re facing isn’t a rep problem.
It’s not even a talent problem.
It’s a systems problem.

And the only leaders escaping the gravity well are the ones who have embraced a new identity:

The Autodidactic Orchestrator is a VP who learns, adapts, and compounds faster than the dysfunction surrounding them.

This article is your blueprint.

The Autodidact Operating Model: The New VP Superpower

Opinions I read in LinkedIn introduce the concept of the Autodidactic Operating Model arguing that the highest-value workers in modern enterprises are:

• self-directed

• self-upgrading

• self‑synchronizing across functions

• able to harness tools without permission or waiting for enablement

In 21 Keys to AI Orchestration, I argue the same truth from another angle:

The leaders who win are the ones who can orchestrate beyond just manage data, teams, tools, incentives, and signals.

The two models snap together like puzzle pieces.

An Autodidactic VP of Sales is someone who:

• learns faster than the market shifts

• composes systems instead of chasing tools

• sees signals others miss

• blends human + machine capabilities for asymmetric performance

• never waits for permission to fix what’s broken

This is how you escape the quota crisis.

The 7 Pain Points Choking GTM (and Why AI Alone Won’t Save You)

The VP Sales file makes it painfully clear: the problems killing revenue today are structural. Each one maps directly to the orchestration principles in the book.

3.1 Forecasting Collapse

Forecasts are consistently unreliable because they’re built on:

• weak predictive infrastructure

• rep‑assigned probabilities severed from reality

• ignored early danger signals

Chapters from the book, tie‑into these pains:
“Foundation First,” “Signals Over Spray,” and “Data is Culture” are three chapters of my book that relate to the point of forecasting.

Autodidactic move:
Build a personal predictive signal stack instead of relying on CRM fields.

3.2 Quota Attainment Freefall

Average attainment is now 43% .
This isn’t a motivation problem. It’s math.

“Human + Machine” is a chapter from my book that ties into this pain because quota failure is a misallocation of human effort.

Autodidactic move:
Construct your own Quota Realism Index using historical, TAM (or TRM - total relevant market), and deal velocity.

3.3 Rep Turnover at 35%

The hidden cost is not the $115K (or whatever it is) per rep replacement number .
It’s the lost 60–90 days of pipeline momentum that disappear during transitions.

“Future Ready Means People‑Ready” is a chapter from my book that connects into this pain.

Autodidactic move:
Redesign coaching from performance evaluation → performance enablement.

3.4 Pipeline Decay & Stalled Deals

55% of revenue loss is because deals get stuck .
Not lost. Not competitive. Just… idle.

“Blueprint Beats Buzz,” and “Stakeholder Power” are a couple chapters from my book that link into these points.

Autodidactic move:
Build deal‑health models based on engagement signals, not deal stage.

3.5 CRM Data Rot

76% of CRM data is inaccurate or incomplete .
You cannot run AI on garbage.

“Governance = Speed,” “Data is Culture,” “Playbooks, Not Pilots” are three chapters of my book that relate to the point of data rot.

Autodidactic move:
Create personal and team‑level Data SLAs.

3.6 Territory Misalignment

Uniform quotas on non-uniform territories = silent sabotage.

“GTM Alignment” is a chapter from my book relating.

Autodidactic move:
Run micro‑TAM analysis monthly instead of yearly.

3.7 Time Management Collapse

Your reps spend 70% of their time not selling .
This is the silent killer of every sales organization.

“Momentum Flywheels,” and “Human + Machine” are a couple chapters from my book that mesh with the time self management element.

Autodidactic move:
Implement agentic automations that reclaim 5–15 selling hours weekly.

Why the Solution Isn’t AI Tools. It’s AI Orchestration

Every VP has tools.
Almost none have orchestration.

Orchestration is the ability to unify:

• data

• human judgment

• signals

• systems

• governance

• enablement

• process

into something that compounds.

Inside 21 Keys to AI Orchestration, these show up as:

4.1 Foundation Before Innovation

Broken data → broken GTM.
Chapter 2’s mantra: clean pipelines beat clever models.

4.2 Signals Over Spray

Intent signals > activity volume metrics.
Chapter 7 shows how a 40% increase in conversions came from reading the right signals.

4.3 Humans + Machines = Multipliers

Machines should remove admin burden; humans elevate strategy.
This synergy is real and measurable.

4.4 Governance = Speed

Guardrails (SDLC, compliance packs, audit trails) accelerate adoption.

The Autodidactic Application of the 21 Keys to AI Orchestration Book

Here’s how modern VPs apply the Autodidactic Operating Model directly to the orchestration keys.

5.1 Self‑Directed Learning → Literacy is a Growth Driver

Your teams upgrade only after you upgrade.
In the book, the “Dashboard Jedi” and “AI Skills Fest” examples show how literacy accelerates revenue velocity .

5.2 Self‑Correction → Momentum Flywheels

Small wins → bigger wins → cultural flywheels (Chapter 18).

5.3 Self‑Trust → AI Mindset

Reps trust AI when leaders model transparency (Chapter 1).

5.4 Self‑Alignment → Orchestrator‑in‑Chief

Cross-functional alignment = revenue velocity (Chapter 9, 10).

The Autodidactic VP’s Revenue Engine (Blueprint)

This is the template I see separating winners from laggards across SaaS, logistics, security, and services:

Layer 1 Mindset

• AI as co‑pilot

• Transparency over black boxes

• Curiosity over defensiveness

Layer 2 Data

• unified truth

• signal graph

• pipeline hygiene

• data stewards + SLAs

Layer 3 Execution

• next‑best‑action workflows

• deal‑health alerts

• automated QA

• GTM process governance

Layer 4 Human Layer

• literacy programs

• localized champions

• co‑creation sessions

• criticism → collaboration loops

This is how you get reps from 30% selling time → 45–50%.
This is how you go from gut‑driven forecasts → statistical predictions.
This is how you reduce rep churn and increase quota attainment.

What an Orchestrated VP Can Fix in 90 Days

These numbers come directly from the pain‑point analysis :

• +10–15% forecast accuracy

• +20–35% pipeline velocity

• +5–15 reclaimed selling hours weekly

• $2M–$5M unlocked from territory redesign

• 20–30% CRM quality improvement

This is what a VP becomes when they operate like an Autodidactic Orchestrator.

Not a firefighter.
Not a tool administrator.
Not a spreadsheet hostage.

A systems composer.

Why Solopreneurs and Fractional Operators Give VPs Unfair Advantage

VPs don’t have time, bandwidth, or internal skill sets to fix foundational GTM mechanics .

Fractional operators are the new leverage objects.

They deliver:

• diagnostic depth

• GTM orchestration capability

• data cleanup

• playbook creation

• forecasting redesign

• signal‑based selling systems

Without adding headcount.
Without adding politics.
Without waiting for annual planning.

This is the easiest arbitrage opportunity in modern GTM.

Closing: Future Ready = People Ready

The final chapter of 21 Keys states it simply :

Technology changes fast. People change slowly. Orchestration is how you bridge that gap.

Your job as a VP is no longer running deals, managing opinions, or filling dashboards.

Your real job is to create conditions where:

• humans get more powerful,

• machines handle the drudgery, and

• systems become self‑reinforcing.

Because once you orchestrate your people, your data, your process, your signals, and your tools into one flywheel…

You stop playing catch‑up.
You start compounding.

The Autodidact VP is the one who wins this era.
And your transformation starts the moment you decide to lead like an orchestrator instead of a manager.

You’ve got the keys.
Now go unlock what’s next.

Share

The Great GTM Transition

The data is stark: 92% of marketing teams report AI productivity gains, yet only 5% of companies see measurable ROI from their AI investments. This disconnect isn't a technology problem—it's an orchestration problem.

I argue in 21 Keys of an AI Orchestrator, that leaders who master AI aren't those who deploy the most tools, but those who orchestrate human and machine intelligence into systematic, scalable revenue engines.

For founders scaling from founder-led sales to delegated growth, this transition from people-based to system-based GTM represents the difference between linear scaling and exponential growth.

Web by Design announces their inaugural issue of Growth due to be released in physical form this fall.

The People-Based GTM Trap

Most founders scale revenue the only way they know how: adding people. More SDRs, more AEs, more marketing coordinators. This approach compounds both growth and costs, creating what Jacco van der Kooij calls the "SaaS native scaling trap"—where every dollar of growth requires proportional increases in headcount and overhead.

Current State:

Jacco van der Kooij of Winning by Design delivers keynote at Benchmarkit AI SaaS Metrics Executive Summit in San Francisco

The result? Founders find themselves trapped in what AJ Gandhi identifies as revenue team fragmentation—marketing generates leads, sales works them individually, and customer success operates in isolation. Growth becomes a function of hiring speed rather than systematic improvement.

The System-Based Alternative: AI Orchestration Framework

My orchestration approach transforms this dynamic by replacing human variability with systematic intelligence. The framework operates on three core principles:

1. Signal Detection Over Activity Generation

Instead of more calls and emails, system-based GTM focuses on identifying and acting on predictive signals: intent data, engagement patterns, product usage indicators, and competitive intelligence.

2. Orchestrated Decision-Making

Rather than individual rep intuition, decisions flow through coordinated intelligence that combines human expertise with machine analysis—what I call "human-AI symbiosis."

3. Compound Learning Systems

Every interaction feeds back into system intelligence, improving targeting, messaging, and timing across all future engagements.

Craig Rosenberg moderates the discussion “Leveraging AI in GTM - The ROI”

Five Critical Insights for Founder-Scale Transition

Insight #1: AI Orchestration Requires a Dedicated Leader

Brandon Redlinger's research reveals that companies with a designated "Go-to-Market Engineer" or AI leader are 30% more likely to see significant AI impact. This isn't about technology management—it's about orchestrating the transition from people-dependent to system-dependent growth.

The Orchestrator Role:

• Strategizes AI integration across GTM functions

• Designs human-machine workflows

• Measures system performance vs. individual performance

• Builds organizational AI literacy

Insight #2: Value Realization Must Be Systematized

AJ Gandhi's GTM fundamentals framework identifies value realization as a critical area where most companies rely on human judgment rather than systematic measurement. System-based GTM transforms this through:

• Automated ROI tracking and communication

• Predictive customer success indicators

• Systematic expansion trigger identification

• AI-powered customer journey orchestration

Insight #3: The Revenue Engine Becomes Multi-Dimensional

Traditional people-based GTM optimizes single functions in isolation. System-based GTM orchestrates across dimensions:

Insight #4: Advanced Use Cases Drive Real ROI

While 92% see productivity gains from basic AI (content generation, email automation), real ROI comes from advanced orchestration:

• AI Targeting & Lead Scoring: 3% more likely to report increased pipeline

• Campaign Analysis & Optimization: 5% more likely to report increased conversion rates

• Predictive Customer Success: Automated expansion identification and churn prevention

• Real-Time Sales Coaching: AI-powered deal guidance and objection handling

Insight #5: System-Based GTM Requires New Metrics

Traditional metrics (MQLs, activity volume, individual quotas) don't capture system performance. Orchestration demands different measurement:

System Performance Indicators:

• Revenue per GTM system dollar (not just per employee)

• Signal-to-conversion efficiency rates

• Cross-functional orchestration effectiveness

• AI-human collaboration quality scores

• Systematic learning speed (improvement rate over time)

AJ Gandhi leads roundtable topic of comprehensive framework for evaluating GTM efficiency and initiatives for improving performance.

Three Priority Action Items for Founders

Priority Action #1: Establish AI Orchestration Leadership

Timeline: 30 days
Investment: $120K-180K annual salary or 20% fractional engagement

Why Priority: Without dedicated orchestration leadership, AI implementations remain siloed productivity tools rather than systematic revenue engines. The 30% effectiveness boost for companies with dedicated AI leaders isn't accidental—orchestration requires intentional design.

Founder Impact:

• Accelerates time to systematic scaling (6-12 months faster)

• Reduces scaling costs (compound growth without linear cost increases)

• Creates transferable systems (reduces founder dependency)

• Builds competitive moats through systematic advantage

Implementation Framework:

1. Define orchestration responsibilities (not just AI tool management)

2. Establish cross-functional authority (marketing, sales, customer success)

3. Create systematic learning processes

4. Build organizational AI literacy programs

Priority Action #2: Implement Real-Time Signal Intelligence

Timeline: 90 days for MVP, 6 months for full orchestration
Investment: $50K-100K in tooling + integration costs

Why Priority: The gap between 92% productivity gains and 5% ROI exists because most companies optimize activities rather than outcomes. Real-time signal intelligence transforms random acts of marketing and sales into systematic revenue generation.

Founder Impact:

• Improves CAC efficiency by 25-40% through better targeting

• Increases sales velocity through predictive deal scoring

• Reduces customer acquisition costs while improving quality

• Creates systematic expansion opportunities

System Components:

• Intent data integration and scoring

• Product usage analytics for expansion signals

• Competitive intelligence automation

• Customer health scoring for retention/expansion

• Real-time deal risk assessment

Priority Action #3: Design Human-AI Orchestration Workflows

Timeline: 4-6 months for full implementation
Investment: Process redesign + team training (typically $75K-150K)

Why Priority: Most AI implementations fail because they automate existing inefficient processes rather than orchestrating new capabilities. Systematic workflows ensure AI enhances rather than replaces human expertise.

Founder Impact:

• Scales founder expertise through systematic processes

• Reduces key-person dependencies

• Improves consistency across all GTM functions

• Creates compound learning that improves over time

Orchestration Design:

The Compound Effect: From Linear to Exponential

The transition from people-based to system-based GTM creates compound advantages:

Year 1: System foundation reduces scaling costs and improves consistency
Year 2: AI orchestration begins driving systematic improvements across all functions
Year 3+: Compound learning effects create sustainable competitive advantages

Future State:

The Orchestration Imperative

My central thesis proves prescient: AI orchestration isn't about replacing human intelligence—it's about systematically amplifying it. For founders scaling beyond founder-led sales, this represents the difference between building another consultancy (people-dependent) versus building a systematic revenue engine (people-enhanced, system-driven).

The companies that master this transition won't just scale faster—they'll create sustainable competitive advantages that compound over time. The question isn't whether to make this transition, but how quickly one can orchestrate it systematically.

The 5% who achieve real ROI from AI aren't the ones with better technology. They're the ones with better orchestration.

Doug Skinner is the author of "21 Keys of an AI Orchestrator" and founder of Intentional Management LLC, helping B2B SaaS founders transition from people-based to system-based growth. Connect with him on LinkedIn or learn more about systematic revenue orchestration at https://gtmsos.com.

At Kyocera, our AI-powered change management launched with fanfare, then quickly devolved into nonsense. Different SKU codes across regions meant our analysis couldn't determine if a 40% price differential was genius or insanity. We were sailing without nautical bearings on fragmented data.

The turnaround required cultural shift, not merely technical cleanup. We make data stewardship everybody’s business. After launching our "Dashboard Jedi" program, team members could earn badges by scoring 85% on data quizzes. Badge holders hit targets 1.9x faster than peers.

Core principle: AI accelerates culture, not tools.

Foundation Before Orchestration

Most companies implement AI tools then wonder why adoption stalls. At Audit Associates, our pre-cursor AI data project was lead scoring and it generated 200% MQL growth, but sales dismissed them, because underlying data was corrupt: duplicates, outdated contacts, zero source tracking.

We launched a six-week foundation rebuild and established four pillars:

Data Quality: Named stewards with SLAs.

Access Governance: arranging dataset tiers so users know what's enriched with AI and can be trusted.

Embedded AI Literacy: Learning was tied to performance incentives. We coupled learning and the next element.

Insight Storytelling: Teaching narrative construction from data. Tiers: Management with frontline workers, and frontline workers with customers.

Only after this groundwork did AI deliver 17% conversion improvements. You can't orchestrate chaos into clarity.

The Transparency Imperative

At Microsoft's Security Partner Advisory Council, our pre-cursor product to today’s Zero-Trust rollout struggled because partners operated from different frameworks. Success came when we implemented transparent risk scoring where partners could see the logic: "This client has basic security maturity; similar patterns preceded breaches at comparable organizations."

Partners trusted our recommendations because they understood the "why," driving our multi-million-dollar new product pipeline.

Strategic insight: AI orchestration requires data democracy. When everyone operates from shared truth with explainable logic, resistance melts into collaboration.

Literacy as Revenue Acceleration

At Kyocera, sales reps initially viewed AI with suspicion until our certification program demonstrated practical value. Each 10-minute module ended with immediate application, analyzing calls for objection patterns or optimizing territory coverage.

Certified reps closed deals 2x faster with 25% higher velocity because they understood recommendations rather than blindly following algorithmic outputs.

The breakthrough: gamification with real stakes. Digital badges translated to compensation and advancement. Teams competed during Friday showcases, transforming mindset of "AI threatens jobs" into "AI fluency accelerates careers."

LinkedIn confirms companies with structured literacy programs see 31% greater productivity gains.

Operating Systems Over Tools

Data culture means reflexive data-driven decisions. At FCR Corp, our "Discount Detective" showed reps why 6% commissions were optimal versus 10%. Smaller pieces of bigger pies generate more income and revenue. This prevented pricing disputes while improving close rates 20%.

The cultural shift happens when data fluency becomes visible. At Kyocera, we embedded usage KPIs into compensation. 10% of pay tied to dashboard engagement. When competency drives career advancement, adoption accelerates organically.

Your 30-Day Implementation

Week 1: Audit one critical handoff where data breaks down, typically marketing to sales progression. Establish shared definitions: What constitutes "qualified"? How do you measure engagement intensity?

Week 2: Create stewardship accountability. Marketing owns engagement data accuracy, sales ensures opportunity progression integrity, customer success validates satisfaction metrics.

Week 3: Launch performance-tied literacy. Teams demonstrating data fluency through practical application earn recognition and compensation advantages.

Week 4: Celebrate data-driven wins publicly. When insights drive customer outcomes or revenue growth, spotlight those successes. Recognition breeds advocacy.

The Multiplier Effect

Clean data and trusted processes create compound returns. At Audit Associates, foundational discipline enabled logistics optimization saving customers hundreds of thousands while generating compelling case studies.

The bottom line: revenue alignment requires shared intelligence, not just shared goals. When marketing, sales, and customer success operate from clean, accessible, trusted data, every AI initiative builds on solid foundations.

Make data competency a promotion requirement. Transform teams from data skeptics into data stewards. Watch AI orchestration accelerate when humans trust the intelligence they're amplifying.

Doug Skinner helps B2B SaaS companies build data cultures that accelerate AI orchestration. His upcoming book "21 Keys to AI Orchestration" launches this year. Subscribe to GTMSoS for practical insights into revenue-generating systems.