SALES
Pipeline you can plan around
Outbound, inbound handoff and expansion, run as one motion.
GTM BrainFOR SALES
SEND 01SEND 05
It gets sharper with every reply and every call it reads.
CLAUDE FOR GTMPart of: Claude for GTM: how GTM teams run on Claude

AI in GTM: the five levels, and how to tell which one you are on

Five levels, from a chat tab to a Claude brain: what each one looks like, what it does well, where it stops, and how to tell which one your team is on.

Dark header with the theme From tab to brain above white tiles: a sparkles icon, a layers icon, the Claude logo and a network icon.

AI in GTM covers everything AI does across how a company finds, reaches and wins customers. We sort it into five levels: AI as a tab, a feature, a layer, an engine and finally the brain. Your level is set by what runs in production today. Plans on a roadmap do not count.

We first published the five levels as a short framework on LinkedIn. This page is the long version. For each level it covers what it looks like, what it does well, where it stops and how to tell you are there. For how we run the top level day to day, start with our hub on Claude for GTM.

AI in GTM: the five levels at a glance

The levels differ less in the tools than in who decides each output. Reading the table from top to bottom, decisions move from a person to the system, one step at a time.

What changes from one level to the next
LevelWhat AI doesWho decides each outputThe tell
1. A tabAnswers when someone pastes something inThe person who opened itNothing changes when the tab closes
2. A featureWorks inside one tool, on that tool's dataThe person using the toolEach tool's AI knows nothing the others know
3. A layerResearches, enriches and drafts inside the processA person, every timeWork waits in a review queue
4. An engineRuns a chain from a signal to a queued sendRules written in advancePeople check the system instead of doing the steps
5. The brainChooses what runs next and learns from the resultsThe system, inside limits people setEach campaign reads the results of the last

Level one: AI is a tab

What it looks like. Someone opens Claude or ChatGPT, pastes in a LinkedIn profile or a call transcript, and copies the answer back out. The process around it stays exactly as it was.

What it does well. It is fast, cheap and easy to start. A rep can rewrite an email, summarise a long thread or rehearse an objection in a few minutes. It also teaches the team what a model can do.

Where it stops. Every session starts from zero. The model does not know your ICP, your offer or what worked last month, so each person briefs it again from memory. Two reps get two different answers to the same question, and nothing is kept.

How to tell. Picture every AI subscription cancelled for a week. If the lists, the sequences and the pipeline report would look the same, you are at level one.

Level two: AI is a feature

What it looks like. The AI comes bundled inside tools you already pay for. Apollo suggests who to contact, HubSpot writes the deal summary and LinkedIn offers to rewrite a message.

What it does well. Nobody has to change how they work. Each feature runs on the data its tool already holds, so the suggestions make sense inside that tool.

Where it stops. Each tool's AI only sees its own data. The contact Apollo suggests knows nothing about the call HubSpot summarised. People still carry information between tools by hand, and every new tool adds one more AI working alone.

How to tell. List the AI features your team uses. Then mark each one that passes its output to another tool without a person copying it. If nothing on the list is marked, you are at level two.

Level three: AI is a layer

What it looks like. AI now sits inside the process itself. Clay enriches each record before it reaches a sequence. Claude researches the account and writes the first draft, and a person reviews it before anything moves.

What it does well. Quality goes up and control stays where it was. Research a rep used to do by hand arrives attached to the record, and the draft starts from it. Prospecting shows this clearly, and we cover the limits in prospecting with Claude.

Where it stops. Each draft and each list still needs a person to sign it off, so the system only moves as fast as people can review. The review step becomes the queue. The AI also forgets between runs unless someone stores what it learned.

How to tell. Look at where the work waits. If drafts and enriched lists sit in a queue, and nothing moves until a person clicks, you are at level three.

Level four: AI is an engine

What it looks like. Signals start the work. A job change triggers enrichment in Clay, the copy gets written and the lead lands in Smartlead. n8n runs that chain without anyone approving each step.

What it does well. It brings speed and consistency. An account gets worked in the week its signal fires, and every record goes through the same rules. In her version of the framework, Judith from our team marks this level with one line: "This is where GTM Engineering begins."

Where it stops. The engine runs the rules it was given and never questions them. When a segment stops replying or a signal goes stale, the chain keeps firing until a person notices. Nothing inside it asks whether the play still deserves to run.

How to tell. Look at a normal Monday. If the team spends it checking runs and fixing broken steps, rather than building lists and writing copy, you are at level four. As the original post put it: "People watch the system instead of working inside it."

Level five: AI is the brain

What it looks like. Claude sits at the centre and chooses the next job to run. Supabase is the memory, so a new campaign reads the replies and scores of the ones before it. The system reasons through who to contact, when and why, using the company's ICP, proof and past results.

What it does well. Learning adds up across campaigns. A message that failed in one segment does not get retried blindly in the next, because the record says it failed. The method lives in skills, so a fix to one skill reaches every workflow that runs it. Ours are in our library of GTM skills.

Where it stops. People stay at this level too. Strategy, spend and closing remain theirs, and so does every message that reaches a buyer. It also depends on the four levels below it, because a brain with no data and no loops has nothing to decide.

How to tell. Ask the system why it chose this week's segment. At level five it answers from its own records: the replies, the scores and the change log. If the answer only exists in someone's head, you are one level below.

What goes into one is on our GTM brain page, and the repos, loops and memory behind it are in Claude Code for GTM.

The system does the work; a person approves what reaches a buyer.
David Turewicz · Co-founder, Kinetyca

How to move up one level

Each level relies on the one below it. An engine built on drafts nobody reviewed sends those drafts faster. So move one level at a time, and start with the job that costs the most hours.

  1. 01From a tab to shared contextWrite the ICP, offers, proof and objections into one place every AI tool can read. This is the step that gets two reps the same answer.
  2. 02From features to a layerPick one job that repeats every week, such as account research or call prep. Run it inside the process, with a person reviewing the output.
  3. 03From a layer to an engineOnce reviewers stop changing the drafts, chain the steps around that job and let a signal start each run.
  4. 04From an engine to a brainStore every result, and have Claude read those results before it plans the next run. Keep sends and spend behind a person while you do it.

The first move costs the least. Matteo put it this way in his version of the post: "Same tool a lot of teams already pay for. A different job."

The AI SDR question

An AI SDR is software sold as a sales development rep. It picks the leads, writes the messages, sends them and answers the replies, with the model in front of the buyer. Salesforge, for example, sells one called Agent Frank next to its sending platform, as our Salesforge page notes.

On the five levels, an AI SDR is a level-four engine sold as a product. It runs the chain on the vendor's rules and the vendor's memory. The point of buying one is that nobody has to approve each send.

Prospects ask us about it on sales calls: are AI agents doing the outreach? On our accounts, they are not. Claude drafts, people approve, and every send stays behind a human gate.

  • Claude drafts. Sequences, follow-ups and the next reply are written by our copy and reply triage skills, and they land as drafts.
  • A person approves. Someone who knows the account reads each draft before it goes out, and edits it when the tone or the facts are off.
  • The send sits behind a gate. Claude has no way to send by itself. Campaigns wait in the sending tool as drafts until a person sets them live.

We hold that line because of what our clients sell. A low-price product with one obvious next step, such as a free trial, can take more automation. An offer that needs a conversation to scope and price cannot. One wrong reply to an interested buyer costs more than the minutes a person saves by skipping review.

Everything around the send runs on its own. Research, scoring, drafting, campaign builds and the morning read of every live campaign need nobody to start them. The person approving a draft is checking the work of the whole system, then making the one call that reaches the buyer.

What is AI in GTM?

It is the use of AI across how a company finds, reaches and wins customers: research, enrichment, copy, routing and reporting. We place it on five levels, from a chat tab someone opens to a system that decides what runs next and learns from the results.

How to use AI in GTM?

Start by writing the ICP, offers and proof into one place every tool can read. Then move one repeating job, such as account research, into the process with a person reviewing it. Chain the steps around it once the drafts stop needing edits, and keep sends and spend behind a human sign-off.

What are the best AI tools for GTM?

It depends on the level you are building. We use Claude for the reasoning. Clay handles enrichment inside outbound, n8n moves data between tools, Supabase holds the memory, and EmailBison or Smartlead and HeyReach do the sending. You do not need all of them on day one: start with Claude and add one tool per job.

Will SDR be replaced by AI?

The research, list building and first drafts of the SDR job are moving to systems. The conversations, the judgement on an interested reply and the relationship stay with a person. On our accounts a person approves every message that reaches a buyer, so the role shifts towards reviewing, replying and booking.

Do AI SDRs actually work?

For a low-price offer with a short, predictable path, a fully automated sender can do the job. For a considered offer, we would not let one send unreviewed. We take the speed from Claude drafting and scoring, and keep a person on every send to protect the buyer relationship.

FURTHER READING
David Turewicz
WRITTEN BYDavid TurewiczCo-founder and CEO, Kinetyca

Software, accelerator and startup background. Runs the GTM architecture side: how the system is designed, what it is built on, and where AI actually earns its place.

LinkedIn ↗YouTube ↗
KINETYCA GTM NEWSLETTERGet this a week early.Everything we publish here goes to newsletter readers first, along with the cases and numbers that never make it onto the site. Tuesdays and Thursdays, written by David and Matteo.
TWICE A WEEK · NO SPAM · ONE-CLICK UNSUBSCRIBE
Kinetyca GTM NewsletterNews, cases and what is actually working in GTM right now.
© 2026 KinetycaPrivacyTermsImprint
Follow the foundersDavidCEOMatteoCOO