How the work is scoped, in practice
We're building out a public case-study library as engagements complete and clients agree to be featured. In the meantime, this page documents how we approach and report on a typical project, so you know what to expect before you ask for a reference.
A note on what you'll find here
We don't publish invented client names or fabricated metrics. As engagements complete and clients agree to be named publicly, their case studies will be added here with real, verifiable detail.
Until then, this page walks through the shape a typical engagement takes — scope, cadence and reporting — and points you to how to request references directly for engagements already underway.
The shape of a typical engagement
- Week 1–2
Audit
Baseline review of the site, current visibility and conversation flow.
- Week 3–6
First phase build
Implementation on priority pages — technical, structural or agent work depending on scope.
- Ongoing
Monitoring & reporting
Monthly reporting cadence against the agreed baseline.
What we report on
Engineered web
- Core Web Vitals movement
- Index coverage
- Crawl errors resolved
AI visibility
- Citation and mention log across monitored engines
- Schema coverage
- Structural fixes shipped
Agents
- Conversation volume
- Qualification rate
- Handoff quality reviewed monthly
We'd rather show you exactly how we measure a real engagement than publish a number nobody can verify.
Questions about references
Ask for a direct reference
If a public case study isn't up yet for a comparable engagement, we can usually arrange a direct conversation with a current client.
Published: — Inten