# Round book and balances for window cleaners

Round book and balances for window cleaners is a SaaS idea for window cleaning businesses with regular rounds, from solo cleaners to small crews, priced to test at $15 a month per cleaner. The whole round lives in a notebook: who’s due, who wasn’t home, who owes for last time. With it, window cleaners see who’s due today in street order, mark each house done on the phone, and know who still owes.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

The whole round lives in a notebook: who’s due, who wasn’t home, who owes for last time. Chasing payments and selling the round both become a mess.

**Why now:** Many customers now pay by bank transfer instead of leaving cash out, so a notebook can’t keep track.

## What do they use today?

Most rounds run on a paper notebook or a printed street list, with ticks beside each address and sums in the margin. Payments are matched by memory against the bank statement.

## How does it work?

Each morning a window cleaner opens the app on their phone and sees the houses due today in street order. After each house they tap done, skipped or not home, and the app keeps a balance for each customer and emails a reminder when someone owes. When the round is sold or handed over, the cleaner exports its full history.

## What goes in the first version?

- Customer list with address, price and visit frequency
- Today’s due list in street order on the phone
- Mark done, skipped or not home with a tap
- Balances owed and payment reminder emails
- Round history export for selling or handing over

## Who pays, and how much?

- **Who pays:** Window cleaning businesses with regular rounds, from solo cleaners to small crews
- **Price to test:** $15 a month per cleaner

Each cleaner works their own round, so one price per cleaner is fair to a solo operator and grows only when the crew does. It replaces a paper notebook that the cleaner already carries every day.

## How to test it in 7 days

1. Ask ten window cleaners how they track their round and who owes them.
2. Post a mock-up in window cleaning business groups on Facebook and count replies asking for access.
3. Ask one cleaner to try a shared spreadsheet round for a week and list what’s missing.

## Where to find the first customers

- Window cleaning business groups on Facebook
- Window cleaning subreddits
- Suppliers of water-fed poles and cleaning kit

## What are the risks?

- Cleaners work in rain with wet hands, so the app needs big buttons and few steps.
- Round apps for cleaners already exist; win on price and simple payment tracking.

## How to build it on shipanysaas

4 of the parts it needs are already in the kit, the phone app with the All-in plan. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.

**Already in the kit:** Teams and roles, Billing, Emails, Phone app with All-in

**You build:**

- Round list with frequencies and street order
- Done, skipped and not-home tracking
- Balances and payment reminders

[Get the kit](https://www.shipanysaas.com/pricing)

### The starting prompt

```text
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase; with the All-in plan, the Expo phone app is in apps/native. Help me build the first version of Round book and balances for window cleaners.

Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it.

## The product
- What it does: Window cleaners see who’s due today in street order, mark each house done on the phone, and know who still owes.
- Who pays: Window cleaning businesses with regular rounds, from solo cleaners to small crews
- Their problem: The whole round lives in a notebook: who’s due, who wasn’t home, who owes for last time. Chasing payments and selling the round both become a mess.
- Price to test: $15 a month per cleaner (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Customer list with address, price and visit frequency
2. Today’s due list in street order on the phone
3. Mark done, skipped or not home with a tap
4. Balances owed and payment reminder emails
5. Round history export for selling or handing over

## Already in the kit: reuse it, never rebuild it
- Teams and roles: team accounts with members, roles and invitations
- Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments
- Emails: transactional email through Resend or Nodemailer
- Phone app: an iPhone, iPad and Android app on the same backend (All-in plan)

## New code it needs
- Round list with frequencies and street order
- Done, skipped and not-home tracking
- Balances and payment reminders

## How to work
1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK.
2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files.
3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next.

## Rules
- Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel.
- Leave the parts of the kit this product doesn't use as they are.
- If apps/native is not in your copy (the Starter plan), build the web app only.

Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
```

### Guides for the parts it uses

- [Expo Supabase setup: one backend for your web and phone apps](https://www.shipanysaas.com/blog/expo-supabase-one-backend)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://www.shipanysaas.com/blog/multi-tenant-saas-teams-roles-invitations)
- [How to add Resend email to a Next.js + Supabase app](https://www.shipanysaas.com/blog/nextjs-supabase-resend-email)

## More ideas: Local services

- [Photo proof and sign-off for cleaning companies](https://www.shipanysaas.com/saas-ideas/cleaning-photo-proof): Cleaners photograph each job against a checklist, and the client signs off from a link, so a complaint comes with evidence.
- [Maintenance requests for small landlords](https://www.shipanysaas.com/saas-ideas/landlord-maintenance-requests): Tenants report repairs with photos, and the landlord assigns a handyman and follows every job to the end.
- [Digital food safety logs for small restaurants](https://www.shipanysaas.com/saas-ideas/food-safety-logs): Staff record fridge temperatures, cleaning and deliveries on a phone, and the owner has the record ready for an inspection.

- [All SaaS ideas](https://www.shipanysaas.com/saas-ideas)
- [Try the free generator](https://www.shipanysaas.com/saas-ideas#generator)