Case study · Product deep-dive · inside PaperPlay
Band Builder
A structured way for bandleaders to fill a lineup without living in a group text — or exposing private calendar data.
Availability in. Private calendar data stays out.
01 · Context
Where this came from.
Putting a band together means finding players, checking availability, agreeing pay, absorbing declines, and keeping the event record current — usually in one person's head and phone. Band Builder turns that fragile process into a repeatable workflow while keeping the organizer in control.
02 · What I owned
Mine, personally.
- The workflow model, product boundaries, and integration contract
- The privacy model: availability signals in, raw calendar data never stored
- The manager-facing experience and the backend lifecycle beneath it
03 · What's built
What a skeptic should know.
Reusable roster templates, role-based lineup runs, sequential invitation attempts with expiry, decline, backout, and replacement paths, payout snapshots, and accepted-member sync into the event lifecycle — built as a bounded product domain inside PaperPlay, currently staged behind a rollout flag ahead of public release.
04
How it's built
- Modeled the real exceptions first: no response, late decline, backout, payout change
- Sequential invites with expiry and automatic replacement paths
- A privacy boundary that uses availability without storing calendar events
Automation becomes trustworthy when it is designed around exceptions, not the happy path.
05 · What this transfers to
Why it matters in-house.
- Exception-first process design — the heart of reliable ops automation
- Privacy-boundary thinking: collect the signal, refuse the raw data
What to verify
Ask for a walkthrough of a lineup run — it's a two-minute demo.
Hiring for senior operations? Let's find out fast.
Open to full-time senior operations roles · Huntsville, AL · local or remote · Updated August 2026
Send the job description — the reply comes from me, not a form. · phillip@paperplay.live