What is GTM
product thinking?

Most GTM leaders now live in two worlds.

  • At home, a chatbot plans the family vacation in 10 minutes: the itinerary, the trains, the restaurants, everything delivered with an interactive map, a timeline and reservation confirmations.
  • At work, AI is scattered across a mess of isolated Gemini notebooks, Claude projects and endless copy-pasting of prompts and outputs.

The models are capable enough. The work is finding where AI gives your GTM the most leverage, then building an ownership model for your people, software and ops, so an AI-assisted process connects your buyers to your sellers and delivers value. This guide walks through how to think about GTM as a product, how to map the work you’re doing and the leverage it is or isn’t creating, and the right model of product ownership to transform your GTM with AI.

GTM product thinking is running GTM as a product: built around the buyer, with an owner and builders who fix it once for everyone.

Your harness

Everything between your team and your market is your harness

The harness is the SaaS you own, the connectors between it, the Slack bots, the Claude skills, the agents. Nobody bought it as one thing. It grew one integration at a time, and it decides what reaches your buyer, and how fast. Every GTM team has one, whether anyone designed it or not.

No one tool is the harness. Not Claude, not Gong, not Salesforce. The whole system is, and it’s where your AI work lands.

Our working model of AI GTM leverage

Along the bottom is what you put in: your GTM team and the harness it works through. Up the side is what it moves in your market. The line is your leverage, and it bends up at two points.

Process leverage is how your team sells. Buyer experience is what your buyer meets, and it moves the market further. Every project lifts the line at one point or both, and the lift is the project’s shape.

Process leverage

Big moves on the process side were possible long before AI. Anyone who’s ever seen an integration knows how far one can reach. When an acquisition lands well, two sales teams, two playbooks and two sets of systems become one way of selling. Leading a GTM team through a product pivot reaches as far.

Rebuilding how your team sells with AI can be just as large.

Buyer experience

On the buyer’s side, a product-led launch can change who a company sells to. When buyers can try the product on their own, the addressable market changes, not only the conversion rate.

A seller’s call-prep skill

Now look at a typical AI project. A seller writes a Claude skill that preps her calls. It feels like a lot of AI. On the model, it’s a thin wedge on the process side.

In a 2026 Gartner survey, 210 sales leaders said AI saves each seller 4.8 hours a week. That’s about an hour a day, the hour we used to get by buying dinner and asking everyone to stay late. Worth having. Is it the payoff for AI in GTM?

Gartner, 2026 Sales Productivity in the AI-Enabled Era Survey (n=210 CSOs and senior sales leaders), as presented in the keynote “Reimagining Sales Productivity in the Age of AI,” May 2026.

1mind lifts both sides

Amanda Kahlow built 6sense, then started 1mind around one question: why does a buyer wait three calls to talk to someone who knows the product? 1mind puts what it calls “a headless Solutions Engineer on every call,” an AI that answers deep technical and product questions from the first call.

The buyer, in Kahlow’s words, “gets expert depth at the first touch instead of four handoffs later.” For the team, it’s built to mean fewer handoffs, fewer meetings and deals that move faster. One product, a band across both sides.

1mind, Ride-Along, read October 6, 2026. Amanda Kahlow on Topline, July 28, 2026.

But what about the biggest opportunities?

The biggest bets take an executive

The biggest opportunities cross marketing, sales and success at once. They change who does the work, what each team is measured on and what the buyer sees. Nobody below the executive team owns all three, so the bet waits, however ready the build is.

Monaco, an AI-native sales platform, shows what that looks like. Its sellers are Forward-Deployed Account Executives. Each one owns a customer “from first outreach to signed contract and through the onboarding kickoff,” then helps that customer set up its outbound engine. Most GTM teams split that work across an SDR, an AE and an onboarding manager, each reporting to a different leader and measured on a different number. A new company can draw the job that way on day one. An established team needs an executive to redraw it.

Monaco, Forward-Deployed Account Executive (New Business), job post read October 7, 2026.

The results you get from AI match the size of the bet. The big one needs a product leader with the responsibility to deliver an outsized result and the authority to set priorities and change how the work is done. That leader owns four things a builder can’t:

  • The goal. The line in next year’s plan the bet has to move, and the number that says it worked.
  • The two experiences. How your team sells and how your buyer buys, run as one product.
  • The trade. Which work moves between teams, and whose targets, budget and comp change with it.
  • The order. What ships next, what waits, and when a change lands, usually at a plan boundary.

Builders and an owner for the harness get you a harness that works. Without the executive, it speeds up today’s job and leaves the job as it was.

Executive LeadershipWhy does AI in GTM need executive leadership?Go deeper
A dragonfly drawn as a wireframe mesh in brown line, four wings spread, an orange cell near each wingtip.

Your GTM harness is a product

Skills and systems, adding up to GTM motions your team can run on demand. Its job is to make it really easy for your team to use AI everywhere. Tools like Lovable already let anyone on your team build a working app in an afternoon. The harness makes sure what they build knows what you sell, who you sell to and how you sound.

Here’s ours, as of October 2026, in three steps.

Notes on a page, then one round of edits

A Field Guide page with three numbered notes pinned to it and a side panel listing them above a Submit button

Three notes pinned to a guide page, waiting for the agent.

We kept making pages that got 80% of the way there. Then we wanted to stop prompting and just fix them. So anyone on our team can open a page, pin a note where it’s wrong and say what they want: shorten the headline, cut the lede, rewrite an intro.

The same page mid-round: the notes marked as with the agent, and a banner saying Claude Code is taking a screenshot to check the result

Claude works through the notes and checks each edit with a screenshot.

One press sends the notes to Claude as a round. It works through them one by one and checks each edit with a screenshot.

The page after the round: a shorter headline, a three-sentence lede, and a banner summarizing what the agent changed

The round is done: every note answered, the edits on the page.

Sixty-four seconds later the page came back with all three notes answered and a summary on top. Nobody opened a chat window.

October 7, 2026

The partnership room we built for Lovable

The Fresh Context and Lovable partnership room, its Partnership tab

The Partnership tab. The plate is a Studio drawing in Lovable's colors; both marks are each company's own file.

We built it in Lovable. Lovable’s agent made the app. Our harness made it ours: their brand beside ours, drawings from our image service in their colors, and the joint plan on one page, written from the same context as everything else we make.

That’s the stretch. The harness isn’t one tool. It’s whatever your team builds with, reading the same context.

September 30, 2026

The ABM campaign for one enterprise account

Deterministic Context (Targeting), Canonical Context (Positioning) and Brand Context (Brand) each send their own stream into a round lattice labelled Harness. One stream leaves it for the Campaign Page, a web page outlined in orange whose three slots hold one piece from each source.

Three kinds of context meet in the harness and leave as one campaign page.

Then the harness goes to work on pipeline. Our ABM campaign for one enterprise account has been in market since September 24, 2026: research on the account, a point of view written for its leaders, and rooms of its own, each built from the same three kinds of context.

Targeting says who. Positioning says what. Brand makes it look like us. The harness puts all three on one page for one account, then does it again for the next.

None of the three started from a blank page. The same context and the same skills sat under each one.

Ben Thompson

An agent that “can create any app that I want on command, even if that app is only for me.”

Ben Thompson, author of Stratechery, on what comes after the app economy. “Apps, Agents, and Aggregation”, September 28, 2026.

Inside a GTM team, that’s already true. A page, a partner room, a campaign for one account: any app, on demand. What makes each one yours is the harness under it, and it has two users. Your buyer should get one clear answer at the first touch. Your team should see a new message live everywhere in days instead of a quarter.

Your harness is the code for your GTM product. Build it or buy it, and run it like a product. You can buy the parts, but the full product is your own.

Your revenue plan is your roadmap

How do you decide what to build? Every product team argues about it. Your harness already has its answer, and your team is writing it this quarter: next year’s revenue plan.

The plan says what has to be true. Time to ramp. Reps at quota. Pipeline per program dollar. Each line is an assumption. For each AI proposal, name the line it could change, the number it has to move and the teams whose work would change. A proposal that reaches no line is a tool, not a bet.

The lines are under strain. In Bridge Group’s 2026 sample, 48% of reps were at quota, down from 51% in 2024, and ramp took a record 6.2 months.

Bridge Group, 2026 (N=158).

So the plan gives the product leader a rule: build what the plan needs, measure the work against the number the plan set, and leave the rest alone. It gives the executive what an AI council can’t: one list, in order.

AI × Revenue Planning RoadmapYour plan decides which AI work gets funded.How we help

That's GTM product thinking

Individuals use AI to do the job they had before AI, a little faster. Leaders redesign the work around what AI can do. GTM product thinking is how a GTM team gets from the first to the second.

Your buyers already work with AI. So do your people, every evening.

The GTM between them is the last thing still designed for 2020.

The first company in a market to run GTM as a product stops getting compared. It becomes the comparison.

Three questions show how big your bet is

  1. Which line in next year’s revenue plan does our AI work reach, and who decided it would? If nobody can name one, the AI line in the plan is a list of tools.
  2. Of everything we shipped with AI this year, what changed for a buyer, or for how the team sells? If the answer is a few saved hours, the bet was small.
  3. Which change would cross marketing, sales and success, and who could say yes to it? If the answer is nobody below the CEO, that’s the bet waiting for an owner.

This week, pull the draft of next year’s plan and circle the assumption whose failure would hurt most. Ask which AI investment is aimed at it, which teams’ work it would change, and who can say yes. If no investment is aimed at it, that’s the first item on your roadmap, and it’s probably a big one.

Questions leaders ask

How is GTM product thinking different from GTM engineering?

GTM engineering builds the skills, automations and agent flows. GTM product thinking decides what's worth building, for whom and in what order, and owns the result. One person can do both, and a GTM engineering lead is a natural product owner. Most teams we see already have builders. Far fewer have someone whose job is to decide.

We already have an AI council. Do we still need a product leader?

Keep the council for policy, security and spend. Give the roadmap to one named person: which change ships next and what waits. A council spreads exactly the decision a product leader exists to hold, and a roadmap that needs a meeting to reorder moves at the speed of the meeting.

How do you know GTM product thinking is working?

Give every bet a baseline, a target and a review date on the plan number it has to move, such as pipeline from target accounts. Track the change for the buyer or the team that should produce it. If neither moves by the review date, the owner changes the bet or stops it.