Loading page…
Cloud reservation software that lets tours and attractions sell, distribute, and scan tickets without enterprise setup fees.
250–300 customers · about $10K/mo profit · 1.5%–3% take rate
The wedge was not another expensive ticketing suite; it was a simpler system priced for the long tail of tours and activities.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Carl Pihl built TicketingHub out of an operational problem in his earlier business, Lost in London. His team printed tickets for language schools, events, attractions, and tours, then discovered how easily paper tickets could be copied when venues did not scan third-party tickets. A ticketing vendor quoted a $20K setup fee plus a 200,000-ticket annual minimum, so Carl hired a developer and built a more accessible back end. The company later acquired Minicards for roughly $13K–$20K to gain hotel and hostel distribution. TicketingHub now serves tour and activity companies with ticket sales, distribution, and point-of-sale tools. Carl reported 250–300 customers, about $200 average monthly revenue per account, approximately $50K monthly revenue, more than $90K in the bank, and about $10K monthly profit. It is fully bootstrapped, with nine people and Carl retaining 100% ownership.
The first customers came from a distribution problem the founder already understood. Lost in London was working with about 100 schools and universities, so those relationships supplied the initial audience for a digital ticketing workflow.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“…covered strong they've got over 90 000 bucks in the bank 10 000 bucks a month in profit and we love Carl because he's 100 bootstrap hey folks my guest today is…”
0:13 · hear it in the videoData credibility: Carl Pihl reported the operating metrics in a founder interview: 250–300 customers, about $200 average monthly revenue per account, roughly $50K monthly revenue, more than $90K in the bank, and about $10K monthly profit. The figures are founder-reported and unaudited; the transcript also contains auto-caption errors around some earlier amounts.
The first dollar should arrive when a ticket is sold, because the value of the product is directly connected to a completed reservation. TicketingHub charges a percentage of sales, generally around 3%, with discounts down to about 1.5% for larger customers.
The flywheel combines distribution and product breadth. Every tour company, school, hotel, or attraction that uses the system adds another place where tickets can be discovered and another operational case that improves the platform.
TicketingHub survived several stretches where demand and confidence were weak. The copied-ticket problem nearly sank the earlier business, and the pandemic removed most tourism activity.
TicketingHub is a commerce and operations layer for tours, attractions, and activity companies. An operator can publish availability, accept ticket orders, manage distribution, run point of sale, and check visitors in using ordinary phones or tablets. The product sits between supply and demand: it gives a supplier a reliable booking ledger while giving partners such as hotels, schools, and activity marketplaces a way to sell inventory. The transcript compares it with Shopify for tickets, which is a useful mental model but not a complete product specification. The key design choice is accessibility. A small operator should be able to start without buying specialized scanners or paying a large setup fee. The platform can still support enterprise customers, but the copyable wedge is a low-friction workflow for the long tail of tours and experiences that need dependable reservations more than they need a complex enterprise suite.
The main revenue stream is a transaction fee on ticket sales. TicketingHub generally charges about 3% of sales, with larger customers negotiating toward roughly 1.5%. Its reported average account contributes around $200 per month, and 250–300 customers support approximately $50K monthly revenue. That implies a broad customer base rather than dependence on a few very large contracts. Some operators prefer a flat fee derived from the same volume calculation, so the commercial model can accommodate predictable budgeting without losing the connection to usage. The company also benefits when customers grow their ticket volume, and it can expand revenue by adding distribution, point-of-sale, and operational services. The tradeoff is that payments, refunds, fraud, seasonality, and customer support become part of the cost structure. Keep the pricing legible: operators should understand the fee per booking before they trust the platform with their customer relationship.
The founder described a mobile-friendly hardware-light setup: customers can use an iPhone or Android device, then buy their own payment device and printer if needed. That keeps deployment costs lower than a proprietary scanner fleet. The business has nine people and five full-time developers, so engineering and support are the largest visible costs. The reported $90K in the bank and about $10K monthly profit show a bootstrapped operation with cash discipline, but they do not reveal gross margin by payment method or customer segment. A new entrant should start with hosted checkout, a responsive operator dashboard, webhook-driven payment reconciliation, and integrations only after the core booking state machine is reliable. Measure payment fees, support minutes per booking, failed check-ins, refund rate, and revenue per active venue. Do not promise enterprise reliability before monitoring inventory, payment, and scanning flows in real operating conditions.
Copy the decision to serve a large overlooked middle: businesses that sell enough tickets to feel operational pain but do not want a $20K setup fee or a 200,000-ticket minimum. Copy the use of existing distribution relationships, the hardware-light deployment, and the percentage pricing that lets small customers start without a large commitment. Change the scope for an initial build. A new founder should choose one activity type, one region, and one booking channel before attempting to connect every marketplace. Treat check-in reliability and refund handling as core product work, not later polish. Add an operator-facing migration tool because importing schedules, ticket types, and customer data is often the real switching cost. The opportunity is not to build a generic events platform; it is to own a narrow inventory workflow and then add adjacent channels when repeated customers ask for them.
The largest risk is operational trust. A copied ticket, double booking, payment error, or failed scan can make an operator lose money and reputation immediately. Tourism is seasonal and vulnerable to travel restrictions, weather, and economic shocks, so a transaction-only model can see revenue fall quickly. Large reservation vendors and marketplaces can bundle similar capabilities, while enterprise customers may demand integrations that consume more engineering time than their fees justify. The business also carries security and compliance responsibilities because it handles customer information and payment events. Competition from cheaper point tools can pressure the take rate, while a complicated product can undermine the simplicity that attracted smaller operators. Keep inventory states explicit, log every ticket transition, make exports easy, and build cash reserves before expanding the team. Carl’s figures are first-party and unaudited, so the model should be evaluated with cohort retention and net transaction margin, not revenue alone.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,435 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click