Get in touch.
If you're considering a measurement engagement - implementation, audit, infrastructure build, or training - the fastest way to find out if it's a fit is a 30-minute conversation.
Replies within one working day.
Schedule a call
Send me a few times that work and I'll confirm.
What to expect
A first call is 30 minutes. We use it to understand your current setup, the problem you're trying to solve, and whether the engagement model fits both sides. If there's a match, I'll follow up with a written proposal - scope, timeline, price. If there isn't, I'll usually be able to point you to someone who's a better fit.
Frequently Asked Questions
What's the typical engagement?
Most engagements are project-based, 2-12 weeks, fixed scope. Retainer arrangements are routed through 8-bit-sheep for continuity and contracting. Training and workshops are scheduled separately.
How embedded is "embedded"?
As embedded as your team allows. I prefer working in your Slack, your ticket system, and your repo, joining standups and design reviews where useful. The Forward Deployed Engineer model is core to how I deliver.
What if our stack isn't Google?
The methodology travels. Signal Engineering applies whether the warehouse is BigQuery, Snowflake, or Redshift, and whether the analytics platform is GA4, Amplitude, or something else. The Google stack is where I have the deepest production experience, but the way I think about measurement isn't tool-specific.
How quickly can we start?
1-4 weeks for new projects, depending on scope and current capacity. Audits and short engagements are sometimes possible faster.
What happens after the engagement ends?
The deliverable is always something your team can run without me - documented contracts, code in your repo, and a working knowledge transfer. Many clients move from a project to retainer support; others run the system themselves and I'm available for spot questions.