How We Work — Kodaflow
HOW WE WORK

We make the calls.Here's how we make them.

We're a young independent studio out of the restaurant world. Our family runs food businesses, so there's no agency overhead and no guesswork. Nothing below is theory. It's all come out of standing behind a counter on a Friday night.

01

We stand in your shop

Before a single pixel: we watch your counter. Where orders bottleneck, what the kitchen shouts, what customers ask twice. FT Smash's ticket printer exists because we watched staff misread handwritten orders mid-rush.

// field notes, week one
→ peak rush 18:40–20:10, queue at the till
→ phone orders interrupt kitchen mid-service
→ regulars ask “usual?” → saved reorder
→ drivers ring in for addresses → GPS + auto-route
02

Colour is a job, not a vibe

A palette has a job. We test it against the job. FT Smash's red is appetite and urgency, kept pure against griddle-brown and cream so the menu reads outdoors on a cracked screen. KoolKutz runs darker and moodier. It's one barber's personal brand, not a takeaway.

Everything ships at WCAG AA contrast minimum. If your nan can't read the price, it's wrong.

FT SMASH · #E80000
Appetite. Urgency. Order now.
#1A0F0B
Griddle brown.
KOOLKUTZ · #D6292F
Sharp. Personal.
KODAFLOW · #FF5F1F
Signal. Us.
BONE · #ECE6DA
Legibility first.
↑ HOVER
03

UX for thumbs, UI for glances

Your customers order one-handed, walking, at night. So: every tap target at least 44px, checkout inside thumb reach, three taps from menu to paid. We wireframe in greyscale first, so layout gets decided on structure and not colour. Then the brand goes on.

The owner's side is the opposite problem: designed for two-second glances between orders, readable from a metre away with greasy hands.

WIREFRAME FIRST
CTA · 44PX MIN
THEN THE BRAND
FT CLASSIC
FT Classic£8.50
Wings (10pc)£9.00
CHECKOUT · £17.50
04

We test like it's Friday night

A system that works in a demo and dies in a rush is worthless. Before launch we hammer it: cheap Androids on slow 4G, fifty orders in ten minutes, the printer unplugged mid-service to check failover, payments declined on purpose. Then we soft-launch on a quiet Tuesday and stand in the shop watching.

BEFORE WE LAUNCH ANYTHING
£80 Android, slow 4G, cracked screenPASS
50 orders / 10 min load testPASS
Printer offline → failover alertPASS
Card declined → graceful retryPASS
One-thumb checkout, walkingPASS
Soft launch, quiet Tuesday, in personALWAYS
05

Ship it, then keep it running

Launch day isn't the end. That's what the monthly covers: hosting, updates, uptime monitoring that pings our phones before you notice anything, and menu or price changes when you need them. You message us on WhatsApp and you're talking to the person who wrote the code, not a ticket queue. A down system is a closed shop, so ours don't go down.

24/7
MONITORED
DIRECT
TO THE DEVELOPER
1
WHATSAPP AWAY
QUESTIONS YOU PROBABLY HAVE
How much does a full system cost?{{ f0i }}

Priced per project. A booking system and a full ordering platform are very different builds. There's a build fee up front, then a monthly for hosting, updates and support. No commission on your takings, ever. Message us with what you need and you get a straight number, not a sales funnel.

Why not just stay on Deliveroo / Just Eat?{{ f1i }}

Keep them if they bring you new faces. But your regulars shouldn't cost you 15–30% a time. Your own system takes 0% and you keep the customer data, so you bring people back yourself with SMS instead of renting them back from a platform.

Who owns everything after the build?{{ f2i }}

You do. The code, the data, the domain, the merchant account. We host it for you as part of the monthly, so if you ever want to leave you take the lot and move it somewhere else. We'll help you shift it. Nothing's locked to us.

What if something breaks during service?{{ f3i }}

We usually get the alert before you do. Monitoring pings our phones. WhatsApp us any time; you talk to the person who wrote the code, not a ticket queue.