Website
Proposal

1. Line items priced separately. No bundled retainer math. Each piece of work stands on its own and is priced against its own value.
2. A structure that fits how you plan accounting and budget. Project-based pricing where possible, not recurring commitments that obscure what each dollar is buying.
3. Clear line of sight from each dollar to the business outcome it drives. Every line in this proposal should answer the question: what does this specific piece do for Raydar's bottom line.

That feedback shaped this proposal:

• One workstream per conversation. This document covers the website only. Google Ads management becomes a separate conversation once 1ST ON THE LIST access is restored and we have the spend and conversion history to work with. AI consulting becomes a separate in-person session on a different timeline and a different budget structure.
• Three website tiers, priced as one-time projects. Pick the tier that fits this quarter's budget and Raydar's near-term priorities. The other two stay available as future expansions.
• Every feature in every tier traces to a measurable outcome. No bundled value-stack math. No "trust the long term." Each line in the tier breakdown is there because it moves a number you care about.

What that means in practice:

• Mobile-first. Most collision repair searches happen on a phone, often from the side of the road. The site is engineered for that moment.
• Geolocation-driven. A visitor lands, allows location access or types their city, and immediately sees the closest Raydar shop on a map. One tap opens the location page. One more tap opens a fully branded booking flow.
• Dual-brand respected. Every location page leads with its legacy shop name. Coache Collision in North Vancouver shows up as Coache Collision first, identified as part of Raydar Collision Group second. The acquisition story is preserved and amplified, not erased.
• Ray on every page. Raydar's existing voice and chat assistant is embedded site-wide as a concierge. Visitors who want to talk to Ray instead of clicking through the site can do so, and Ray hands off to the right shop's Project Sync booking flow when the conversation reaches that point.
• Owned end to end. Raydar holds the keys. Code, content, hosting credentials, design files, customer data. Internal staff handles routine updates through a clean admin portal. No phone calls to an external developer for content changes.

• Raydar runs at roughly 8% net margin. Any growth investment has to make sense in profit dollars, not revenue dollars.
• A $9,500 per month expense against a projected $1,000 to $3,000 per month profit lift does not pencil.
• Anything beyond your $10,000 anchor for a website investment needs explicit justification.

Three rules this proposal follows:

1. Entry tier priced inside your $10K anchor. Foundation is $9,750 one-time. Not a recurring retainer. Not a bundled monthly fee.
2. Value calibrated to profit dollars, not revenue dollars. Every ROI number in section 10 is shown at Raydar's 8% net margin. The numbers you should care about, in the form you care about them.
3. Every tier shows measurable ROI inside 12 months without relying on speculative compound effects. Foundation pays back inside the first year on conversion lift alone. Growth pays back faster. Ecosystem add-ons each carry their own ROI math when triggered, scoped against the specific growth question they answer.

What that means day to day:

• Internal staff updates the site. Hours, photos, blog posts, FAQ, location pages, insurance partner logos, OEM certifications, careers postings. No phone calls to a vendor. No tickets in someone else's queue.
• New locations slot in cleanly. When Raydar acquires the next shop, internal staff can add a location page from the template. No new web project required.
• VELOXA is available when you want us, never required. The relationship is yours to define. Maintenance retainer is optional. Future Phase 2 features can be brought online when Raydar is ready, not when a contract dictates.

Hosting and infrastructure: Hosted on Vercel with edge network distribution. Database on Supabase (PostgreSQL). Both are industry-standard, fully transferable to any provider. No proprietary CMS lock-in. The full codebase ships with documentation and runbooks if Raydar ever wants to take operations entirely in-house or move providers.