Most destination marketing organizations don't lose funding in the council meeting. They lose it in the eleven months before, when the people voting had no particular reason to think about the DMO at all.
By the time the budget is on the table, those people have already formed an opinion. It came from a news story, a comment from a hotelier, a line in last year's annual report, or nothing. A strong presentation on the night can't undo a year of silence.
The fix is a steady, low-effort habit of telling the right people what the organization did, in a form they will read or watch.
Good results don't protect a budget on their own
A DMO's funders rarely see its work directly. Council members don't sit in on sales calls. Lodging partners paying an assessment don't see the media placements. Board members see a summary once a quarter, if that.
So at budget time, the people voting are asking "what do I remember about the DMO?" more than "did the DMO perform?" An organization that communicates badly looks, at that moment, a lot like one that performed badly.
There's a second problem. If the only time a funder hears from you is when you need something, every message reads as a pitch. Regular updates that ask for nothing are what make the eventual ask credible.
Know who decides, and what each of them is judged on
Each stakeholder group answers to someone different, so each needs different evidence.
| Stakeholder | What they're judged on | What to show them |
|---|---|---|
| City council or county commission | Tax revenue, resident sentiment, the budget | Lodging tax collections, visitor spending, how visitor taxes ease the burden on residents |
| Hotels and lodging partners | Occupancy, rate, revenue per room | Group business booked, need-period campaigns, leads you passed along |
| Attractions, restaurants and retail | Foot traffic and sales | Events you supported, where they were featured, what's coming |
| Your board | Strategy, governance, risk | Progress against the plan, what changed, what you need from them |
| Residents | Quality of life | What visitors pay for, how impacts are managed, local businesses that benefit |
Use your own numbers. Research partners, your lodging tax reports and your CRM already hold most of what you need. A figure you can source beats a bigger one you can't.
Build a cadence you can keep
A short monthly update that goes out every month does more than a polished quarterly report that goes out late. Consistency is what builds the memory you're counting on at budget time.
A rhythm that works for most DMOs:
- Monthly: a short update to all stakeholders. Two or three minutes of video, or about 300 words.
- Quarterly: a deeper briefing for council and the board, with numbers against plan.
- After major events or campaigns: a quick results note while it's still fresh.
- Two to three months before budget season: a funding-focused recap of the year (more on that below).
If monthly sounds impossible, look at what's making it slow. For most teams, the slow part is the writing. The director already knows what happened this month, and getting it onto the page takes the afternoon.
What goes in a monthly update
Keep the structure the same every month so it's fast to produce and easy to scan.
- One result, with a number. Lodging tax collections, group room nights booked, event attendance, website leads. Pick the one that matters most this month.
- One story. A partner who benefited, a group that chose your destination, an event that filled the hotels.
- What's next. The campaign, event or sales trip coming up.
- One invitation. Attend something, share something, or reply with a question.
A simple outline for a video version:
This is [name] from [DMO] with your [month] update.
The headline this month: [result and number].
Here's what that looked like on the ground: [one story].
Next month we're focused on [what's next].
If you want to [invitation], reply to this email. Thanks for being part of this.
That's a two-minute recording. Most directors can do it without a script once they've done it a few times.
Tell each audience its own version
The same facts land differently depending on who's listening. Say a youth sports tournament brought 40 teams to town last month.
- Council hears about lodging tax generated and the local spending that came with it.
- Hotel partners hear about room nights, and that the organizer is already talking about next year.
- Restaurants and retail hear which weekends were busiest and which areas saw the traffic.
- Residents hear what the event paid for, and how parking and road impacts were handled.
The data behind the event is the same, but four stakeholders care about four different parts of it. Sending everyone the council version wastes the story on three of them.
Make it easy to consume
Funders are busy, and a PDF attachment is easy to ignore. A short video from the director is personal and much harder to skip. It also carries tone and conviction that a written report flattens.
Always include a written version as well. Some people won't press play, and the written summary is what gets forwarded to a colleague or quoted in a staff report.
Keep both short. If an update runs past three minutes of video or a single screen of text, it's probably two updates.
Before budget season: the funding recap
Two to three months before your budget is decided, send a recap built for the people voting. If the monthly updates have done their job, nothing in it will be news to them.
A funding recap should cover:
- The year's headline results against the plan you presented last year. Include the misses and what you learned from them.
- The return measures you already report. Don't invent a new ROI figure for the occasion. Council staff will ask where it came from.
- Partner voices, used with permission. A hotel general manager explaining what the group sales program meant for their property carries weight you can't.
- What a cut would mean, specifically. Name the campaign, trade show or need period that would go unsupported, instead of saying "reduced marketing."
- A clear ask. The amount, what it funds, and the decision you need.
Send it to council members individually as well as through official channels. Offer a short meeting with anyone who wants one.
Measure whether it's working
Track who opens and clicks on your updates, by audience. If a council member hasn't opened anything in six months, you know who needs a phone call before the vote. If lodging partners engage heavily with group sales news and ignore everything else, give them more of that.
Budget outcomes arrive once a year. Open and watch data arrives every month, so it warns you much sooner.
Where Stakeholder Studio fits
We built Stakeholder Studio for this problem. The director records a short video update. Stakeholder Studio writes the email, social posts, a written recap and a PDF briefing from it, then sends each stakeholder group its own version and shows you who opened it.
It's in beta now. If you run a DMO or CVB and want early access, join the waitlist.