A resident asks for the clubhouse on a Saturday for her son's graduation party. The senior services department wants the multipurpose room every Thursday morning. A company from outside the district asks about the pavilion for a picnic, and whether the pool comes with it.
A regular asks whether the back room is free for her husband's 40th on a Saturday in March. A company wants the whole taproom on a Thursday night in December. A dad calls about two hours in the party room for eight kids after school. Each one is a booking you want.
“I’m showing my prices, and it seems to be scaring people away. ” The plain answer first: fewer inquiries after you post prices is normal. Some people who would have asked now see the number and decide on their own. That part is expected. The upside is your time.
A member's daughter wants the main hall for her wedding reception. The quilting guild has had the meeting room every Tuesday for years. A family from town calls the canteen about a retirement party and asks whether they can bring their own beer. Each request is routine.
A family asks to use the fellowship hall for a 50th anniversary party. A scout troop asks about Tuesday nights. A couple who grew up in the congregation wants the sanctuary for their wedding and the hall for the reception. Each request is reasonable.
You post the question in an industry group. Twenty people answer. Half say publishing prices dried up their leads. Half say it filtered out the tire kickers and made every inquiry easier to close.
A photographer books a tree farm for one Saturday in November. She sets up one backdrop, one link, and a thermos of coffee. " email. In Check Cherry that format is called a Mini .
A parent books your Snow Princess for a one-hour party at $250. That is the whole order. No second character, no extra time, no favor bags, because none of it was on the menu when they booked. The party itself is fine. The invoice is smaller than it needed to be.
Your website already does it. Someone lands on the page, picks a Saturday, ticks a couple of checkboxes, pays, and the money shows up in your account. It cost you a plugin, a payment connection, and one long afternoon.
The contract is signed. The date is on your calendar. Now you need a few dozen answers from the couple: the first dance song, how the maid of honor pronounces her last name, whether explicit lyrics are okay while the grandparents are still on the floor.
You are quoting a client, or shopping around for a booth to hire, and the same question stops you cold: what is normal? Quote high and the room goes quiet. Quote low and you leave money on the table, or wonder if the cheap booth is cheap for a reason. So here are real numbers.
You run a profit and loss report and there it is: the processing fees line. About 3 percent of money you already earned, gone before it reached your bank. Somewhere in your payment settings is a switch that would make clients cover it instead, a few percent added at checkout.
A couple is choosing between three photo booth companies for their wedding. All three quoted about the same price. One has six Google reviews, one has 23, and one has 87 with a reply from the owner under most of them. Nobody calls the first company.
Most DJ contracts get handed down. A template a friend used. A document the operator picked up early in their career, modified a couple of times, and never really revisited. The contract works most of the time. When it fails, it fails in specific, predictable, expensive ways.