Key takeaways
- Define scope.
- Assign owners.
- Sell useful delivery, not guaranteed placement.
Agree on scope
Choose a category and primary market. Confirm which services the client wants to sell and which competitors buyers compare. Ask sales for common objections. Record exclusions so the report does not imply coverage you did not test.
Deliver the original records
Include prompts, settings, dates and source URLs. Mark whether the client was mentioned, cited or recommended. Separate branded from discovery questions and explain how failed responses affect the denominator.
Assign accountable work
Name the affected page, evidence gap, owner and approval step. Publishing a support-policy page is a task someone can estimate and complete. “Build authority” alone is not. Prioritize information that would change a buyer’s decision.
Price capacity and deliverables
Estimate research, writing, development and outreach. Set limits for markets and review cycles. Confirm the software supports the scope. An invented standard retainer range does not establish value.
Report commercial context
Show completed tasks, measured sample changes and qualified outcomes where observable. Explain uncertainty and external changes. Do not force every metric to tell the same positive story.
References and further reading
Primary documentation and product references. Practical checklists and worked examples above are editorial guidance, not claims about private ranking algorithms.