Agency White-Label Brief: Scope, Intake, and Delivery
A white-label brief should make an agency look organized, not omniscient: one named client, a defined research question, inspectable evidence, and actions the client can actually own.
What the brief is for
A white-label AI-answer visibility brief turns a defined research request into a client-ready document an agency can deliver under its own brand. It can explain where a client appeared or did not appear in a scoped set of observations, who appeared instead, which sources shaped the answers, and what to test next.
White-label changes the presentation and handoff. It does not justify hiding sources, presenting a sample as the whole market, or promising that an answer engine will cite a particular page.
Lock the scope before research
Write the scope in plain language and get it approved before collecting observations. The minimum useful boundary is:
- One named end client and its primary URL.
- Category and offer definition in the client’s language, including what is out of scope.
- Audience or ICP and the buyer decisions the brief should inform.
- Geographies and languages that could change the answer context.
- Competitor set with up to five named competitor URLs for the Agency Pack scope.
- Priority answer engines or surfaces, listed in order.
- Observation window and evidence rule, including access dates and fact-check expectations.
- Delivery treatment: agency brand, client brand, footer, version date, and whether a “research by CiteMap” line is retained.
If the client cannot answer these questions, the next step is scope clarification—not a bigger spreadsheet.
Use a decision-shaped brief structure
1. Cover and scope note
Show the agency and client names, delivery date, version, category, platforms, prompt families, competitor set, and a short caveat that the findings are scoped observations.
2. Executive readout
Separate what appeared, what was absent or misframed, and what should happen next. Keep statements proportional to the evidence. “In this review” is often the most important phrase on the page.
3. Observation and gap map
Group the work by buyer question, competitor, topic, platform, or recurring citation domain. A useful row includes the prompt family, observation, gap type, cited URL, likely owner, and recommended next test.
4. Source and fact-check appendix
List URLs with access dates. Mark client facts that need confirmation and distinguish client-provided material from independently collected observations.
5. Prioritized action plan
Route actions into lanes such as product marketing, technical SEO, documentation, editorial content, PR, analyst relations, or community participation. Add a proposed owner and review date. “Publish more content” is not a complete action.
Set a clean intake
| Intake item | Why it matters |
|---|---|
| Agency name and logo | Sets the white-label treatment and delivery owner. |
| Client name and primary URL | Prevents research from drifting across brands or properties. |
| Category, offer, and ICP | Defines what a relevant answer actually means. |
| Geographies and languages | Provides context for buyer language and source selection. |
| Up to five competitor URLs | Sets the comparison boundary for the agency scope. |
| Priority engines and success metric | Aligns the review with the client’s decision; qualitative is fine. |
| Deadline, timezone, and fact-check contact | Creates a practical review and correction path. |
| White-label preference | Clarifies brand, footer, and research-credit treatment. |
For the CiteMap Agency Pack, the stated delivery window is 7–10 business days after complete intake. Missing required fields pause the clock; payment alone does not make an incomplete scope ready for research.
QA before sending to the client
- Scope: Does every conclusion fit the named client, platforms, prompts, dates, and competitor set?
- Evidence: Can a reviewer inspect the URL and access date behind each factual statement?
- Branding: Are agency, client, version, date, contact, and footer details consistent?
- Claims: Did any sentence imply guaranteed rankings, citations, traffic, revenue, or share of voice?
- Privacy: Are private notes, credentials, unapproved screenshots, and other clients’ details excluded?
- Actions: Does each priority have a clear lane, owner, test, and review date?
- Handoff: Is it clear what is evidence, what is interpretation, and what is proposed work?
Keep the raw research log separate from the polished delivery PDF. The client needs a readable decision document; the agency needs an audit trail that can answer reasonable questions.
What belongs outside the scope
A white-label brief is not continuous monitoring, a dashboard license, a live strategy workshop, unlimited revisions, or a guarantee of citations or rankings. It should not include invented metrics, testimonials, or proof. If a number was not measured with a stated method, do not present it as a result.
Likewise, do not reuse a client-specific brief for a second end client or publish it as a generic template without the appropriate agreement. Clear boundaries protect the agency, the client, and the usefulness of the research.
Write with evidence-sized confidence
Prefer “this source was cited for the comparison prompt on the access date” to “this domain controls the category.” Prefer “the client was absent from these observations” to “the client has no visibility.” Those distinctions are not hedging; they are what make the document defensible.
Choose the lightest useful next step
If you are scoping an agency engagement, the free CiteMap Agency One-Pager is a compact overview of the offer and intake. When you are ready for one named client, a defined category, and a client-ready white-label brief, review the Agency Pack. Questions about fit can be sent to morpheusqilee@gmail.com.