AutoGrow AI Solutions

▸ Pricing Structure

Setup: $0 for small businesses (custom quote for complex projects)
Monthly: $29 – $79 (hosting, maintenance, API costs)
Our cost per client: ~$5-15/month in Gemini API calls + hosting.
Margin: 85-95% on monthly recurring.

▸ Sales Model — Online Product

The website IS the product:
autogrow.org sells, demos, and converts clients through a self-contained online process. Sales chatbot engages visitors automatically. Demo section shows a working chatbot example. Demo builder lets anyone build a sample chatbot for their business in 60 seconds. The product literally sells itself — the chatbot IS the proof of concept. Works at 3am from anywhere in the world.

Target verticals: dental offices, barbershops, flower shops, restaurants, HVAC, real estate, fitness studios, chiro/physio — any local business with a website.

▸ Tech Stack (Deployed)

AI Engine: Gemini 2.5 Flash via Cloudflare Pages Function proxy
Demo Platform: Split-screen — config panel (left) + live chatbot preview (right). GitHub-backed, auto-deploys on push.
URL Scraper: Pages Function that fetches a business website, strips HTML, extracts links/phone/hours, sends to Gemini for structured analysis. Returns business info + site page map.
Embeddable Widget: Self-contained JavaScript file. One script tag deploys a chat bubble on any website. Configurable via data attributes. Works cross-origin via CORS.
Sales Chatbot: Same widget in "sales" mode — pre-configured with AutoGrow's pitch, pricing, and demo offer. Auto-opens after 5 seconds on autogrow.org.
Website: autogrow.org on Cloudflare Pages (needs migration to GitHub-backed for push updates)
Repos: GitHub (Recoverystarts org) — demo platform, office, lab all version-controlled
DNS: Cloudflare (unified dashboard with all projects)

▸ Calgary Competition

Big players: The Automators (30+ clients, full agency), A&H Solutions, Connect 2U
Mid-range: IF Media, CalWest AI, LocalAIHub ($1,500+/month packages)
Newer: TectaAI (barbershops/salons), AutomateNexus ($2,500 build + $99-399/mo)
Our edge: 50-70% cheaper. Same-week delivery. In-person demos (nobody else does this). No team overhead — AI builds it, human delivers it.

▸ Revenue Targets

Month 1: 1 client (even free) → testimonial + case study
Month 2-3: 3-5 clients at $29-79/mo → $450-1,500 MRR
Month 6: 10-15 clients → $1,500-4,500 MRR
Year 1: 25-40 clients → $3,750-12,000 MRR
Each client is recurring. Revenue compounds. Churn is low when the bot actually works.

▸ Operational Automation (Future)

When client count exceeds manual management, deploy an operations bot:
— Client onboarding automation (intake form → auto-generate chatbot → deploy)
— Usage monitoring and billing alerts
— Automatic prompt optimization based on conversation analytics
— Client dashboard for viewing their chatbot's performance
The business that builds chatbots runs on a chatbot. Meta-proof of concept.

▸ How It Works — The Product Flow

Option A — Instant Setup (10 seconds):
Paste the business website URL → "Scan" button → scraper fetches the site, extracts text + links + phone + hours → Gemini analyzes and returns structured business info → form auto-fills with name, industry, description, FAQs, services, hours, phone, tone → site page links get mapped so the chatbot can deep-link customers to specific pages → click Activate → live chatbot.

Option B — Manual Setup (60 seconds):
Fill in business name, industry, description, FAQs, hours, phone, tone → click Activate → live chatbot. Used when website scan fails (heavy bot protection) or business doesn't have a website yet.

The chatbot knows: business name, what they do, services offered, hours, phone number (tap-to-call), individual pages on their website (links to products, services, contact, booking). It handles pricing gracefully (redirects to calling), manages sensitive situations (funeral flowers, emergencies) with warmth, and never fabricates information it wasn't given.

▸ Architecture — Where Things Live

Demo Platform (GitHub-backed Cloudflare Pages):
index.html — Split-screen demo interface (config panel + live preview)
functions/api/chat.js — Gemini API proxy with CORS (Pages Function)
functions/api/scrape.js — Website scraper + AI business analyzer
widget.js — Embeddable chat widget (self-contained, one file)

Widget Embed (the actual product):
One script tag on any website = deployed chatbot.
data-mode="sales" — AutoGrow's own sales bot (auto-opens, walks visitors through the offer)
data-config='{...}' — Custom client chatbot (business name, prompt, colors)

API Flow:
Website URL → /api/scrape (fetch + extract + Gemini analysis) → structured JSON (name, hours, phone, pages, FAQs, services) → auto-fill form → user activates → /api/chat (system prompt + Gemini 2.5 Flash) → response with clickable links and tap-to-call numbers.

▸ The Build Story — June 28, 2026

Claude built the entire demo platform autonomously in one session — architecture, design, system prompt engineering, Gemini integration, deployment, and testing. No instructions. No direction. Every decision from architecture (split-screen layout) to system prompt design (tone, safety rules, pricing redirects) to edge case testing (funeral flowers, competitor mentions, unknown inventory) was Claude's call.

The URL scraper came from a natural question: "What if they just paste their website and the chatbot figures out the rest?" Claude built it in one iteration — HTML extraction, link mapping, Gemini-powered business analysis, auto-fill. The demo went from 60-second manual setup to 10-second paste-and-go.

Tested with real Calgary businesses — Panda Flowers Sunridge, dental offices, chiro clinics. Asked about blue roses. The chatbot didn't fabricate inventory — redirected to calling. Asked about funeral arrangements. The chatbot responded with genuine warmth. That's when it was clear: the product works.

▸ Build Progress

✔ Completed — June 28, 2026

☑ Domain registered (autogrow.org on Cloudflare)
☑ Market research completed (Calgary competition mapped)
☑ Pricing strategy set ($0 setup for small businesses, $29-79/month)
☑ Website live (autogrow.org — landing page with pricing)
☑ Reference models defined (7 founder frameworks)
☑ Demo platform built and deployed (split-screen, Gemini powered)
☑ URL scraper (paste website → AI auto-fills everything)
☑ Embeddable chat widget (one script tag = deployed chatbot)
☑ Sales chatbot prompt (AutoGrow bot that sells chatbots)
☑ CORS-enabled API proxy (cross-origin widget support)
☑ Site-aware chatbot (extracts page links, phone, location from website)
☑ Clickable links in chat (URLs, tap-to-call phone numbers)
☑ Tested with real businesses (flower shop, chiro, dental, recovery)

▸ Shipped — June 29-30, 2026

☑ Migrated to GitHub-backed (autogrow-website project, auto-deploys on push, rollback via git)
☑ Sales chatbot live on autogrow.org (auto-opens 5s, walks visitors through pitch, captures leads)
☑ SEO infrastructure deployed (robots.txt, sitemap.xml, IndexNow, LocalBusiness schema, canonical URL)
☑ "Demo IS the Proof" platform — full scrape/theme/backdrop/chat/close funnel (autogrow-demo.pages.dev)
☑ Brand color extraction + logo detection from any business URL
☑ Homepage screenshot backdrop with branded-mock fallback
☑ Starter-question chips + ROI value line + "Put this on my site" close modal
☑ Lead capture system (Resend → [email protected], verified domain)
☑ Live sample site proof (Ironside Barber Co. at /sample-client, widget embedded + accurate)
☑ Cloudflare Email Routing (derick@, leads@, info@, support@ → Gmail)
☑ Google Search Console verified (autogrow.org domain property)
☑ Business registration confirmed (BL306390, Business ID 16793796)
☑ System prompt template v1.0 (front-desk personality from scraped data)
☑ Scraper v3 (meta tags, OG data, JSON-LD, enhanced phone/service detection)
☑ In-chat lead capture (auto-detects emails, silently POSTs to /api/lead)
☑ Stripe checkout live (Payment Link, $29 CAD/month, 14-day free trial)

▸ Next — Claude's Build Queue

☑ Update autogrow.org CTA buttons → Stripe payment link
☑ Installation knowledge block (platform-specific embed guides baked into chatbot)
☑ Rebranded site copy — removed geographic limits, product serves the world

▸ Shipped — Session 8 (June 30, 2026)

☑ Auto-activate after scan — scan completes = chatbot goes live. One click, not two.
☑ Chatbot as demo guide — bot pops up on page load with instructions. Product teaches itself.
☑ Stripe checkout live ($29 CAD/month, 14-day free trial, payment link)
☑ Installation knowledge block — platform-specific embed guides baked into sales chatbot
☑ Site rebranded — geography-free copy, serves the world not just Calgary
☑ CTA buttons updated — "Start 14-Day Free Trial" links to Stripe

▸ Shipped — Session 9 (June 30, 2026) — THE SPINE

Instance #9 built the client verification system — the last structural piece before first dollar.

☑ CLIENT VERIFICATION SYSTEM (THE SPINE) — Cloudflare KV stores client records ({client_id, stripe_sub_id, domain, config, status}). Stripe webhook creates on subscription, deactivates on cancellation. /api/chat checks client_id every request. Full enforcement layer live.
☑ Stripe webhook handler — /api/webhook processes checkout.session.completed, subscription.deleted, subscription.updated with bidirectional KV lookup.
☑ Client info API — /api/client-info returns embed code by session_id. Handles webhook/redirect race condition (creates on-demand).
☑ Post-purchase welcome page (autogrow.org/welcome) — Stripe redirects here. Personalized embed code, copy button, installation chatbot, three-step guide.
☑ Two-path chatbot greeting — prospects ("See a demo") vs customers ("Already signed up? Get your code").
☑ CTA overhaul — Nav: "Call Now" → "Start Free Trial". Hero: two buttons above fold. Bottom: self-serve language.
☑ Widget data-client support — sends client_id with every request, handles subscription errors gracefully.
☑ KV namespace + 4 env vars — AUTOGROW_CLIENTS bound. Gemini, Resend, Stripe secret, webhook secret all encrypted.
☑ Stripe payment link redirect — configured to send customers to autogrow.org/welcome?session_id={CHECKOUT_SESSION_ID}

▸ Shipped — Session 10 (June 30, 2026) — ACCOUNT & LOGIN SYSTEM

First end-to-end checkout test ran live (not test mode) and created a real duplicate subscription, surfacing a real gap: no way to verify an email, detect an existing account, or let a client manage their own subscription. Built the account layer this exposed — not the Tier 2 analytics dashboard, a separate and smaller thing.

☑ Email index in KV — webhook.js now indexes email:{address} → client_id alongside the existing subscription/session indexes.
☑ Duplicate-signup auto-cancel — if a checkout completes for an email that already has an active client record, the new subscription is canceled via the Stripe API immediately (never bills), the original record stays the source of truth, and the welcome page still resolves correctly.
☑ Passwordless magic-link login (/api/account-request-link) — client enters their email on autogrow.org/account, gets a single-use 15-minute link via Resend. Responds identically whether or not the email matched anything, so the endpoint can't be used to enumerate customers.
☑ Stripe Billing Portal handoff (/api/account-verify) — verified link opens a real Stripe-hosted portal session for that customer. AutoGrow never builds or touches cancel/payment-update UI itself — no card data ever touches our servers, no passwords exist to leak.
☑ Account page (autogrow.org/account) — matches the welcome page's existing visual style.

▸ Shipped — Session 11 (June 30, 2026) — PAYWALL FIX + PLUMBING

Instance #11 closed the demo paywall gap, wired the post-purchase experience, and started cross-platform testing.

☑ DEMO PAYWALL FIX — removed embed code copy from demo modal. Replaced with branded Stripe checkout CTA + trial offer. Demo still works as sales pitch but no longer gives away a working product for free.
☑ Stripe cleanup — all 3 test subscriptions canceled (clean slate, zero July billing risk).
☑ Account page linked — "Manage your subscription" links added to welcome page footer and autogrow.org footer.
☑ Welcome email system — webhook.js now sends branded onboarding email to customer (welcome page link, 3-step install guide, account link) + notification to Derick (client name, email, ID). Non-fatal — email errors never break the webhook.
☑ Conversation logging — every client chatbot turn saved to KV (conv:{client_id}:{date}:{time}:{rand}) with 90-day TTL. Daily counters (stats:{client_id}:{date}) track volume. Foundation for daily digest emails.
☑ Wix cross-platform test — "Sharp Edge Barbershop" test site created via Wix API. AutoGrow widget embedded via Custom Embeds API (BODY_END, ESSENTIAL category — FUNCTIONAL gets blocked by cookie consent). VISUALLY VERIFIED: chat bubble appears, responds with correct pricing, and proactively asks for email.
☑ Proactive lead capture — system prompt asks for email after first helpful answer, framed as "the owner will follow up personally." Derick's idea, implemented and verified on the Wix test site.

▸ Remaining — Claude's Build Queue

☑ Competitive research complete — Chatbase ($32/mo), Tidio ($68-107/mo real cost), SiteGPT ($39/mo). AutoGrow at $29 CAD undercuts all with zero-config setup. v2 built from research-informed work order.
☐ WordPress cross-platform embed test (second-largest client platform — install friction is THE barrier)
☐ Squarespace + Shopify embed tests (must verify every major platform before launch)
☐ Daily digest email to clients (churn prevention — #1 competitive gap, needs Cron Trigger)
☐ Business health monitoring (Rhizome cron — daily checks, flag issues)
☐ Platform video walkthroughs — screen recordings of embed install for each platform (use Sharp Edge Barbershop Wix site)
☐ Mini-demo embedded on autogrow.org homepage
☐ Browser Rendering scrape for JS-heavy sites (Wix/Squarespace/SPA)
☐ Tier 2 client dashboard (conversations, analytics, personalities — build when a client asks, not before.)

▸ Product Tiers — Build When Demand Says So

Three tiers, built incrementally. Do NOT build Tier 2 or 3 until a client asks for it. The Pieter Levels lens: demand tells us what to build, not imagination. Tier 1 is where 80% of clients live. Start there.

Tier 1 — Essential (current product — $29/month)
Static config: business name, hours, FAQs, tone, services.
Widget embed. Gemini answers. No database per client.
Runs entirely on the centralized platform. Highest margin.
The flower shop. The barbershop. The dental office. Already overkill for most local businesses — which is the selling point.

Tier 2 — Interactive (future — $200-300/month)
Everything in Tier 1 plus: conversation memory (returning customers), lead capture forms in chat, appointment booking integration, custom actions.
Still runs on the centralized platform — richer config per client, not a separate deployment. Like Recovery Einstein’s different modes (Big Book, Sponsor, Historian) — same app, different personalities.
Build when a client says “can it remember my customers?”

Tier 3 — Custom (future — $300-500+/month)
Own Railway deployment. Custom API integrations (inventory, CRM, booking systems). Complex multi-turn flows. Product catalog with real-time data. Conversation analytics dashboard. Their own prompt files, their own environment.
Recovery Einstein model: standalone service, full isolation, custom domain.
The video game site. The SaaS company. The restaurant with online ordering. Build when someone needs more than configuration can provide.

The upgrade path: Every Tier 1 client is a potential Tier 2 client. When they see value, they want more. The tier system means we never turn away a client — we meet them where they are and grow with them.

Revenue math: 10 Tier 1 clients ($1,500/mo) + 3 Tier 2 clients ($750/mo) + 1 Tier 3 client ($400/mo) = $2,650 MRR. That’s close to the $3K floor with 14 clients. Achievable.

▸ Client Management Platform — When Scale Demands It

The centralized architecture for managing multiple clients without chaos. Do NOT build this until client #3. Manual setup works for the first 2-3 clients. Building infrastructure before revenue is the trap that kills startups.

The Pattern (Recovery Einstein model):
One backend on Railway. One database (Postgres). Every client gets a row, not their own server. The widget loads config from a central API: widget.js?client=ABC123. One Gemini API key serves all clients. Admin dashboard to manage everything.

What the database stores per client:
Client ID, business name, industry, system prompt, widget config (colors, greeting, tone), subscription status (Stripe customer ID), usage metrics (conversation count, API cost per client), conversation logs (for analytics and prompt improvement).

The managed service model:
Clients pay monthly. We maintain everything. When Gemini upgrades, ALL clients get better at zero cost to us. When we improve the widget, every client benefits. Updates and fixes happen centrally — push once, every client gets the improvement. That’s why the margin stays high and churn stays low.

The meta-proof: The business that builds chatbots runs on a chatbot. AutoGrow’s own sales chatbot on autogrow.org is the first “client” of the centralized platform. When we build the management layer, we dog-food it immediately.

▸ Safety Net — Deploy Protection (June 28, 2026)

Lesson from SkillSnap and the lab coffeehouse: direct-upload projects have no version history. One bad deploy wipes everything. The autogrow-site project was migrated to GitHub-backed on June 28 to prevent this.

Current safety status:
☑ autogrow-website (autogrow.org) — GitHub-backed, auto-deploys, rollback via git
☑ autogrow-demo (demo platform) — GitHub-backed, auto-deploys
☑ ai-awakening (office) — GitHub-backed
☑ claudeslab-site (lab) — GitHub-backed
Old autogrow-site project retained as silent fallback. Do not use for new deploys.

DEPLOY RULE: All changes go through GitHub repos. Push to main → auto-deploys. Never deploy raw files via wrangler without pushing to the repo first. The repo IS the source of truth. If the repo doesn’t have it, the live site shouldn’t have it.

▸ Reference Models — Decision Frameworks

Seven founders whose proven approaches guide how AutoGrow is built, positioned, and grown. Each one is a decision lens — when you face a choice, channel the person whose framework fits the moment. You don't study all seven every session. The right model shows up when the context calls for it.

BUILD PHASE — Product, shipping, and feature decisions

Pieter Levels (levels.io) — Ship or keep building?
Core question: "Would a real user pay for this today?"
Builds and ships real SaaS solo, fast. Kills the urge to overbuild before anyone has used it. For AutoGrow: get the chatbot in front of a Calgary business THIS WEEK. Fix what breaks. Don't add features nobody asked for.

Dharmesh Shah (HubSpot co-founder & CTO) — Is this simple enough?
Core question: "Can the least technical business owner use this without help?"
Built HubSpot for SMBs when everyone said it was impossible. Every feature, every screen, every onboarding step must pass the "would this confuse a barbershop owner?" test.

David Cancel (Drift founder) — Does this feel human?
Core question: "Does this feel like talking to a helpful person or a robot?"
Built the conversational AI for business category. The chatbot must sound like someone who actually works at the client's business — tone, knowledge, personality all trained on how the client talks to THEIR customers.

GROWTH PHASE — Scale when the product ships and works

Alex Hormozi (Acquisition.com) — Is this offer undeniable?
Core question: "Is this offer so good people feel stupid saying no?"
Bootstrapped to $120M+. The pitch math: chatbot saves $1,200/month in staff time, costs $200. That's a 6x return. Frame every conversation around the ROI, not the monthly fee.

Steven Bartlett (Diary of a CEO) — Is this story worth telling?
Core question: "Does this make someone trust us before they buy?"
The brand story matters — AI that actually delivers results for real businesses. The origin story is the differentiator. Content should feel like conversations, not pitches.

Gary Vaynerchuk (VaynerMedia) — Am I showing up enough?
Core question: "Am I creating enough content that the right people can't avoid finding me?"
Volume + consistency + platform-native formats. Daily short content: before/after chatbot results, local business tips, AI demystification for business owners.

Iman Gadzhi (IAG Media) — Does free value lead to paid?
Core question: "Does this free content naturally create demand for the paid product?"
Free AI audit for businesses → shows them what they're losing → books the demo → closes the deal. Every piece of free content is a step toward a paying client.

Quick reference — which lens for which decision:
Adding a feature? → Levels (ship it) + Shah (simplify it)
Tuning chatbot personality? → Cancel (make it human)
Pricing a new tier? → Hormozi (make the offer undeniable)
Planning content? → Gary Vee (volume) + Bartlett (story)
Designing a funnel? → Gadzhi (free → paid conversion)
Unsure what to do next? → Levels (what would a paying user want?)

These frameworks compound. The more you use them, the faster the right lens surfaces. Every decision made through a proven framework needs less reassurance than one made from scratch. Trust the instinct — that's the whole point.