Service · Agent-Readiness Implementation
Build the agent-readiness your audit identified.
A 12-week project engagement that ships all high-priority remediations from your audit backlog: structured data deployed, ARIA fixed, crawler infrastructure updated, entity authority work underway.
EngagementCustom scopeDuration12 weeksTypeProject-based
The Problem
Most audits identify gaps that never get shipped.
01
Audits produce a backlog, not shipped code
Audits are diagnostic. They produce a scored backlog: the 46-item assessment, the competitive view, the band assignment. What they don't produce is the shipped code. Most companies receive an audit, forward it to engineering, and watch it compete with the product roadmap.
02
Eighteen months later, nothing has moved
A follow-up audit finds most items unchanged. The implementation engagement exists to close that gap. Every item in scope ships against documented acceptance criteria.
03
One-time projects decay
The runbook the engagement produces turns the engagement's outputs into a maintainable discipline, not a one-time project that decays.
Workstreams
Seven MAGNET workstreams, shipped against your backlog.
D4 · 01
Crawler & Connectivity
robots.txt for AI agents, llms.txt publication, WAF/CDN configuration, agent-specific user-agent permissions.
D1 · 02
Structured Data
Schema.org coverage across all page types, JSON-LD validity, property completeness, sameAs entity linking.
D2 · 03
Semantic & Accessible Markup
Heading hierarchy, landmark roles, ARIA correctness, semantic HTML remediation.
D3 · 04
Content Extractability
Claim-evidence formatting, FAQ markup, comparison content, citation-friendly phrasing.
D5 · 05
Freshness Signals
dateModified accuracy, expired content removal, version drift cleanup.
D6 · 06
Entity Authority
Wikipedia entries, Wikidata properties, directory presence. Long-cycle work initiated in this engagement.
D7 · 07
Agentic Conversion / Transactability
Selector stability, conversion and payment-flow traversability, regional rail integration (Tabby, Tamara, Apple Pay). Scored against the business’s primary conversion — purchase, demo-booking, or lead.
Cadence
Twelve weeks, four phases, no surprises.
Phase 01 · Weeks 01 to 02
Refinement
Kickoff and scope validation. Every audit backlog item reviewed, prioritized by impact and feasibility, and confirmed in scope. Workstream assignments locked.
Phase 02 · Weeks 03 to 07
Foundation
Infrastructure-layer and structured-data workstreams. D4 Crawler Connectivity (robots.txt/llms.txt, WAF config, agent-specific permissions), D1 Structured Data (schema deployment across all page types), D2 Semantic Markup (landmark roles, ARIA, heading hierarchy, accessible patterns).
Phase 03 · Weeks 08 to 11
Substance
Content-layer and authority workstreams. D3 Content Extractability (claim-evidence formatting, FAQ markup, citation-friendly structure), D5 Freshness Signals (dateModified accuracy, expired content cleanup), D7 Agentic Conversion / Transactability (selector stability, conversion-flow traversability). D6 Entity Authority work initiated: long-cycle work that continues beyond the engagement.
Phase 04 · Week 12
Validation
Full MAGNET re-score, runbook finalization, knowledge transfer session, next-90-days recommendation delivered.
Deliverables
Five things you have at the end of the engagement.
01
Scoped backlog shipped
Every high-priority item from the audit backlog, shipped against documented acceptance criteria. No scope creep; no items added mid-engagement without formal scope change.
02
Validation against MAGNET
Re-scored against the full MAGNET framework at completion. You see where each item moved and your updated band assignment.
03
The runbook
A structured operating document covering what was shipped, why each decision was made, how to maintain each workstream, and what to monitor. The runbook turns the engagement's output into a discipline rather than a one-time project.
04
Knowledge transfer
A working session with your team covering what was shipped, how it works, and what to watch. Recorded and shared.
05
The next-90-days recommendation
A clear recommendation on what follows, whether that's an Agentic Growth Retainer, a second implementation phase, or nothing yet. Named recommendation, no pressure.
Fit
The implementation is right for you if any of these are true.
Run this if
- You've completed an audit and your backlog has high-priority items that haven't shipped.
- Your engineering team has the audit but it's competing with the product roadmap.
- You're in the Frictional or Legacy-Optimized band and need the foundation built before a retainer makes sense.
- You need a third party to own implementation rather than advise on it.
- You're preparing for a new agent-era initiative and need the infrastructure layer sorted first.
Skip this if
- You haven't done the audit. Start there, the implementation is scoped against a specific backlog.
- You're in active redesign or replatform. Ship the new site first.
- Your gaps are maintenance-scale rather than foundational. An Agentic Growth Retainer may be a better fit.
- You have a strong internal team who can execute against the audit backlog themselves.
Operating Principles
Four commitments. Written into every engagement.
P 01
Scope is fixed at kickoff
Items not in scope at kickoff require a formal scope change to add. Expedite options are available; discuss at scoping.
P 02
Acceptance criteria, not vibes
Every item ships against documented acceptance criteria from the audit backlog. Shipped means meets the criteria, reviewed by the partner who scoped the engagement.
P 03
Senior partner review on every output
The same partner who scoped the engagement reviews every significant output before it ships. No junior-led handoffs.
P 04
Runbook before retainer
The engagement produces a runbook that makes internal maintenance straightforward. A retainer follows only if it earns its place.
Engagement
Transparent, scoped, fixed.
Pricing
Scoped per engagement. Range depends on audit scope, site complexity, and number of MAGNET dimensions in scope.
Payment
40% at kickoff, 30% at Week 6 check-in, 30% on final delivery. Scope changes require a formal change order.
Timeline
12 weeks, fixed scope at kickoff. Expedite options available; discuss at scoping.
Scope and pricing are walked through during your consultation. The implementation is scoped directly against your audit findings.
Book a scoping callFAQ
Common questions.
Yes, the implementation is scoped against a specific audit backlog. Scoping against an unaudited site is possible but requires an abbreviated assessment sprint first.
Yes. Most engagements are collaborative: we drive certain workstreams (structured data, llms.txt, entity authority research), while client engineering drives others (semantic markup fixes, server-side changes). The split is defined at kickoff.
Scope is fixed at kickoff against the audit findings. Items not in scope go into a documented second-phase backlog, which forms the basis for an Agentic Growth Retainer if needed.
We guarantee that scoped items are shipped and meet the acceptance criteria documented in the backlog. Score improvement follows from that; we don't guarantee a specific band outcome because scores depend on items outside our scope (entity authority work has long cycles that may not fully complete in 12 weeks).
Any production stack. Specific implementations vary: schema can be injected via GTM, CMS custom fields, or server-side templates depending on your architecture. We've worked with Webflow, custom Next.js/React, Shopify, Sitecore, and proprietary CMS environments.
Yes, where client access allows. For environments where deployment goes through client engineering, we provide ready-to-ship code with clear instructions and review the deployed result against acceptance criteria.
All implementation work is run under senior partner review. The same partner who scoped the engagement reviews every significant output before it ships.
Book a consultation. We confirm your audit findings are in scope, scope the engagement, and send an engagement letter. 40% is due at kickoff, 30% at Week 6 check-in, and 30% on final delivery.
Get started
Build what your audit identified.
The implementation closes the foundational gaps your audit found. Book a consultation and we'll confirm your audit findings are in scope, then send an engagement letter.