Services
Four ways I work with marketing and revenue teams. They share a pattern: the technical work is half the job, and the half that decides whether it lands is organisational — definitions, adoption, process, ownership. Each service is built around that half.
The four services
Onboarding and strategic implementation
Platform deployments where the configuration is half the job and producing a system the whole business will actually use is the other half. Configuration, process alignment, and adoption — run in parallel, not sequence. → /services/onboarding
Martech landscape fit and integration
The work where the CRM is one node in a wider stack — ERP, CDP, data warehouse, custom systems — and the question is how the parts fit, not how to configure one platform in isolation. → /services/martech
Customer workflow and RevOps solutions
The translation between commercial process and platform configuration — and the inverse, redesigning process where it doesn’t survive contact with the platform. → /services/revops
Fractional marketing operations / CRM manager
Embedded, part-time ownership of the martech practice — for the stage where the system has outgrown its current owner but hasn’t justified a full-time hire. → /services/fractional
The work that doesn't have a name yet
Not every problem arrives labelled as a martech project. Sometimes the brief is a leadership development programme that needs multi-language assessment forms, back-end logic, and automated reporting built around it. Sometimes it’s raw third-party intent data that has to become a weekly stream of qualified opportunities a sales team will actually act on.
The four services above are where most engagements land. But the underlying skill is narrower than “consulting” and broader than any one of them: taking a business problem that needs data, systems, and automation, and building the thing that solves it — whatever it ends up being called.
If you have a problem that clearly needs that kind of senior, hands-on technical thinking but doesn’t fit a neat category, it’s worth a conversation. Let’s talk!
Not sure which fits?
Most engagements start with a conversation about whether I’m the right fit — I’ll tell you straight if I’m not. From there, scope depends on the problem: a fixed-scope project, a retainer, or embedded ownership. Platform-neutral by default; the right tool for the situation is part of what we work out.