Most local SEO proposals are scope documents dressed up as strategy. They describe what the agency will do, what tools they will use, and how much it costs. They are nearly identical from agency to agency. When proposals are identical, clients choose on price.
A proposal built from the prospect’s own scan data is different. It references their specific GBP score, their named competitors, and the exact categories where they are losing ground. F! Insights provides the data foundation that makes this possible – and this guide gives you the section-by-section structure to build from it.
Why Generic Proposals Lose on Price
A generic proposal presents a standard set of deliverables and asks the prospect to trust that they are the right ones for their situation. The prospect can’t evaluate the scope. They don’t know what’s actually wrong with their GBP, how severe the gap is, or what fixing it should realistically accomplish. So they evaluate the price. When scope is indistinguishable, the agency that wins is the one that charges less.
This is how agencies end up in a race to the bottom they didn’t mean to enter. The problem isn’t the price; it’s that the proposal didn’t make the scope look different from every other proposal the prospect received. “Monthly GBP management, review response, and local rank reporting” sounds the same whether you charge $400/mo or $1,400/mo.
A data-backed proposal presents the prospect’s specific situation first. The scope is a direct response to what the data shows. “GBP profile optimization: you have 4 service categories listed. The top-ranked business in your category has 11, covering 26 specific services. We will expand your services list to 25+ with descriptions targeting the specific queries your competitors are showing for” is a different statement than “GBP profile optimization.” It’s specific. It’s verifiable. It anchors the price to a concrete deliverable.
The Data-Backed Alternative
To learn more about turning free audits into signed retainer clients, visit Turn Free Audits Into Retainer Clients. Build a Review Request Sequence Your Clients Will Use and Turn a Low Review Score Into a Local SEO Sales Conversation cover adjacent steps in detail.
When you run a prospect’s business through F! Insights before writing the proposal, you have:
- Their GBP score across 8 categories (0–100 per category, composite overall score)
- Named competitors with review counts, average ratings, and relative positioning in the local pack
- The specific profile fields they are missing or underoptimized
- Their mobile PageSpeed score and the category average for their market
- Prioritized recommendations generated by AI based on their actual data – which gaps to close first, in order of impact
- A comparison of their post cadence and photo activity against category leaders
Every item in the scope section of your proposal should trace back to one or more of these findings. That’s what makes the proposal read as diagnosis rather than pitch.
Proposal Structure
The proposal has five sections. Each one builds on the previous. Do not skip straight to scope and price. The client hasn’t yet seen that the scope is specifically their scope.
Section 1: Your Current Position.
Present the scan findings as a data summary. Overall score, each category with its score and a one-line explanation of what that score means, and the named competitors they’re benchmarked against. This section should look like an audit report, not a sales pitch. The word “we” should appear as few times as possible here. This is about them, not you.
Sample language: “Your Google Business Profile was scored across 8 categories against the top-ranked businesses in [Category] in [City]. Overall score: [X]/100. The category leader, [Competitor Name], scored [Y]/100. The areas with the widest gap are Customer Reviews ([their score] vs. [competitor score]) and Website Performance ([their score] vs. [competitor score]).”
Section 2: The Gap Analysis.
For each low-scoring category, explain what the gap means in practical terms, not in SEO jargon, but in terms of what it costs them. The audience is a business owner who knows they’re not getting enough calls, not an SEO practitioner who knows what PageSpeed means.
Sample language: “Your Customer Reviews score is [X]/100. [Competitor Name], the business currently ranking #1 when someone searches ‘[Primary Keyword] [City]’, has [review count] Google reviews. You have [their count]. That gap means that for most searches in your market, your business appears lower in local results than this competitor, even when you’re geographically closer to the searcher. Closing the review gap is the highest-impact single action available in your profile.”
Section 3: The Scope.
Map each deliverable directly to a gap from Section 1. Every line item in the scope should answer the question: which gap from the audit does this address?
Section 4: Success Metrics.
Use the gaps as the baseline. Specific numbers, specific targets, specific timelines. Avoid vague language like “improve local presence.”
Section 5: Investment.
Price, payment terms, and what happens next. One clear call to action at the end.
The Scope Section
The most common mistake in data-backed proposals is reverting to generic scope language after a strong audit section. If Section 1 says “Customer Reviews: 34 reviews vs. competitor average of 210,” Section 3 cannot say “monthly review management.” It has to say something specific.
Map every scope item to a specific finding from the scan:
| Audit Finding | Scope Line Item | Target Outcome |
|---|---|---|
| Customer Reviews: 34 reviews. Category average: 127. Top competitor: 287. | Review acquisition system: SMS request template, post-job trigger workflow, monthly follow-up sequence | 50+ new reviews in 6 months; close gap to category average by month 9 |
| Website Performance: Mobile PageSpeed 23. Category average: 54. Top competitor: 78. | Core Web Vitals audit and site speed optimization (developer hours included) | Mobile score above 60 within 60 days of engagement start |
| Business Information: 5 services listed. Category leader: 24 services. | GBP services expansion: add 20+ specific services with keyword-targeted descriptions | Profile Completeness score above 80 within 30 days |
| Local SEO Signals: Post cadence of 0 posts in last 30 days. Category leaders: 4–5 posts/month average. | GBP post scheduling: 4 posts/month (AI-drafted, approved by client, published on schedule) | Consistent weekly post cadence within 30 days |
For how to use the scan report as the proposal foundation in a sales meeting rather than a written document, see How to Run a Diagnostic Sales Meeting for Local SEO.
Metrics and Timeline
Proposals fail to close when they make vague promises about outcomes. Use the scan data to anchor your success metrics to specific, measurable gaps. The metrics section should have a clear structure:
- Baseline: the specific number from the scan report. Not “your current reviews are low” – “your current review count is 34, as of [scan date].”
- Target: the specific number you are committing to move it to, and by when. “50 additional reviews within 6 months” is a target. “Increase reviews” is not.
- Leading indicator: the activity metric that shows progress before outcomes appear. “4 review requests sent per week via the SMS workflow” is the leading indicator that predicts the 50-review outcome.
Be honest about timelines. Review velocity improvements compound over 3–6 months. GBP profile completeness improvements show faster. Website speed improvements typically resolve within 60 days of implementation. Competitive position changes (showing up higher in Map Pack results) lag behind the profile and review improvements by 4–12 weeks.
A timeline table in the proposal is useful when it’s specific:
| Month | Activity Milestones | Outcome Milestones |
|---|---|---|
| Month 1 | Profile optimization complete; services list expanded; review system deployed; first 4 GBP posts published | Profile Completeness score above 80; baseline ranking documented via geogrid |
| Month 2–3 | Review cadence established; weekly posts maintained; website speed fixes delivered | 10–20 new reviews; mobile PageSpeed above 60; initial Map Pack movement visible |
| Month 4–6 | Ongoing review velocity; monthly reporting; post cadence and photo updates | 30–50+ new reviews; measurable Map Pack position improvement; monthly reporting shows trend |
Pricing the Proposal
Price the proposal based on the gap severity, not on a standard rate card. A business with a composite score of 28/100 across 8 categories has more work ahead than one with a score of 62. The same deliverables cost you more time to execute when the starting point is worse.
Tiered pricing that maps to gap severity is one approach: a “Foundation” scope for businesses with moderate gaps, a “Competitive” scope for businesses with severe gaps in multiple categories, and a “Aggressive” scope for businesses with wide competitive gaps that need to close quickly. The audit data tells you where each prospect lands.
Retainer vs. project pricing is a separate decision. For businesses with acute, fixable gaps (profile completeness, photo count, services list), a one-time project fee makes sense if the client wants to self-manage after the initial work. For ongoing deliverables (review velocity, post scheduling, monthly reporting), a retainer is the right structure. The audit data usually makes clear which category a prospect falls into: businesses with profile gaps need project work first, then ongoing maintenance. Businesses with review gaps need ongoing systems, not one-time fixes.
For the retainer conversion conversation – moving a client from a one-time project to ongoing work – see Use a GBP Report to Justify Your Monthly SEO Retainer.
Sending It
Send the proposal as a PDF or a shared document. Include a one-paragraph cover note that references the single most significant finding from their scan, the gap that should feel most urgent to the business owner.
Sample cover note: “Attached is the full proposal based on the GBP audit we ran for [Business Name] last week. The most significant finding was the review gap: [their count] reviews versus [competitor name]’s [competitor count]. The scope in Section 3 prioritizes closing that gap first, which is where ranking movement is most likely to come from in months 1–6. Happy to walk through any section. Just let me know a good time.”
The proposal should be readable without context. A decision-maker who was not in the original conversation should be able to read it and understand the problem, the solution, and the price without needing to ask you what any of it means. If any section requires explanation to make sense, rewrite it before sending.
Set a follow-up appointment before you send, not after. “I’m sending this now. Can we schedule 20 minutes on Thursday to go through the scope section together?” A confirmed follow-up meeting means you review the proposal with the client rather than waiting for them to reply. Reviewed proposals close at significantly higher rates than unreviewed ones.
For the follow-up sequence after sending if you don’t have a meeting confirmed, see How to Follow Up After a Free SEO Audit Request.
Ready to build proposals from real data? See F! Insights pricing here.
Frequently Asked Questions
- How long should a local SEO proposal be?
- 5–8 pages for a standard retainer proposal. Long enough to present the audit findings, map the scope to specific gaps, and show clear success metrics. Short enough that the decision-maker reads all of it before the follow-up call. A 20-page proposal with detailed methodology sections works in large enterprise sales cycles. For local business clients, it’s usually too much. Keep the focus on their specific situation and the scope that addresses it.
- Should I include the scan report itself in the proposal?
- Yes. Include the scored audit as an appendix or within Section 1. The data is what makes the proposal specific. Without the scan data visible in the document, the proposal reads like a standard scope list. When the client can see their own scores, their competitor’s names, and the specific gaps, the scope section has a clear referent. Many agencies present the scan report first and then walk through the proposal as the plan for addressing what it shows.
- What if the prospect asks for a cheaper version of the scope?
- Map the scope reduction to the audit. If they want to drop review management from the scope, note specifically: “Your review count is 34 against the competitor average of 210. Removing review management from the scope means the primary gap driving your current ranking position isn’t addressed in months 1–6. I can scope that out, but I want to be clear about what that means for the expected outcome.” This isn’t pushback. It’s honest advice. Some prospects will reduce scope anyway; others will reconsider when they see what they’re removing.
- How soon after the initial conversation should I send the proposal?
- Within 24–48 hours of the discovery conversation, while the specific findings are fresh for the prospect. A proposal that arrives a week later, after the prospect has had multiple conversations with other agencies, is arriving into a different mental context than one that arrives the next morning. If you need more time to build the scope correctly, send a brief note that the proposal is coming tomorrow rather than sending a rushed version the same day.