What event platforms actually cost in Southeast Asia

The published price of an event platform is usually the least interesting number attached to it. What decides your actual spend is the pricing model, because the model determines whether a free 600-person internal town hall costs you nothing or costs you six hundred times something.

This is a guide to the cost structures you will meet as a corporate event organiser in Malaysia and Singapore, what each one suits, and where the money actually goes.

The three models

1. Per ticket sold

The global ticketing platforms are built on this. The platform takes a percentage of each ticket plus a fixed fee, and payment processing sits on top. Free events are usually free to host.

Suits: public, paid events where the ticket revenue funds the platform - concerts, conferences, festivals, paid workshops.

Does not suit: the typical corporate event, which is free to attend and invitation based. You get a platform designed to optimise ticket conversion when what you needed was a door that works, and the moment you do sell a ticket, the fee lands on your client's gross revenue rather than on a budget line.

The trap: a platform that is free for free events sounds ideal until you discover that the free tier is also where the support, the branding controls and the on-site tooling are missing. You are not the customer on a free event; the ticket buyer is.

2. Per seat, per month

The SaaS subscription model. You pay for a number of user seats, billed monthly or annually, regardless of whether you ran an event that month.

Suits: organisations running events continuously - a university, an exhibition company, an association with a year-round calendar. If the platform is in use every week, a subscription is the cheapest form of access.

Does not suit: the agency or corporate marketing team running four to eight events a year in clusters. You pay for twelve months and use four. Worse, seat-based pricing punishes exactly the thing you want at an event, which is more people with access on the day - your client's team, your crew, the venue coordinator.

The trap: annual commitment negotiated during a busy season, renewed automatically during a quiet one.

3. Per event

You license the platform for one event, at a capacity that covers it.

Suits: corporate and agency organisers with a lumpy calendar. One event, one line item, one invoice, one number for the client to approve. It maps cleanly onto how corporate events are actually budgeted, which is per project rather than per year.

Does not suit: very high event frequency. Past a certain number of events a year the maths flips and an annual licence is cheaper - most vendors including us will offer one if you ask.

The trap: capacity tiers. Check what happens when you exceed the guest cap mid-event, because "up to 500" is either a hard limit or a surprise invoice, and you want to know which before you find out.

AnnexHub uses this model. Free for one live event up to 50 guests, from RM890 per event up to 500 guests, from RM2,500 per event up to 1,000 guests with our team building it with you, and quoted per event above that.

Why headcount is the wrong cost driver

The intuition is that a 1,000-person event costs a platform more to serve than a 200-person event. In practice the difference in infrastructure cost is negligible.

What actually costs money is setup labour. A 200-guest event with an approval workflow, three ticket types, session capacity limits, a custom-branded kiosk and a client who wants the confirmation email redesigned twice is far more work than a 900-guest open registration with one ticket type.

This is why our own tiers are segmented by who builds the event rather than by headcount, with the guest cap following as a consequence. It is worth checking how any vendor segments their tiers, because it tells you what they think they are selling you.

The costs that are not on the pricing page

This is where budgets actually break.

• Payment processing. Separate from the platform fee, always. If you are selling tickets, add it.
• SMS and WhatsApp. Per message, and it adds up fast at 500 guests times three reminders. Email is free; the channels people actually read are not.
• Badge printing. Printer rental, ribbons, blank stock, and someone to operate it. Frequently larger than the software line.
• On-site crew. If you need four check-in lanes, that is four people for a morning, plus a lead. Whether this comes from the platform vendor, your agency or the client changes the number materially.
• Custom domain and SSL if the client insists registration lives on their domain.
• Data residency or security review. Rare but expensive when a bank or a GLC asks for it. Budget the time, not just the money.
• The second event. Per-event pricing is honest about this. Subscription pricing hides it, and per-ticket pricing makes it invisible until it is large.
• Cleaning the client's guest list. It arrives as a spreadsheet with duplicate rows, missing email addresses, three spellings of the same company and a merged cell somewhere. Someone spends half a day on it and that half day is rarely in anyone's budget.
• Late changes. A session added four days out, a ticket type that suddenly needs an approval step, a venue change. The platform absorbs it in minutes; the person reconfiguring and re-communicating it does not.
• Badge reprints. Names and job titles change after badges are printed. Budget a reprint margin and an on-site printer, or budget the awkwardness instead.
• Chasing registrations. The gap between the client's invite list and who has actually registered gets closed by a person sending emails. On a 500-person event that is real hours, and it is the single highest-value hour of the whole build.
• A backup connection. A 4G router at the door costs very little and removes the worst failure mode of the day. Cheap insurance, almost never in the first draft of a budget.
• Translation. If registration copy and confirmation emails need to work in English and Chinese, that is a real task with a real turnaround, not a toggle.

A worked comparison

Take a realistic Malaysian corporate scenario: four events a year, free to attend, averaging 350 guests, run by a marketing team of three who build the events themselves.

• Per ticket sold: nominally free, because no tickets are sold. In practice you are on a free tier with the platform's branding on your client's event, limited support on event day, and no white-labelling. The cost is paid in credibility rather than cash.
• Per seat, per month: three seats, twelve months, whether or not there is an event that month. Add seats temporarily for event-day crew and it grows. You are buying continuous access to something used on four days.
• Per event: four licences at the tier that covers 350 guests. Nothing between events. In AnnexHub's case that is four Self-serve licences at RM890, white-labelled, with a clean per-project line item for each.

None of these is universally right. The point is that the models produce genuinely different totals for the same event calendar, and the difference is much larger than any difference in headline price.

Questions worth asking any vendor

1. What is the total for my calendar - this many events, this size, this year?
2. What happens when an event exceeds its guest cap on the day?
3. Is white-labelling included, or is it the thing that moves me up a tier?
4. What is included in support on event day, and what does "priority" actually mean in hours?
5. Is setup labour included, extra, or not offered at all?
6. Can I be invoiced in Ringgit, and can you provide the documents my finance team needs?
7. If I run twelve events next year instead of four, what changes?

The last one is the one that separates a vendor who wants a customer from a vendor who wants a transaction.