WORKING NOTES FROM THE PRACTICE.SIGNALS, AGENTS, ATTRIBUTION, COMMANDCENTERS, MARKETING AS CODE, AND WHATANY OF IT COSTS. WRITTEN FROM THE BUILD.
Workingnotes

How to Build a Growth OS: Marketing Infrastructure You Own, in Five Components
The five components of a Growth Operating System, the order they must be built in, what each needs from the last, and the mistakes that leave you with tools.
Read the piece
Allbound: Stop Fighting Inbound vs Outbound and Wire One Loop

First-Party Intent Data: Building Buyer Signals You Own

Agentic Marketing: What AI Agents Actually Do in a B2B GTM, and What They Never Should
Motion
3 articles
Outbound Deliverability: Domains, Warmup and the Arithmetic of Volume
The infrastructure under cold outbound treated as engineering: domain strategy, SPF, DKIM and DMARC, warmup, volume per inbox, and what to monitor.
- 02

AI Personalization in Outbound: Where It Helps and Where It Gets You Blocked
The four levels of outbound personalization, what AI is good at in each, the failures that burn domains, and how to configure an engine grounded in signals.
- 03

ABM in the DACH Market: Signals, Buying Committees and the Outbound Pairing
Account-based marketing for German-speaking B2B: the signals that turn a list into a queue, the committee map, the consent constraints.
Signals
3 articles
Third-Party Intent Data: What Is Worth Buying and What Is Not
The five categories of bought intent, how each is collected, why latency and non-exclusivity limit them, and a test to run on a provider before signing.
- 02

Website Visitor Identification: What It Really Resolves
Reverse-IP tools resolve a company from an IP address, sometimes. Honest match rates, why they keep falling, and what the signal is good for.
- 03

CRM Signal Routing: From Buyer Event to Rep in Under a Minute
Wire buyer signals into the CRM so the right rep sees the right account in time: routing by score instead of round-robin, plus the rules that stop collisions.
Automation
4 articles
CRM Data Hygiene: Duplicates, Account Matching and the Merge You Cannot Undo
Where duplicate records actually come from, why account matching is harder than person matching, and why a false merge costs more than the duplicate it fixed.
- 02

Lead Routing and Lifecycle: Definitions That Survive Contact With Reality
Why lifecycle stages rot within two quarters, what each routing model breaks, the merge problem, honest speed-to-lead, and a ten-lead audit you can run today.
- 03

Marketing Automation vs Orchestration: Where the Workflow Builder Stops
Automation is a trigger and an action. Orchestration is state, ordering, retries, idempotency and observability, and the gap shows up as bugs.
- 04

B2B Marketing Automation That Compounds: Ads, Signals and Agents
Why most marketing automation is a chain of emails, what it takes to automate the parts that move pipeline, and how AI ad optimisation works wired to revenue.
Marketing as Code
3 articles
CI/CD for Marketing: The Tests Worth Running and the Deploy Worth Trusting
The checks a marketing pipeline should run in order, how a merge reaches an ad platform or an email tool, and why the rollback path is the part that matters.
- 02

Version Control for Marketing Copy: The Repository Layout and the Review That Holds
What belongs in a marketing repository and what does not, a directory structure that survives a real team, and the pull request that makes review worth doing.
- 03

Marketing as Code: Version Control, Review and CI/CD for Campaigns
Running copy, ads, sequences and scoring rules from a Git repository: the review gates that catch mistakes before spend, and how a merge deploys everywhere.
Infrastructure
4 articles
A Data Warehouse for Marketing: The Spine Under Every Number You Report
Why the warehouse became affordable, what should land in it, why definitions belong in version-controlled SQL, and the modelling costs nobody budgets for.
- 02

Consent Mode and Cookieless Measurement: What Survives When the Visitor Says No
What Google Consent Mode v2 actually does, what conversion modelling estimates, and which numbers remain real when a third of your traffic refuses consent.
- 03

Server-Side Tracking in Germany: First-Party Event Capture Under the DSGVO
How server-side first-party event capture works, what it changes and does not change about DSGVO consent, and how to set it up to be usable and defensible.
- 04

RevOps Software Compared: Systems of Record, Views, and What to Consolidate
Compare revenue operations tools by what they hold, not by features: systems of record, views, actors, and where the same data is being paid for twice.
Measurement
4 articles
B2B Funnel Metrics: Definitions That Hold Up Under Pressure
Why MQL and SQL differ in every company, the five-part template that makes a definition durable, and the quarterly review that stops it rotting.
- 02

Marketing Mix Modelling vs Attribution in B2B: Two Instruments, Two Different Questions
Attribution says which touch preceded a deal, mix modelling says what happens if you change spend, and most B2B companies cannot run the second one honestly.
- 03

Incrementality Testing for B2B: Geo Holdouts, Audience Holdouts and the Power Problem
How to run a holdout that shows whether a channel caused pipeline, which design fits a B2B business, and how to tell when you are too small to test at all.
- 04

Closed-Loop Attribution for B2B: Wiring Revenue Back Into the Networks
What closed-loop attribution is, why B2B needs it more than e-commerce, the four connections that make the loop, and the honest limits of any attribution model.
Command Centers
3 articles
Pipeline Forecasting for Marketing Leaders: The Arithmetic Behind the Number You Commit To
Why 3x coverage is folk wisdom, how forecast error compounds across four inputs, and how to define marketing-sourced pipeline so the argument finally ends.
- 02

Marketing Dashboard Metrics That Change Decisions: The Test Every Tile Has to Pass
One test for every tile on a marketing dashboard, the metrics that survive it, the ones that are theatre, and why vanity numbers turn dangerous near pay.
- 03

The C-Level Marketing Command Center: What the CEO, CMO and Sales Lead Each Need to See
Why one marketing dashboard fails three audiences, the few numbers each role decides on, the cadence that fits each number, and what makes a dashboard trusted.
Strategy
4 articles
What a Growth OS Costs to Run: The Bill After the Build
The recurring cost of operating go-to-market infrastructure: hosting, data, sending, model spend, observability, and the human hours nobody budgets for.
- 02

An ICP Definition That Actually Filters: Rejection as the Test
Most ICP documents describe rather than exclude. How to write one that rejects accounts, encode it so systems can apply it, and review it quarterly.
- 03

The Marketing Readiness Audit: Seven Layers, One Constraint
Audit a B2B marketing operation so the result is one binding constraint and a build order, not a forty-item list: the seven layers in order.
- 04

Agency, In-House, or a System: The Third Option for B2B Marketing
The agency-versus-in-house debate is missing a column. A framework for deciding, the costs each model hides, and when replacing the process beats staffing it.
GTM Engineering
3 articles
Build or Buy Your GTM Stack: Four Questions That Settle It
A decision framework for the go-to-market stack: where buying wins, where building wins more often than expected, and the hidden costs of both.
- 02

The GTM Engineer: What the Role Actually Does and How to Hire One
The day-to-day work of a GTM engineer, how it differs from growth, marketing ops and RevOps, the real skill mix, and how to interview and hire one.
- 03

GTM Engineering: What It Is, What It Costs, and How to Choose a Provider in Germany
A plain definition of GTM engineering, how it differs from RevOps and agencies, what a buildout costs, and the questions that expose a rebranded agency.
AI Engineering
4 articles
Evals for Marketing AI: Numbers Instead of Vibes
Building a golden set, which metric fits which task, the four biases of a model judge, and the regression run that blocks a merge before quality drops.
- 02

Model Orchestration: Routing by Task, Cost and Latency
Why one hardcoded provider is a business risk, what the routing key actually is, where caching is safe, and what an abstraction layer costs you.
- 03

Prompt Management: A Registry, Not a Google Doc
Why the live prompt exists in six places, what a registry stores beyond the text, how prompt review works, and what a provider deprecation costs you.
- 04

RAG That Cites Its Sources: Retrieval You Can Actually Check
The stages of a retrieval pipeline and what breaks in each, why hallucination is usually a retrieval failure, and the permission leak nobody notices.
Growth OS
3 articles
The 60-Day Growth OS Buildout: What Each Phase Actually Looks Like
A week-by-week account of a sixty-day Growth OS engagement, the preconditions for each phase, the client hours it costs, and what slips the timeline.
- 02

Growth OS for Agencies: Productising Delivery Without Selling Hours
How agencies turn go-to-market delivery into a system, what to productise and what to keep bespoke, multi-tenant architecture, pricing, and where it fails.
- 03

Growth OS vs CRM vs CDP: Which One Your Problem Actually Needs
What a CRM, a CDP and a Growth OS each actually are, where they overlap, why B2B teams buy the wrong one, and a short diagnostic to tell them apart.
Agents
3 articles
Content Agents: From Brief to Draft to Review Without Publishing Filler
What an agent needs in a brief to produce usable content, why context files beat prompts, who reviews, and how to measure quality with an eval set.
- 02

Agent Approval Gates: How to Let AI Act Without Losing the Room
Three gate patterns matched to how expensive an action is to undo, what belongs in the audit log, blast radius caps, and why gates decay into rubber stamps.
- 03

AI SDR: What It Actually Automates and Where It Breaks
The six jobs an AI SDR genuinely does, the deliverability ceiling nobody sells against, how to evaluate a vendor, and the honest cost comparison.
Ready to build it
These notes
are the system
Every piece here is written from a build we ran. Your motion is different, so start with twelve questions and get the build order back within 48 hours, sequenced and priced.
Get in touch
Bring us
the problem.
If one of these notes describes something on your desk, write two sentences. We read every one and answer with what we would build first.
Get the next one
One new working note every few days. No sequence, no sales pitch, unsubscribe from every send.