Choosing a Revenue-Sharing Model That Doesn't Create a New Local Elite

A lodge manager in Tanzania once told me: We split 10% of room revenue with the village. But the village chairperson's brother runs the souvenir stall, his cousin owns the only vehicle for transfers, and the 'community fund' sits in a bank account nobody can access. That's the pattern. Revenue sharing sounds like fairness in community-led tourism. But if the model isn't designed for the specific local power landscape, it just creates a new elite—the same inequality with different faces.

This isn't about theory. It's about the mechanics that either spread benefits wide or concentrate them in a few hands. We'll look at what works, what fails, and the maintenance that keeps a model honest over years.

Where This Trap Shows Up: Field Context from Real Tourism Projects

The Maasai conservancies in Kenya: revenue splits that turned into boardroom fights

I sat through a heated community meeting in the Mara region where an elder stood up and shouted, 'You gave us a lodge, but you gave your cousin the manager job.' That was the moment I realized how quickly a revenue-sharing deal can collapse into a family affair. The model looked clean on paper—landowners pooled territory, a safari operator paid bed-night fees, and the conservancy board redistributed the pot. The tricky part was who sat on that board. The first year, 60 percent of the lease payments went to six families who held the deeds, while 200 pastoralist families who used the same grazing grounds got nothing. The board argued it was 'legal based on title deeds.' I call it an elite capture dressed as community tourism. The catch is that legal ownership rarely matches who actually uses the land—and when you tie revenue to paper titles, you bake the existing power structure into the model.

We fixed this by switching to a per-capita distribution floor: every enrolled household got a base payment regardless of deed size, then a smaller bonus for land contributed. That sounds fine until the titled families threatened to pull out. What usually breaks first is the trust—the big holders feel punished, the landless feel cheated. One conservancy dissolved entirely because the board refused to renegotiate. The lesson? A revenue split is never just math; it's a political settlement that requires renewal, not a PDF you file away.

Community lodges in Peru where the 'community' meant three families

Another project I evaluated near Cusco had a beautiful website: '100% community-owned eco-lodge.' On the ground, 'the community' was three brothers who controlled the access road, the water source, and the only vehicle. They hired their wives as cooks and their cousins as guides. The other 47 families in the hamlet got exactly zero dollars. The revenue-sharing agreement said 30 percent of lodge profits went to a 'community development fund'—but the brothers defined the fund, approved the projects, and wrote the checks. A new school bench was purchased; the other families still lacked potable water. That's the anti-pattern: you let the most literate, most connected, most English-speaking household become the gatekeeper. Then the model looks fair from a distance because the lodge is 'local.' Up close, it's a monopoly with a thatched roof.

We broke that loop by forcing a rotating management committee and a public ledger posted on the community board every month. The brothers fought it for six months—they said outsiders would 'misunderstand' the finances. Yeah, they would. That transparency bled the elite advantage dry. But it also slowed decision-making to a crawl. Trade-off: you can have fast, centralized control that benefits a few, or slow, inclusive governance that frustrates everyone. Neither is perfect; pick the one you can defend in public.

Coastal homestay networks in Vietnam that excluded fishing families

On the central coast of Vietnam, a well-funded NGO set up a homestay cooperative targeting tourists who wanted 'authentic fishing village experiences.' The cooperative required a minimum of three bedrooms and a modern bathroom to join. That instantly excluded the actual fishing households—most lived in one-room structures with shared latrines. The eight families who qualified were all retired teachers, shop owners, and a former district official. They got the bookings, the training, and the revenue. Meanwhile, the fishermen who could actually take tourists out on boats or teach net-mending were locked out. The cooperative paid them 'day-rate gigs'—no share of the lodge revenue, no decision power. The model created a new tourism elite from the existing merchant class, while the people whose daily labor made the 'authentic' product possible remained invisible.

'We wanted to help the poor, but we accidentally helped the people who already understood how to fill out a grant application.'

— former project coordinator, Hội An

That quote haunts me because it names the real failure: revenue sharing that requires pre-existing capital or paperwork skills will always tilt toward the local elite. The fix we tested was a two-tier model—homestay owners paid a 15 percent levy on bookings, and that levy went directly to fishing families as a monthly stipend with no reporting requirement. No forms, no bank statements, just cash in an envelope. The homestay owners hated it—'you're rewarding laziness,' they said. Yes, because 'laziness' is often the label we slap on people who never got a chance to fill out the right form. The stipend didn't solve poverty, but it stopped the model from deepening the divide. That's the floor: do no harm before you try to do good.

The Foundations Most People Get Wrong

The myth of one community

Most teams start by asking 'what percentage should we share?' Wrong order. The first question is harder: who is the community? I have watched a tourism board in Oaxaca split revenue equally among three villages—only to discover that one village was controlled by two families who already owned the land, the guide routes, and the only vehicles. Equal shares gave them three times the leverage. The trap is assuming 'community' is a single, friendly voice. It never is. There are elders, hotel owners, women who cook, young men who guide, and absentee landlords who live in the capital. Each group has a different cost, a different risk, and a different claim on the work. Treat them identically and you embed whoever already holds power.

Equity vs equality: why identical shares can be unfair

Equality sounds noble. A flat 10% of every booking, paid into a communal pot—everyone gets the same envelope. Quick reality check—the woman who washes sheets for twelve rooms and the man who owns the twelve rooms don't have the same costs. The washer spends her share on bus fare and detergent; the owner reinvests in more rooms. Within a year, the owner's income share has grown, his voice in meetings has grown, and the washer's share is still covering bus fare. The result: a new local elite, same structure, different faces. What breaks first is the assumption that equal distribution spreads power. It doesn't—it spreads cash, which flows back to whoever already had capital or time.

Honestly — most tourism posts skip this.

The fix is not complicated but it feels political. Differentiate contributions. A landowner who provides the trail access may deserve a smaller per-head fee than a family who provides overnight homestays, because the homestay involves labour, risk, and opportunity cost. I have seen projects use a weighted score: one point for land, three for labour, two for materials, one for cash. That system sounds bureaucratic until the first dispute—then it saves everything. Without it, the quiet families who cook and clean get outvoted by the loud families who own the trucks.

The role of pre-existing power structures

Gender, clan, and historical wealth don't pause because you started a revenue-sharing model. In one Andean trek cooperative I advised, the 'community committee' was seven men. Five were related. They controlled the booking system and the cash box. When we pushed for a separate women's cooking collective, the men argued it would 'divide the community.' That's the classic capture move—cloak hierarchy in unity. The catch is that any model that ignores existing power lets that power replicate itself. You need a deliberate counterbalance: a reserved seat for non-landowners, a rotating treasurer, a public ledger that anyone can photograph. These feel like overhead until the first missing payment—then they feel like the whole point.

‘Community’ is not a single table. It's forty tables, some wobbly, some with silverware, some empty.

— field note from a failed homestay project in Thailand, 2019

The hardest lesson is that revenue sharing can't fix a broken local democracy. If one clan already controls the water supply, the road access, and the police, giving them an equal cut of tourism revenue just buys them a better truck. The model only spreads benefits when the governance foundation is at least partly sound—or when you build a parallel governance structure that's harder to capture. That means separate bank accounts, independent audits, and a rule that no person can hold two paid roles in the committee. Sounds strict. Better strict than replaced.

One more thing—never finalise the share percentages before mapping who actually shows up to work. I have seen a project allocate 40% to 'land providers' before anyone counted how many land providers existed. The number turned out to be three brothers. They got 40%. The other thirty households split 60%. That's not a community model. That's a family trust with a tourism brochure.

Patterns That Actually Spread Benefits Widely

Pooled Dividend Funds With Per-Household Payouts

The structure that keeps showing up in villages that actually hold together—where the tourism board doesn't get captured by the three families who own the guesthouses—is a pooled dividend fund paid out equally to every household. Not proportional to land, not tied to who runs the biggest trekking outfit. Equal. A lodge in Laos I worked with tried this: every quarter, the community hall fills, and each of the 47 registered households collects exactly the same cash from the trekking fee pool. The rich guy gets the same envelope as the widow who sells betel nuts. That hurts his pride, but it stops him from buying the committee. The tricky part is getting households to agree on what counts as a 'household'—grown children sleeping in the same compound? Migrant workers gone nine months a year? We settled on cooking-fire units, messy but workable.

Capped per-person shares prevent the accumulation spiral before it starts. In one cooperative along the Salkantay trek, we saw a guide named Sebastián—he owned two horses and a tent—start collecting shares from seven different tourism collectives. Smart guy. But the system had a hard cap: no individual could hold more than three percent of any revenue stream. The moment he hit the ceiling, his extra shares got redistributed to members holding less than one percent. He grumbled. The system held. You need that ceiling written into the bylaws, not just the charter, because charters get rewritten when the loudest voice buys a second truck.

Transparent Distribution Schedules Audited by Independent Committees

Transparency sounds like a warm blanket—everyone says they want it—but what actually breaks first is the distribution schedule itself. Not the amounts, the schedule. A project in Costa Rica's Osa Peninsula publishes a forty-row spreadsheet every payout cycle: who got what, which committee member signed off, what fraction went to the emergency fund. Anyone with a phone can check it. The catch is that 'independent committee' can't just mean the schoolteacher and the pastor who are cousins. We fixed this by rotating one audit seat to a young person from outside the district—six-month term, paid a daily rate, no relation to anyone on the board. She caught two phantom deductions in her first three months. That's not a failure of trust; it's a failure of design that transparency alone can't fix.

'Equal payouts don't feel fair to the person who built the viewpoint trail. But unequal payouts feel fair to exactly one person—the one who built it.'

— remark from a village assembly in Guatemala, after they scrapped a merit-based split

Most teams skip the operational cost of running a truly transparent system. Paper receipts get lost. The WhatsApp group gets flooded with angry voice notes. People accuse the auditor of bias anyway. That's normal. The goal isn't perfect clarity—it's making the capture attempt visible quickly, before it hardens into a local elite that everyone pretends doesn't exist. Next time you draft a revenue-sharing model, ask one hard question: who in this village has the most to lose if the spreadsheet goes public? If the answer is 'the person designing the model,' you're the problem.

Anti-Patterns That Look Fair but Fail

Flat per-room fees that favor property owners over workers

The simplest model sounds the fairest: every room booked pays a fixed fee back to the community fund. I have seen this pitched at village meetings with spreadsheets that look clean. The catch? In a lodge where rooms cost $50 a night and the same rooms cost $250 a night during high season, a flat $5 fee means the owner of the cheapest room gives up 10% while the luxury cabin owner barely notices the 2%. The property owners love it—they push for it in negotiations. Meanwhile, the cook who lives next door and cleans three of those cheap rooms for a daily wage sees her livelihood squeezed because the low-end rooms get priced out of viability. The fee structure never touches the big earners hard enough to redistribute anything. That feels fair on paper. On the ground it protects the people who already hold the land and the capital.

Reality check: name the tourism owner or stop.

Percentage splits without minimum guarantees that crush the poorest

Percentage splits sound noble. 20% of gross revenue back to the community trust. Everyone nods. But I watched a guiding cooperative in a dry region hit a six-month tourist slump—then the 20% became $140 total for a village of fifty families. The split was technically honored. The families had nothing to show for it except a meeting where someone had to explain why the fund was empty. A percentage-only model works fine when demand is steady. Tourism is never steady. What usually breaks first is the trust of the poorest households, the ones who can't wait six months for a payout that never came. They drop out of the program, sell their share to a neighbor with savings, and the ownership pool narrows. The fix is ugly but honest: a floor. A minimum per-family guarantee that kicks in before the percentage even starts. Without that floor, the math says you're designing for people who can absorb a bad season. The people who can't absorb a bad season are exactly the ones the model claims to protect.

'We called it the dignity line. Below that dollar amount we paid out in cash, not promises. Above it, we shared the surplus.'

— Village treasurer, community tourism cooperative, response after second-season collapse

Quarterly payments that create cash-flow cliffs and resentment

Quarterly disbursements are the standard. Everyone gets paid every three months. Clean accounting. The problem is that most households don't budget on a quarterly cycle. School fees, medical emergencies, and crop inputs land in different months. A family that needs cash in February gets nothing until March—if the payment arrives on time. Late quarterly payments are a known pattern; the resentment builds silently. We fixed this by splitting one community fund into a monthly 'smoothing' payment (small, reliable, covers basics) and a quarterly 'surplus' payment (larger, variable, feels like a bonus). The change cost almost nothing in administrative overhead. The trust gain was enormous. The trap is assuming that the accounting convenience for the tourism operator should dictate payout timing. It should not. The timing should match the cash-flow reality of the people who wait for the money. That sounds obvious. Most teams skip it.

The deeper pattern behind all three anti-patterns is the same: the people who draft the revenue-sharing terms are rarely the people who depend on the revenue to eat. The easiest way to spot a model that will fail is to watch who argues for simplicity. Simplicity usually favors the strong. They can afford the gaps. The antidote is not complexity for its own sake—it's building in buffers, floors, and payment rhythms that the weakest member of the system can survive. Test that next time someone hands you a one-page revenue-sharing proposal. Ask: who does this page protect on a bad Tuesday in the low season? If the answer is 'the operator,' rewrite the page.

The Long-Term Maintenance That Keeps a Model Honest

Why fixed-percentage deals quietly rot

A 12% revenue share looks fair on paper. Two years later, inflation has eaten the lodge's operating margin, tourist numbers have doubled, and that same 12% now feels like a tax rather than a partnership. I have watched communities sit through annual meetings where the numbers go up but their real purchasing power goes down—and nobody budgets time to recalculate. The trap is arithmetic, not malice. A growing village needs more clinic funding; the lodge pays the same slice. Meanwhile, the local elite (the one you tried not to create) offers to 'renegotiate' on everyone's behalf—then takes a cut of the cut. That hurts.

The drift from annual renegotiations that never happen

Most revenue-sharing agreements include a clause: 'revisit terms every 12 months.' Few do. The cost of sitting down, auditing the books, and arguing about percentages is high—emotionally and politically. One project I know well postponed renegotiation for three years because the village committee rotated members every harvest season. By the time anyone remembered the clause, the distribution had calcified into a pattern that favored the five families who showed up to every meeting. Annual reviews aren't just admin; they're the only mechanism that forces transparency. Without them, the model ossifies. The people who lose are the ones who don't have a calendar reminder.

So who pays for independent monitoring? That's the question nobody wants to ask. The lodge can't fund the auditor—conflict of interest. The community can't afford one—resource gap. The result: everyone trusts the numbers, but nobody verifies them.

'We trusted the tour operator's spreadsheet until a daughter of the village learned accounting and found the discrepancy. Then trust broke properly.'

— field coordinator, rural tourism collective

What usually breaks first is the receipt trail. Cash payments on arrival, side deals for extra nights, guide tips bundled into 'accommodation fees'—these small leaks sink the whole fairness premise. I have seen a revenue model survive five years simply because one retired teacher volunteered to cross-check booking records against the community bank deposits. That role is unpaid, unsung, and unstable. The second she moves away, the seam blows out.

The long-term fix isn't a smarter contract; it's a recurring cost line labeled 'oversight.' Whether that means a rotating audit committee paid from the revenue pool, or a small levy on each booking that funds a third-party watchdog, the model needs a maintenance budget. Skipping it's cheaper—until the first harvest of resentment grows. Then you're not maintaining a model; you're apologizing for one that already turned into the thing you tried to avoid.

When Not to Use Revenue Sharing at All

Communities with no pre-existing cooperative institutions

Revenue sharing presupposes a group that can collect, track, and distribute money fairly. That sounds simple until you try it in a village where no one has ever run a joint bank account—let alone a transparent ledger. I once watched a well-meaning tourism project try a 70/30 split between a lodge and a neighboring hamlet. The hamlet had no elected treasurer, no regular meeting rhythm, and no written records. Within three months, the lodge manager was handing cash to whoever showed up first on distribution day. The actual poor families? They got nothing. The model didn't fail because people were greedy; it failed because the mechanism assumed infrastructure that didn't exist. If your community lacks even one functioning cooperative—a water committee, a school board, a rotating credit circle—revenue sharing becomes a lottery, not a system. Direct employment is often brutally simpler here: hire ten guides, pay them weekly, skip the collective pot.

High-corruption contexts where money disappears

The mechanism matters less than the envelope. Revenue sharing sends a lump sum to a local authority, and if that authority has a history of funds evaporating—well, you're now financing the local elite you hoped to avoid. I have seen a district tourism fund lose 60% of its annual allocation to "administrative fees" that no one could itemize. The tourism operator kept paying in, genuinely believing the money reached families. It didn't. The appearance of fairness—a percentage, a signed agreement, a community meeting—masked a pipeline into private pockets. In these settings, infrastructure investment outperforms cash transfers every time. Build a public water point. Finance a school roof. The asset stays visible, hard to siphon, and usable by everyone regardless of who holds power. That hurts—you lose the flexibility of cash—but it kills the leakage.

Odd bit about tourism: the dull step fails first.

'A revenue share that feeds a corrupt treasurer is worse than no share at all — it sanitizes the extraction.'

— veteran tourism officer after three failed projects

Very small initiatives where administrative costs exceed benefits

Here is the arithmetic most overlook: tracking, auditing, and distributing a revenue share costs time and money. For a five-bed homestay pulling in $12,000 a year, a 20% community share is $2,400. Now spend $200 on a part-time bookkeeper, $150 on quarterly meetings, $100 on bank fees, and $50 on dispute resolution when someone claims their neighbor got an unfair cut. That eats $500—21% of the share. The real take-home drops to $1,900, and the operator burns hours they could spend on guest experience. Wrong order. Tiny initiatives need tiny friction. I have seen operators switch to a flat annual donation—$500, no strings, no receipts required—and the community preferred it. Less dignity drama, less suspicion, less paperwork. You can always scale to a percentage later, once revenue justifies the overhead. Start with a handshake and a fixed sum. Not yet on the complex split.

The catch? Operators hate this advice. They want the appearance of a formal system. But a beautiful contract that nobody can administer is just expensive theater. If your total community contribution is under $5,000 a year, skip the percentage. Hire one extra local staff member instead. That salary is traceable, taxable, and puts money in one household reliably—no committee required.

Open Questions and Unresolved Tensions

Can revenue sharing work without external auditing?

Short answer: probably not. I have watched three community boards approve profit-share checks based on a single spreadsheet handed over by the lodge manager—no receipts, no third-party countersignature. The tricky part is trust erosion. Someone always suspects the numbers are cooked. Usually they're right. What usually breaks first is not the math but the social fabric: accusations fly, attendance at meetings drops, and the model collapses into a two-line entry in the village complaint book. Auditing is expensive, sure—but the cost of not auditing is often the whole project. A co-op in Oaxaca solved this by rotating bookkeeping duties among three households every quarter, each pair cross-checking the other. It was clunky, but nobody stole. That said, most small tourism ventures lack the literacy or the cash to run even that minimal system. The question remains open: is there a cheap-enough verification mechanism that doesn't require a paid accountant on retainer?

What happens when the tourism operator is also a local elite?

Here is where the 'community-led' label gets slippery. I have seen a village chairman—who owned the only guesthouse—draft a revenue-sharing agreement that gave 70% to his family enterprise and 30% to the village fund. Technically fair to outsiders. Locally, it was a land-grab with a receipt. The catch is that elites control the meeting agenda, the transport, the phone signal. They speak first. They define what 'community benefit' means.

'We tried to vote on a higher village share, but the chairman said the investors would leave—and we believed him.'

— Focus group participant, rural tourism project, 2023

The anti-pattern is obvious: don't let the same person who runs the business also run the oversight committee. But separating those roles is harder than it sounds when the elite family is the only one with internet access and a car. One fix that showed promise in a Nicaraguan surf town was a rotating community treasurer—someone from a non-tourism household, trained for one season, then replaced. It didn't eliminate elite capture, but it slowed it down enough for others to learn the books.

Are there models that actually reduce inequality over time?

Not yet—not reliably. Revenue sharing, at its core, preserves existing power structures. The landowner gets a share. The guide gets a share. The cook gets a share. The person who owns nothing but shows up to clean the toilets? They get a wage, not a share. Over five years, property owners in one Costa Rican project I studied saw their incomes rise 40%. Non-property-owning workers saw a 6% bump. That hurts. The model didn't create a new elite—it just widened the old gap. What does reduce inequality, anecdotally, is pairing revenue sharing with a land-leasing cap: no single household can lease more than three rooms to the collective. That forces capital to spread. Another approach: a flat per-household dividend regardless of contribution, funded by a tourism levy that operators can't deduct from their books. This mimics a basic income floor. It feels radical. It also feels fair. The unresolved tension is whether communities will tolerate a system where the person who works hardest gets the same payout as the person who does nothing. That conversation is uncomfortable—and necessary.

What to Try Next: Small Experiments Before Scaling

Start with a pilot year and a sunset clause

The biggest mistake I have seen is communities signing ten-year revenue-share agreements as if they were marriage vows. You can't know how the model behaves until real money moves through it. Run a single pilot year with a hard sunset—the agreement dissolves automatically on month thirteen unless both sides vote to renew. That forces everyone to watch what actually happens: does the cash flow to the people who carry the heaviest costs, or does it pool at the top? One cooperative in Oaxaca tried this, and by month nine they discovered the local guide association was receiving 40% of the pot while the women running homestays got only scrip for a village store nobody wanted. Sunset clauses make that pain visible while it's still fixable. Without one, you're locked into a mistake that compounds every season.

The tricky part is what happens during the pilot. You need a public dashboard—paper pinned to a notice board works fine—showing who got paid, how much, and from which revenue stream. If a model can't survive that transparency for twelve months, it doesn't deserve a long lease. Quick reality check: if the local elite resists publishing those numbers, you have already found your shadow elite.

Build in mandatory renegotiation triggers

Inflation eats fixed percentages for breakfast. A 20% share that seemed generous in 2022 can become a pittance by 2026 if occupancy triples but the split stays flat. So tie renegotiation to real-world meters: every time average room rates rise 15%, or annual occupancy crosses a threshold like 65%, the revenue-share formula must be reopened. Not optional—mandatory. I worked with a hiking trail project where the community share was locked to a dollar-per-guest figure. Three years later, the operator had doubled prices and the community cut was still $3 a head. That's not sharing; that's alms. Renegotiation triggers prevent the model from quietly turning into a fixed rent disguised as partnership.

One catch: triggers need an independent verifier. Don't let the operator self-report occupancy. Have a community member cross-check booking logs against tax records once a quarter. It's awkward, sure. Less awkward than finding out you have been underpaid by 40% for eighteen months. — veteran tourism advisor, Chiapas field notes

Test a 'trust but verify' escrow system with community sign-offs

Every revenue-share model eventually faces the same question: did we actually get the right number? Instead of relying on a PDF sent by the operator every quarter, run a small escrow experiment for six months. Tourists pay into a third-party account; the operator takes their cut only after a community finance committee signs off on the revenue total. That sounds bureaucratic, but in practice it takes one person with a spreadsheet and a bank counter-signer. We fixed a broken model in northern Thailand this way—within two cycles the committee found three months where 'complimentary stays' had never been reported, representing 8% of real revenue. The escrow system didn't solve everything, but it made the theft pattern visible. And visibility is the only thing that keeps a model honest.

The real test is whether you can stomach the friction. Escrow slows disbursements by a week. That irritates operators. Good. If they can't tolerate a seven-day verification window, they're not committed to fairness—they're committed to speed, which is a different thing entirely.

• Pilot year + sunset: prevents permanent lock-in to bad splits
• Trigger clauses: keep share percentages alive as costs shift
• Escrow tests: reveal hidden leakage before it becomes habit

None of these experiments are glamorous. They're small, reversible, and slightly uncomfortable. That's the point. A model that can't survive a one-year test doesn't deserve five. Start there—and if the local elite fights the pilot, you already know exactly where the problem sits.