Solutions
Work
Blogs
About
Start a project →
← Everywhere we work

Web design for Nottingham.
For a year with a three-month hole in it.

A lot of Nottingham trade lives off a student population, which means the trading year has a shape most systems ignore: a violent September, a strong term, and a summer where volume collapses. Building for the average of that year produces something that is overwhelmed in October and expensive in July.

Start a project

Designing for a year that is not flat

Four decisions that look like details and decide whether the system suits the business.

Nothing should cost per month per terminal

A per-seat subscription is paid in August at the same rate as October. A bought system is the same price in a quiet summer, which is most of the argument for building rather than renting.

Opening hours and menus by season

Term-time and vacation as switchable configurations rather than something somebody edits twice a year and forgets once.

September is the only load test that counts

Freshers week is the peak and it is predictable to the day, so the capacity conversation happens in July, not during it.

The customer leaves in three years

A loyalty scheme in this market churns its entire base regularly, so it should be cheap to join and immediately rewarding, not a long-horizon points balance.

What works on this audience specifically

  • Group ordering A house of six ordering together, split however they like. The most requested feature we have seen in a student market and the least commonly built.
  • Collection, heavily Dense, walkable catchments make collection the dominant order type, and it carries the whole margin — the aggregators’ own published rates are what it is being compared against. Build it first.
  • Nothing to install A pass in Wallet, a web page saved to the home screen, a QR code on the table. An app download is a conversion step this audience does not complete.

When we are the wrong firm for this

If you are an established Nottingham business with a steady local trade and no student exposure, this page is about somebody else and the useful page is the ordering or booking one. And if your plan depends on being busy every week of the year, a seasonal business needs a cost base that flexes — which is an operations decision we cannot solve with software.

What software can do is stop the quiet months costing you a subscription for capacity you are not using.

Questions

Before you ask.

Can the system switch between term-time and vacation?

Yes — hours, menus and delivery rules as switchable seasonal configurations, rather than something edited by hand twice a year and forgotten once.

Can a group split an order?

Yes, and in a student market it is the feature most asked for and least often built: one order, several payers, split however they choose.

Is a built system sensible for a seasonal business?

It is usually the stronger argument. A monthly per-terminal subscription costs the same in a dead August as in a frantic October; a bought system does not.

Ready to get started?

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

Start a project →