TickFind — Ticket Discovery & Marketplace

TickFind — ticket discovery & marketplace (web MVP)

Allatrack self-funded and led a full end-to-end development of a web-first ticket discovery product during COVID.

We built a responsive frontend, admin UI, backend, and integrations. The product launched to production but did not reach expected commercial traction due to market conditions and partner marketing choices.

The platform was production-ready and handled real-world traffic in initial rollouts.

The Problems:

Event organisers and users needed a single discovery channel for tickets. Existing services were fragmented; organisers wanted better discovery, ticket-locking flows, and a simple admin UI to manage offers.

Full-stack delivery:

Responsive web frontend + admin panel + backend services

Team:

Senior-only delivery (engineers, PM, QA)

Timeline:

MVP → production (project spanned ~0,8–1,5 years of work)

Development:

We covered development and product engineering; partner handled marketing

What we built

Responsive web app (HTML5 + Bootstrap) for users
Admin panel built with Backbone.js for event management
Backend implemented in Perl (legacy / core services) with integrations for payments and ticketing APIs
Dev workflow: weekly demos, CI/CD, staging → production deployments

Note: There was no native mobile app — product was web-first with responsive layout.

Design system* & UI kit

Include typography, color palette, buttons, form fields, datepicker and table examples from UI kit.
Show 2–3 key components (primary button, search field, ticket table) as proof of design discipline.

* – Design system: reusable UI kit (typography, color palette, inputs, datepickers, buttons, tables) that enabled rapid, consistent feature delivery across customer and admin flows.

Roadmap & business model

Original plan: agency-led sales + secondary resale marketplace (resale/auction, escrow guarantees).
We delivered core discovery, checkout and admin flows; resale was a planned next step (technical foundations in place).

Product roadmap included marketplace + secondary resale and monetisation paths. Core flows were validated; GTM & partner marketing determined commercial outcome.

Outcomes & learnings:

TickFind reached production and validated the core technical and product assumptions. Below are three concise outcome areas and our reflective narrative on what we learned.

Technical (what worked):

Stable backend and resilient checkout
Payment gateway integrations (payments, retries, payouts)
CI/CD and staging → production workflows

Product (what we proved):

Responsive UI and admin flows (Backbone.js)
Reusable UI kit for faster iterations
Ticket-lock & checkout flows validated in real scenarios

Commercial (what happened):

Launched to public channels and listed in stores
Ticket sales operations and post-launch support handled by Allatrack/partners
Limited commercial traction due to COVID and partner marketing choices
Resale & GTM remained under-funded by partners

Our story:

We built TickFind as a company-funded product and invested significant engineering effort over ~0.8–1,5 years to bring a production-ready platform to market.

The team delivered robust technical foundations — a responsive frontend, an admin panel, a Perl backend and payment integrations — and validated critical user flows like ticket reservation and checkout.

Commercially, the project faced headwinds outside of engineering control: the pandemic shifted live-event demand and the partner-led marketing plans did not scale the user acquisition needed to reach product-market fit.

From this experience we distilled three practical lessons:

align go-to-market and marketing commitments before heavy development;
validate real demand with small paid tests before large ad spends;
and formalise partner responsibilities in contracts to avoid gaps in post-launch execution;