SweepSign

Inspiration

Residential cleaners often finish a job with the checklist, photos, and final notes scattered across texts or paper. The work may be complete, but the handoff is hard for the customer to follow. SweepSign turns those last few minutes into one clear record.

What it does

SweepSign helps a residential cleaner record what was completed, note an exception, add a small set of proof photos, choose the next action, and share a customer-safe handoff link. The customer can read the result without creating an account. Cleaners can save jobs and reusable scope templates behind real authentication.

How we built it

SweepSign is a web-first Next.js and TypeScript application with Better Auth, protected Route Handlers, and server-side PostgreSQL persistence. A thin Capacitor Android debug shell runs the canonical hosted product for the Next Gen device demonstration. RevenueCat's official web SDK connects each authenticated user to the sweepsign_pro Test Store entitlement. That entitlement removes SweepSign attribution from the signed-in handoff preview.

Challenges

The main product challenge was keeping SweepSign smaller than a cleaning CRM. We cut scheduling, invoicing, customer management, and AI-generated completion claims. The engineering challenge was keeping public handoff links useful without exposing account data, while keeping premium server actions locked until server-side entitlement verification exists.

Accomplishments

• A complete signup, onboarding, create-job, preview, save, reopen, share, and revoke flow.
• Customer-safe public handoff pages with no recipient account required.
• Responsive use at phone, tablet, and desktop sizes.
• A real, no-charge RevenueCat Test Store purchase and restore flow that changes the signed-in product experience.
• A packaged Android debug build for the Next Gen device demonstration.

What we learned

The useful product is not a larger operations suite. It is a focused trust moment: make the end of the job legible to both cleaner and customer. We also learned to keep client-side entitlement state out of server authorization decisions until a server-side RevenueCat verification contract exists.

What's next

Before inviting real customers, SweepSign needs reviewed object storage for proof photos, operational domain email, a production billing decision, and server-side premium authorization. Current verified revenue is $0, and the Shipaton build uses RevenueCat Test Store only.

Built With

• capacitor
• next.js
• playwright
• postgresql
• react
• revenuecat
• supabase
• typescript
• vercel
• vitest