Back On Stage App @BackOnStageApp

Clicked a band operator's profile today expecting a bandleader. The bio led with a different profession. Band was line two. That's the job. You're not the bottleneck because you're disorganised. You're the bottleneck because you're the only one holding the information.

Read a band's contact page today: the booking manager is also the drummer. Fine on a Tuesday. On Saturday your business is at its busiest and its only decision-maker is on a stage for nine hours. That is not bad time management. It is one person holding all the information.

Most top-rated NY wedding bands aren't one band. Six brand names, one office, largely the same players. Smart structure. The hard part isn't the players, it's six calendars pulling from one pool of humans. The ceiling was never demand. It's what one head can hold.

A musician accepting a gig and a musician showing up to it are two different events, and they can be six weeks apart. He said yes in July. Nothing has touched that yes since. The gap between confirmed and remembered is where a Saturday goes wrong. backonstageapp.com

A booking is two jobs, and only one involves the client. Enquiry, quote, contract, invoice: your CRM has that covered. Call order, conflicts, charts per chair, who's driving, the eight-way split: it has nowhere to put any of it. Not a discipline problem. A scope problem.

Nobody decides to start an entertainment company. It happens to you. One band. Then a trio. Then a ceremony quartet. Then a DJ. Admin per booking is fixed. Revenue isn't. Four configurations = four small businesses sharing a phone number.

"I haven't fully explored the features yet, but I'm sticking with what I've got." Setup never finishes because it's nobody's job, has no deadline, and no client is waiting on it. Fix: run your next real booking through it end to end. Borrow a deadline.

A duo generates an enquiry, a quote, a contract, a deposit, an invoice, a payment to chase and someone to pay. A 12-piece generates the same list. Only the payout line changes. Admin per booking is fixed. Revenue isn't. "Too small for a system" is backwards.

A cleared deposit is not a commitment. A signature is. They feel identical right until they don't. Nothing in the usual process makes payment and signature happen together, so they drift apart by default. Close the gap the day the money lands.

"I'll fix the admin in the off-season." Spring: enquiries, already behind. Summer: gigging, no time. Fall: still catching up. Winter: quiet, but you can't feel why it mattered. The season never opens a window. There's no better week coming, only the one that costs least.

"Hey, did I get paid for Saturday?" Fair question. They played. The problem is you're the only person who can answer it, and you don't remember either. Being the sole source of truth on money isn't diligence. It's a bottleneck with your name on it.

"I sent it in the group chat" is not the same as everyone knowing. You can't see who read it. It scrolls away. The sub wasn't in the thread when you sent it. A chat is built for conversation, not for truth. Put the gig details on the gig.

Trio for cocktail hour. Nine-piece for the reception. Same night, same band, two completely different sets of charts. Selling that flexibility is smart. Being the only thing holding the versions apart is not. Put the setlist on the service, not in your head.

Two emails I sent bands this week bounced. The booking address on their own site doesn't exist. Neither knows, because a lost enquiry makes no sound. Send yourself a test enquiry through your own website today. Takes 4 minutes.

"Did you send the invoice?" You did. Three weeks ago. Possibly. Now you're scrolling a sent folder building a case. That's not a memory problem. It's that the proof lived in three different places and none of them talked to each other.

"I already have a system that works." Usually true. It's just made out of you. Which works right up until you want a Saturday off. The question isn't whether your system works. It's whether it works without you.

Client says yes. You send a PDF. It lands in an inbox with 400 unread emails. Three weeks later the date still isn't locked and nobody's at fault, which is why it keeps happening. Generate it from the booking. Let them sign on their phone. Same conversation as the yes.

Run two acts off one talent pool and eventually two gigs land on the same Saturday. You don't catch that by being careful. You catch it by having the conflict show up on the call list before the offer goes out. One calendar, every act.

Most software hands you a login and calls that onboarding. An empty system isn't a system. It's homework. Every BOS trial starts with a real person on a call, putting your actual gigs in.

keyboard_arrow_left Previous keyboard_arrow_right Next

A couple messages you 9pm Tuesday. You see it Thursday between gigs. They've booked someone else. Not because that band was better. Because they replied first. You don't fix that by checking your phone more. You fix it by having something that answers when you can't.