Signup checkpoint
The signup page should name the selected sample workspace and explain that sample data will be ready after signup.
Quickstart
Use the music and publishing sample workspaces when you want to see a complete royalty close path without connecting production revenue, payout rails, bank data, KYC, tax forms, or manual onboarding.
Before You Begin
Expected Result
A seeded sample workspace with payees, catalog items, versioned split rules, sample revenue rows, one completed calculation run, and one locked proof run with statement, reconciliation, and auditor-bundle export actions available.
Steps
Each step keeps source revenue, rules, calculation output, and statement evidence in a reviewable sequence.
Open `/try/music-royalty-sample-data` for the Music Label Royalty Close sample, or `/try/publishing-royalty-sample-data` for the Small Publisher Royalty Close sample.
Create a workspace from the signup page. The selected sample intent should already be attached to the signup flow.
After registration, open onboarding and confirm the matching sample preset is already loaded.
Inspect the seeded revenue source and confirm the rows are marked as sample/demo data.
Open Products or catalog mappings and confirm sample tracks, albums, books, or titles are mapped.
Open Payees and Rules to review the sample rights holders, contributors, labels, publishers, or authors and the split logic used for the sample period.
Open the completed sample calculation run and inspect payee allocations and explanations.
Open the locked proof run from onboarding, then review statement, reconciliation, and auditor-bundle export actions for that run.
Use reset or reseed controls only when you want to clear preset-tagged sample data; user-created data should remain separate.
Screen Checkpoints
The signup page should name the selected sample workspace and explain that sample data will be ready after signup.
Onboarding should show the active Music Label Royalty Close or Small Publisher Royalty Close preset with links into seeded revenue, catalog mappings, rules, proof run, statements, reconciliation, and exports.
The proof run should be locked or otherwise review-ready before statement, reconciliation, and auditor-bundle export actions are used as close evidence.
Details
The samples show the royalty close workflow using realistic but non-production records.
The sample workspaces do not execute payouts or replace a music, publishing, tax, or banking system.
Reference Tables
Use this checklist to confirm the sample workspace is ready for evaluation.
| Area | What to check | Expected result |
|---|---|---|
| Entry point | The `/try/...` URL redirects to signup with the matching sample intent. | Signup names the selected royalty or publishing sample. |
| Seeded data | Revenue source, catalog items, payees, rules, and revenue rows exist. | Records are org-scoped and marked as sample/demo data. |
| Completed run | A completed sample calculation run exists for the sample period. | Payee allocations and explanations are visible. |
| Proof run | A locked proof run is available from onboarding. | Statements, reconciliation, and auditor-bundle export actions use that run. |
| Reset/reseed | Preset controls remove only preset-tagged data. | User-created records remain untouched. |
Troubleshooting
Return to `/try/music-royalty-sample-data` or `/try/publishing-royalty-sample-data` so the `sample_intent` query value is restored.
Confirm the matching preset is active in onboarding and that the sample workspace has not been reset.
Create or import a non-sample revenue source, map products, review rules, and run a separate calculation instead of editing sample rows into production records.
Feedback
Send a note if a step is unclear, missing, or out of date.
Start free, use sample data, then replace examples with your own revenue rows when the workflow is clear.