KHC has restructured its product tiers into four deployment packages. The dividing principle is not a feature count but the three factors that decide how hard a project actually is: event scale, peak concurrency, and the level of operational commitment the organisation needs.
Why not divide by features
Dividing by features forces a customer to guess what they need before they understand their own problem. It also produces the familiar outcome where a small organisation buys a high tier for one feature, or a large event buys a low tier and then fails in the first minute of the on-sale.
All four KHC tiers share one core platform: a ticketing webapp, dynamic QR tickets, gate check-in with offline readiness, and sales reporting. What differs is the operations layer, the defence layer and the committed service level.
The four tiers and the lines between them
| Package | Applies to | What separates it |
|---|---|---|
| Single event | One or a few days, moderate traffic | Fast deployment, organiser runs the event day |
| Season and series | Many fixtures, many on-sale waves | Repeatable operations and an accumulating data layer |
| Large scale with commitment | High peak traffic, service-level needs | Defence layer, load testing, written commitment |
| Purpose-built model | Cases the three tiers do not describe | Survey first, then a revenue model of its own |
The real line between the second and third tiers is peak concurrency, not total tickets. Selling five thousand tickets over three days and five thousand in fifteen minutes are different engineering problems.
Five questions that settle the tier
Is this one event or a whole cycle. What is the expected peak concurrency. Is there a seat map, and is seat selection required. Are membership, merchandise and food and beverage required. And finally, who carries the event day.
Those five are usually enough to settle the tier in one working session, and they also frame what the KHC team prepares for the survey.
On pricing
KHC does not publish prices for the four packages. Audience size, number of events in a cycle, peak concurrency and current ticketing practice differ from one organisation to the next, so each customer is surveyed first and then receives a figure of their own with a scope document.
This is slower than a printed price list, but it avoids the common outcome of a template quote followed by change orders once real delivery starts.
Frequently asked questions
Can a lower tier be upgraded later
Yes, because all four share the same core platform. Upgrading mainly adds the operations layer, the defence layer and the service level rather than replacing the system.
Who is the purpose-built package for
For cases the three tiers do not describe: an organisation that owns a large community but runs no events, a manufacturer seeking access to an existing community, or a federation needing one shared model across member organisations.
What does the survey cover
A review of current ticketing, membership care, existing sponsorship packages and where the data sits today. It usually takes one working session on site.
Conclusion
Tiering by scale and commitment lets both sides speak the same language from the first meeting. To find out which tier fits, book a survey of where you stand today.
See also the four KHC deployment packages.
Leave your details and KHC will be in touch.
