Organic Retainer Scope Lock (Onboarding)
A checklist with 7 steps: Inventory every asset the client already owns before quoting a retainer.
By InnovaAI ResearchPublished
What are the steps?
Organic Retainer Scope Lock (Onboarding)
- 01
Inventory every asset the client already owns before quoting a retainer
Pull the domain list, existing content library, and any legacy analytics access. Agencies that skip this step routinely discover a second site or a neglected blog after the scope is signed.
- 02
Separate what the platform reports from what the client actually needs
A crawl of 100+ data points will surface hundreds of issues; sort them into revenue-blocking, brand-risking, and cosmetic tiers so the proposal prices the first two only.
- 03
Set the measurement split between ranked position and AI answer citation
Two independent studies cited in September 2026 confirm AI-generated answers now surface ahead of traditional results, so the retainer must track both outcomes separately rather than reporting rank alone.
- 04
Define the content volume the fee actually funds
Convert the retainer into a unit the client can audit: briefs per month, words per brief, revision rounds, and who owns subject-matter interviews. Vague 'ongoing optimization' language is what makes month-three invoices feel unjustified.
- 05
Name the technical work that sits outside scope
Migration support, CMS rebuilds, and developer tickets are the three requests that most often consume unbilled hours. List them as change orders with an hourly rate before kickoff.
- 06
Assign one named owner per workstream on both sides
Client-side approval delays are the single largest cause of missed content calendars. Get a written approver for copy, a separate approver for technical changes, and a response-time expectation.
- 07
Document the data handling position for every AI tool in the stack
Forrester's September 2026 analysis argues private AI deployments outperform public tools for B2B marketing because shared model access erases differentiation. Record whether client data enters a shared training pool and put the finding in the signed scope.