Skip to content
Marc Gasser
The operator's manifesto

Operator-built.Evidence-led.Bespoke, not opinionated.

Nine operating principles for building GTM systems that stay useful after the kickoff deck is forgotten.

Why this exists

Stillness is not stability

Your go-to-market system is already changing while you read this.

Markets move. People change. AI makes the best and average tools better. Your company's strategy, product and positioning force new decisions. Standing still is not a neutral choice.

GTM Science exists to design systems that keep adapting without turning the organisation into chaos theatre. The unit of progress is not a prettier plan. It is a closed loop: decide, ship, learn, standardise, repeat.

These principles are our guardrails. They make the work opinionated enough to move fast and pragmatic enough to survive reality.

01
Start where it hurts

Earn the right to standardise

We do not start with a playbook. We start with the bottleneck.

Every company is a different organism. We diagnose the operating constraint before we suggest the system. What is blocking growth? Where is trust breaking down? Which handoff bleeds speed?

Only after the constraint is clear do we decide what deserves a shared pattern and what must remain bespoke.

Bespoke beats best practice when best practice ignores context.

02
AI is infrastructure

Build the AI-native spine

AI belongs inside the workflow, not in a side project.

AI is now part of core GTM infrastructure: routing, research, synthesis, QA, content, service, forecasting and operations.

We design small, controlled capabilities that compound. Humans keep accountability. Machines absorb repetition and expand coverage.

Automate the obvious. Augment the important. Keep judgement human.

03
Move fast, keep control

Create speed through observability

Fast matters only when fast remains auditable.

We want short loops and visible feedback. That requires instrumentation: owners, decision logs, source quality, metrics, rollbacks and a shared understanding of what changed.

Observability lets a team ship weekly without governance becoming a quarterly punishment.

Speed without traceability is just faster confusion.

04
Evidence over elegance

Optimise for truth, not theatre

A beautiful deck is not a learning system.

We prefer evidence from customers, pipelines, workflows and shipped experiments over internal consensus. Strategy should become testable behaviour.

If a hypothesis cannot be observed, measured or falsified, it is not ready to govern the system.

The story gets stronger when reality is allowed to edit it.

05
Humans own the outcome

Keep accountability with the operator

Delegation to AI is not delegation of responsibility.

Systems can recommend, draft, classify and execute. People still own the decision, the exception and the consequence.

We design explicit escalation paths so the team always knows where judgement enters the loop.

AI can carry the load. It cannot carry accountability.

06
Design for change

Assume the operating model will evolve

If the system only works in one market state, it is already obsolete.

We design modular workflows, reusable primitives and clear interfaces so change is less expensive. That includes tools, roles, data contracts and the language teams use to make decisions.

The goal is not to predict the next shock. It is to reduce the recovery time.

Resilience is the ability to adapt without rebuilding everything.

07
Share the recipe

Open methods compound

Knowledge gets better when it can be inspected.

We share frameworks, prompts, templates and practical findings because open methods increase trust and raise the floor for everyone.

Proprietary value should come from judgement, context and execution quality, not from hiding basic mechanics.

Make the method visible. Earn the value in the application.

08
Enterprise ≠ bespoke

Govern variation, do not worship it

Complexity is often a symptom, not a requirement.

Enterprise environments need control, security, integration and accountability. They do not automatically need a unique process for every team.

We standardise the repeatable core and isolate the valuable exceptions. That is how scale becomes manageable.

Standardise the spine. Customise the edge.

09
Standardise only what works

Turn proven loops into operating standards

A process deserves permanence after it earns evidence.

We experiment in small loops, measure what changes and only then turn the winning behaviour into templates, workflows and governance.

Documentation is not the finish line. Adoption and measurable improvement are.

Ship first. Learn fast. Standardise second.

The commitment

Aim = competitive advantage

A GTM system should make the company faster, clearer and harder to compete with.

That is the test. Not how much automation exists. Not how many tools are connected. Not how sophisticated the architecture looks. The system must create better decisions, better execution and a learning speed competitors struggle to match.