Brief
You send the brief. We clarify venues, menus, bookings and the fastest path to useful.
We clarify venues, outcomes, existing tools and success metrics before the sprint starts. No mystery requirements, no vague hand-waves.
no fluffprocess
Async, visible, fast.
The work moves through clear briefs, tight feedback loops and production-ready delivery. No mystery stage. No calendar theatre. Venues, menus and bookings get mapped before a single pixel moves — whether the room is in London, the South, the North, Scotland or Ireland.
start a restaurant projecttimeline
Six stages, zero fog.
Every project moves through the same spine — brief, map, prototype, build, launch and improve — with async updates at each step.
Map
We map your venues, menus, booking journey, existing platforms, content and integrations before a single pixel moves.
We audit the tech, menus, audience and operational constraints so the build has a sensible spine. Research happens here — not as a separate black box.
real insightPrototype
See menu, booking and mobile journeys before expensive development starts.
You see the diner journey early — menu, booking, mobile — with room to react while changes are still cheap. Prototypes are for decisions, not decoration.
early signalBuild
We connect the website to the tools your team already uses wherever practical.
We ship the real thing in small visible increments, wired to booking, EPOS or Quiteful where it earns its keep. Async updates you can scan quickly. No black boxes.
fast loopsLaunch
We launch, test, optimise and document what changed.
Deployment, analytics, QA and handover notes are part of the work, not an afterthought. Launch day should feel boring — in a good way.
zero dramaImprove
We monitor performance, conversion and operational friction after launch.
We measure what matters — bookings, menu freshness, mobile speed, staff effort — and keep tuning the system after it meets the world.
always aliveai × human
AI in the loop, humans in charge.
We use AI to move faster on the repetitive parts — structuring a menu spreadsheet, not deciding sesame. Taste, approval, allergen facts and final calls stay with people who know the venues.
Human leads
Brief, taste, approval and final calls stay with people who know the venues. AI suggests — humans decide. Allergen facts are never left to a model.
AI accelerates
Menu spreadsheet structuring, boilerplate and repetitive transforms move faster with AI in the loop — with a human check before anything diner-facing ships.
Guardrails
Review steps, logging and clear sign-off gates. Nothing ships without a human check — especially menus, allergens and dietary information.
tools
The stack we reach for.
The stack changes per project — these are the tools we reach for most.
working with
writing
read the journal Notes on how we work.
Practical posts on restaurant websites, live menus, launches and shipping hospitality technology without dropping taste or care.
scope++
How to spot scope creep before it eats the restaurant budget
process
LGTM?
Async feedback that does not stall a restaurant build
process
access.zip
What a good restaurant project handover looks like
process
read me.txt
How to write a brief a restaurant studio will not misread
process