Skip to content
European companyFounded in 2014Built and operated in EuropePayments secured by Stripe
Gradax

Found by people standing two streets away

Local search, ordering and pre-order systems for cafés and bakeries, built around footfall and the orders worth taking in advance.

Sold as
One contract
Starts with
A free review

The vendors we build on, operate and resell.

  • Cisco
  • HPE
  • Dell
  • Lenovo
  • Veeam
  • WordPress
  • WooCommerce
  • Google
  • Stripe
  • Zoho
  • Atlassian

Most café discovery happens within a few hundred metres and inside a map application, not on a website. What decides whether somebody walks in is whether the hours are right, the photographs are real and the reviews are recent, all of which live outside your site.

Where a website earns its keep is pre-orders: celebration cakes, catering trays, morning orders for an office. Those are high-value, planned purchases that a phone call handles badly and a form handles well.

The search side is not separate from that. "Coffee near me", "bakery open now" and "birthday cake" plus a town, the last of which is a real order rather than a walk-in. Ranking for those means the pages exist, the business is verified where it operates, and the reviews are real and recent.

How a pre-order moves through a bakery

Walk-in trade runs itself, while cake and office orders are where mistakes cost money.

  1. Order placed

    Cake orders taken by phone in the morning rush get the details wrong, so the online form captures size, message and collection time.

  2. Deposit and lead time

    Orders inside the lead time get accepted and then cause panic, so the calendar refuses dates you cannot bake for.

  3. Bake list

    Orders written on loose paper get missed, so each morning's bake list prints from the confirmed orders.

  4. Collection

    Uncollected cakes are a straight loss, so a reminder goes out on the morning of collection.

Software we built for businesses like yours

A product we are building now, shown here as the work we do.

HoReCa POS (in development)

HoReCa POS, our till and back office for cafés, is in development and is built to keep selling when the internet drops.

A waiter taking an order at a restaurant table

What people in this trade ask us

Do we even need a website?
A small one, yes, and mostly for orders you cannot take over a counter. But fix the map listing first: it is where more of your customers are looking.
Can we take cake orders online?
Yes, with a deposit and a lead time you control, which removes both the rush-hour phone call and the order somebody never collects.
What matters most for local search?
Correct hours, real photographs, and recent reviews. In that order, and all three matter more than anything on your site.
Can we run a loyalty card without paper stamps?
Yes, a digital stamp tied to a phone number. It is only worth doing if staff can add a stamp in one tap while the queue is out of the door.
Can office customers order on account?
Yes. Regular office orders can be invoiced monthly instead of paid each time, which keeps the standing order without a card at the counter every morning.

The infrastructure under it

Managed by the engineers who build the software, on the same contract and the same bill.

Web Hosting

A small site that loads instantly on a phone two streets away, without you ever thinking about it.

A developer working on a website on a laptop in an office.

Cyber Security

Card payments for cake deposits and office orders need a checkout that cannot be tampered with.

Two monitors showing security logs in a dark room.

What one contract covers

  • One contract. The build, the infrastructure and the work that brings people to it, on one invoice.
  • A named team. The person on the first call stays on the project. No account managers, no handoffs.
  • Operated, not delivered. We keep it running after launch: patching, backups, monitoring and the phone when it breaks.
  • European hosting. Servers in Europe, run by us, with the data staying where you expect it to.
  • Monthly reporting. What changed, what it cost and what it produced, in language you can forward to a board.
  • No lock-in. The code, the domains and the accounts are yours. Leaving is a handover.

See what is costing you customers before you spend anything.

A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first.

  1. 01You tell us what is not working
  2. 02We review the site, the search presence and the enquiry path
  3. 03You get the three fixes worth doing, and what each is worth