# Monthly pay statements for practitioners on revenue share

Monthly pay statements for practitioners on revenue share is a SaaS idea for owners of physio, chiro, massage and dental clinics paying a revenue split, priced to test at $8 per practitioner a month. At month end, the owner exports billings, works out each practitioner’s share in a spreadsheet and emails it. With it, clinic owners import monthly billings, apply each practitioner’s split and deductions, and send each one a clear pay statement.

_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?

At month end, the owner exports billings, works out each practitioner’s share in a spreadsheet and emails it. Mistakes lead to awkward conversations, and pay goes out late.

**Why now:** Practice software already exports billings by practitioner, so the missing piece is the split and the statement.

## What do they use today?

Most owners keep a home-made spreadsheet with a row per practitioner and formulas built years ago. Each month they check it by eye, then send the numbers in an email or a message.

## How does it work?

At month end the owner uploads the billing export from the practice system and maps its columns. The product applies each practitioner’s split rules, such as a percentage, tiers or deductions, and builds a statement for each person. Statements go out by email as a PDF, practitioners can sign in to see their own, and year-to-date totals sit alongside.

## What goes in the first version?

- Import billings from a spreadsheet export
- Split rules per practitioner: percentages, tiers and deductions
- Monthly statement per practitioner, emailed as a PDF
- Practitioners sign in to see their own statements
- Year-to-date totals for each practitioner

## Who pays, and how much?

- **Who pays:** Owners of physio, chiro, massage and dental clinics paying a revenue split
- **Price to test:** $8 per practitioner a month

Per-practitioner pricing matches the unit that matters here: one statement for each person each month. The owner pays for the people on a revenue split, and a small clinic pays for only a few.

## How to test it in 7 days

1. Ask five clinic owners to walk you through last month’s pay spreadsheet, with figures hidden.
2. Ask clinic accountants how often split mistakes cause rework or disputes.
3. Build one owner’s statements by hand from their export and ask if they’d pay.

## Where to find the first customers

- Accountants and bookkeepers who work with clinics
- Clinic owner groups on Facebook and LinkedIn
- Dental and physio practice consultants

## What are the risks?

- Billing exports may name patients, so strip them on import; privacy rules for health data apply.
- Every practice system exports differently, so each format needs its own import mapping.

## How to build it on shipanysaas

4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.

**Already in the kit:** Teams and roles, Billing, Admin panel, Emails

**You build:**

- Billing import with column mapping
- Split rules with tiers and deductions
- PDF pay statements

[Get the kit](https://shipanysaas-demo.vercel.app/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. Help me build the first version of Monthly pay statements for practitioners on revenue share.

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: Clinic owners import monthly billings, apply each practitioner’s split and deductions, and send each one a clear pay statement.
- Who pays: Owners of physio, chiro, massage and dental clinics paying a revenue split
- Their problem: At month end, the owner exports billings, works out each practitioner’s share in a spreadsheet and emails it. Mistakes lead to awkward conversations, and pay goes out late.
- Price to test: $8 per practitioner a month (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Import billings from a spreadsheet export
2. Split rules per practitioner: percentages, tiers and deductions
3. Monthly statement per practitioner, emailed as a PDF
4. Practitioners sign in to see their own statements
5. Year-to-date totals for each practitioner

## 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
- Admin panel: a super-admin panel that needs two-step sign-in
- Emails: transactional email through Resend or Nodemailer

## New code it needs
- Billing import with column mapping
- Split rules with tiers and deductions
- PDF pay statements

## 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.

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

### Guides for the parts it uses

- [How to add Resend email to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-resend-email)
- [How to add Stripe embedded checkout to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-stripe-embedded-checkout)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://shipanysaas-demo.vercel.app/blog/multi-tenant-saas-teams-roles-invitations)

## More ideas: Health and wellness

- [Supervised hours log for pre-licensed therapists](https://shipanysaas-demo.vercel.app/saas-ideas/therapist-supervision-hours-log): Pre-licensed therapists log client and supervision hours weekly, supervisors approve them online, and practices see who is close to a licence.
- [Lab case tracking for dental practices](https://shipanysaas-demo.vercel.app/saas-ideas/dental-lab-case-tracker): Dental practices log every case sent to the lab and see which ones won’t be back before the patient’s appointment.
- [Cancellation waitlist for physio and chiropractic clinics](https://shipanysaas-demo.vercel.app/saas-ideas/clinic-cancellation-waitlist): When a patient cancels, matching patients on the clinic’s waitlist are offered the slot, and the first to accept takes it.

- [All SaaS ideas](https://shipanysaas-demo.vercel.app/saas-ideas)
- [Try the free generator](https://shipanysaas-demo.vercel.app/saas-ideas#generator)