Web Base

BACKGROUND

Introduce your business and what you do there.

I’m the manager of a company that sells tickets for events in Romania.

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire Web Base to accomplish for your ticketing business?

We hired Web Base to build our website.

SOLUTION

What was the scope of their involvement?

Web Base has built and maintains our custom ticketing platform, including a checkout flow with real-time seat selection using Firebase so seats lock instantly and can't be double-booked. Main deliverables have included a custom ticket serial number system for tracking and reconciliation, PDF ticket generation with barcodes, integration with Netopia Payments for local card processing, social login through Google and Facebook, and an admin dashboard for sales reporting. The team has also set up SMS reminders for upcoming events and handled ongoing feature updates as our needs changed.

What is the team composition?

We work with 2–5 teammates from Web Base.

How did you come to work with Web Base?

We found them through a referral. We chose them over other options because they had high ratings, good value for cost, and their company values aligned with ours.

What is the status of this engagement?

We started working together in February 2026, and the engagement is ongoing.

RESULTS & FEEDBACK

What evidence can you share that demonstrates the impact of the engagement?

Since launching the Firebase-based seat locking system, we've had zero incidents of double-booked seats during high-traffic on-sale periods, which was a recurring problem before. The custom ticket serial number system has cut down significantly on the manual reconciliation work our team used to do after each event. PDF ticket generation and delivery is now instant and error-free, with no more barcode or formatting issues that used to generate customer support requests. The admin sales dashboard also gives us real-time visibility into ticket availability per event, which we didn't have before and now use daily.

Before, it typically took our team around 3–4 hours after each event to manually cross-check ticket sales and reconcile everything. Now, with the serial number system, that's down to under an hour, sometimes less, depending on the event size. Support requests related to ticket delivery or barcode issues, which used to come in regularly during busy periods, have essentially stopped since the fix.

How did Web Base perform from a project management standpoint?

Communication has been direct and responsive throughout. This isn't a one-time project but an ongoing collaboration, so we regularly request new features or fixes, and they get scoped and delivered quickly, usually within days rather than weeks. When something urgent comes up, like a bug affecting live ticket sales, it gets prioritized and fixed the same day.

We don't get formal project timelines or Gantt charts. It's a more informal, agile way of working, but it's worked well for us because our needs change often, and we need someone who can move fast.

What did you find most impressive or unique about them?

What stands out most is how much custom, technical work they're willing to take on that a typical WordPress agency would probably say no to, including real-time seat locking with Firebase, a custom ticket serial number system built from scratch for our specific reconciliation needs, and PDF generation with precise formatting requirements. It never feels like we're limited to whatever a plug-in or theme allows. If we need something specific to how our ticketing business actually works, they build it rather than telling us to adapt to a generic solution.

Are there any areas they could improve?

The only thing I'd point to is that because we work in a fairly informal, fast-moving way, we don't always get a clear estimate upfront on how long a more complex feature will take. Sometimes it's quick, and sometimes it takes longer than we initially expected. Written documentation for some of the custom features has also lagged behind the actual development since things get built and shipped quickly. It hasn't caused real problems for us, but a bit more structure around timelines and documentation would be a nice addition.