# Costume sizes and orders for dance studios

Costume sizes and orders for dance studios is a SaaS idea for owners of dance studios that put on yearly shows or compete, priced to test at $149 a year per studio. Every show season, studios measure every dancer and copy sizes into supplier forms by hand. With it, parents enter dancers’ measurements online, and the studio gets one sized costume order per routine, with fees tracked per family.

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

Every show season, studios measure every dancer and copy sizes into supplier forms by hand. Wrong sizes and unpaid costume fees turn up weeks before the show.

**Why now:** Costume suppliers take orders online with long lead times, so studios need clean size lists months ahead.

## What do they use today?

Most studios ask parents to send sizes by message or write them on a sheet at the door, then copy them into the supplier’s form. Payments are ticked off on a list, and reminders are personal messages.

## How does it work?

The owner sets up each routine and lists the dancers in it. Parents get an emailed link to a measurement form, and the product suggests a size for each dancer from the chosen supplier’s size chart. It then builds one order list per routine and supplier, and tracks which families have paid their costume fee, sending reminder emails to those who haven’t.

## What goes in the first version?

- Routines with the dancers in each one
- Measurement form for parents, sent by email link
- Size charts per supplier to suggest each size
- One order list per routine and supplier
- Fee status per family with reminder emails

## Who pays, and how much?

- **Who pays:** Owners of dance studios that put on yearly shows or compete
- **Price to test:** $149 a year per studio

A yearly price per studio fits the studio’s calendar, where costume ordering comes in seasons around each show. One yearly charge per studio is easy to plan for and does not tick over month by month.

## How to test it in 7 days

1. Ask five studio owners how they collected sizes and costume fees for the last show.
2. Ask in online dance studio owner groups what went wrong with last year’s costume orders.
3. Turn one studio’s costume spreadsheet into a mock-up and ask what it’s missing.

## Where to find the first customers

- Dance studio owner groups on Facebook
- Dance teaching associations
- Costume suppliers who want cleaner orders from studios

## What are the risks?

- Ordering is seasonal, so a monthly price would see studios cancel between shows.
- Suppliers size differently; a wrong chart means a wrong costume and an angry parent.

## 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, Emails, In-app notifications

**You build:**

- Routines, dancers and measurement forms
- Supplier size charts and order lists
- Costume fee tracking per family

[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 Costume sizes and orders for dance studios.

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: Parents enter dancers’ measurements online, and the studio gets one sized costume order per routine, with fees tracked per family.
- Who pays: Owners of dance studios that put on yearly shows or compete
- Their problem: Every show season, studios measure every dancer and copy sizes into supplier forms by hand. Wrong sizes and unpaid costume fees turn up weeks before the show.
- Price to test: $149 a year per studio (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Routines with the dancers in each one
2. Measurement form for parents, sent by email link
3. Size charts per supplier to suggest each size
4. One order list per routine and supplier
5. Fee status per family with reminder emails

## 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
- In-app notifications: a notifications bell in the web app

## New code it needs
- Routines, dancers and measurement forms
- Supplier size charts and order lists
- Costume fee tracking per family

## 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 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)
- [How to add in-app notifications to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-in-app-notifications)

## More ideas: Education

- [Weekly parent updates for tutoring centres](https://shipanysaas-demo.vercel.app/saas-ideas/tutoring-session-parent-updates): Tutors write a short note after each session, and parents get a weekly update on what their child covered.
- [Mock driving test marking on the instructor’s phone](https://shipanysaas-demo.vercel.app/saas-ideas/driving-mock-test-marking): Driving instructors mark mock tests on their phone during the drive, and pupils get a fault summary straight after.
- [Term rebooking and weekly timetables for music teachers](https://shipanysaas-demo.vercel.app/saas-ideas/music-term-timetable-rebooking): Music teachers open next term’s lesson times, returning families pick first, and the timetable fills without chasing anyone by text.

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