Status: Archived prototype. No longer under active development. ReachLineAZ was my first substantial AI-assisted project. It was an exploration of an automated inbound-lead follow-up service for local businesses. It was never launched as an operating business, has no customers, and is not a live service. It is preserved here as a portfolio and learning artifact.
Local service businesses (contractors, trades, and other inbound-call-driven businesses) routinely lose potential customers because follow-up to missed calls and inquiries is slow, inconsistent, or forgotten. ReachLineAZ explored whether a lightweight, automated follow-up system could capture those leads and prompt timely responses.
Small, local, inbound-call-based service businesses that don't have time to manage complex software — the kind of owner who misses a call on a job site and never follows up.
| Artifact | State | In this repo |
|---|---|---|
| Marketing website (single page) | Built (static HTML/CSS) | website/index.html |
| Privacy Policy page | Built (static HTML) | website/privacy-policy.html |
| Terms & Conditions page | Built (static HTML) | website/terms-and-conditions.html |
| Lead-tracker spreadsheet (schema/template) | Built — headers only, no real data | lead-tracker/ReachLineAZ_Lead_Tracker.xlsx |
| Client onboarding checklist (the cloning runbook) | Built (documentation) | docs/CLIENT_TEMPLATE_CHECKLIST.md |
| System overview (scrubbed) | Built (documentation) | docs/SYSTEM_OVERVIEW.md |
These are the things that demonstrably exist. The website and legal pages are real static files; the spreadsheet is a real data-model template; the checklist and overview are real documentation.
The backend "automation" was assembled from third-party no-code services (Twilio + Zapier + Google Sheets + Gmail) configured through their consoles — not from source code in this repo. Based on the owner's project notes, a single end-to-end voice + logging + email-alert flow was set up and reported to work in a live test. However:
- There is no code in this repository that proves the Twilio/Zapier/Sheets/Gmail automation, because that wiring lived in external dashboards, not in committed files.
- SMS / text-back automation (the headline feature on the website) depended on A2P 10DLC registration, which the project's own notes record as not confirmed. SMS should be treated as planned, not delivered.
- No multi-client deployment ever happened; the "one isolated install per client" model was a plan, not an operating system with clients.
Honest summary: the front end and documentation are real and included here; the backend automation was a no-code configuration that is not represented by code in this repo, and the SMS capability was never confirmed working.
I chose to stop pursuing ReachLineAZ as a business and to redirect my focus (now toward NewGenAI TV Network and my studies). I'm keeping it as a learning artifact rather than deleting it.
- End-to-end product thinking: identifying a real pain point, scoping an MVP, and designing a service around it.
- Workflow / systems design using no-code tools (Twilio voice, Zapier orchestration, Sheets logging, email alerts).
- Compliance awareness — discovering that SMS automation requires A2P 10DLC registration and live Privacy/Terms pages, and that you shouldn't promise SMS before it's approved.
- Documentation discipline — writing a repeatable onboarding/cloning checklist.
- AI-assisted building — using AI tools to design copy, pages, and process docs.
Product design · workflow architecture · no-code integration design · compliance/legal page preparation · data-model design · technical documentation · AI-assisted development.
Static HTML/CSS (website + legal pages) · spreadsheet data model · and planned/configured no-code services: Twilio (voice + telephony), Zapier (orchestration), Google Sheets (logging), Gmail (alerts). The no-code services are described, not included as code.
Built with significant AI assistance (Claude and other AI tools) for copywriting, page
generation, and documentation. See AI_ASSISTANCE.md.
- Not a live service; no customers; no revenue.
- Backend automation is not represented by code here (it was external no-code config).
- SMS automation was never confirmed working (A2P registration unconfirmed).
- Contact email and live service endpoints have been removed/redacted for publication.
Add screenshots of the rendered website and the lead-tracker schema to screenshots/
(see screenshots/README.md). The website is plain static HTML — open
website/index.html in a browser to view it.
This repository is intentionally archived. It represents an early, discontinued prototype and is published for portfolio and learning purposes only. Please do not interpret anything here as an active product or business.
See PROJECT_STATUS.md for an evidence-labeled breakdown of every
claim, and PRIVACY_REVIEW.md for what was redacted.