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

LandingRating
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 8

System Requirements Document for review-care

1. Introduction

The "review-care" project aims to provide an automated Google review request system for local businesses, specifically targeting auto repair shops or hair salons/barbershops. The product is designed to streamline the process of collecting customer reviews by sending automated SMS requests after each service. It directs satisfied customers to leave a review on Google while capturing feedback from less satisfied customers before they post publicly. The service is offered at a flat rate of $19 per month, with no contracts or complex dashboards.

2. System Overview

The system facilitates automated review requests for local businesses, focusing on simplicity and ease of use. It allows business owners to manage customer interactions and feedback efficiently. The product includes a public-facing rating page for customers and a protected dashboard for business owners to manage requests and view feedback. The system uses Next.js for both frontend and backend, Supabase for database and authentication, Twilio for SMS, Stripe for billing, and is hosted on Vercel.

Page 2 of 8

2a. Product Interpretation and Delivery Boundary

The product is designed for local business owners who need a straightforward way to manage customer reviews. It excludes multi-platform support, AI-generated responses, analytics, team accounts, multi-location support, and native mobile apps. The system uses a public Google review link, avoiding the need for Google API/OAuth. The customer-facing pages are public and do not require login, while business owner interactions are protected by simple email/password authentication.

2b. Source Content Inventory

Not applicable as no content source directive was provided.

2c. Page Content and Component Coverage

Landing

  • Information/State: Product description, pricing, and how it works.
  • Primary Actions: Sign-up link, contact form.
  • Components: Hero section with oversized headline, call-to-action button.

Login

  • Information/State: Email/password fields.
  • Primary Actions: Login button.
  • Components: Simple form for authentication.
Page 3 of 8

Rating

  • Information/State: Star rating selection.
  • Primary Actions: Redirect to Google review or feedback form.
  • Components: Star rating interface.

Dashboard

  • Information/State: List of sent requests, response status.
  • Primary Actions: View details, send new requests.
  • Components: Request list, alert notifications.

Settings

  • Information/State: Business profile, Google review link.
  • Primary Actions: Save changes.
  • Components: Form for profile settings.

Customers

  • Information/State: Customer records.
  • Primary Actions: Add new customer, import CSV.
  • Components: Customer list, import interface.

New Customer

  • Information/State: Name and phone number fields.
  • Primary Actions: Save customer.
  • Components: Form for adding a customer.
Page 4 of 8

Import Customers

  • Information/State: CSV upload interface.
  • Primary Actions: Upload and import.
  • Components: File upload field.

Requests

  • Information/State: Sent requests, response status.
  • Primary Actions: Send requests, view details.
  • Components: Request management interface.

Feedback

  • Information/State: Feedback form for low ratings.
  • Primary Actions: Submit feedback.
  • Components: Text input for feedback.

Billing

  • Information/State: Subscription status.
  • Primary Actions: Manage subscription.
  • Components: Stripe integration for billing.
Page 5 of 8

3. Functional Requirements

  • As a Business Owner, I should be able to add customers manually or via CSV upload to manage review requests. (explicit)
  • As a Business Owner, I should be able to send review requests with one tap or automate them based on a schedule/trigger. (explicit)
  • As a Customer, I should be able to rate the business on a public page, redirecting to Google for high ratings or providing feedback for low ratings. (explicit)
  • As a Business Owner, I should receive alerts for low ratings via email or SMS. (explicit)
  • As a Business Owner, I should manage my subscription and billing through a simple interface. (explicit)
  • As a Business Owner, I should configure my Google review link for accurate routing. (required_inference)
  • As a Business Owner, I should authenticate using email/password to access protected workflows. (required_inference)
  • As a Customer, I should access the rating and feedback flow anonymously. (required_inference)

4. User Personas

  • Business Owner: Configures the business profile, manages customers and review requests, receives low-rating alerts, and handles billing.
  • Customer: Receives review-request SMS messages, rates the business, and provides feedback.

5. Core User Flows

Business Owner Flow

  1. Login: Enter email and password to access the dashboard.
  2. Dashboard: View request activity and alerts.
  3. Add Customer: Manually enter customer details or import via CSV.
  4. Send Request: Initiate review requests manually or set up automation.
  5. Settings: Configure business profile and Google review link.
  6. Billing: Manage subscription through Stripe integration.
Page 6 of 8

Customer Flow

  1. Receive SMS: Click on the unique link provided.
  2. Rating Page: Select a star rating.
  3. High Rating: Redirect to Google review page.
  4. Low Rating: Provide feedback through the form.

6. Visuals Colors and Theme

  • Muse: Haraldur Thorleifsson
  • Palette: Background #FAF9F7, Surface #FFFFFF, Text #333333, Primary #FF6B6B, Accent #FFD93D, Muted #E0E0E0
  • Typography: Headings Sora, Body Karla
  • Shape Language: Rounded cards and buttons
  • Layout: Flexible grid with generous spacing
  • Imagery: Custom character illustrations and bold iconography

7. Signature Design Concept

The landing page will feature an oversized headline in Sora against a coral block, with a friendly call-to-action button in yellow. Rounded cards with soft shadows will be used for customer entries, and color-blocked sections will guide the user’s eye. The hero section will include illustration-led design with lively animations.

Page 7 of 8

8. Interaction Model & Motion Direction

  • Interaction Model: Animated
  • Motion Tempo: Expressive
  • Hero Dimensionality: Layered_2d
  • Landing Hero Motion Brief: The hero section will feature an oversized headline with a friendly call-to-action button. Upon interaction, elements will animate expressively to engage users, with reduced-motion states available for accessibility.

9. Non-Functional Requirements

  • Performance: The system should handle up to 1000 requests per day with minimal latency.
  • Scalability: The architecture should support easy scaling as the user base grows.
  • Security: Ensure data protection and secure authentication for business owners.

10. Tech Stack

  • Frontend/Backend: Next.js
  • Database: Supabase
  • SMS: Twilio
  • Payments: Stripe
  • Hosting: Vercel

11. Assumptions and Constraints

  • The product will initially target auto repair shops or hair salons/barbershops.
  • Only Google reviews are supported in v1.
  • The system will not include advanced analytics or multi-platform support.
Page 8 of 8

12. Glossary

  • Business Owner: The user managing the business profile and review requests.
  • Customer: The recipient of review requests who provides feedback or ratings.
  • Review Request: An SMS sent to a customer asking for a business rating.
  • Google Review Link: A public link directing customers to leave a review on Google.
Landing design preview
Landing: View landing page
Login: Sign in
Dashboard: View request activity
Customers: View customer list
New Customer: Add customer manually
Import Customers: Upload CSV
Requests: Send review requests
Settings: Configure review link
Billing: Manage subscription
Landing design preview
Landing: View landing page
Login: Sign in
Dashboard: View request activity
Customers: View customer list
New Customer: Add customer manually
Import Customers: Upload CSV
Requests: Send review requests
Settings: Configure review link
Billing: Manage subscription