The mandatory Belfast scenario
Fourteen guided steps through Amplify’s full value: Autopilot programming, budget transparency, automatic fallback after a decline, Amplify Cover rescuing a Saturday night, musician-initiated cover sharing (both inside Amplify and out), reduced-lineup fee scaling, fee overrides and fair cancellation compensation. Everything below mutates the live demo data — check the venue programme, offers and owner dashboard as you go.
Every notification below also fires a real push notification and email in production — not just the in-app banner shown here.
1. The Long Room sets up its Music Plan
A fictional Belfast hospitality venue needs live music every Friday (acoustic), Saturday (full band) and Sunday (relaxed solo). It creates recurring slots with a £1,000 all-in weekly budget and chooses Approve the Programme.
2. Amplify proposes the programme
The matching engine ranks suitable, available performers within budget and sends timed offers — each with clear match reasons and the exact net fee.
3. Two accept, the band declines
Friday and Sunday performers accept. The proposed Saturday band declines — watch what happens next.
4. Automatic fallback finds the next band
Amplify immediately offers Saturday to the next suitable band — the venue never restarts the process. The replacement band accepts.
5. The venue approves the week in one tap
Bookings are confirmed, shared Gig Packs are created and payments are scheduled — performer fees, Amplify's fee and simulated processing all itemised.
6. The Saturday drummer drops out
Amplify Cover checks the band's trusted substitutes and drummers across the network, and identifies ranked replacements. The booking stays active.
7. A trusted substitute accepts
The line-up updates, the Gig Pack records the change and the payment split moves the drummer's share to the substitute automatically.
8. Fully covered — and the books balance
The venue sees 'Your week is fully covered'. The owner dashboard records managed spend and Amplify's service revenue — never the whole venue payment.
Beyond the launch week
9. The venue nudges Friday's fee up
Fridays have been going well, so The Long Room decides to pay a bit more than the original rate — a fee can always be adjusted after confirmation, in either direction, right up until it's actually paid.
10. A second Saturday setback — no one's free in time
Another band member also drops out, too close to the gig for a substitute. Rather than cancel, the venue simply plays the night as a smaller lineup — the fee scales down automatically to match.
11. Sunday's performer shares the gig outside Amplify
She's got a clash, and rather than wait on Amplify's own network she shares the gig with a friend directly — a real, public link that works whether or not that friend has ever used Amplify.
12. A newcomer accepts
Marcus, a fiddler who's never used Amplify before, opens the link and accepts on the spot. Because he's a brand-new, unverified account, this doesn't confirm instantly — it's proposed, and the venue gets a say first.
13. The venue approves the newcomer
One tap, and Sunday is genuinely confirmed: line-up, Gig Pack and payment split all update exactly as they would for any other substitute.
14. A late cancellation, handled fairly
A follow-up Friday booking has to be pulled with only 3 days' notice — the venue's fault, not the performer's. Amplify pays out 50% compensation automatically; the performer never has to chase it.
This guided tour runs in your own private sandbox, so it’s safe to share with as many people as you like — nobody else’s run-through is affected, and yours doesn’t affect theirs. Want to poke around the rest of the product separately? Sign in as the venue, a musician or the platform admin from thedemo accountspage — a separate, always-available set of seeded data.