Studio CRM

A dance studio CRM built around enrollment, not generic sales

Track dance studio leads from first enquiry to enrolled family: contacts with lifecycle stages, a pipeline of enrollment opportunities, follow-up tasks, message templates and consent-checked automations.

14 days, no credit card. POIZ HQ overview.

The job: stop losing the family who enquired last Tuesday

A trial booking that nobody follows up on is the most expensive thing in a studio's week. A CRM is only worth having if it makes the next follow-up obvious.

The POIZ HQ CRM models the way studios actually enroll: an enquiry becomes a trial, a trial becomes an enrolled dancer, and every step leaves a task or an activity behind.

Contacts with a real lifecycle

Contacts with a real lifecycle

  • Contacts for dancers, parents and guardians in one list
  • Lifecycle stages the CRM actually stores: lead, trial, active, inactive, alumni, archived
  • Contact activity history so you can see what already happened
  • Notes and tags on the contact record

Enrollment pipeline and follow-up tasks

Enrollment pipeline and follow-up tasks

  • Enrollment and lesson opportunities moved through your own pipeline stages
  • Open and close opportunities with an amount attached
  • Follow-up tasks with owners, so a lead is never just a feeling
  • An enrollment board for the families currently mid-decision

Automations that respect consent

Recipes are deliberately narrow and idempotent — a repeated run does not re-send, and every send re-checks consent in the database before it goes out.

Automations that respect consent

  • New lead follow-up
  • Trial reminder and trial no-show follow-up
  • Unsigned waiver and unsigned membership agreement reminders
  • Inactive contact win-back
  • Reusable message templates with a fixed, safe variable list

Consent, guardian routing, quiet hours and the approval policy are re-applied server-side on every send — the browser cannot bypass them.

Questions

Straight answers

Which lifecycle stages does the CRM use?
Lead, trial, active, inactive, alumni and archived. Those are the only values stored, so reporting means the same thing everywhere.
Will automations message a minor directly?
Guardian routing and adult-to-minor controls are applied server-side before anything is queued, so minors are routed to their guardian where the policy requires it.
Is the CRM separate from the rest of the workspace?
No. CRM contacts, classes, attendance, documents and billing are the same workspace and the same records.

Ready to see it with your own roster?