Custom web apps, built with Next.js and React.

Businesses that have outgrown spreadsheets and email chains, teams paying for three tools that don’t talk to each other, and founders with an idea for a web product who want it built by people who have launched their own. You don’t need to be technical: you need to know what’s slowing you down.

For when an off-the-shelf tool almost fits, and almost costs you hours every week.

• Web applications: tools your team or customers use in the browser, on any device.
• Integrations and APIs: getting the systems you already pay for to talk to each other, so nobody copies data between them by hand.
• Workflow automation: the repetitive steps (reports, reminders, exports) done by software instead of a person.
• Modernising old systems: moving a spreadsheet, an Access database or an ageing app onto something you can use from any device.

Next.js, React and TypeScript for the app itself, styled with Tailwind CSS. Supabase (Postgres, sign-in and storage) when it needs a database and accounts, and Stripe when it takes payments. Progressive web apps when it needs to work offline and install on a phone like an app.

That’s what we use for our own products, so it’s what we know best. This site is built with Next.js and TypeScript too. If your project is better suited to something else, we’ll say so rather than bend it to fit.

Our own products are the best evidence: CakeyTops is a design studio that runs in the browser and produces 300 DPI print-ready sheets. Chalkmate is an installable, offline-first app with live statistics and leaderboards. DiscoverTCG recognises trading cards with the phone’s camera, on the device, and maps UK card shops. We designed, built, launched and still run all three.

You talk directly to the person writing the code: no account managers, ticket queues or hand-offs. We agree what you need, what it costs and when it’ll be ready before any work starts. Then you see the design before we build it.

• Talk: we agree what you need, what it costs and when it’ll be ready, before any work starts.
• Design: you see the design and say what to change before we build it.
• Build and launch: we build it, test it on phones and computers, and put it live.
• Look after it: updates, fixes and backups carry on for as long as you’re with us.

You don’t need a specification. A few honest answers are enough to start:

• The problem in a sentence or two: what takes too long, goes wrong or can’t be done today.
• Who will use it: customers, staff, or both, and roughly how many.
• What you use now, whether that’s spreadsheets, paper or another piece of software, and what you’d keep.
• What it must do in the first version, and what could wait.
• Any date it has to be ready by, and why.

Software is quoted per project, and the quote depends on how much there is to build. The biggest factors are the number of different kinds of users (customers, staff, admins), how many other systems it has to connect to, whether existing data has to be moved across, and how polished the first version needs to be. A focused first version you can use and improve is usually the best-value place to start.