nuvelo.
About

Built by one person, for venues that aren't chains

nuvelo is built and run by Christian Lewis. I've spent twenty years delivering software — mostly the unglamorous kind that has to work on a Tuesday morning when somebody's business depends on it.

It started with a straightforward observation. Independent restaurants, bars and soft play centres were paying a slice of every booking to systems designed for groups with head offices. The fee scales with your success, the software is built for someone else's problems, and the money goes somewhere else first.

A booking system should cost the same in a quiet January as in a busy December, and the money your guests pay should land in your account, not someone else's.

What that means in practice

One flat monthly price. No fee per cover, per child or per booking. A busy weekend costs you nothing extra.

Your money goes to you. Deposits and payments run through your own Stripe, Square or SumUp account. nuvelo never holds your takings and never takes a cut of them.

Built for one venue, not fifty. Your floor, your tables or sessions, your day — on one screen, usable on the tablet by the door.

Where it is today

nuvelo is early, on purpose. I'm working directly with the first ten venues before opening it up properly, because software for a trade I don't work in should be shaped by people who do. Those ten get every feature at the Pro price, locked for as long as they stay.

Being straight about it: you'd be among the first, some things are still being built, and you'd have my phone number. That's the trade.

If something breaks

The platform is watched around the clock — automated checks run every minute and raise anything unusual immediately, so you are not the one who has to spot it. Report a problem from inside your admin and it is logged and acknowledged, with another email when it is fixed. Anything touching bookings or payments is treated as urgent rather than queued; other fixes go out in a nightly release when one is needed.

Questions rather than faults? [email protected] — I answer these myself.