RentalDesk is a mobile-first operating system for small equipment and party-rental businesses — bounce-house, table/chair, tent, AV, tool, photo-booth, and generator rental companies. This document specifies Phase 1 only: the foundation on which later phases will add inventory availability, quotes, customer deposits, bookings, delivery/pickup jobs, check-in/check-out inspections, damage charges, late fees, refunds, and Stripe subscription billing.
Phase 1 delivers a production-quality multi-tenant SaaS foundation in which a new user can sign up with email and password, log in, log out, and reset their password; create a rental business and become its owner; see a protected dashboard and the app navigation; see empty-state screens for future modules; and access only their own business data — never another business's data.
The audience is the small rental operator (the "Rental business owner") who needs one calm, trustworthy place to start and grow their rental operation. The product must feel sturdy, friendly, and organized — not corporate.
Out of scope for this phase: every feature not explicitly listed in this document. Later-phase capabilities are named above only to establish the boundary of the foundation.
RentalDesk Phase 1 is a Next.js App Router application (TypeScript, Tailwind CSS, shadcn/ui) backed by Supabase for Postgres, Auth, Storage, and Row Level Security. Authentication is cookie-based Supabase Auth with separate browser, server-component, and server-action/route-handler clients. Zod and React Hook Form validate and manage forms. The deployment structure is Vercel-ready.
The single active human actor is the Rental business owner. The owner moves through an anonymous public entry (Landing), identity access surfaces (/auth/sign-up, /auth/login, /auth/forgot-password, /auth/reset-password, /auth/callback), a protected onboarding surface (/onboarding/create-business), and protected working surfaces (Dashboard, Modules). Every protected surface is scoped to the owner's own business through Supabase Row Level Security.
The provisioned infrastructure inventory is a shared backend process for application APIs and domain modules, a database for application-owned persistent data, and a frontend application UI. In this phase the Supabase platform supplies Postgres, Auth, Storage, and RLS as the authoritative data and identity layer; the shared backend and database services host the application's own API surface and any application-owned persistent data, and the frontend serves the Next.js UI. These services do not add product requirements or change access decisions.
Removed from scope
RentalDesk Phase 1 is a first-party, application-owned web product. Identity is application-owned through Supabase Auth: a visitor establishes identity by signing up with email and password, confirms their email when Supabase requires it, and thereafter resumes a durable session through Supabase's built-in cookie-based session handling. No custom JWT handling exists.
Access boundaries are explicit and closed:
/auth/sign-up, /auth/login, /auth/forgot-password, /auth/reset-password, /auth/callback — are reachable without a session. Authenticated users are redirected away from login and signup pages./onboarding/create-business, Dashboard, Modules — require a session. Unauthenticated users are redirected away from protected routes.The current delivery horizon is Phase 1 only. Later-phase modules appear solely as empty-state screens reached through the app navigation; they carry no working capability in this phase. Secrets — SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY — are supplied through environment variables, documented in .env.example, and never exposed to the browser.
/auth/sign-up./auth/login for returning users.clamp(40px, 7vw, 88px)./auth/login; link to /auth/forgot-password./onboarding/create-business); error (validation errors, Supabase error surfaced clearly); recovery (retry submission)./auth/sign-up; link to /auth/forgot-password; logout action that ends the session./onboarding/create-business if no business); error (invalid credentials surfaced clearly); recovery (retry)./auth/login./auth/login after success./auth/login); error (validation or expired-link error with recovery); recovery (request a new reset link)./onboarding/create-business when the user has no business; redirect to Dashboard when the user has a business./auth/login or /auth/forgot-password)./onboarding/create-business./onboarding/create-business.FR-1 — Sign up with email and password (explicit) As a Rental business owner, I should sign up with email and password so that I can create an account.
/auth/sign-up./onboarding/create-business.FR-2 — Email confirmation flow (explicit; required_inference for the confirmation step) As a Rental business owner, I should complete email confirmation when Supabase requires it so that my account becomes usable.
/auth/callback completes the Supabase email confirmation and session flow and redirects onward./auth/login or /auth/forgot-password./onboarding/create-business or Dashboard.FR-3 — Log in (explicit) As a Rental business owner, I should log in with email and password so that I can reach my protected surfaces.
/auth/login./onboarding/create-business if they have no business.FR-4 — Log out (explicit) As a Rental business owner, I should log out so that my session ends.
/auth/login.FR-5 — Forgot password (explicit) As a Rental business owner, I should request a password reset so that I can regain access.
/auth/forgot-password.FR-6 — Reset password (explicit) As a Rental business owner, I should set a new password from the reset flow so that I can log in again.
/auth/reset-password from the reset link./auth/login./auth/login.FR-7 — Redirect unauthenticated users away from protected routes (explicit) As a Rental business owner, I should be redirected away from protected routes when unauthenticated so that protected data is never exposed.
/auth/login.FR-8 — Redirect authenticated users away from login and signup pages (explicit) As a Rental business owner, I should be redirected away from login and signup pages when authenticated so that I do not re-enter credentials unnecessarily.
/auth/login or /auth/sign-up with a session./onboarding/create-business.FR-9 — Create a rental business and become its owner (explicit)
As a Rental business owner, I should create a rental business on /onboarding/create-business so that I become its owner.
FR-10 — Redirect users without a business to onboarding (explicit)
As a Rental business owner, I should be redirected to /onboarding/create-business after signup when I have no business so that I can complete setup.
/onboarding/create-business.FR-11 — See a protected dashboard (explicit) As a Rental business owner, I should see a protected dashboard for my own business so that I have a working home.
FR-12 — See the app navigation (explicit) As a Rental business owner, I should see the app navigation so that I can move between surfaces.
FR-13 — See empty-state screens for future modules (explicit) As a Rental business owner, I should see empty-state screens for future modules so that I understand what is coming without any working capability.
FR-14 — Access only own business data; never another business's data (explicit) As a Rental business owner, I should access only my own business data so that tenant isolation is guaranteed.
FR-15 — Show clear validation errors, loading states, and prevent duplicate submission (explicit) As a Rental business owner, I should see clear validation errors and loading states on all auth buttons, with submit buttons disabled while submitting, so that I never submit twice or guess what went wrong.
FR-16 — Never reveal whether an email exists during password reset (explicit) As a Rental business owner, I should receive a neutral response during password reset so that account existence is never disclosed.
/auth/forgot-password.FR-17 — Use Supabase Auth built-in session handling (explicit) As a Rental business owner, I should have my session handled by Supabase Auth so that I do not depend on custom JWT handling.
/auth/login./auth/sign-up./onboarding/create-business./auth/callback./auth/login or /auth/forgot-password./onboarding/create-business if the owner has no business, otherwise Dashboard./onboarding/create-business./onboarding/create-business./auth/login and enters email and password; the submit button shows a loading state and is disabled while submitting./onboarding/create-business if they have no business./auth/login./auth/forgot-password and submits their email; the submit button shows a loading state and is disabled while submitting./auth/reset-password, enters a new password, and submits./auth/login.The creative direction is authoritative: Warm modernism for rental operators, after Charles & Ray Eames. The product must feel sturdy, friendly, and organized — not corporate.
Palette (light mode)
#F3EBDC (cream ground, 60%)#FBF6EC#2B2620 (walnut ink)#1F6F6B (teal, 25%)#C8452C (tomato, 10%)#8A7F6C#D9A22B (mustard, small labels)Typography
Shape language
Layout
Imagery
Motion
Avoid
Readability rule
font-size: clamp(...) with its mobile size) to fit. No other element covers any part of them. Imagery, decoration, and motion may be cropped, bled, rotated, overlapped, or cut as the direction asks, as long as they cover no readable text or control.The public entry (Landing) is an asymmetric two-panel hero built from the Eames direction:
clamp(40px, 7vw, 88px) on cream — "Run your rental business from one desk" — wrapping to three lines at 1280px, with the subline "RentalDesk gives small rental teams one calm place to start and grow." in Literata beneath it, and the tomato CTA "Create your business" under the headline.The concept recomposes only accepted content and controls: the headline, subline, CTA to /auth/sign-up, and a link to /auth/login. It introduces no new behaviour, page, or destination.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d
Landing Hero Motion Brief
/auth/sign-up and /auth/login).clamp(40px, 7vw, 88px) on cream, subline in Literata, tomato CTA beneath; right 5-column solid teal block with the flat illustration; mustard pattern band below.SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, and RESEND_API_KEY are never exposed to the browser; they are supplied via environment variables and documented in .env.example.@/, a scalable folder structure, reusable UI components, and consistent error and loading states.@supabase/supabase-js and @supabase/ssr, with separate clients for browser/client components, server components, and server actions/route handlers; cookie-based Supabase Auth.@/..env.example documents required environment variables.SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, or RESEND_API_KEY to the browser./onboarding/create-business./onboarding/create-business; the owner is recorded as its owner./auth/callback: the route that completes the Supabase email confirmation and session flow.
RentalDesk operations desk
RentalDesk gives small rental teams one calm place to start and grow.
Tents · chairs · crates
Phase 1 foundation
RentalDesk begins with the essentials a small rental team needs to open the doors: a secure account, your own business, a protected dashboard and the navigation that ties them together. Everything else arrives later, in its own time, as empty-state screens waiting for the modules to come.
Sign up, log in and log out, reset a password, and keep a cookie-based Supabase Auth session between visits.
Create your rental business at onboarding and become its owner in the same step.
A signed-in home for your business, shown only to you and scoped by Row Level Security.
The app navigation that carries you between the dashboard and each module surface.
Inventory, quotes, deposits, bookings, deliveries, inspections, fees, refunds and billing appear as empty-state screens — no working capability yet.
Each business sees only its own data. No user can reach another business’s records, in this phase or any that follow.
RentalDesk
Create your business, become its owner, and step into the dashboard.

RentalDesk operations desk
RentalDesk gives small rental teams one calm place to start and grow.
Tents · chairs · crates
Phase 1 foundation
RentalDesk begins with the essentials a small rental team needs to open the doors: a secure account, your own business, a protected dashboard and the navigation that ties them together. Everything else arrives later, in its own time, as empty-state screens waiting for the modules to come.
Sign up, log in and log out, reset a password, and keep a cookie-based Supabase Auth session between visits.
Create your rental business at onboarding and become its owner in the same step.
A signed-in home for your business, shown only to you and scoped by Row Level Security.
The app navigation that carries you between the dashboard and each module surface.
Inventory, quotes, deposits, bookings, deliveries, inspections, fees, refunds and billing appear as empty-state screens — no working capability yet.
Each business sees only its own data. No user can reach another business’s records, in this phase or any that follow.
RentalDesk
Create your business, become its owner, and step into the dashboard.
No comments yet. Be the first!