It depends on the size of the estate and the state it is in, so I quote after a call rather than publishing a number that would be wrong for most people. What I will commit to on that call is a fixed scope and a fixed price — no hourly billing, and no change order for something that was obviously part of the job.

For a typical single-brand site, a working week from access to written findings. Large multi-brand estates or containers with heavy custom templating take longer, and I will tell you that before starting rather than halfway through.

Often, but not always, and I will say so when the answer is no. Server-side GTM earns its keep when you are losing conversions to ad blockers and ITP, when you need to enrich events with data the browser should not hold, or when you want one governed pipeline out to several vendors. If your real problem is a data layer nobody maintains, moving the same broken events to a server does not fix it — it just makes them harder to debug.

Yes, and it is usually the fastest route. I write the tagging spec, your developers implement the data layer, and I validate it in the container. That split keeps the work in your codebase and out of a black box only I can open.

You keep everything: the container, the documentation, the dashboards, and a recorded walkthrough. There is no proprietary layer to license and nothing that stops working if you stop paying me. Ongoing support is available, but it should be a choice rather than a dependency.

Yes. Where a client’s name is under NDA, the case study on this site describes the work and abstracts the brand — it does not invent a substitute.