The initial diagnostic tells you whether your problem is worth fixing. Project price gets locked in after that, not before.
If you’re not sure yet whether your problem is worth fixing.
Before proposing anything, I need to understand what’s actually broken. Skip this and any quote would just be a guess.
If you suspect your tracking is leaking but don’t know where.
Full review of your tracking stack, prioritized by revenue impact, not a generic checklist.
If you’ve already lost conversions to ITP/ad-blockers and want them back.
Server-side tagging migration with end-to-end validation, not just "move it to the server and hope".
If your tracking is already fixed and you don’t want it silently breaking again.
Continuous monitoring so a broken event doesn’t take months to notice, which is what usually happens.
Yes. Based in the EU, I work with agencies and companies across Spain, the rest of Europe, and clients in the US and Canada.
No. Every project price is fixed before work starts, right after the initial diagnostic. No scope surprises halfway through.
Every project is validated in Preview/DebugView before being marked complete. If something doesn’t work as specified, it gets fixed at no extra cost.
Yes, it’s one of my main channels. I work white-label when the agency requires it.
No. The initial diagnostic just needs a screen-share session; I don’t need access to anything. If the project moves forward, I ask for read-only access first, and edit access only to what we’re actually going to touch, never more than needed.
I’ll tell you directly, without artificially stretching the project. That’s exactly what the diagnostic is for: sometimes fixing something costs more than it recovers, and I’d rather tell you that upfront than bill you for a project that doesn’t make sense.
Not sure? Start with the initial diagnostic: it’s the cheapest way to find out.