CiteMind Academy
Back to Academy

MODULE 06 / ACCOUNT MANAGEMENT

Account management

Keep the client after the first report.

Run meetings that show value, handle renewals before they become risks and respond calmly when visibility drops. Retention is where a GEO service becomes a profitable one.

06.01Lesson

Run effective client meetings

An effective GEO client meeting follows one agenda: what changed, why it changed, what we did and what comes next. Send the report beforehand, spend the meeting on discussion and decisions instead of reading numbers, end with owners and dates, and follow up in writing the same day.

Choose a meeting rhythm

Monthly review (30 to 45 minutes). Reviews the report, confirms the actions for the next month and handles questions. The core meeting of the retainer.

Quarterly review (45 to 60 minutes). Looks at the wider trend, business changes, the competitor landscape and whether scope still fits. Include the budget owner.

Use a shorter ad-hoc call only when a decision cannot wait.

A reusable agenda

1. Headline (3 minutes). One sentence on how the period went.

2. What changed (10 minutes). Visibility, Brand Knowledge, sentiment, competitors and notable answers.

3. Why it changed (10 minutes). Sources, model or site events, competitor activity and the work completed.

4. What we did (5 minutes). Actions completed and their status.

5. What comes next (10 minutes). Priorities, owners, dates and questions for the client.

6. Decisions (5 minutes). Confirm what was agreed and what needs approval.

Before the meeting

  • Send the report early enough for the client to read it.
  • Mark the two or three points that need discussion.
  • Check open tasks, owners and dates.
  • Note changes in the client's products, markets or priorities.
  • Prepare a recommendation for next month.
  • Invite the person who can decide when a decision is needed.

Questions to ask the client

  • What has changed in the business since our last review?
  • Which products, markets or audiences matter most now?
  • Have customers asked questions that should be added to the tracked set?
  • Has a competitor launched something important?
  • Are there approvals or technical constraints affecting the plan?
  • Which result or action is most useful to you?

During the meeting

Keep the conversation on business outcomes, not on every metric. Use the report as a guide, pause for questions and make decisions explicit. If a new request changes scope, note it and agree to estimate it separately.

Mistakes to avoid

  • Reading the report aloud.
  • Spending the meeting on metrics that do not affect a decision.
  • Arriving without a recommendation for next month.
  • Letting action owners and dates remain vague.
  • Accepting scope changes without discussing effort.
  • Waiting until renewal to discuss value.

Templates

Follow-up note after the meeting

Subject: {{client}}: summary and next steps from {{meeting_date}}

Hi {{first_name}},

Thanks for the time today. The headline was {{headline}}.

Agreed actions:
- {{action_one}} — owner: {{owner_one}}, due: {{date_one}}
- {{action_two}} — owner: {{owner_two}}, due: {{date_two}}

For next month we will focus on {{next_priority}}.

The next review is {{next_meeting_date}}.

{{sender_name}}

FAQ

Who should attend?+

The day-to-day marketing contact, and, for quarterly reviews, the person who owns the budget. On your side, the person who knows the data and actions best.

What if the client keeps cancelling meetings?+

Take it as a signal. Send the report and a short written summary, ask what would make the meeting more useful and offer a shorter format.

How do I handle a client who wants more than the scope covers?+

Write down the request, estimate the work and offer it as a scope change. Do not absorb it silently.

How do I keep meetings short?+

Send the report beforehand, follow the agenda and move detail to a written appendix.

See your whole portfolio at a glance

Explore a live demo of the CiteMind portfolio view, with visibility, Brand Knowledge and sentiment for each client.

View a live demo
06.02Lesson

Renewal, retention, and upsell

Retention starts on day one, not at renewal. Keep a record of progress from the baseline, watch for at-risk signals, open the renewal conversation early with a clear summary of results and a plan for the next period, and propose expansions when they follow naturally from what the client needs.

Retention is built over time

Clients renew when they feel three things:

  • The work is understood. They know what you are doing and why.
  • The service is useful. Reports and meetings help them make decisions.
  • The next period has a plan. They can see what comes next and why it matters.

At-risk signals

Watch for early warnings:

  • Meetings are repeatedly cancelled.
  • The client stops replying or approving actions.
  • The report is opened but never discussed.
  • They question the value without asking what could change.
  • A new decision-maker arrives with no context.
  • Scope grows while the budget stays fixed.
  • Results are flat and you have not explained what you learned.

The renewal timeline

Start early. Raise renewal in the quarterly review before the term ends, then follow with a formal proposal. Review the baseline, progress, actions completed, what changed in the business and the plan for the next period. Leave enough time for the client to decide.

The renewal pack

A short document or presentation that covers:

  • The original objective and baseline.
  • Progress in visibility, Brand Knowledge and sentiment.
  • Actions completed and the sources or questions they addressed.
  • What you learned, including limits or flat periods.
  • The priorities for the next period.
  • Any change in scope, price or cadence.
  • The decision and date needed.

Natural upsell opportunities

Expand scope when it follows from a real need:

  • A new product or market needs its own question set.
  • More assistants matter to the client's buyers.
  • The client wants more actions or content.
  • A new brand joins the portfolio.
  • The client needs a dashboard or more frequent reviews.

Base every suggestion on a business change or audit finding, and present it as an option.

If a client decides to leave

It will happen. Handle it well. Confirm the end date, deliver what is owed, document the current state, ask for feedback and leave the door open. Do not make the handover difficult or argue about the decision. A professional exit protects your reputation.

Templates

Opening the renewal conversation

We are coming up on the end of the current term, and I wanted to start the conversation early. Here is what we have done since the baseline: {{summary}}. Here is where I think the biggest opportunities are for the next period: {{opportunities}}. I would like to hear what is changing on your side, and then send you a proposal that reflects both. When would be a good time to talk?

FAQ

When should I raise the renewal?+

Early. Open the conversation during the final quarter with a review of results and priorities, then send a proposal with enough time for the client to decide.

Should I raise prices at renewal?+

If scope or cost has grown, yes, and explain the reason. If scope is the same, keep the price or show added value.

How do I upsell without being pushy?+

Base each suggestion on data or a business change, and present it as an option. Let the client decide at their own pace.

What if results were flat?+

Be honest. Explain what you learned, what you would change and what the realistic plan is. Clients usually value candor more than a defensive summary.

Keep a clear record from day one

Start every client with a baseline so renewal conversations have a clear before and after. Free analysis for one week. No credit card required.

Run a free AI audit
06.03Lesson

What to do when visibility drops

When a client's AI visibility drops, first confirm that the drop is real and sustained, then find its scope: which questions, assistants and categories. Check the likely causes in order: access, site changes, model changes, source changes, competitor activity and news. Decide on an action, tell the client before they notice, and log what you found.

Do not panic, and do not wait

A drop can be noise or a real problem. Both need a quick, calm check. Do not rewrite the strategy based on one answer, but do not hide a sustained movement either. Start with the data and keep the client informed.

Step 1: confirm it is real

Compare the same question set across several runs and assistants. Check whether the movement is outside normal variation, whether competitors moved too and whether the drop affects visibility, Brand Knowledge or sentiment.

Step 2: find the scope

Narrow the problem. Identify the affected question groups, assistants, categories, markets and time period. A drop everywhere suggests a different cause from a drop on one product or one assistant.

Step 3: check the likely causes

Work through this checklist in order:

  • Access: robots.txt, CDN, firewall, errors and server logs.
  • Site changes: migrations, redirects, removed pages, content or structured-data changes.
  • Model changes: updates or retrieval changes affecting one assistant or many.
  • Source changes: cited pages updated, removed or replaced.
  • Competitor activity: new content, launches or presence on important sources.
  • News: events changing how the brand is described.

Step 4: decide the action

Match the response to the cause. Restore access if a crawler is blocked, fix inaccurate or missing information, update relevant content, build presence on the sources behind the gap, or monitor when the cause is a wider assistant change. Record what you know and what remains uncertain.

Step 5: tell the client before they notice

Bad news is easier when it comes from you, with a plan. State what changed, what you checked, the likely cause, what you are doing and when you will review it again.

Set up alerts so you see it first

Do not rely on a monthly check. CiteMind supports MCP and works with n8n and other orchestration tools, so you can build workflows that alert you to visibility drops and sentiment shifts. Decide what counts as an alert, who receives it and what the first check will be.

Step 6: log and follow up

Record the date, scope, suspected cause, action taken and result. Review the log at the next meeting. Over time, it builds a playbook of what causes drops in your clients' markets.

Templates

Message when a drop looks real

Subject: {{client}}: change in AI visibility on {{topic}}

Hi {{first_name}},

We found a change in AI visibility for {{client}} on {{topic}}. We checked {{checks}} and the most likely cause is {{cause}}.

We are taking {{action}} and will review the next {{period}} of data. I wanted you to hear it from us before the next report. I will update you by {{date}}.

{{sender_name}}

FAQ

How big does a drop need to be before I act?+

Act immediately on access problems. For other drops, look for a sustained pattern across questions and assistants before changing the plan.

What if every client dropped in the same assistant?+

That points to a change in the assistant. Log it, tell clients that it is a wider movement and watch the trend.

Should I tell the client even if I am not sure of the cause?+

Yes. Say what you checked, what you suspect and what you will do next. Early honesty protects trust.

How do I show that a recovery is real?+

Show the trend over several weeks across the affected questions and assistants, and compare it with the period before the drop.

Catch drops before your client does

Learn how CiteMind works with MCP and n8n to alert you to visibility and sentiment changes across your portfolio.

Read the MCP documentation