A managed outbound engine for a holdings group
We act as the embedded GTM engineering function across the portfolio — building and running the engine, not handing over a sequence.
- Parts built
- 03
- Stack
- Clay · n8n · HubSpot · Smartlead
- Ownership
- Client’s own accounts
The problem
A holdings group needed outbound across several portfolio companies without hiring a full in-house GTM team for each.
What we built
Targeting and enrichment architecture
CRM, campaign infrastructure and the automation joining them
Ongoing iteration on what the data says is working
What changed
FIG. 03.3 — Outcome
A maintained system with an owner for it — fractional, without the in-house headcount.
Stack
FIG. 03.4 — Tools in this build04 tools
Clay
n8n
HubSpot
Smartlead
What the client owns
As on every engagement, the domains, data and workflows sit in the client’s own accounts and are documented. If the client leaves, they keep all of it.
Standing policy · every engagement
Next step
Your build could be the next one here.
Thirty minutes. We’ll look at your market and tell you honestly whether outbound will work for you — and where we’d start.
Book a strategy call30 minutes · no obligation · no sequence afterwards