Method
Three stages, no grand announcements
5 to 10 days
Diagnose
We open your logs, your WAF rules and your templates. You get a factual report: what is blocked, on which templates, at what criticality, and what each fix costs. Usable as-is in a steering committee.
2 to 8 weeks
Fix
We execute the plan: access rules, server-side rendering of critical templates, structured data, feeds, instrumentation. We work in your repositories, with your teams, on your deployment pipelines.
Ongoing
Steer
The dashboard runs, alerts catch regressions, and a monthly review decides what comes next. The goal is that you no longer need us to observe — only to decide.
In practice
What we need from you, and what you get
What we need to start
- Read access to thirty days of your server or CDN logs — the one indispensable item
- Read access to your bot-protection console, if you have one (Datadome, Cloudflare, Akamai)
- The list of your critical templates: home, category, product, cart
- One technical contact available for one hour, once, so we do not have to guess your architecture
What you have at the end
- A diagnostic report usable as-is in a steering committee: what is blocked, on which templates, at what criticality
- A cost in days for each fix, so you can decide without calling us back
- The verification commands, so your teams can re-run the check without us
- A one-hour debrief with your technical teams, questions included
We do not bill overruns on an audit: the scope is set upfront, the price is firm. If the diagnostic concludes that everything is fine, we say so and the engagement stops there.
Your competitors will discover the problem when they read their October numbers.
A diagnostic takes five to ten days. It tells you whether AI agents reach your catalogue, what stops them, and what the fix costs.
Start a diagnosis