Development Agency
Contact Sign in Get a project quote

Service

Cafe website development

For café, coffee shop and tea room owners who want a website that keeps up with a counter that changes every morning, instead of a brochure site that is wrong by the second week.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A café is a small business with a fast-changing product.

  • The cake selection depends on what was baked at six, the soup changes daily, a batch of the house blend runs out mid-afternoon and the sandwich list shifts with the season.
  • Almost no café website reflects any of this.
  • It was built once, with a PDF menu and a photo of a flat white, and the opening hours on it still say what they said eighteen months ago.
  • Customers phone to ask whether the café is open on the bank holiday, whether the gluten-free brownie is on today and whether they can pick up six coffees and a box of pastries for a nine o'clock meeting.

Where it gets harder

The owner answers those questions from behind the machine during the morning rush.

  • Pre-orders are taken on a notepad and a cup is sometimes made twice or not at all.
  • The loyalty card is a stamp on cardboard that gets washed in a pocket.
  • Event nights, a book club, a supper club or a local maker's pop-up, are announced on a social feed where they vanish within hours.
  • A nearby office asks about a weekly order of thirty sandwiches and the enquiry lives in a direct message nobody can find later.
  • Meanwhile the map listing shows the café as open at a time it has been shut for months, and a one-star review arrives from the person who found the door locked.

Scope of the service

What the build covers

A custom café build covers a website whose menu is edited from a phone behind the counter in the time it takes a kettle to boil:

  • Sections Items, dietary tags, today's specials and a sold-out toggle
  • Opening hours With weekday patterns and holiday overrides that also feed the map listing
  • A loyalty scheme that lives on the customer's phone Earned at the till and redeemed against a drink or a bake
  • Collection pre-orders For a limited menu with time slots that respect how many orders the counter can make in a ten-minute window
  • An events and community board with dates Capacity and a simple sign-up
  • A wholesale or catering enquiry form That lands somewhere it will actually be read

How discovery works

Discovery works through a weekday morning and a Saturday with you: who bakes and when the cake counter is settled, how often the menu actually changes, whether pre-orders are wanted at all and how many the counter can take on in a rush, how the stamp card works today and what you would honour, which events you run and who manages them, and whether wholesale is a real line of business or an occasional ask. Each answer becomes a named workflow stage in the scope document.

  1. Browse menu
  2. Pre-order or visit
  3. Collect
  4. Stamp
  5. Return

Deliberately out of scope

  • Table service and reservations, full delivery ordering with drivers, stock and purchasing, and the till itself. A café that needs a delivery pipeline is better served by the online ordering topic

When the scope grows

Scoping scenario

A bakery-café with two shops wants one website where each shop publishes its own cake counter each morning, pre-orders are routed to the right shop by collection point, loyalty stamps are honoured at both, and a weekly office order for one of the shops is managed as a standing order. That is a different build from a single twelve-seat espresso bar that mostly needs its hours and menu right, and the scope document says which you are buying.

Deliverables

What you receive

  • Discovery notes from a morning and a Saturday behind the counter
  • A written scope document naming each stage from browsing the menu to loyalty redemption, with what is out of scope
  • Design of the public site, the menu editor and the pre-order flow on a phone first, then desktop
  • The build, deployed to your hosting or ours
  • Migration of menu items, event listings and any existing loyalty balances, where relevant
  • Training for the owner and counter staff, with a one-page guide for the daily menu update
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts and a look at your current website, map listing, social feeds and how the menu and hours are published today.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner and whoever runs the counter in the morning; the scope document and milestone plan are agreed.

    Project stage: Planning

  3. Design

    Clickable designs of the menu page, the daily editor and the pre-order flow, checked on the phone the owner actually uses behind the counter.

    Project stage: Design

  4. Development

    Built in stages: menu and hours first, then pre-orders and loyalty, then events and enquiries.

    Project stage: Development

  5. Client review

    The counter runs the daily menu update and a week of test pre-orders and tells us where the editor is slow or the slots are wrong.

    Project stage: Client review

  6. Revisions

    Editor layout, slot capacity and loyalty rules are adjusted from the review and re-checked against the scope.

    Project stage: Revisions

  7. Ready for launch

    Menu and events loaded, map listing hours connected, order notifications tested on devices you control, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The café runs on the new site; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card payment providers for paid pre-orders
  • Google Business Profile and map listings so opening hours are published once
  • Till systems where loyalty stamps are to be earned at checkout
  • Email and SMS providers for order-ready notifications and event reminders
  • Social feeds for cross-posting the daily specials and events
  • Accounting software for pre-order and wholesale invoicing

How we would approach it

Worked example

Concept demo

A neighbourhood café with a morning pre-order rush

The situation

A café near a cluster of offices wanted to take pre-orders for coffee and pastries without the counter being buried at half past eight.

Why it is a custom build

This needs a custom build rather than a generic ordering app because the constraint is the espresso machine, not the kitchen: capacity is counted in drinks per window, the menu is a subset of what is on the counter, and the whole thing must switch off with one tap when the queue at the door is already long enough.

The scope we would propose

  • A limited pre-order menu of drinks and the day's bakes, published from the same editor as the main menu
  • Collection slots in ten-minute windows with a cap on drinks per window set by the owner each morning
  • A kitchen-side list on a tablet by the machine that shows what to make next
  • A ready notification to the customer so nobody waits at the counter asking

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of shops and whether each publishes its own counter
  • Whether pre-ordering is wanted, and how capacity per window should be counted
  • Loyalty scheme rules and whether existing stamp cards are honoured
  • Events and community board with sign-ups and capacity
  • Wholesale or catering enquiries and any standing orders
  • Connection to the till or the map listing
  • Photography and content for the launch menu
  • Hosting choice: your own hosting or ours

Start from a package

Cafe website package

A café website with a phone-edited daily menu, holiday-aware opening hours, collection pre-orders with capacity per window, loyalty on the customer's phone and an events board.

Custom build
View the package

FAQ

Frequently asked questions

Do we need a custom build, or would the package do?

Most single-site cafés are covered by the café website package with configuration: menu, hours, loyalty and a simple pre-order flow. A custom build is the honest answer when several shops publish different counters, when pre-order capacity has unusual rules, or when wholesale is a real line of business. Discovery is where we tell you which.

How quickly can we change the menu each morning?

The editor is designed for a phone behind the counter: toggle today's bakes on or off, mark something sold out, and type a special. The website updates straight away. There is no publishing step and nothing to upload.

Can we switch pre-orders off when we are slammed?

Yes. One tap pauses new pre-orders and shows customers the next available window instead. Orders already accepted stay in the list, and the owner can cap drinks per window differently on different days.

Who owns the website afterwards?

You do. Source code and your data are handed over at delivery; hosting and maintenance are optional and separately agreed, and the site can be moved to another provider.

Get a project quote for café software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences