No setup fees.
No long-term contract.
You keep all data and assets we create.
Simple, transparent pricing for done-for-you outbound.
Our pricing
One retainer. Shipped weekly. Built inside your tools.
No long-term contract.
You keep all data and assets we create.
You want a straight answer on budget.
Most engagements start from €2,500/month. That covers one “system lane” end-to-end: strategy, build, launch, and weekly optimisation — inside your tools.
- Outbound: targeting, deliverability, messaging, multi-channel execution + CRM handoff
- CRM / RevOps: pipeline, lifecycle, routing, reporting, hygiene + governance
- Workflows: automation across your stack (Make/n8n/Zapier), logging + alerts
- Inbound: speed-to-lead, SLAs, routing, follow-up + attribution
I don’t publish rigid tiers because scope isn’t “small/medium/large” — it’s how clear your ICP is, what’s already working, and how quickly we can find signal.
Your system could be live in ~3 weeks
Most B2B SaaS builds follow this path. If your CRM needs a rebuild, we extend and agree the plan upfront.
-
1📌 You’re hereQuick check + fitConfirm goals, constraints, and which “system lane” matters most right now.
-
2💬 Discovery (Day 0–2)Align on ICP + success metricsTarget accounts, what a “good meeting” means, and where signal should show up.
-
3🧾 Plan & Scope (Week 1)Map the buildPick the lane, define success, and outline messaging + targeting + tooling.
-
4⚙️ Build & Setup (Week 2)Wire it end-to-endDeliverability, routing, tracking, sequences, and CRM handoff built properly.
-
5🚀 Launch & Calibrate (Week 3)Go live + improve weeklyCampaigns live, replies handled, early learning captured, optimisation cadence begins.
What your retainer covers
One system lane, built end-to-end — then improved weekly.
The Service
- You work directly with me (no handoffs)
- Strategy + execution + iteration in one loop
- Weekly shipping: improvements, tests, fixes
- Ownership of outcomes, not activity
Targeting & Data
- ICP refinement + segmentation
- Account/list build + enrichment
- Ongoing list QA (relevance, gaps)
- Clear tracking by segment/source
Multi-Channel
- Email + LinkedIn that work together
- Reply handling + routing rules
- CRM handoff so leads don’t die in inboxes
- Optional inbound routing where needed
Messaging
- Angles per segment (not one-size-fits-all)
- Copy iteration based on replies
- Objections turned into better sequences
- A playbook your team keeps using
Transparency
- Weekly update: what changed + what we learned
- Monthly review: decisions + next priorities
- Visibility into targeting + messaging
- Reporting tied to qualified conversations
Tools & Tech
- Deliverability + sending best practice
- Stack wiring (CRM + outbound + workflows)
- Slack alerts / logging / automation
- Documentation so the system survives
Pricing & Engagement
The practical questions: budget, timelines, what’s included, and how we work month-to-month.
Budget & structure
How pricing works, terms, and what’s separate.
Most clients start with a focused sprint to stabilise the highest-impact lane (Outbound, CRM/RevOps, Workflows, or Inbound), then go month-to-month while we ship weekly improvements.
If you’re not sure which lane is the blocker, we’ll map it quickly on the call and recommend the cleanest starting point.
For system work, 30–60 days is usually the minimum to get a stable loop (build → run → learn → improve).
After the initial stabilisation, you can stay month-to-month.
No fake guarantees. Meeting volume depends on offer, market, list quality, and follow-up.
What we do guarantee is a clean system: targeting rules, deliverability hygiene, messaging tests, reply ops, and reporting you can trust.
Tools and data are typically separate (because you own the stack): inboxes/domains, outbound tools, data providers, CRM seats, automation tooling.
If you want, I’ll tell you what you actually need (and what you don’t).
What’s included
What you get weekly, and what you keep.
Weekly shipping and visibility:
- A clear “what changed” update (Slack/Loom)
- Live improvements shipped (targeting, copy, routing, workflows, reporting)
- Signal review (reply quality, speed-to-lead, conversion, handoff health)
Yes. I’m not “replacing” your team — I’m building the system they run.
We’ll define ownership clearly (follow-up, routing, qualification, SLA) so work doesn’t fall between stools.
Yes. Your sequences, routing rules, dashboards, workflows, docs, and learnings stay in your workspace.
Typically within days, depending on access and whether deliverability/setup needs doing first.
If your domains/inboxes are unhealthy, we’ll stabilise that before pushing volume.
Ops & admin
Access, approvals, pausing, and boundaries.
- Tool access (or screenshare) + one point of contact
- ICP + deal context (ACV range, typical objections, best customers)
- Follow-up owner + response expectations (so leads don’t die)
After the initial stabilisation phase, most clients are month-to-month.
If you pause, the system stays yours — you can restart later without rebuilding from scratch.
Not simultaneously in the same niche where it’s a conflict. We’ll align on boundaries up front.
We keep approvals lightweight so momentum doesn’t die.
- Weekly update: what shipped + what changed + what we learned.
- Approval points: ICP/segments, compliance stance, messaging angles (early), then we iterate fast.
- Clear ownership: who follows up, what “good lead” means, and SLA expectations.
Compliance & safety
Governance, suppression, and safe sending.
GDPR depends on your region, ICP, and legal stance. We’ll align on a compliant approach you’re comfortable with before scaling.
Operationally, we keep suppression and preferences tight so you’re not contacting people who’ve replied/unsubscribed.
Yes — volume ramps are governed by health metrics (bounce/unsub/spam signals), not by a quota.
If health slips, we slow down, fix the cause, and only then scale again.
We build “do not contact” and suppression into the system — not into someone’s memory.
- Unsubs/bounces/replies trigger suppression automatically.
- We avoid sensitive categories and keep fields to what’s needed to operate.
- If you’re stricter internally, we follow that.
Yes. If your company requires an NDA/DPA for access to systems, we’ll align early so it doesn’t slow the start.
We also work cleanly: least-privilege access, clear ownership, and documented handover.