Once two AI visibility proposals cover the same work, calculate what each would cost through the same decision date. Include setup, agency fees, required software and work your own team must deliver. Keep confirmed supplier charges separate from internal estimates and unresolved charges. That separation lets you see which figure you can approve and which still depends on a clarification.
The AI Visibility pricing guide already explains how to align the underlying scope, including prompts, surfaces, languages and implementation. This article starts with a common scope and reconciles the financial and operational differences that remain. The worked quotes are fictional. AI Visibility is published by Lunasol, which offers related GEO and AEO services. GEO pricing and scope guide and Lunasol service overview
Start with the review date and the minimum commitment
Choose the date when your team will decide whether the work should continue. Then determine how many payments each proposal requires to get there and what commitment remains after that date. A three-month review can fall inside a longer software term. An apparent monthly rate can also be an annual payment expressed as a monthly equivalent. Capture cash payable through the review and any commitment beyond it in separate rows.
For each quote, identify the first invoice, setup fee, recurring charge and any tools that the buyer must purchase directly. Check when work starts if the buyer needs time to supply approved facts, release access or reserve development capacity. A review date linked to a successful deployment can move when those dependencies slip. The quote should explain which recurring charges continue during such a delay.
Keep three amounts distinct throughout the comparison. The first is the supplier cash you expect to pay through the review. The second is the commitment still payable afterward under the proposed terms. The third is the cost of the internal resources you expect to use. The total depends on the question you are answering. A cash approval, a budget exposure review and a decision about scarce development hours use different views of the same proposal.
Separate bundled costs from charges you pay directly
An agency’s public offer can indicate where to ask for detail. For example, 009 Agency distinguishes a complimentary audit, a full-cycle retainer with panel reruns included and a separately scoped technical implementation option. It also says its retainer assumptions depend partly on how much implementation the customer’s team can absorb. This is evidence of how one seller describes its offer. Your project figures need to come from the written quote. 009 Agency pricing and scope
Look for costs that can be included, passed through at cost, charged with a markup or paid directly to a third party. Record the payer and invoice timing. A tool listed in a proposal may be an agency expense already covered by its fee. A different proposal may require you to hold the tool account and pay its subscription. Adding an already bundled cost twice can reverse the comparison.
Ask how the quoted allowance is assigned. A licence may cover multiple clients or sites, while your quote only reserves a portion of it. Confirm how much your project gets, what happens when that portion is used and whether optional capacity needs your approval. Also ask which files and historical records the team can take at the review date. Export availability can affect the cost of handing the work to someone else.
Turn the monitoring schedule into a billable unit
A prompt is a question or task. A measurement is one attempt or completed result under a defined combination of surface, market, language and date. A credit is whatever the supplier defines as a billing unit. Use the tool’s definition to translate the agreed schedule into expected usage.
GeoStars’ US pricing page describes a base credit as a successful measurement and says failed attempts do not consume credits. It also lists different credit weights for additional API models, and says unused credits expire at month end. This is one supplier’s published specification. Ask any provider quoting a similar unit how they count failure, retries, model weights and unused capacity. The cited price page is for the US market. UAE configuration and charges need confirmation for a UAE proposal. GeoStars credit terms
Take an illustrative panel of 12 prompts measured weekly over four cycles on two base surfaces and one additional surface billed at five credits per result. If all scheduled results are delivered, the schedule produces 144 results. The weighted demand is 336 credits, calculated as 12 prompts multiplied by four cycles and by the sum of the three weights, 1 + 1 + 5. A quote with 300 credits would leave a gap of 36 credits under those assumptions. The schedule and allowance in this example are fictional.
If a quote says it will check a model without specifying the interface, clarify which surface the unit covers before using the arithmetic. Google’s dated Argon announcement names different product and subscription contexts. It illustrates why one model name can appear in several line items. Use the proposal and the tool specification to confirm which context is in scope and how its measurement is charged. Google’s official 13 October 2026 announcement
Keep first-party reporting on its own line
A proposal may include both sampled answers and a report from a platform’s webmaster tools. Ask what each line will produce and whether it depends on the site having enough data. A panel logs scheduled observations for agreed questions. A webmaster report summarises what that platform can report for the site over a period.
For example, Microsoft describes its Bing Topics Portfolio as a beta view with approximate figures and visibility that depends on sufficient data. It also says that opportunity citation volumes are shown as ranges. If a proposal includes a Topics Portfolio review, make it conditional on the feature and data being available for your property, and agree what output you will receive if they are absent. A reporting row can stay useful if it clearly records the coverage and limitation. Bing Topics Portfolio beta documentation
Check whether these rows carry separate fees. If a proposal includes a monthly findings meeting, clarify whether the fee covers interpreting the tool output, preparing actions and reconciling the result with the panel. An automated export and a review led by someone familiar with the project can both serve the buyer. Their deliverables and cost should be identifiable.
Reconcile two fictional proposals through month three
Assume both providers price a three-month scope with an agreed monitoring panel, two updates to existing pages and a review after the changes. Proposal A supplies implementation instructions and verification. The client’s developer ships the updates. Proposal B includes publishing the updates and charges a setup fee. Both use the same required monitoring coverage and deliver an export at the end. All amounts below are invented in AED for the calculation.
| Cost or dependency | Proposal A | Proposal B |
|---|---|---|
| Agency fee over three months | 3 × 3,000 = 9,000 | 3 × 3,600 = 10,800 |
| Setup | Included | 600 |
| Required monitoring software | 3 × 250 = 750, paid by client | Included |
| Supplier cash through review | 9,750 | 11,400 |
| Client implementation and approval time | 18 hours | 6 hours |
| Internal time at assumed AED 150 per hour | 2,700 | 900 |
| Planning cost through review | 12,450 | 12,300 |
Proposal A requires AED 1,650 less supplier cash. In this scenario it uses 12 more hours of internal time. Valuing that time at AED 150 per hour adds AED 1,800 to the difference. Proposal B has the lower planning cost by AED 150. If internal time were valued at AED 100 per hour, the extra 12 hours would add AED 1,200 and Proposal A would have the lower planning cost by AED 450.
The crossover is AED 137.50 per additional internal hour, obtained by dividing the cash difference of AED 1,650 by 12 hours. That figure is only meaningful under these fictional assumptions. It helps the team identify what to verify first. If it cannot reserve the developer for the dates required, the first proposal’s lower invoice may carry a delivery risk regardless of the hourly assumption.
Keep internal estimates visible even when the staff salary is already budgeted. The team can decide whether those hours displace higher-priority work. If finance uses a different planning rate, retain the supplier cash calculation and substitute the approved internal assumption. Record separately any additional fee, continuing commitment or applicable tax amount as shown on the actual quote.
Resolve uncertain rows with specific questions
Treat an unknown as a separate state. An unspecified tool allowance, a developer estimate awaiting review or a charge described as payable if needed can all change the outcome. Write down the condition that triggers each charge, the person who can verify it and the deadline for doing so.
If overage is possible, ask for the cost of an extra block and the effect of declining it. The tool may pause collection, reduce frequency or offer another tier. If the proposal includes multiple languages or markets, ask whether measurements come from the same credit pool. A small expansion can draw down the allowance faster than a reader would infer from the number of prompts alone.
For implementation, ask the internal owner to estimate the work against the actual deliverable. Include approval, publishing, testing and rollback arrangements where relevant. If a vendor estimates six hours of client time and the actual team expects twelve, carry both as scenarios until the task owner reviews the proposed workflow. Changing the estimate changes the comparison without changing the supplier quote.
Before approving an amount, verify whether work classified as included shares a limit with other work. For example, two page updates might draw from the same hours that pay for technical diagnosis. Ask how the proposal handles a finding that takes longer than expected and what output you would receive if the allowance runs out.
Give both bidders the same cost assumptions
Send a short reconciliation back to each provider. Identify the review date, fixed deliverables, what you expect to pay directly, the tool usage you calculated and the tasks the buyer expects to perform. Ask each bidder to correct any interpretation and give a revised price or explain any unresolved charge in writing.
If a provider suggests a different method or scope, keep it as a separately priced option. This preserves the common comparison while making the alternative easy to assess on its own terms. Capture the revised quote date so your team can trace which assumptions support the figures it is reviewing.
Use separate totals for supplier cash, commitments after review and internal resource cost in the approval note. Attach the key unresolved item and explain when it will be settled. If the outcome depends on tool overage or a narrow estimate of internal time, compare two plausible scenarios before committing. The quote that fits is the one your team can fund and deliver through the same review date.
Research checked 5 November 2026. The worksheet figures and monitoring schedule are illustrative. Verify the provider’s current written terms for your scope and market.



