Don't automate bad sales. Redesign it.
In two days to a named GTM bottleneck, a human-AI autonomy matrix and a system plan built around real customers, your CRM and the buying signals that matter.
Powered by the open-source GTM Science framework.
Thirty minutes with an operator. Then you get scope and a fixed price.
- CRO and chief commercial officer
- VP Sales and Head of Sales
- GTM and revenue leaders
- Founders carrying revenue
- Marketing and sales leads in B2B software companies
Direct gtm.science compatibility: software companies with product-market fit, roughly 20–500 employees, DACH and EU.
The starting point
Buyers want self-service and human validation at the critical decision points. More outreach automation doesn't resolve that tension. The actual job is to design autonomy deliberately.
69% of B2B buyers go to sales reps to validate AI-generated insights. At the same time, research in sales increasingly starts with AI. Both hold at once – and that's where the work sits.
Dream outcome
The revenue team knows its bottleneck, works from a shared Context Workspace and knows, for every relevant task, what an agent does alone, what a human checks and what stays human.
Your first result
GTM heatmap with a bottleneck hypothesis
Within five working days of a complete intake, the team receives a GTM heatmap with the most likely bottleneck and the three most important questions for the system lab.
What may an agent decide on its own in your team?
Assign eight typical GTM tasks to an autonomy level. Our default recommendation appears alongside immediately – with the reasoning.
GTM Agent Autonomy Snapshot
Basis: 162 valid responses, 106 of them with demographic detail. AI Monitor 2026, published by Teklens with ETH Zurich and the University of St. Gallen. Self-assessments, normalised to 0–100. Pre-release.
What the Decision Lab includes
Every component names the obstacle it removes, the artefact you receive and when it is delivered.
We work on the CRM and pipeline extract and on your messaging and content artefacts.
- Obstacle
Teams optimise symptoms rather than the bottleneck
ArtefactHeatmap from customer, CRM, positioning, process and stack signals
Deliveredbefore the lab
- Obstacle
Sales, marketing and RevOps work off separate models
ArtefactA shared decision and system-design sprint
Delivereddays 1–2
- Obstacle
Messaging and pipeline stages don't reflect the buying process
ArtefactConfirmed positioning and buying-process decisions
Deliveredday 1
- Obstacle
Agents get built for tool capability rather than process value
ArtefactTask, data, inputs, outputs, limits, review and metric
Deliveredday 2
- Obstacle
Automation gets treated as binary
ArtefactRules for autonomous, human approval and human only
Deliveredday 2
- Obstacle
No integrated sequence across twelve levers
ArtefactA prioritised roadmap along the GTM Science framework
Deliveredwithin five working days of the lab
- Obstacle
Positioning, customer knowledge and agent context drift apart
ArtefactA versioned source for the team and approved agents
Deliveredwith the roadmap
Included accelerators
- Agent registry template
- Signal dictionary template
- Human approval review checklist
- Growth loop review agenda
Templates created during the lab that your team keeps using afterwards. We don't attach invented individual values to them.
When the evidence holds: Execution Track
100-Day AI GTM Operating System
The Decision Lab plus 100 days of execution along the twelve gtm.science projects.
- Execution along the twelve gtm.science projects
- Signal-based workflows
- An orchestrated GTM stack
- Agreed working agents, where data and process readiness are confirmed
- Agent org chart and autonomy rules
- Growth loops and review cadence
- Updated GTM Context Workspace
Price, cohort logic and module sequence stay in sync with the canonical gtm.science source. We only commit to working agents once data and process readiness are confirmed.
Proof
Problem proof
- 6 in 10
also reach for personal AI tools – even though 87% are given tools by their employer.
Basis: 162 valid responses, self-reported tool usageLimitation: Self-reported. It shows personal tools are in use, not what data flows through them. - 69%
of B2B buyers go to sales reps to validate AI-generated insights.
Source: Gartner, B2B Buyer Survey (2026)Basis: Buyer surveyLimitation: Buyers self-reporting their own behaviour. - 75%Projection
of B2B buyers will prefer sales experiences that put human interaction ahead of AI by 2030.
Source: Gartner (2025)Basis: Analyst projection for 2030Limitation: A projection, not a measured figure.
ETH Zurich and the University of St. Gallen are research partners on the AI Monitor. They are not Teklens reference customers.
Mechanism proof
Anonymised example · B2B software, around 60 employees
| Task | Level | Review | Metric |
|---|---|---|---|
| Signal monitoring and list building | Autonomous | Weekly spot check | Hit rate |
| First-contact sequence | Human checks | Before sending | Reply rate |
| Proposal draft | Human checks | Before sending | Turnaround time |
| Price negotiation | Human only | — | Margin |
Delivery proof
What we have actually delivered: cases, customer quotes or an anonymised before-and-after. Where nothing is cleared yet we show a clearly labelled anonymised example – not an empty placeholder.
We do · You provide
We do
- GTM diagnostics and synthesis
- Preparing the heatmap and bottleneck hypothesis
- Facilitation and system design
- Agent blueprint, autonomy matrix and roadmap
- Context Workspace structure
You provide
- CRM and pipeline extract
- Relevant positioning, messaging and content artefacts
- Two lab days with the core team
- About three hours a week during the Execution Track
- Named GTM and RevOps owners
Investment
Two options, one scope. The Execution Track sits first because it shows the full extent – the recommended entry is the Decision Lab.
2-Day AI GTM System Lab
Diagnosis, a shared decision and a concrete execution plan. For teams that need clarity before they commit capital or capacity.
- Role-specific diagnosis
- First-value snapshot
- One to two workshop days
- Decision Pack
- Context Workspace
- 90- or 100-day plan
- First result
- 5 working days after a complete intake
- Full result
- 5 working days after day 2
- Effort on your side
- 2 lab days, then about three hours a week
The scope is set; the price is fixed in the scoping call and confirmed in writing. No line items appearing later.
When the agreed inputs are complete, we deliver the defined Decision Pack by the agreed date. If an agreed component is missing, we keep working at no extra fee until the pack is complete.
The revenue team knows its bottleneck, works from a shared Context Workspace and knows, for every relevant task, what an agent does alone, what a human checks and what stays human.
Review your GTM system100-Day AI GTM Operating System
The Decision Lab plus real execution, reviews and embedding into how the team works.
- Everything in the Decision Lab
- Execution on the real portfolio, backlog or GTM system
- Agreed working assets or agents
- Quality and governance gates
- Review cadence
- Handover and ongoing development in the Context Workspace
- First result
- 5 working days after a complete intake
- Full result
- 5 working days after day 2
- Effort on your side
- 2 lab days, then about three hours a week
The scope is set; the price is fixed in the scoping call and confirmed in writing. No line items appearing later.
When the agreed inputs are complete, we deliver the defined Decision Pack by the agreed date. If an agreed component is missing, we keep working at no extra fee until the pack is complete.
The revenue team knows its bottleneck, works from a shared Context Workspace and knows, for every relevant task, what an agent does alone, what a human checks and what stays human.
Review your GTM systemA decision you can act on – or we keep working.
When the agreed inputs are complete, we deliver the defined Decision Pack by the agreed date. If an agreed component is missing, we keep working at no extra fee until the pack is complete.
We guarantee defined outputs and dates that we control. No revenue, transformation or autonomy guarantee – that depends on your execution, and we can't stand behind it.
- a validated baseline
- prioritised decisions
- reasoned wait and stop decisions
- named owners
- success criteria or metrics
- a roadmap and the next review point
- an updated Context Workspace
- Complete inputs by the agreed date
- The agreed stakeholders take part
- Decisions stay within the agreed scope
- Access and permissions are in place
- No external blocker prevents the work
Fit gate
After Decode and Shape, you decide – not us.
The Execution Track does not start automatically. A reasoned wait or stop is a valid result – and often the most valuable one.
- Amplify
The evidence holds. We start the Execution Track.
- Experiment
A bounded test resolves the open uncertainty before capacity is committed.
- Wait
Fix the groundwork or the input first. With a criterion and a review date, not as a postponement.
- Stop
No sensible business case. Recording that with reasons saves more than any pilot.
Decode → Shape → Amplify → Evolve.
A loop, not a transformation with an end date.
- 01
Decode
Understand reality, context and the bottleneck
Where do we actually stand?
- 02
Shape
Set decisions, priorities and limits
What do we change – and what don't we?
- 03
Amplify
Turn decisions into real work
How does measurable impact happen?
- 04
Evolve
Embed learning, governance and routine
How does the system get better?
The Decision Lab covers Decode and Shape and hands over to Amplify and Evolve. The Execution Track runs the whole loop.
Your company leaves with a system, not a slide deck.
Every lab leaves behind a versioned Context Workspace: evidence, decisions, work, rules and what you learned, in one place. Human-readable, machine-readable for approved agents, exportable.
- Versioned, with traceable sources and assumptions
- An owner per artefact; decisions dated and reasoned
- Human-readable and machine-readable for approved agents
- Exportable – no artificial lock-in
- Permissions and data residency settled, update rhythm defined in Evolve
/gtm-os/
00_context/
01_goals/
02_projects/
03_skills/
04_agents/Common questions
Not sure which Lab fits?
Thirty minutes with the founding team. You get a clear recommendation, the right scope – or a reasoned no.