Built now
Static route, responsive UI, modular catalog, local fallback packets, and Cloudflare request API.
Modular towing websites that become owner CRMs.
A reusable frame for urgent roadside conversion, local SEO, customer accounts, owner dashboards, payments, reviews, and later dispatch integrations.
Demo route only. It does not provide live roadside service, payment collection, or booking confirmation.
Service-area modules
Customer front end
Reusable towing service modules.
Each module collects the details dispatchers need without exposing owner/admin tools to retail customers.
Subscription model
Sell the operational wedge first.
These are planning ranges for product strategy validation, not verified market prices.
Progressive intake
Capture the stranded customer fast, then enrich the job.
Account separation
Retail, owner, staff, dispatch, and driver roles stay distinct.
Production Google login must be verified server-side before account or admin data is shown.
Backend boundary
What exists now and what still needs production wiring.
Required next
Google Identity Services, secure sessions, D1 or external database, R2 photo storage, SMS/email, and payment provider setup.
Blocked claims
No automatic booking, no fake dispatch, no exposed admin tools, no client-side secrets, and no payment capture without provider configuration.