What you will take away
- Venue terms should match risk, service responsibility, and what the venue actually wants.
- Rent, revenue share, hybrid minimums, and amenity logic can all work when the terms are clear.
- The best first agreement is often a measured pilot with reporting, review dates, and clean exit terms.
Ready for machine fit help?
Use what you learned here, then bring your venue, budget, and timeline into the quote conversation.
Negotiate the operating relationship, not just the payment
When a venue asks about rent or revenue share, it is tempting to jump straight to a number. Slow down. The money term only makes sense after both sides understand placement, guest experience, service responsibility, reporting, access, and what happens if the pilot needs adjustment.
A cotton candy machine can be a revenue source, an amenity, a guest-experience upgrade, or a little bit of each. The right term structure depends on which story the venue believes.
This article does not give standard percentages or legal advice. It gives you a practical way to structure the conversation so you do not accidentally agree to vague terms that are hard to operate.
Operator mindset
If the venue wants the upside of the machine, they also need to understand the operating plan that protects the guest experience.
Compare the main term structures
Most placement conversations fall into four buckets: fixed rent, revenue share, hybrid minimums, or amenity logic. None is automatically best.
Fixed rent gives the venue predictable payment but puts more demand risk on the operator. Revenue share aligns the venue with performance but requires clean reporting language. Hybrid terms can balance both, but only when the minimum is realistic. Amenity logic can work when the venue mostly wants a better guest experience.
Use this table to choose the conversation path, not to copy a number.
| Structure | How it works | Watch-outs |
|---|---|---|
| Fixed rent | Operator pays a set amount for the placement period | Riskier before demand is proven; define access, utilities, and review dates |
| Revenue share | Venue receives a share of agreed receipts or sales measure | Define gross/net treatment, reporting cadence, refunds, taxes, and payment timing |
| Hybrid minimum | A lower fixed minimum plus a revenue share above a threshold | Can be fair, but the minimum should not make a pilot impossible to learn from |
| Amenity logic | The venue prioritizes guest experience, dwell time, or party value over direct payment | Still define service duties, review dates, and what success means |
Start with a pilot when demand is unknown
A pilot is not a weak ask. It is a professional way to reduce risk for both sides. You are saying: let's test the placement, measure the right things, and decide with evidence.
The pilot should have a clear length, a specific machine location, service owner, reporting cadence, commercial term, review date, and exit path. If any of those are missing, the pilot can drift into confusion.
Plain-language pilot terms to put on one page.
| Term | What to define | Why it matters |
|---|---|---|
| Pilot length | 30, 60, or 90 days, with the review date already on the calendar | Prevents the test from becoming indefinite |
| Placement | Exact location, power, visibility, access hours, and cleaning path | The same machine can perform differently in two spots |
| Service owner | Who refills, cleans, monitors, supports, and responds to issues | Keeps venue staff from inheriting hidden work |
| Commercial term | Rent, revenue share, hybrid minimum, or amenity logic | Makes the money conversation explicit before launch |
| Reporting cadence | Weekly or monthly owner update with agreed fields | Turns the test into a managed experiment |
| Exit and adjustment | How either side can pause, move, adjust, or remove the machine | Protects the relationship if the first version is not right |
Define revenue share before you say yes
Revenue share sounds simple until someone asks what counts as revenue. Is it gross sales before fees? Net of payment processing? Net of refunds? Before or after sales tax? What happens if the payment app has a reporting issue?
These questions are not awkward; they are normal business hygiene. A friendly agreement can still be precise.
Operator checklist
- What sales measure is used for the share
- Whether taxes, refunds, chargebacks, and payment fees are included or excluded
- How often reports are sent
- When the venue is paid
- Who has access to reporting screenshots or exports
- How disputes or reporting gaps are handled
Use scripts that sound like a partner
The goal is not to win a rent argument. The goal is to show that you understand the venue's priorities and that you will operate responsibly.
Use these as starting points, then make them specific to the venue. The best script includes one detail that proves you actually walked the space or studied the customer flow.
Venue-term conversation starters
If your main goal is predictable payment, we can talk through a fixed rent pilot, but I would like to keep the first term short enough that both sides can review real performance.
If you want the machine to feel more aligned with guest demand, a revenue-share pilot may fit better. We would define the reporting method and review date up front so it stays clean.
If the machine is mainly an amenity for families or birthday guests, we can frame success around guest response, placement, and service reliability, not only direct venue payment.
Before we pick terms, I want to confirm the placement, power, service access, and staff expectations. Those details affect the model as much as the payment structure.
Report like an operator after launch
Reporting is not only for money. It builds trust. A short update shows the venue that you are paying attention, keeping the area cared for, and using the pilot to learn.
Do not overwhelm the owner with a spreadsheet they did not ask for. Send a clean note with agreed metrics, service notes, issues, and the next adjustment.
Simple 30/60-day review cadence.
| Timing | What to review | Possible adjustment |
|---|---|---|
| First week | Placement, visibility, staff questions, service access, early guest response | Move the machine angle, signage, or service timing |
| 30 days | Sales pattern, uptime, supplies, cleaning, staff feedback, customer questions | Adjust placement, reporting, menu, operating hours, or owner communication |
| 60 days | Whether terms still match performance and service effort | Continue, renegotiate, extend pilot, relocate, or exit cleanly |
Agree on exit terms before either side needs them
Exit terms are not negative. They are how professional partners protect the relationship if a placement is not right.
A good exit clause explains notice period, removal timing, final reporting, final payment, site cleanup, and who owns any signage or collateral. It also makes relocation easier if the first placement is weak but the venue relationship is still promising.
Operator checklist
- Notice period for either side
- Who can request relocation inside the venue
- Removal timing and access window
- Final report and final payment timing
- Site condition and cleanup responsibility
- What happens to signage, decals, or venue-specific materials
Bring term assumptions into your payback model
Before you agree to terms, run the placement through a simple payback model. Compare rent, revenue share, and hybrid structures using conservative demand assumptions.
If one term structure only works when traffic is excellent from day one, it may be a poor fit for a pilot. If another structure gives both sides a fair learning period, it may produce a healthier relationship.
- Model rent as a fixed monthly cost.
- Model revenue share as a sale-based cost and define whether it is based on gross or net receipts.
- Model hybrid minimums as both a fixed obligation and a sale-based upside.
- Model service costs honestly, because a venue with difficult access can quietly change the economics.
