# Gwinnett Home Services: launch plan

Prepared for RocStarr Media · October 13, 2026

## Outcome
Build an owned local directory that helps homeowners discover service businesses and supports a separate RocStarr verification and business-development workflow. Launch in Gwinnett County; preserve a national data model for later Metro Atlanta and Georgia expansion.

The supplied plan is the source brief. Its Vercel and Supabase choices are proposals, not requirements: the requested prototype uses GPT Sites. No real lead export was supplied, so this prototype uses 12 explicitly fictional businesses.

## Recommended approach
Start with a private, interactive Sites prototype, then a data-backed private pilot, then a public directory. This lets us review the user journeys before importing real records or opening public submissions.

Alternatives: a directory-only launch reduces operational scope but delays the sales workflow; a full CRM integration from day one adds cost and complexity before the intake and verification process is proven. The phased approach provides the most useful first test.

## Phase 1: prototype (delivered experience)
- Homepage, six category filters, eight city choices, text search, combined filters, and empty states.
- Business profile dialogs with service descriptions, location, and explicit information-verification status.
- Free listing / claim form that validates entries and demonstrates a moderation handoff. It sends and saves no submission data.
- Separate verification demonstration with editable confirmation status, service gaps, and fictional notes saved only to the current browser.
- Launch roadmap and downloadable import template.
- Responsive blue, cream, and navy design with original CSS neighborhood illustration.
- Private hosting and noindex metadata; no fabricated reviews, ratings, real contact details, or claims of vetted contractors.

Acceptance: search and filters work together; clearing filters restores records; profiles open and close; owner form validation works; demo updates persist locally and can be reset; mobile layout remains usable.

## Phase 2: data preparation (planning estimate: 2–4 working days after export access)
1. Confirm the system containing existing leads. The source document's platform guess is unverified; use RocStarr Connect in public-facing language.
2. Export business fields into the accompanying CSV template. Do not copy private personal notes into public listing content.
3. Deduplicate by normalized phone, domain, and business name/address. Keep original source IDs for traceability.
4. Normalize service categories and city names. Validate county by address; city alone does not reliably determine county.
5. Select approximately 200 useful Gwinnett listings across key categories as an initial target, not an existing verified count.
6. Retain other regions in the underlying dataset. Exclude them from the Gwinnett storefront until expansion is approved.
7. Review source terms, freshness, public contact details, correction/removal process, and publication eligibility.

Acceptance: required fields are valid, duplicates reviewed, geography checked, and unverified records labeled honestly. Do not delay launch until every business is verified, but require minimum data quality for publication.

## Phase 3: data-backed private pilot (planning estimate: 1–2 weeks after scope approval)
Use Sites-supported server storage as the initial platform option, or evaluate an external database if existing integration requirements justify it. The original Vercel/Supabase architecture remains an alternative; no migration or external service has been provisioned.

Data entities:
- businesses: id, source_id, name, slug, category, public phone, website, business address, city, county, state, service area, publication state, source URL, imported_at, updated_at.
- verification_events: business_id, timestamp, staff user, method, checked fields, outcome. Derive public confirmation status from valid events; provide a date and scope.
- opportunities (staff-only): business_id, observed service gaps, notes, outreach stage, owner, next action, last contact, opt-out status.
- owner_requests: business_id (optional), request type, submitted business details, moderation status, identity-verification outcome.

Separate public fields from private operations. Add staff sign-in and server-side authorization, moderation, validation, rate limits, change history, backups, and error handling. A hidden tab is not access control. Production submissions require durable storage and a truthful success response. Keep commercial outreach distinct from contact verification and respect recorded opt-outs.

Acceptance: anonymous visitors cannot access staff data or mutations; form submissions survive refresh and reach moderation; approvals and corrections are logged; import reconciliation works; backup restore is demonstrated.

## Phase 4: public launch (planning estimate: 3–5 working days after pilot acceptance)
- Confirm a name and available domain before purchase; Gwinnett Home Services is a working title, not a confirmed domain registration.
- Publish indexable, stable category and business URLs with unique content, canonical metadata, appropriate structured data, and a sitemap. Prototype hash tabs and dialogs are not the production SEO architecture.
- Publish a clear directory disclosure and explain exactly what confirmation does and does not establish. Never imply a license, insurance, screening, or quality check that was not performed.
- Add correction and removal requests plus a real business claim process.
- Turn on analytics for search usage, zero-result searches, profile visits, contact clicks, and owner requests. A contact click is intent, not a confirmed lead or completed job.
- Review mobile, keyboard, search, profile routing, forms, access controls, and data accuracy; remove noindex only for approved public content.
- Submit the sitemap and monitor indexing. Search ranking and customer acquisition are not guaranteed.

## Verification and revenue workflow
Free listing → verify public information → record a specific service gap in the protected workspace → ask permission to discuss it → offer a relevant growth consultation → qualify for RocStarr's services.

Position the 90-Day Customer Acquisition System at $5,000/month with a 90-day minimum, or $12,500 prepaid for the initial 90 days. Managed Growth Accelerator is $25,000/month with a 90-day minimum and at least $5,000/month ad spend. Match the offer to the business's needs, size, and ability to invest; not every small directory business fits the $2M–$20M ideal client profile. The Plan 2 qualified-call guarantee requires its stated terms and should not become a promise of directory results.

After demonstrating directory demand, test optional recurring enhanced listings or clearly labeled sponsorships. Prices are not set. Free information verification must remain independent from purchasing promotion. Do not promise a free website without defining scope, ownership, hosting, and recurring costs.

## Weekly operating measures
- Data quality: published listings, duplicate rate, stale information, correction turnaround.
- Verification: attempts, completed checks, confirmed fields, age of last check.
- Homeowner utility: searches, useful result coverage, profile views, contact intent.
- Business pipeline: eligible prospects, permission-based conversations, booked consultations, qualified opportunities, closed MRR.
- Economics: delivery time, operational cost, customer acquisition cost, retention, and actual gross profit. Do not assume a 5× margin advantage simply because package price is 5× higher.

## Expansion gate
Expand after the team can maintain Gwinnett listings, process corrections, and show useful homeowner activity and a repeatable verification workflow. Add region pages and filters using the existing city/county/state model. Keep out-of-area profiles unpublished until their data quality and publication eligibility have been reviewed.

## Inputs needed for the live pilot
The actual lead-source location and export; permission to publish the selected business fields; chosen domain; verification owner and process; staff access requirements; and a decision on the production data integration. None is required to review the current fictional prototype.

## Prototype limitations
No live CRM integration, email delivery, real contact actions, shared database, authentication within the page, payments, or public indexing. Local demo notes are not secure storage. The private Sites audience protects this prototype as a whole; the operations demo must be replaced by genuine authorization before any public launch.