review-care

byDevelopers Void

Here's the full plan — from product spec through a build sequence you can actually follow. 1. Product Description (for your landing page / pitch) Name idea: something simple like "Loopreview," "StarNudge," "ReviewPing" — anything short and literal works fine at this stage. One-liner: Automated Google review requests for local businesses. Text customers after every job, route happy ones to Google, catch unhappy ones before they post. Target customer (v1): pick ONE vertical to start — I'd suggest auto repair shops or hair salons/barbershops because they have clear single-visit triggers, high review sensitivity (people check ratings before booking), and owners are reachable in person. Core value prop: "Set up in 20 minutes. $19/mo. No contract, no sales call, no bloated dashboard you'll never open." 2. Feature Scope (v1 only — resist adding more) Must have: Add customer (name + phone number), manually or via CSV upload One-tap "send review request" (or auto-send on a schedule/trigger) Customer-facing page: tap 1-5 stars → 4-5 redirects to Google review link, 1-3 goes to a private feedback form Owner dashboard: list of sent requests, response status, low-rating alerts (email/SMS to owner) Stripe billing, single $19/mo plan, no tiers yet Explicitly NOT in v1 (cut these no matter how tempting): Multi-platform (Yelp, Facebook) — Google only AI-generated review responses Analytics/reporting dashboards Team accounts / multi-location Native mobile app 3. Tech Stack (optimized for solo speed) Frontend + backend: Next.js (one codebase, easy deploy) Database: Supabase (Postgres + auth, generous free tier) SMS: Twilio (pay-per-message, ~$0.0079/SMS in the US) Payments: Stripe (Checkout + one webhook for subscription status) Hosting: Vercel (free tier covers early usage) Google review link: just the business's public "leave a review" short link — no Google API/OAuth needed in v1 Total infra cost before you have paying customers: close to $0. 4. Data Model (minimal) businesses — id, name, phone, google_review_link, stripe_customer_id, subscription_status customers — id, business_id, name, phone, created_at requests — id, customer_id, sent_at, rating (nullable until answered), feedback_text (nullable), status (sent/rated/converted) That's the whole schema for v1. 5. Week-by-Week Build Plan Validation Build the one-page landing site with pricing and a Stripe payment link or waitlist form Goal: 5+ people willing to hand over a phone number to test with, or pre-pay Core backend + owner flow Supabase schema + auth (simple email/password for owners) Owner dashboard: add customer manually, add customer via CSV Twilio integration: send SMS with a unique link per request Customer-facing flow + billing Public rating page (no login): tap stars → branch to Google link or feedback form Low-rating alert to owner (SMS or email) Stripe Checkout + webhook to activate/deactivate subscription Deploy to Vercel, connect a real domain Polish + onboard first users Smooth out the "add your Google review link" onboarding step (this is the one place people get stuck — make it foolproof with a short video or GIF walkthrough) Onboard your 5 validated businesses for free for the first month Watch usage closely, fix whatever breaks, ask them directly what's confusing Convert to paid + expand outreach Convert free trials to $19/mo Ask happy users for a warm intro to one other business owner they know (this is your distribution engine — local owners talk to each other) Start cold outreach to 20 more businesses in the same vertical