Web design for Edinburgh.
For a city that quadruples in August.

Edinburgh is the clearest example in Britain of a trading year with a spike in it, and the businesses that handle August well are the ones whose systems were designed for it rather than scaled up in July. The work we are useful for here is capacity: timed entry, ticketing, pre-order and the arithmetic of how many people a kitchen or a door can actually take.

Start a project

Capacity is the product

Four things that decide whether a venue has a good August or a chaotic one.

Timed slots with a real limit

A slot is a capacity, not a label. The limit has to come from what the kitchen or the door can genuinely do in that period, and the system must stop selling when it is reached — including when two people are mid-checkout for the last two places.

Holding a place during checkout

Overselling at peak happens in the ninety seconds between choosing and paying. A short hold on the inventory while payment completes is a small piece of engineering that prevents the worst customer conversation there is.

A door that works offline

Scanning a ticket on a venue door with bad signal has to work without a network and reconcile afterwards. A check-in screen that depends on wi-fi will fail at exactly the wrong moment.

Refunds and transfers, decided in advance

Your policy, in writing, on the screen where the money is taken. Peak trade generates the most disputes and that is where they are settled.

Sources, checked 26 October 2026

legislation.gov.uk, Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, regulation 30: the 14-day cancellation period

What August does to the rest of the system

The menu shrinks on purpose A seasonal configuration — fewer items, faster to cook, switchable in one action — is an operational decision the system should support rather than obstruct.
Staff who are new and temporary If a new starter cannot use the till in ten minutes without training, the system is wrong for this city. Simplicity at the counter beats features.
Eleven quiet months Which is the argument against anything priced per terminal per month, and for something owned.

When we are the wrong firm for this

If you need a full ticketing platform with allocated seating, agent allocations and resale, buy one of the established ticketing products — that is a mature category and building it bespoke would be a waste of your money. We are the right call for timed entry, capacity and the operational systems around a venue, not for being a ticketing company.

And if your Edinburgh business is steady year-round, this is the wrong page for you; the booking and ordering pages are the right ones.

Questions

Before you ask.

Can you build timed entry with real capacity limits?

Yes, including the hard part: holding the place while the customer pays, so two people checking out for the last two slots cannot both succeed. That ninety seconds is where overselling happens at peak.

Will ticket scanning work if the venue signal is poor?

It has to. The door screen works offline and reconciles when it reconnects, because a check-in that depends on wi-fi fails at the busiest moment of the day.

Should we build our own ticketing platform?

Almost certainly not. For allocated seating, agents and resale, buy an established ticketing product. We are useful for timed entry, capacity and the operational systems around the venue.

Ready to get started?

Tell us what you need. We will scope it, price it and build it.

Start a project →

Web design for Edinburgh.For a city that quadruples in August.