PawSchedule — the spec

A SaaS platform for solo dog-walking business owners to manage recurring client bookings, collect payments automatically, and track revenue — replacing the chaos of spreadsheets and manual invoicing with one purpose-built tool.

---

Decisions locked

---

The core loop

1. Owner creates a client profile with pet details and sets available time slots on the recurring booking calendar.
2. Client receives a booking link via SMS or email, selects a recurring walk schedule, and enters payment details.
3. Owner confirms the booking; client gets an automated confirmation.
4. Reminder notifications fire automatically before each walk.
5. Payment is collected automatically on the billing cycle; an invoice is sent to the client.
6. Owner reviews the revenue dashboard to track completed walks, income, and slot utilisation.

---

v1 scope

Recurring Booking Calendar with Client Slots
Owners define weekly time slots; clients book recurring appointments against those slots. The calendar view shows confirmed, pending, and open slots across the week. Lives on the main Calendar screen.

Automated Payment Collection and Invoicing
Stripe integration charges clients on a recurring schedule tied to their booking. Invoices generate and send automatically after each payment cycle. Lives on the Payments screen.

Revenue Dashboard and Walk Analytics
Summarises total revenue, completed walks, average revenue per client, and slot fill rate for any date range. Gives the owner a single-screen read on business health. Lives on the Dashboard screen.

Client Management with Pet Profiles
Each client record holds contact details plus one or more pet profiles (name, breed, age, vet notes, special instructions). Referenced at every booking. Lives on the Clients screen.

SMS/Email Client Reminders and Confirmations
Automated messages fire at booking confirmation and a configurable window before each walk (e.g. 24 hours, 1 hour). Delivered via a transactional messaging API. Configured on the Settings screen; logs visible on the Client detail view.

---

Deliberately later

• Real-time GPS walk tracking and proof — requires mobile-native scope; v2 after the web core is validated.
• Walk notes and photo uploads per dog — valuable retention feature, but adds storage and media complexity that distracts from the booking-and-payment loop in v1.
• Cancellation and rescheduling automation — edge-case logic (partial refunds, slot reopening rules) that needs real client behaviour data to design correctly; build it once patterns emerge.

---

Data model sketch

• users — id, name, email, password_hash, stripe_account_id, notification_preferences, created_at
• clients — id, user_id (owner), name, email, phone, created_at
• pets — id, client_id, name, breed, age, vet_notes, special_instructions
• time_slots — id, user_id, day_of_week, start_time, end_time, max_bookings
• bookings — id, client_id, pet_id, slot_id, recurrence_rule, status (pending/confirmed/cancelled), start_date
• payments — id, booking_id, stripe_payment_intent_id, amount, status, invoice_url, paid_at
• notifications — id, booking_id, channel (sms/email), type (confirmation/reminder), sent_at, status
• analytics_snapshots — id, user_id, period_start, period_end, total_revenue, walks_completed, slots_filled

---

Screens

• Dashboard — revenue summary, walk count, and slot fill rate for the selected period.
• Calendar — weekly view of all slots with booking status; owner manages availability here.
• Clients — list of all clients with search; entry point to individual client and pet profiles.
• Client Detail — contact info, pet profiles, booking history, and notification log for one client.
• Payments — transaction history, invoice status, and upcoming scheduled charges.
• Booking Flow — client-facing page (shareable link) for selecting a recurring slot and entering payment details.
• Settings — Stripe connection, notification timing, messaging templates, and account preferences.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are fully defined.
• Keep it as the single source of truth while you build, so every feature decision stays anchored to the core loop and the 30-day metric.