This proposal responds to all seven sections of the Service Pros Auto Glass RFP. It is built for a 15-market service-area business that wants to scale paid acquisition, local visibility, and closed-loop attribution under fixed-fee economics with full account ownership.
Three things are true today, sourced from independent audit data we ran the week of April 21–25, 2026:
The keyword footprint gap tells the same story in one number. Service Pros ranks for 313 keywords at $789 per month in estimated organic traffic value. Safelite ranks for 6,428 keywords at $4.1 million per month. That is a 20-times keyword footprint gap and roughly a 5,250-times traffic value gap.
This is not an optimization engagement. The RFP describes the next 12 months as scale phase. The audit data says the build phase is unfinished. Our recommendation reframes the work as fix-then-scale: a defined seven-day repair on the existing site, a Next.js platform migration in Days 1 to 45, a 60-day attribution wiring, and a per-market scaling cadence that runs on cost-per-closed-job economics by Day 60 in Sarasota and on a documented trajectory in the rest of the portfolio by Day 180.
The platform migration is in scope and called out explicitly. The current WordPress + Elementor + Zynith stack cannot be iterated fast enough across 14 markets to drive per-market CPJ to target. Migrating to Next.js in the first 30 to 45 days, with AI-assisted development, is the precondition for the cross-portfolio CPJ commitments. We are not hiding that work or charging for it later. It is in the setup fee, the timeline, and the named deliverables.
PathOpt's commercial structure is aligned to RFP Section 9 by default. Service Pros owns every account. Service Pros pays Google directly. Zero markup on media. Fixed monthly retainer. 90-day initial term. 30-day cancellation after that. Full data and IP ownership stays with Service Pros.
Investment: $16,000 one-time setup (covers the Next.js migration plus initial GBP build-out across the 14 missing markets plus attribution wiring). $15,000 per month retainer.
This proposal commits to four things you will not see from most vendors who respond to this RFP.
Six outcomes were named in the RFP. Each is addressed in the scope, the 90-day plan, and the reporting commitment that follows.
| RFP Section 3 Outcome | Where It Lands in This Proposal |
|---|---|
| Achieve cost per closed job below $100 | Section 9 CPJ Reporting and Trajectory (Day-60 reporting; portfolio target by Day 180) |
| Increase qualified lead volume across all markets | Section 6 Per-Market Paid Architecture; Section 7 GBP Build-Out |
| Build full-funnel attribution (click → lead → closed deal) | Section 8 Closed-Loop Attribution Stack |
| Improve cost efficiency (CPL and CPS) | Section 9 Reporting; Section 11 Pricing Anchored on Conservative ROAS |
| Support expansion into new markets via repeatable model | Section 10 Sarasota Blueprint; Charleston 30-Day Proof |
| Integrate tightly with internal sales operations | Section 8 GoHighLevel and Inside-Sales Loop |
The RFP also names a marketing-philosophy constraint: each market is treated as an independent performance unit, with no blended reporting. We honor that constraint at the campaign-architecture level. Per-market budget, per-market CPL and CPJ, per-market GBP, per-market dashboard view. No cross-market averages used to obscure under-performers.
Pulled live from Google Ads Transparency Center, DataForSEO, Whitespark, CrUX field data, Common Crawl, and Maps API as of April 25, 2026. Sources are itemized in the appendix.
Service Pros is absent from the Google Local 3-Pack across all 10 of its website-targeted city pages.
| City Page | Local Pack Position | Top 3 Winners |
|---|---|---|
| Sarasota (HQ, 707 reviews, 4.9 stars) | Not in pack | A Star Auto Glass (185), Adonis Auto Glass, Safelite |
| Tampa | Not in pack | TRUE Mobile Auto Glass, FMG Florida Mobile Glass (288), Same Day Windshield (2.5K) |
| Orlando | Not in pack | Glass Doctor, Safelite, regional independents |
| Jacksonville | Not in pack | Safelite, Auto Glass Now, regional |
| Ft Myers | Not in pack | Regional + national |
| Tallahassee | Not in pack | Regional |
| Ocala | Not in pack | Regional |
| Brighton Bay (St. Pete) | Not in pack | Bay Area Auto Glass (literally on Brighton Bay Blvd) |
| Largo | Not in pack | Regional |
| Clearwater | Not in pack | Regional |
The most expensive line on this table is Sarasota. With 707 reviews at 4.9 stars and a 96% response rate, the only reasons not to be in the pack are GBP configuration and on-page signal. Both are inside our scope.
Hollywood, Miami, Lakeland, Melbourne, Charleston, Columbia, and Greenville are not represented above because no city page currently exists for these markets, so there is nothing yet for the Local 3-Pack to evaluate against. These 7 markets become Local Pack candidates as their Next.js city pages and GBPs come online (Section 10).
DataForSEO live pull, Florida market, April 2026:
| Brand | Ranked Keywords (FL) | Estimated Traffic Value (Monthly) |
|---|---|---|
| Safelite AutoGlass | 6,428 | $4,146,185 |
| Service Pros Auto Glass | 313 | $789 |
That is roughly a 20-times keyword gap and a 5,250-times traffic value gap. Service Pros' top organic rankings are essentially brand-only. Of 24 cross-market keywords tracked across the portfolio, zero sit on page one in any market. Average position across ranked terms is 39.5. Orlando shows zero organic visibility on its 4 tracked keywords.
Google Ads Transparency Center, pulled April 25, 2026: zero active ads, zero recent ads, no detected creative footprint for serviceprosautoglass.com. The brand is not even bidding on its own brand terms. Florida search demand for the seed keyword set is 40,800-plus per month. Long-tail is 80,000-plus. Weighted Florida CPC is $11.60. Peak is $22.50 for "windshield replacement st petersburg." Florida Statute §627.7288 means the customer pays $0 and the shop bills insurance $300 to $1,200-plus per job. There are 17.2 million registered vehicles in Florida (Florida DHSMV, 2025).
The math is straightforward. There is real demand, real margin per job, and real intent volume. None of it is being captured.
The full SEO audit (April 25, 2026) flagged six issues that need to be fixed before any optimization or scale work yields compounding returns. Each is referenced by ID below and re-appears as a Day-1-to-30 deliverable in Section 10.
| ID | Issue | Why It Matters |
|---|---|---|
| C1 | 24 indexed /project/* placeholder pages with theme-demo titles ("Helthy Solutions", "Market Expansion", "Washing Cars") | Sitewide quality liability. Generic boilerplate content, ~250 words each, indexable, in /sitemap.xml. Drags every other page's quality score. |
| C2 | Tampa city page declares conflicting NAP (3104 N Armenia Ave + 813-819-9989) vs. Sarasota HQ | Creates a duplicate business entity for citation crawlers. Yelp, BBB, and Yext will harvest a phantom second location. Real commercial concern, not a cosmetic one. |
| C3 | GBP likely misconfigured as Brick-and-Mortar instead of Service-Area Business | Whitespark's 2026 ranking factor study lists this as the #1 local-pack suppressor (-176 score). For a mobile-only operator, this is a category-level mistake. |
| C4 | Zero structured data sitewide | No rich-result eligibility. No AI Overview citability. No LocalBusiness, AutoRepair, FAQPage, Article, Service, or AggregateRating schema present. |
| C5 | Duplicate /service/[slug] and /our-services/[slug] URL paths | 4 services × 2 paths = 8 indexed duplicate pages splitting PageRank between mirror URLs. |
| C6 | OG title is the WordPress page label "Home Page 02"; duplicate H1 with typo "Repairs Services" | Every social share, every LLM crawl, every link preview shows "Home Page 02" as the brand name. Brand-damaging at every linked surface. |
Field performance (CrUX 28-day p75 real-user data): FCP 1376ms good, LCP 1833ms good-borderline, INP 60ms good, CLS 0.17 needs improvement, TTFB 890ms needs improvement. Mobile Lighthouse Performance scores 23 to 47 across the three sampled URLs.
| Market Tier | Count | Status |
|---|---|---|
| Sarasota | 1 | Verified, 707 reviews, 4.9 stars, 96% response, last review 1 day ago. Only working GBP. |
| Markets with site page, no GBP | 7 | Clearwater, Orlando, Jacksonville, Ft Myers, Tallahassee, Tampa, Ocala (page exists; no Maps presence). Plus 2 additional site pages discovered in audit but not in RFP appendix: Brighton Bay (St. Pete) and Largo, both flagged for committee resolution in Section 17. |
| Markets with no site page and no GBP | 7 | Miami, Hollywood, Lakeland, Melbourne, Charleston SC, Columbia SC, Greenville SC |
Sarasota is the proof point. It is also the only one. Building 14 GBPs across the rest of the footprint is the single highest-leverage local SEO move on the table.
We are not pitching this as a teardown. The conversion infrastructure on the site is solid. Click-to-call phone in the header. Active contact form. Live chat widget. Online booking widget. SSL, viewport meta, H1 present. The Sarasota GBP is a category-leading review profile (707 at 4.9 stars). Tranel confirmed call tracking is in place and GoHighLevel is the CRM. Edit access on the site is available to the marketing partner. The bones for closed-loop attribution exist; they need to be wired.
The RFP describes the next 12 months as scale phase. Independent audit data says the foundation does not yet support compounding returns from scaled paid spend. Spending $30,000 to $60,000 per month into a site that scores 39/100, GBPs that do not exist in 14 of 15 markets, and an attribution layer that cannot tie spend to closed jobs is the textbook definition of expensive learning.
The 90-day plan that follows splits the work into two tracks running in parallel.
Track 1: Fix. The six critical site issues (C1 through C6), the four high-priority issues (H1, H2, H6, H10), and the GBP build-out for the 14 missing markets. Engineering work moves the SEO score from 39 to roughly 55. The full GBP build runs 60 to 90 days depending on Google's verification cadence per market. None of this requires a media budget.
Track 2: Scale. Paid restructured for Sarasota first because it is the only market with a working GBP and review base to support it. Charleston as the end-to-end proof commitment, built natively on the new platform as the first market on Next.js. Per-market paid expansion follows once each market has a verified GBP, a Next.js city page, and the attribution layer is wired.
The scale lever is real. Florida demand is real. Insurance economics are real. The reason to fix first is not caution. It is that compounding returns require working infrastructure and the site does not yet have it.
The current site runs on WordPress + Elementor + Zynith SEO + WP Engine + Cloudflare. That stack got the brand to where it is. It will not get the brand to sub-$100 cost-per-closed-job in 14 markets that do not yet have working pages.
Two reasons.
First, iteration speed. Per-market landing-page work, conversion-rate testing, schema deployment, location-page generation at scale, and Core Web Vitals tuning all run faster, cleaner, and cheaper on Next.js than on Elementor. The current CLS score (0.17, needs improvement) and TTFB (890ms, needs improvement) are tied to the Elementor bloat and the WP Engine origin. We can patch CLS as a Day-1 fix (H10), but we cannot drive performance to where it needs to be for paid efficiency without leaving the page builder.
Second, dependency control. Every change to an Elementor + Zynith site that goes beyond cosmetic risks pulling in a third-party plugin developer. That breaks the "we control the build" commitment and adds delivery time and cost we do not control. Migrating to Next.js means PathOpt's team owns the codebase end-to-end. No Elementor consultants. No Zynith plugin dependencies. No WP Engine-tied performance ceiling.
We will not hide this. The migration is in scope, in the timeline, and in the setup fee. AI-assisted development across the build is how we hit the 30-to-45-day window without inflating cost. Section 10 lays out the parallel-track plan.
Migration risk and mitigation. The migration runs in a staging environment at a parallel domain throughout the build, with full traffic preserved on the existing WordPress site. Cutover is single-step at completion, with all 80-plus existing URLs preserved or 301-redirected as part of the launch. Search Console is monitored for indexation changes for 14 days post-launch. If Day 45 slips for any reason (Google verification cadence, content review delays, or scope clarification), the existing WordPress site continues serving traffic at full performance. PathOpt absorbs any cost overrun; the migration is fixed-fee inside the setup, not time-and-materials.
| Channel | Role | Per-Market Allocation Logic |
|---|---|---|
| Google Search (brand + non-brand) | Primary intent capture | 55–70% of per-market budget |
| Google Performance Max | Inventory expansion (Search + Display + Discover + YouTube + Maps) | 20–30%, after first 30 days of Search baseline |
| Google Demand Gen (formerly Discovery Ads) | Upper-funnel reach | 5–10%, Sarasota first then expand |
| Meta (Facebook + Instagram) | Retargeting + lookalikes off site visitors and CRM seed lists | 5–15%, secondary per RFP Section 5.1 |
| LSA (Local Services Ads) | Not applicable | Google does not support auto glass as an LSA category. Confirmed via Google's published category list. Implied LSA budget is reallocated to PMax + Demand Gen. |
The LSA point matters because the RFP names it as a possible channel. We checked. It is not eligible. Vendors who include LSA in the proposal are either pulling from a template or have not verified.
Each of the 15 markets runs as its own Google Ads campaign, its own GBP, its own conversion-tracking setup, and its own dashboard slice. Per RFP Section 4: no blended reporting. The dashboard surfaces CPL, CPJ, close rate, and ROAS per market, not as portfolio averages.
Budget allocation is performance-based by market. A market with $3,000 per month and a 3.7-times ROAS is not topped up to match a market that is not yet performing. The under-performer either gets diagnosed or gets paused. That decision is yours; the data is ours to surface clearly.
Tranel described an envelope of $2,000 to $4,000 per market per month. Across 15 markets, that is $30,000 to $60,000 per month aggregate. Ad spend is paid by Service Pros directly to Google, Meta, and any other platform. Zero markup on PathOpt's side. Zero percentage-of-spend fees. Per RFP Section 5.1 and Section 9, both verbatim.
Seven RFP-appendix markets have a site page but no GBP. Seven RFP-appendix markets have no site page and no GBP. Sarasota is the only fully built local entity. Total 14 GBPs to build to bring the RFP appendix into full coverage.
Two additional site pages exist for off-appendix markets (Brighton Bay and Largo). Their status is flagged for committee resolution in Section 17 and they are counted outside the 14-market in-scope footprint until resolved.
The build sequence is Charleston first (the 30-day proof commitment, see Section 10), then the seven RFP-appendix markets with existing site pages, then the remaining six markets from the Service-Area-Business tier. Each build includes:
Per RFP Section 5.4: local SEO per market, location plus service pages, technical SEO, keyword tracking. The work breaks into:
/service/[slug] → /our-services/[slug])The site service-area copy currently lists "Sarasota, Tampa, Orlando, Fort Myers, Tallahassee, Ocala, and Gainesville." The RFP appendix names 15 markets and does not include Gainesville. Tampa is also flagged in C2 for a phantom second NAP (3104 N Armenia Ave). Both fixes happen in Week 1 and require no engineering. They require a decision from your team on the canonical address per market. We will surface the questions; you confirm; we update.
This is the section the RFP flags as critical (Section 5.5: "We are not interested in vendors who cannot close the loop between marketing and revenue.") and the section Tranel confirmed is "still being built out, and that's a core focus of this initiative."
| Layer | Tool | Role |
|---|---|---|
| Click and form tracking | WhatConverts | Per-market call tracking numbers, form-fill capture, source attribution at the channel and keyword level |
| Server-side conversion API | Google Ads Enhanced Conversions + Meta CAPI | First-party data sent server-side to ad platforms for accurate cost-per-conversion reporting |
| CRM and call-center | GoHighLevel (existing) | Lead distribution, technician dispatch, job-status tracking, review-request automation |
| Closed-loop bridge | WhatConverts → GHL → custom dashboard | Lead source flows from ad click through booking through job completion to revenue |
| Reporting | Looker Studio dashboard (per-market view) | CPL, CPJ, close rate, ROAS per market, refreshed daily |
Two-direction loop:
Standing weekly sync between PathOpt and your call-center lead. Monthly review with Tranel on what the data is telling us about lead quality vs. lead volume.
The RFP requires cost-per-closed-job reporting within 60 days. Here is the honest scoping.
Tier 1: Sarasota. Live CPJ measurement reported. Attribution layer fully wired. Playbook documented and running cleanly. Sarasota is the proof market for the cross-portfolio expansion because it has a verified GBP, a 707-review base at 4.9 stars, an active site page, and a working call-tracking setup. The CPJ number itself is the output; the goal of the engagement is to drive that number toward sub-$100 over time.
Tier 2: 3 to 5 markets in mid-build. GBPs submitted to Google (PathOpt-controlled, completed Week 1 to Week 2). Paid campaigns running on existing site city pages while GBP verification works through Google's 60-to-90-day window. Closed-loop attribution is wired by Day 60, so paid CPJ measurement is live and reportable for these markets at Day 60 even before their GBPs verify. Local Pack contribution to CPJ comes online market-by-market as each GBP verifies, which sits in Google's cadence. At Day 60 the committee receives a per-market status report: GBP submission date, expected verification window, paid CPJ measurement to date, and the trajectory line for full (paid + organic) CPJ once verification arrives. Most likely candidates based on existing site presence and submission feasibility: Tampa, Orlando, Jacksonville, Ft Myers, Tallahassee.
Charleston is on its own track. As the first market launched on the new Next.js platform (target Day 35–45), Charleston will have approximately 15 days of post-launch data at Day 60. That window is directional, not statistically meaningful. Charleston's first credible CPJ measurement falls inside the Day 90 review, alongside the Year-2 expansion-market decision.
Tier 3: 9 to 11 markets. Trajectory documented. Written plan showing how each reaches target CPJ by Day 180, with monthly checkpoints at Day 90, Day 120, Day 150, and Day 180.
The Day-60 report covers every market where three operational gates have closed: paid traffic flowing through the new attribution stack, closed-loop attribution wired and producing closed-job data, and enough volume to form a meaningful number. Three factors determine which markets clear those gates by Day 60.
First, GBP verification cadence. 14 of the 15 RFP markets need new GBPs. Verification is a 60-to-90-day process driven by Google's cadence, not ours. Markets verify market-by-market and enter the full paid-plus-organic CPJ report as they do.
Second, the Next.js migration. The current WordPress + Elementor + Zynith stack cannot be iterated fast enough across 14 markets to drive sustained per-market CPJ optimization. The migration in Section 10.2 (target Day 45) is the precondition. Per-market CPJ measurement starts when paid traffic flows; sustained CPJ optimization unlocks once the platform is on Next.js.
Third, the closed-loop attribution layer. WhatConverts plus the GHL job-completion feedback loop is mid-build at Day 0 and operational by Day 60.
The Day-60 report will show, per market: paid CPJ measurement where data exists, GBP verification status, the trajectory line for full paid-plus-organic CPJ, and the path to sub-$100 over the engagement.
Per the search-demand-report's explicit recommendation, we anchor expectations on the conservative case, not the base case. Inputs: $11.60 weighted Florida CPC, 50% lead-drop stress test applied, $350 average ticket, ROAS calculated post-stress.
At the conservative case, $3,000/month per market generates 32 jobs at $93.75 cost-per-closed-job. That is already inside the RFP's sub-$100 CPJ target, on stress-tested assumptions, before any optimization.
| Monthly Spend (Per Market) | Jobs (Conservative) | Revenue (Conservative) | ROAS |
|---|---|---|---|
| $2,000 | 21 | $7,400 | 3.7× |
| $3,000 | 32 | $11,200 | 3.7× |
| $4,000 | 42 | $14,800 | 3.7× |
Even at conservative case with double-stress assumptions baked in, this clears the industry-typical 3-to-4-times ROAS benchmark. In other words: the unit economics work at the floor. The base case (9.5× ROAS, ~$36 CPJ) is what we expect once attribution is wired and per-market optimization is running. Pricing this proposal on the conservative case is a credibility choice, not a math limitation.
The first 90 days run on three parallel tracks: critical fixes on the existing site (Days 1–7), the platform migration to Next.js (Days 1–45), and the attribution wiring and paid restructure (Days 1–60). Charleston comes online as the first market on the new platform. Sub-$100 CPJ commitments beyond Sarasota are gated on the migration completing.
These run on the current WordPress + Elementor site because they cannot wait for migration. They unblock indexation quality immediately and stop active brand damage.
| ID | Deliverable | Outcome |
|---|---|---|
| C1 | Delete or noindex 24 /project/* placeholder pages | Removes sitewide quality liability |
| C2 | Remove or isolate Tampa second-NAP block | Eliminates phantom-location risk |
| C3 | Reconfigure GBP into Service-Area Business mode (hide HQ address) | Removes the #1 local-pack suppressor per Whitespark |
| C4 | Deploy AutoRepair JSON-LD on homepage and per-service pages | Restores rich-result and AI Overview eligibility |
| C5 | 301-redirect /service/[slug] → /our-services/[slug] | Consolidates split PageRank |
| C6 | Fix homepage OG title; fix duplicate H1 with typo | Stops "Home Page 02" from leaking into every share |
| H1 | Sitemap directive cleanup | Crawler signal hygiene |
| H2 | Deploy /llms.txt for AI crawler accessibility | AI search readiness |
| H6 | Cloudflare security headers (CSP, HSTS, X-Frame-Options) | Trust signal for crawlers and browsers |
| H10 | CLS fix on the home page hero (currently 0.17, target <0.10) | Core Web Vitals into all-good range |
These fixes move the audit score from 39 to roughly 55 by end of Week 1. None of it requires media budget. None of it depends on Google verification timing. None of it requires the migration to be complete.
This track runs in parallel with Track A from Day 1 and is the single most important infrastructure decision in the engagement. We are calling it out explicitly so the committee can evaluate it with eyes open.
Scope of the migration:
How we hit 30 to 45 days: AI-assisted development across page generation, schema templating, content adaptation, and component scaffolding. The same per-market template renders 15 city pages with per-market content variation. Without AI assistance, this scope is a 90-to-120-day project. With it, 30 to 45 days is the realistic window.
Charleston as first market on the new platform. Charleston launches on Next.js inside the migration window (target Day 35–45) as the end-to-end proof commitment: new platform, new city page, verified GBP, local SEO setup, review-request flow wired into GHL, paid structure stood up. The committee gets a tangible before-and-after demo at the Day-30 review and a fully-launched first-market proof at Day 45.
Why this unlocks sub-$100 CPJ beyond Sarasota. The current Elementor + Zynith stack cannot be iterated fast enough to drive per-market CPJ to target across 14 markets. Page-speed gains, per-market schema, A/B variants, and conversion-rate tests all run cleanly on Next.js. They do not run cleanly on Elementor without pulling in third-party developers we do not control. The migration is the precondition for the Tier-2 and Tier-3 CPJ commitments in Section 9.
| Component | Amount | Coverage |
|---|---|---|
| One-time setup fee | $16,000 | Next.js platform migration with AI-assisted development (Days 1–45), including site rebuild, per-market location-page architecture, 7 new city pages built natively, 10 existing city pages rebuilt, schema templating, and 301-redirect cutover. Plus: WhatConverts deployment, initial GBP build-out and verification across 14 missing markets, closed-loop attribution wiring, kickoff and audit consolidation, project management for the first 60 days. |
| Monthly retainer | $15,000 / month | Full digital ecosystem management. Paid across 15 markets. GBP and reviews. Local SEO. Content and AI-assisted editorial. Paid social and retargeting. Attribution and dashboards. GHL CRM administration and build work. Client-services management. Ongoing site work. |
| Ad spend (pass-through) | $30,000 – $60,000 / month | Paid by Service Pros directly to Google, Meta, and other platforms. Zero PathOpt markup. Per RFP Section 9. |
Itemized below per the RFP's non-negotiable list. Each item is a hard contract term, not a paraphrase.
| Role | Name | Function |
|---|---|---|
| Engagement Lead | Justin Dews, Founder & CEO | Single accountable owner across all workstreams. Direct execution on Next.js development with AI tooling, GBP buildout across the 14 missing markets, attribution stack wiring (WhatConverts + GoHighLevel + Looker Studio), workflow automation, and per-market paid optimization. Weekly Tranel touchpoint, monthly QBRs. |
| Operating Partner | Jeremy Stakely, Co-Founder | Active execution support across Next.js development and multi-location operational architecture. MSP-era multi-location operator background (technician dispatch, per-location P&L, call-center integration). Co-leads QBRs, escalation, and relationship continuity. |
| Strategic Advisor | Reese Ormand, Co-Founder PathOpt; CEO NeuroGlow | Authored the 15-market GBP audit. Senior-level strategic reviews and operator-relationship lens. |
This is a two-operator delivery model. Justin and Jeremy execute the engagement directly. AI tooling is the leverage layer that makes 15-market parallel delivery economically viable: per-market city page generation, schema templating, GBP content drafting, and attribution dashboard scaffolding all run with AI assistance and human validation. We are not headcount-padding the retainer with junior account managers, nor are we routing the build through contractors named at contract execution. The committee gets a single accountable owner, an experienced operating partner, and direct execution.
All three PathOpt founders built and exited multi-location businesses in the MSP industry. Multi-location service-area economics, technician dispatch, per-location P&L, and call-center integration are not abstractions; they are operating context.
PathOpt has not run an auto-glass marketing engagement. We also do not maintain published case studies. The references in §14.2 are how the committee can interrogate the actual work, in the actual clients' words, instead of reading our marketing copy. We say all of this directly because the alternative is bending an unrelated case study to look like it fits, which would compromise the diligence signal that runs through the rest of this proposal.
The RFP Section 7 language permits home services, automotive, OR multi-location service-area businesses as relevant industries. The two engagements named in §14.2 plus the principals' MSP-era operator background are our most directly applicable work.
What transfers cleanly to this engagement:
What does not transfer and will be absorbed during the engagement:
We will not claim auto-glass operating fluency on Day 1. The audit work already in this proposal shows how PathOpt absorbs unfamiliar categories: independent research, reference to published authorities (Whitespark, DataForSEO, CrUX, Florida DHSMV), and direct conversation with the people who run the business. The same pattern applies to learning the auto-glass-specific mechanics.
Two named references aligned to the RFP Section 7 minimum, included with this proposal. Both speak directly to the multi-location service-area, closed-loop attribution, and WordPress-to-Next.js migration scope that defines this engagement.
PathOpt took over performance marketing from a traditional agency, including Google Ads budget management across both Homeworks Construction and Design and its sister business Chad the Handyman. PathOpt migrated both websites from WordPress to Next.js, deployed WhatConverts for end-to-end lead tracking and attribution (form fills and phone calls from organic, paid, and direct), wired closed-loop attribution through GoHighLevel, and built a custom integration layer to bridge BuilderTrend (a closed line-of-business project management application) into the attribution stack so paid spend ties to closed remodeling jobs. PathOpt also deployed AI voice agents for after-hours call handling.
Contact: chad@homeworks-swfl.com / (239) 877-3979
PathOpt took over performance marketing from a traditional agency, including Google Ads budget management across OFDC's two locations (Fort Myers and Sarasota). PathOpt is currently rebuilding OFDC's website on Next.js (project in flight, not yet shipped) and has deployed WhatConverts for lead tracking and attribution.
Contact: cbaird@ofdc-inc.com / (239) 337-1212
Both references are available for committee outreach and willing to speak directly to:
| RFP Section | Scope Item | Where in This Proposal |
|---|---|---|
| Section 5.1 | Paid Advertising (Core Driver) | Section 6 Per-Market Paid Architecture |
| Section 5.1 | Fixed monthly fee, no % of spend | Section 11 Pricing; Section 12 Commercial Terms |
| Section 5.1 | Client pays platforms directly | Section 12 Commercial Terms (item 2) |
| Section 5.1 | LSA where applicable | Section 6.1 (Note: Google does not support auto glass as LSA category. Reallocated to PMax + Demand Gen.) |
| Section 5.2 | Website and Conversion Optimization | Section 10.1 (C1–C6, H1–H10); Section 7.2 location-page rebuilds |
| Section 5.2 | A/B testing framework | Built into per-market landing page program post-Day 60 |
| Section 5.3 | GBP Management | Section 7.1 14-Market GBP Build |
| Section 5.3 | Review-generation strategy | Section 7.1 (review-request automation in GHL) |
| Section 5.3 | SAB compliance | C3 in Section 10.1; SAB-mode configuration is the build standard |
| Section 5.4 | SEO and Content | Section 7.2 Local SEO Layer |
| Section 5.4 | Per-market location and service pages | Section 7.2 |
| Section 5.4 | Technical SEO | Section 10.1 (C1–C6, H1–H10) |
| Section 5.4 | Keyword tracking | Per-market keyword tracking in Looker Studio dashboard |
| Section 5.5 | Lead Tracking and Attribution (Critical) | Section 8 Closed-Loop Attribution Stack |
| Section 5.5 | Call and form tracking by location | Section 8.1 WhatConverts per-market numbers |
| Section 5.5 | Integrate with internal sales data | Section 8.3 Inside-Sales Integration |
| Section 5.5 | Report on CPL, close rate, CPJ | Section 9 The Honest CPJ Commitment |
| Section 5.6 | Inside Sales Integration | Section 8.3 Two-direction loop |
| Section 5.7 | AI chatbot for lead qualification | Recommended for Phase 2 (Day 90+) once foundation is stable |
| Section 5.7 | Retargeting | Section 6.1 Meta retargeting (5–15% of per-market spend) |
| Section 5.7 | Expansion frameworks | Section 10.3 Year-2 expansion-market decision point at Day 90 |
If this proposal aligns with what the committee is solving for, the path forward is straightforward.
Step 1. Vendor presentation, April 28–30. We will walk the committee through the audit slide, the fix-then-scale reframe, the 90-day plan, and the commercial framework. Time set aside for questions. The committee leaves with the data file and the plan.
Step 1a (during presentation). Four open questions for the committee that affect scope before contract:
Step 2. Selection decision per the committee's stated timeline.
Step 3. Contract execution. Standard PathOpt MSA pre-aligned to RFP Section 9 terms.
Step 4. Kickoff Week 1. C1 through C6 fixes complete by end of Week 1. Charleston build kicked off. WhatConverts rollout started.
Step 5. Day-30 review. Charleston live. Site score moved 39 to ~55. First per-market dashboards live.
Step 6. Day-60 CPJ report. Sarasota target hit. Tier-2 markets in baseline. Tier-3 trajectory plan delivered.
Step 7. Day-90 quarterly business review. Decision point on expansion-market scope and Year-2 contract continuation.
The committee has three responses available.
Yes: This is the partner. Move to contract. Kickoff target Week of [target start date].
No: This is not the partner. We respect the call. We will leave the audit data with you regardless. No catch.
What would have to be true: Tell us what is missing. If the answer is a case study in auto glass specifically, we cannot produce one because we have not done the work. If it is references, we will provide them. If it is scope adjustment, we will adjust. If it is pricing structure, RFP Section 9 already pre-aligns the structure.
All audit data and competitive intelligence cited in this proposal is sourced from:
Source-by-source citations available on request and embedded in the underlying intake document.
Items below need committee input before or during the April 28–30 presentation. None block the written proposal.