What you get in writing

Business outcome

More emergency and water-heater calls from Marietta.

Explicitly out of scope

• Domain, hosting, email, payment processing, premium plugins, third-party APIs, stock assets, and paid advertising costs
• Ongoing content, link acquisition, listing management, reputation management, and recurring SEO
• Additional pages beyond the single optimized landing page, including dedicated service-area pages
• Google Business Profile setup or optimization (an alignment checklist is included)
• Multi-market SEO beyond one primary market
• CRM, booking, SMS, payment and automation integrations (optional add-ons)
• Full copywriting from a blank page (light refinement of client-provided information is included)
• Online booking (P1 / later)
• Financing info for water heaters (P1 / later)

Estimate

Payment model

• 50 / 50
• 50 / 25 / 25
• Other approved: ____

Risk flags

• None

• Content

• Access

• Scope ambiguity

• Integration

• Timeline

• Budget

• 5 pages requested; Local Reach is one landing page → Deliver them as sections on the single page (as briefed). Separate pages need Local Authority or an add-on.

• Client expects form leads to text the owner → Email alerts at launch; offer SMS alerts as an add-on

• Automation wish: “Re-typing form leads into Housecall Pro” → Log as a future opportunity; quote separately if wanted

• Client concern: “Losing the few Google rankings we already have” → Crawl the old site, keep or 301-redirect every indexed URL, re-submit sitemap, monitor Search Console for 30 days. No ranking guarantees.

• A license/credential in the intake is marked as a placeholder → Get the real number in writing before launch; launch checklist item

• Hard date: “Before December (frozen-pipe season)” → Agree input deadlines at kickoff; dates move if dependencies are late (SOW)

• Automation request (“Re-typing form leads into Housecall Pro.”) is outside website packages. Note it as a future opportunity.

Outcome

We are building a mobile-first website for Brightline Plumbing, built around how Marietta customers search so that homeowners in Marietta can find Brightline Plumbing, see why to trust it, and call in one tap.

What should be different 90 days after launch, in your words: “Phone rings more from Google, especially emergency calls, and people stop asking if we're licensed.”

Deliverables

1. One conversion-focused business or product landing page
2. Mobile-first responsive build
3. Core sections: offer, services, proof, about, contact, calls to action
4. Contact form or click-to-call / click-to-email actions
5. Basic on-page SEO and technical indexability setup
6. Light copy refinement using client-provided business information
7. Analytics and search measurement foundation
8. Hyperlocal keyword and service-area mapping for one primary market
9. Localized page copy and high-intent service language
10. Answer engine optimization with useful question-and-answer content
11. LocalBusiness / Service structured data where applicable
12. Google Business Profile alignment checklist
13. Search Console readiness and indexation checks

Included pages / sections

One landing page with these sections: Hero, Proof strip, Services, Why choose us, Reviews, Service area, Quote request form, FAQ, About, Contact + final CTA.

Growth scope

• Basic SEO
• Hyperlocal SEO
• AEO
• GEO (foundation)
• Structured data
• Analytics

Not included

• Domain, hosting, email, payment processing, premium plugins, third-party APIs, stock assets, and paid advertising costs
• Ongoing content, link acquisition, listing management, reputation management, and recurring SEO
• New sections, pages, workflows, or concepts after approval (handled as change requests)
• Guaranteed rankings, traffic, lead volume, or AI-assistant mentions
• Additional pages beyond the single optimized landing page, including dedicated service-area pages
• Google Business Profile setup or optimization (an alignment checklist is included)
• Multi-market SEO beyond one primary market
• CRM, booking, SMS, payment and automation integrations (optional add-ons)
• Full copywriting from a blank page (light refinement of client-provided information is included)
• Online booking (later phase; can be added by change request)
• Financing info for water heaters (later phase; can be added by change request)

Investment

Third-party costs are separate unless listed above: domain, hosting, email, SMS sending fees, your existing subscriptions (Gmail / Outlook, Housecall Pro, QuickBooks) and premium plugins or stock assets.

Timing

The timeline begins when the required deposit and required client inputs are received. If an input, approval or access is late, the delivery date moves with it.

Review rounds

1 consolidated review round is included. Feedback is consolidated by the client decision maker (Marcus Bell) and returned in one set per round, with each item marked as a correction to what was agreed or a new idea. Client feedback target: 2 business days per round. Additional rounds or new requirements use change control.

Client responsibilities

• Provide requested content, approvals, access, legal claims, business information and timely feedback.
• Confirm the factual accuracy of every claim, credential and review we publish; legal / compliance review where applicable.
• Access and inputs we will need: Domain access, Google Business Profile access, Analytics access, Brand assets, Copy approval.
• Content provided and approved by: Marcus (owner) approves all copy and photos.
• Share credentials through a password manager or another secure method, never by email or text.

Change control

Requests outside this scope will be estimated (fee and timeline impact) and approved in writing before additional work begins. Approved changes are added to this scope.

Acceptance

The project is ready for launch when the deliverables meet the Project Brief approved by the client approver and blocking defects are resolved. Launch requires explicit written approval from the client approver. Silence is not approval.

Launch / handoff condition: balance paid before production launch; access and ownership are transferred or finalized after payment, as listed in the handoff pack.

This SOW sits under the Cornerstone Service Agreement / Terms, published as the Service Terms (Service Terms draft 2026-10-08, pending legal review), which govern IP, warranties, liability, confidentiality, termination and payment enforcement. Accepting this SOW in the portal records that version. This SOW does not add or change legal terms. Search and AI visibility work improves discoverability and technical clarity; rankings, traffic, lead volume and AI-assistant mentions are not guaranteed.

Milestones

Known dependencies

• Domain access. Owner: client. Due before build.
• Google Business Profile access. Owner: client. Due before build.
• Analytics access. Owner: client. Due before build.
• Brand assets. Owner: client. Due before build.
• Copy approval. Owner: client. Due before build.

Asset + access checklist

Collect only what the project needs. Never put passwords or secrets in this document. Use the approved password manager.

• Domain / DNS owner confirmed (requested)
• Hosting / platform access
• CMS / website admin
• Logo + brand files (uploaded: brightline-logo.svg)
• Approved photos / video (uploaded: van-and-crew.jpg)
• Business name, address, phone
• Service / product details
• Pricing / offers if public
• Testimonials / reviews approved
• Google Business Profile (requested)
• Search Console
• Analytics / Tag Manager (requested)
• Forms / CRM / booking
• Email sending / notifications
• Privacy / legal pages provided
• Existing copy / content (requested)
• Social links / profiles
• Payment account

Missing dependency + owner + due date: record each open item above with an owner and date at kickoff.

Domain (client): Yes, GoDaddy.

Existing stack (client): Old Wix site; Google Analytics (UA, not GA4).

Definition of done

• Approved Project Brief requirements are met and pass acceptance.
• No launch-blocking (P0/P1) defects; launch checklist complete.
• Client approver has explicitly approved launch and the balance is paid.
• Handoff pack delivered: access, ownership, operating notes, known limitations.

1. Business + objective

Primary objective

• Calls
• Quote requests
• Bookings
• Credibility

5. Analytics + conversion events

Note: The current Universal Analytics property no longer collects data. Set up a new GA4 property and key events.

Baseline (client): ~15 calls/month attributed to the website (owner estimate).

6. Acceptance criteria

Ready for launch when every check below passes and blocking defects are resolved.

• R1 (Click-to-call everywhere on mobile): Given a visitor on a phone, when they tap any Call button, then the dialer opens with [phone redacted] pre-filled.
• R1 (Click-to-call everywhere on mobile): A Call action is visible without scrolling at 360px width and stays reachable (sticky call bar) while scrolling on mobile.
• R1 (Click-to-call everywhere on mobile): Every tap fires the click_to_call analytics event.
• R2 (Quote request form with photo upload): Accepts JPG, PNG, HEIC and PDF up to 10 MB per file (Assumption: limits to confirm); other types or larger files are rejected with a clear message before upload starts.
• R2 (Quote request form with photo upload): Shows upload progress; a failed upload can be retried without losing anything else already entered.
• R2 (Quote request form with photo upload): Photos are optional. The submission saves without them.
• R2 (Quote request form with photo upload): Given a visitor completes the required fields (Name, Phone, Address / ZIP, Problem description, Photos (optional), Is it an emergency?), when they submit, then they see an on-page confirmation and the submission reaches the right person (Office manager during hours, Marcus after 6pm. Respond within 15 minutes).
• R2 (Quote request form with photo upload): Missing or invalid fields show inline errors next to the field; entered data is never cleared.
• R3 (Reviews section): Shows only real, client-approved reviews with first name/initial and source; no invented, merged or edited quotes.
• R3 (Reviews section): Headline proof matches the live source at launch (intake: “140+ Google reviews (4.9★), licensed master plumber, 15 years in business, 1-year workmanship warranty”).
• R3 (Reviews section): Review stars are not marked up as self-serving aggregateRating schema (not eligible for Google review rich results).
• R4 (Service area section): Lists only areas genuinely served: Marietta, Smyrna, Kennesaw and East Cobb.
• R4 (Service area section): No separate thin location pages; area names appear in natural copy, not keyword lists.
• R4 (Service area section): The area list matches the Google Business Profile service areas exactly.
• Every section in the structure above is present with approved content; no placeholder text.
• Mobile (360px) and desktop layouts checked on iOS Safari, Android Chrome and one desktop browser.
• Conversion events (click_to_call, form_submit, quote_request_submit) fire in production.
• Title, meta description, structured data and indexability verified.
• P1 items (Online booking, Financing info for water heaters) are not in launch scope unless approved by change request.

7. Decision log

Honesty rule: No fake service-area pages, no invented proof or reviews, no keyword-stuffed copy, no unsupported claims, and no ranking, traffic or AI-mention guarantees. Local relevance comes from real services, real geography, real evidence and a clear business entity.

4. Query map

Priority services × locations, classified by intent. Targets point at the section or page that must answer the query.

[Trimmed: 6 more rows in the full document.]

Intent mix: Emergency: 3 · Commercial: 6 · Informational: 5. Emergency queries get the call button in the first screen; informational queries are answered in the FAQ.

6. GEO facts: what an AI assistant should understand

Licensed master plumber serving Marietta + East Cobb, 24/7 emergency service, upfront pricing, 140+ 5★ reviews, water heater specialists.

Facts that must be stated exactly as written (verbatim, everywhere):

License number and '24/7' must always be stated exactly. Service area: Marietta, Smyrna, Kennesaw, East Cobb.

Blocker: The license number in the intake is marked as a placeholder. The real number is required in writing before launch.

• Same business name, phone, service list and areas across site, schema, GBP and listings.
• Every claim on the site is verifiable (review count links to the source; license number is checkable).
• Clean business facts in one “About / facts” block near the footer.

8. Google Business Profile alignment checklist

Status: Profile exists. GBP setup and optimization are not included. This checklist aligns the site with the profile.

• Name, phone and address/service-area match the site exactly
• Primary category matches the main service (Plumber)
• Services list matches the site's priority services (4)
• Service areas match: Marietta, Smyrna, Kennesaw and East Cobb
• Website link points to the new home page (with UTM: utm_source=google&utm_medium=organic&utm_campaign=gbp)
• Hours (incl. emergency availability) match the site
• Recent real photos uploaded; review-request link shared with the client

Section map

Tracking

• click_to_call: Tap/click on any tel: link
• form_submit: Successful contact-form submission
• quote_request_submit: Successful quote form submission
• session (organic): Organic landing

Open gaps across the requirement documents

Resolve client-owned gaps before building the affected screen or section, and delivery-owned gaps before the next milestone.

Standard launch checklist

• Approved scope / requirements are complete · requirements gate passed
• Client launch approval recorded
• Required final payment status confirmed · balance pending
• Desktop layout checked (Swapnil, Oct 6, 2026)
• Mobile layout checked
• Primary browser experience checked
• Navigation and links tested
• Forms / calls / email actions tested
• Core MVP flows tested where applicable (n/a)
• Analytics / conversion events checked where included
• Title / meta / indexability checked where included
• Sitemap / robots / canonical basics checked where relevant
• Local business information is accurate where applicable
• Schema / structured data checked where included
• Domain, DNS, SSL, and production URL confirmed
• Backups / rollback path confirmed where applicable
• Admin / ownership access documented
• Known limitations communicated
• Final production smoke test completed

Project-specific checks (Local Reach)

• Backup / snapshot taken immediately before publish
• HTTPS valid on all hostnames (www + apex); HTTP redirects to HTTPS
• Production environment variables / secrets set (none in source control)
• Favicon, social preview image and page titles set
• Privacy policy / terms linked where required
• Old site (Old Wix site; Google Analytics (UA, not GA4)): every indexed URL 301-redirects to its new equivalent; no 404s from Search Console
• Event click_to_call fires in production (tap/click on any tel: link)
• Event form_submit fires in production (successful contact-form submission)
• Event quote_request_submit fires in production (successful quote form submission)
• Event session (organic) fires in production (organic landing)
• Test lead delivered end-to-end: Call goes straight to the office line (owner's cell after hours). Form submissions email the office and text the owner
• Routing rule tested: Emergency checkbox → text owner immediately
• Every Call button dials [phone redacted] on iOS and Android
• LocalBusiness / Service / FAQPage schema validated in the Rich Results Test
• NAP on the site matches the Google Business Profile exactly; GBP website link updated
• Exact facts verified verbatim: License number and '24/7' must always be stated exactly. Service area: Marietta, Smyrna, Kennesaw, East Cobb
• Real license number received in writing and replaces the placeholder
• Sitemap submitted in Search Console; URL inspection run on the home page
• Copy reviewed against “do not say” list: Don't say 'cheapest'. Don't promise arrival times under 60 minutes

Commercial + approval gates

Handoff pack

Ownership confirmed

• Domain ownership confirmed

• Hosting ownership confirmed

• CMS ownership confirmed

• Analytics ownership confirmed

• Search Console ownership confirmed

• Google Business Profile ownership confirmed

• Client owns / can access required accounts

• Basic operating instructions provided

• Known limitations / follow-up items documented

Known limitations / technical debt

• Online booking (P1, not built)
• Financing info for water heaters (P1, not built)

Outcome

Delivery facts for the retrospective

• Review rounds used: 0 of 1 included.
• Feedback items: 0 defects, 0 new preferences.
• Change requests: 0.
• Decisions logged: 2.

Open items

• None
• Listed here: ____

Testimonial / case study permission

• Client may be named publicly
• Logo may be used
• Screenshots may be used
• Results may be used

Metrics to report at 30/90 days: Phone clicks, Form submissions, Quote requests, Google Maps actions, Organic search traffic.

Business outcome

Dispatchers assign jobs in one place and techs see their day on their phone.

Discovery: “No double-booked techs; customers get an arrival window by text.”

Unknowns to resolve before quote

• Final decision-maker (intake)
• Investment range (intake)
• Roles + permissions (intake)
• Discovery: Roles/permissions detail, failure behavior for SMS
• Roles + permissions detail
• Failure behavior for notifications / integrations

Estimate

Payment model

• 50 / 50
• 50 / 25 / 25
• Other approved: ____

Risk flags

• None

• Content

• Access

• Scope ambiguity

• Integration

• Timeline

• Budget

• “QuickBooks invoice sync” requested as a nice-to-have → Keep out of v1; price as a change request after launch

• “Route optimization” requested as a nice-to-have → Keep out of v1; price as a change request after launch

• SMS sender registration (A2P 10DLC) lead time → Register the sender in week 1; launch with in-app status if approval lags

• Platform constraint: “Must work on techs' Android phones; no app-store app in v1” → Test every field flow on a mid-range Android phone in Chrome; responsive web app, no app-store build in v1

• Nice-to-have integration (QuickBooks invoice sync) would exceed the tier's integration limit if pulled into v1. Keep it as a later change request.

• No final decision-maker named. Approvals and payment may stall.

Outcome

We are building a dispatch portal MVP so that Summit Field Services' dispatchers, technicians and ops directors can work from one system. Success means: Dispatchers assign jobs in one place and techs see their day on their phone.

What should be different 90 days after launch, in your words: “Zero double-booked techs and customers receive an arrival window by text without a dispatcher calling.”

Deliverables

1. Requirements translated into a lean build plan before development
2. UI system, core workflows, data model, QA, deployment, and handoff
3. Authentication or user accounts when needed
4. Two to three connected workflows
5. Database and basic admin capability
6. One straightforward third-party integration when scoped
7. Analytics and error monitoring foundation

Included workflows + integrations

• Dispatcher board with drag-to-assign
• Tech mobile job list with status updates
• Automatic customer SMS on 'en route'
• Job notes + photos
• Individual user accounts with role-based home views
• Admin view to see and correct every job
• Open job addresses in maps for directions

Integrations: SMS gateway (provider to select), Device maps app.

Growth scope

• Basic SEO
• Hyperlocal SEO
• AEO
• GEO
• Structured data
• Analytics

Not included

• Domain, hosting, email, payment processing, premium plugins, third-party APIs, stock assets, and paid advertising costs
• Ongoing content, link acquisition, listing management, reputation management, and recurring SEO
• New sections, pages, workflows, or concepts after approval (handled as change requests)
• Guaranteed rankings, traffic, lead volume, or AI-assistant mentions
• More than one third-party integration
• Multiple permission levels beyond basic roles + admin
• Data migration from legacy systems unless listed
• Post-launch feature work (maintenance and iteration are separate)
• No customer self-booking
• No native app-store apps
• No payroll
• QuickBooks invoice sync (later phase; can be added by change request)
• Route optimization (later phase; can be added by change request)

Investment

Third-party costs are separate unless listed above: domain, hosting, email, SMS sending fees and premium plugins or stock assets.

Timing

The timeline begins when the required deposit and required client inputs are received. If an input, approval or access is late, the delivery date moves with it.

Review rounds

2 consolidated review rounds are included. Feedback is consolidated by the client decision maker (Tasha Monroe) and returned in one set per round, with each item marked as a correction to what was agreed or a new idea. Client feedback target: 2 business days per round. Additional rounds or new requirements use change control.

Client responsibilities

• Provide requested content, approvals, access, legal claims, business information and timely feedback.
• Confirm the factual accuracy of every claim, credential and review we publish; legal / compliance review where applicable.
• Share credentials through a password manager or another secure method, never by email or text.

Change control

Requests outside this scope will be estimated (fee and timeline impact) and approved in writing before additional work begins. Approved changes are added to this scope.

Acceptance

The project is ready for launch when the deliverables meet the PRD + DRD approved by the client approver and blocking defects are resolved. Launch requires explicit written approval from the client approver. Silence is not approval.

Launch / handoff condition: balance paid before launch / final handoff; access and ownership are transferred or finalized after payment, as listed in the handoff pack.

This SOW sits under the Cornerstone Service Agreement / Terms, published as the Service Terms (Service Terms draft 2026-10-08, pending legal review), which govern IP, warranties, liability, confidentiality, termination and payment enforcement. Accepting this SOW in the portal records that version. This SOW does not add or change legal terms. Search and AI visibility work improves discoverability and technical clarity; rankings, traffic, lead volume and AI-assistant mentions are not guaranteed.

Milestones

Known risks

• “QuickBooks invoice sync” requested as a nice-to-have → Keep out of v1; price as a change request after launch
• “Route optimization” requested as a nice-to-have → Keep out of v1; price as a change request after launch
• SMS sender registration (A2P 10DLC) lead time → Register the sender in week 1; launch with in-app status if approval lags
• Platform constraint: “Must work on techs' Android phones; no app-store app in v1” → Test every field flow on a mid-range Android phone in Chrome; responsive web app, no app-store build in v1

Definition of done

• Approved PRD + DRD requirements are met and pass acceptance.
• No launch-blocking (P0/P1) defects; launch checklist complete.
• Client approver has explicitly approved launch and the balance is paid.
• Handoff pack delivered: access, ownership, operating notes, known limitations.

Roles + permissions

Assumption: Matrix inferred from user types (no roles/permissions answer yet). “Assigned only” = records assigned to that person. Confirm with the client before build.

3. Requirements + acceptance

P0 = must ship in v1 and passes every listed check. P1 = should, only if it fits the signed scope after all P0s pass.

R1 · P0 · Dispatcher board with drag-to-assign

• Given Dispatcher is signed in, when they assign an unassigned job to Technician (drag-and-drop with a keyboard-accessible alternative), then it appears in that person's lane with its time window and persists on refresh.
• Assigning a job that overlaps the assignee's existing window shows a conflict warning before saving.
• The assignee sees the change on their own view within 60 seconds without a manual refresh.

R2 · P0 · Tech mobile job list with status updates

• Given Technician signs in on a phone, when they open their list, then they see only jobs assigned to them for today, ordered by time window, with address and customer contact.
• Shows a clear empty state when nothing is assigned; readable with 44px tap targets at 360px width.
• Status follows a fixed sequence (en route → on site → done); each change records who made it and when.
• Status changes are visible to Dispatcher within 60 seconds.
• A mistaken status can be corrected; corrections are logged, never silently overwritten.

R3 · P0 · Automatic customer SMS on 'en route'

• Given a job has a valid customer mobile number, when it is marked “en route”, then the customer receives one SMS with the arrival window within 2 minutes.
• Failed sends are logged and flagged to Dispatcher; repeated status toggles never send duplicates.
• Messages identify the business and honor STOP / opt-out replies.

[Trimmed: 6 more subsections in the full document.]

8. Acceptance criteria: the MVP is accepted when

• Flow 1 (Primary flow) runs end-to-end for Customer, Dispatcher, Technician and Ops director on mobile and desktop with no workaround.
• Flow 2 (Sign in and land on the right view) runs end-to-end for any user on mobile and desktop with no workaround.
• Every P0 requirement (R1, R2, R3, R4, R5, R6, R7) passes all of its checks in staging.
• No open P0 (Stop) or P1 (Launch blocker) defects; P2s are fixed or explicitly accepted.
• Each role can only see and do what the roles matrix allows (tested per role).
• The authorized approver (Tasha Monroe) accepts the release in UAT. Silence is not approval.

9. Known edge cases

Missing: What happens when an integration, notification or form fails. Owner: client. Defaults below apply until confirmed.

10. Not in MVP

• No customer self-booking (client)
• No native app-store apps (client)
• No payroll (client)
• QuickBooks invoice sync (P1: next phase unless it fits after the P0s) (nice-to-have)
• Route optimization (P1: next phase unless it fits after the P0s) (nice-to-have)
• More than one third-party integration (tier boundary)
• Multiple permission levels beyond basic roles + admin (tier boundary)
• Data migration from legacy systems unless listed (tier boundary)
• Post-launch feature work (maintenance and iteration are separate) (tier boundary)

2. Screens + states

Design every state below, not only the happy path.

Required states (any screen)

• Empty
• Loading
• Success
• Error
• Permission denied
• Validation

Sign in

• Default
• Loading (skeleton)
• Validation (bad email)
• Error: link expired / invalid
• Session expired
• Account deactivated

Dispatcher board

• Default
• Loading (skeleton)
• Empty (no jobs yet, with the next step)
• Filtered-empty
• Error loading, with retry
• Conflict warning (overlapping window)
• Saving / saved
• Permission denied

Tech mobile job list

• Default
• Loading (skeleton)
• Empty (no jobs yet, with the next step)
• Filtered-empty
• Error loading, with retry
• Status change: submitting → saved / failed
• Permission denied
• Offline / no signal: not sent, with retry

[Trimmed: 5 more subsections in the full document.]

4. Accessibility (WCAG 2.2 AA)

• Text contrast ≥ 4.5:1 (≥ 3:1 for large text and UI boundaries); color is never the only signal (status also uses text/icon)
• Every input has a visible label; helper and error text are linked to the field (aria-describedby)
• Every flow is keyboard-complete, including drag-and-drop (provide a keyboard/menu alternative)
• Visible focus ring on every interactive element; focus never trapped; modals return focus on close
• Form errors are announced (aria-live) and summarized at the top on submit; fields keep their values
• Tap targets ≥ 24px (2.2 AA), 44px preferred on mobile
• Meaningful alt text on content images; decorative images hidden from assistive tech
• Respects reduced-motion and 200% zoom without loss of content

6. Design acceptance criteria

• Every screen above has designed states for the listed cases
• Tokens (type, color, spacing, radius, icons) defined once and applied consistently
• Mobile and desktop layouts reviewed for every primary flow
• Accessibility checklist passes on the design (contrast, focus, labels)
• Design approved by the client approver before build of the affected screens

Screens + required states

Data model (starting point)

Open gaps across the requirement documents

Resolve client-owned gaps before building the affected screen or section, and delivery-owned gaps before the next milestone.

Project-specific checks (Functional MVP)

• Backup / snapshot taken immediately before publish
• HTTPS valid on all hostnames (www + apex); HTTP redirects to HTTPS
• Production environment variables / secrets set (none in source control)
• Favicon, social preview image and page titles set
• Privacy policy / terms linked where required
• Every role tested: sees and does only what the roles matrix allows
• Data validation and error states tested on every form
• SMS gateway (provider to select): success and failure paths tested (customer status texts)
• Device maps app: success and failure paths tested (directions to the job address)
• Error monitoring receiving events from production
• Seed / test data removed; first real admin account created by the client
• Database backup restore tested once

Commercial + approval gates

Standard launch checklist

• Approved scope / requirements are complete
• Client launch approval recorded
• Required final payment status confirmed
• Desktop layout checked
• Mobile layout checked
• Primary browser experience checked
• Navigation and links tested
• Forms / calls / email actions tested
• Core MVP flows tested where applicable
• Analytics / conversion events checked where included
• Title / meta / indexability checked where included (n/a)
• Sitemap / robots / canonical basics checked where relevant (n/a)
• Local business information is accurate where applicable (n/a)
• Schema / structured data checked where included (n/a)
• Domain, DNS, SSL, and production URL confirmed
• Backups / rollback path confirmed where applicable
• Admin / ownership access documented
• Known limitations communicated
• Final production smoke test completed

Handoff pack

Ownership confirmed

• Domain ownership confirmed

• Hosting ownership confirmed

• Repository ownership confirmed

• App / platform admin ownership confirmed

• Analytics ownership confirmed

• Search Console ownership confirmed

• Client owns / can access required accounts

• Basic operating instructions provided

• Known limitations / follow-up items documented

Known limitations / technical debt

• No customer self-booking (out of v1 by design)
• No native app-store apps (out of v1 by design)
• No payroll (out of v1 by design)
• QuickBooks invoice sync (P1, not built)
• Route optimization (P1, not built)

Testimonial / case study permission

• Client may be named publicly
• Logo may be used
• Screenshots may be used
• Results may be used