Proposal & sales

The audit meeting is not a data review. Its goal is a decision: the client agrees to a plan, a pilot or a proposal. Everything you show should move toward that decision.

Aim for three outcomes by the end:

1. The client understands the gap in their own words.
2. The client believes it can be measured and improved.
3. The client agrees to a specific next step.

1. Set the context (2 minutes). Say why you ran the audit: buyers ask assistants for recommendations, and you checked how the client appears. State the scope: which questions, which assistants, which competitors.

2. Show the question and the answer (5 minutes). Pick one realistic buyer question with high intent. Show the assistant's answer. Let the client read it before you comment. This is the most persuasive moment of the meeting.

3. Show the gap (4 minutes). Where is the client absent, and who appears instead? Show share of voice against competitors, then one sentiment or accuracy issue if it exists.

4. Explain why (4 minutes). Show the sources behind the answer. CiteMind's Reasoning Chain Transparency shows why an assistant cited specific sources, which makes your explanation concrete instead of speculative.

5. Present the plan and the next step (5 minutes). Offer three actions ranked by impact and effort. Then propose one next step: a pilot, a proposal or a baseline across a wider question set.

• Confirm who attends. Aim for the person who can approve spend, plus whoever owns marketing day to day.
• Save the results. Capture the answers you will show. Do not rely on live prompts in the meeting, because answers vary and a different answer on the day can derail you.
• Pick the headline. Write one sentence that sums up the finding. For example: "When buyers ask assistants to compare options in your category, two competitors appear and you do not."
• Choose one example question the client will immediately recognize as real.
• Prepare the three actions and what each one involves.
• Know your next step. Decide in advance what you will ask for.

Example opening: "Your buyers are starting to ask AI assistants for recommendations before they visit any website. I checked how those assistants answer questions in your category, so we can see what your buyers see."

Example bridge to the plan: "Here is why it looks this way, and here are the three things that would change it first."

Example close: "My suggestion is {{next_step}}. That lets us set a proper baseline and work on the top actions, and you will see the trend in the first report."

• Showing too many charts. Four or five views are enough.
• Running prompts live. A different answer on the day creates doubt.
• Arguing about one answer. Say that answers vary and that you track patterns.
• Explaining the technology at length. Clients care about what buyers see and what you will do.
• Promising results. Describe the plan and how you will report progress.
• Leaving without a next step.

Pilot. A fixed period, often a few months, with a defined scope. It lowers the client's risk and gives both sides a review point. Good for a first sale.

Monthly retainer. Ongoing monitoring, reporting and a set number of actions each month. The most common model for a recurring service.

Project. A one-time baseline and action plan, delivered as a defined piece of work. The client can continue as a retainer afterwards.

Add-on. A monthly line item attached to an existing SEO or content retainer.

Avoid pricing based on promised outcomes such as mentions or positions. You do not control them, and the model puts your margin at risk.

Your costs have two parts.

Tooling. CiteMind pricing is usage-based: you pay for the monitoring runs you schedule. Each client is configured independently, and one run is executed each day for every tracked question and selected assistant.

Monthly runs = questions x assistants x days

Example: 20 questions x 3 assistants x 30 days = 1,800 monthly runs. Multiply by your run rate to get the monthly tooling cost for that client. You can see the exact monthly impact before you add or change a client's monitoring.

Time. Estimate the hours per month for monitoring review, analysis, actions, content and reporting, and multiply by your internal hourly cost.

Use this as a floor, then adjust for value and market.

Minimum monthly price = (tooling cost + hours x hourly cost) / (1 - target margin)

Where:

• {{tooling_cost}} is the monthly usage cost for that client.
• {{hours}} is the monthly time you expect to spend.
• {{hourly_cost}} is your internal cost per hour.
• {{target_margin}} is the margin you want, as a decimal.

Then compare the result with what the client gets: the value of one new customer, what they pay for similar services and what competitors charge. Price above your floor and in line with value.

Differentiate packages by what the client gets, not by promises. Scope variables to vary:

• Number of tracked questions.
• Number of assistants covered.
• Number of markets or languages.
• Number of competitors benchmarked.
• Actions delivered per month (for example, content pieces or technical fixes).
• Reporting cadence and format (monthly report, live dashboard, review call).
• Support level.

Example package structure (set your own values):

• Core: baseline, monitoring of {{questions_core}} questions on {{assistants_core}} assistants, monthly report, {{actions_core}} actions per month.
• Growth: everything in Core, plus {{questions_growth}} questions on {{assistants_growth}} assistants, competitor benchmarking and a monthly review call, {{actions_growth}} actions per month.
• Portfolio: for clients with several brands or markets, with a dedicated plan per brand.

Three packages are enough. Make the middle one the one you want to sell.

• Quote after the baseline. A baseline lets you size the work properly.
• Set a minimum term. A few months gives time to show a trend.
• Say what is not included. For example, design work, paid media or content beyond the agreed number of pieces.
• Review scope as the client grows. More questions or markets raises your tooling cost and your time.
• Do not discount away your margin. Reduce scope instead of price.

• Start from the audit. Open with the client's own findings.
• Describe work, not promises. Deliverables and cadence, not guaranteed outcomes.
• Be specific. Numbers of questions, assistants, actions and meetings.
• Keep it short. Three to five pages is enough.
• Make the next step easy. One signature, one start date.

For a pilot, shorten the term, narrow the scope and add a review point at the end that describes the choice to continue.

For an existing SEO client, add a line that explains how the work connects to current activity and what remains in the SEO scope.

For a client with several brands, repeat the scope section per brand.

For a project, replace "Cadence" with a delivery timeline and remove the monthly sections.

• Every placeholder is replaced.
• Findings come from the client's real audit.
• No outcome is promised.
• Scope, deliverables and exclusions are explicit.
• The next step and the date are clear.
• Your branding and contact details are correct.
• Someone else has read it for errors.

1. Listen to the full objection. Do not interrupt.
2. Acknowledge it. "That is a fair question."
3. Answer with evidence. Use the client's audit, not general claims.
4. Offer a small next step. A baseline, a pilot or a call.

If you do not know the answer, say so and follow up.

"Is this real, or is it hype?" "Fair question. The easiest way to judge is to look at your own market. Here is what assistants say when your buyers ask about your category. If it is not relevant to your business, we will not pursue it."

"Can you guarantee we will be mentioned?" "No, and nobody honestly can. Assistants generate answers that vary and change over time. What I can commit to is a measured baseline, a prioritized plan, consistent execution and a monthly report on the trend."

"Isn't this just SEO with a new name?" "It overlaps, and your SEO foundations help. It also adds new measurement, such as how assistants describe you and which sources they rely on, and new work, such as presence outside your website. I would keep the scope clear so you know what you are paying for."

"It is too early. Let us wait." "That is reasonable. The risk of waiting is that competitors build presence first, and you have no baseline to compare against. A small pilot costs little and gives you the data to decide."

"We do not have budget." "We can start smaller: a baseline project or a short pilot with a narrow question set. It gives you evidence before committing to a larger plan."

"We will do it in-house." "That can work. If you do, you will need a consistent way to measure across assistants and a plan for actions. We can set up the measurement and plan, and your team can execute, or we can do both."

"AI answers change too much to measure." "They vary, which is why we do not rely on single answers. We track a fixed set of questions over time and look at the trend, the way you would track rankings."

"What if our buyers do not use AI assistants?" "Let us check. If your buyers do not ask these questions, the audit will show little to gain, and we can say so. If they do, you will see where you stand."

"We already have a tool for this." "That is useful. The question is whether it covers the assistants your buyers use, and whether it turns data into actions and reports you can act on."

Some objections are signals that the deal is wrong.

• A demand for guaranteed results. You will be held to something you do not control.
• A request to hide or fake information, such as fake reviews or misleading content. Decline.
• No decision-maker. If you cannot reach someone who can approve, the deal will stall.

It is better to decline politely than to win an account you cannot serve well.

• Keep a one-page list of your answers to the top objections.
• Add real examples from audits you have run.
• Note which objections come up most and refine your first meeting to address them earlier.
• Share the list with anyone on your team who sells.