Software engineering
Web apps, platforms and the systems underneath them, built to be run for years.
The software your business actually runs on. A booking system, a customer portal, an online store, or the internal tool that replaces the spreadsheet everyone is afraid to touch. We build it properly the first time, so it still works when you have ten times the customers, and we write it so that someone other than us can read it.
Who it's for
- Service businesses that take bookings
- Shops selling online
- Founders with a product idea and no team
- Companies outgrowing their spreadsheets
Tools we use
- Next.js
- React
- TypeScript
- Python
- PostgreSQL
- WordPress
- Stripe
- AWS
What we build
Web apps and customer portals
Somewhere your customers log in to book, pay, track an order or see their account. Built around how your business works, not squeezed into a template.
Booking and payments
Calendars, deposits, invoices and refunds that match your real availability and prices, with a confirmation sent the moment a payment clears.
Online stores
Product pages, checkout, discount codes and order tracking, on a platform your team can run day to day without calling us.
Internal tools
The spreadsheet that runs the business, turned into a proper tool. The right people see the right things, and nothing gets lost in an email chain.
Websites that bring in customers
Fast, easy to find in search, and written so a visitor knows within seconds what you do and how to get started.
Connecting your tools
Your CRM, accounts, calendar and messages talking to each other, so nobody has to copy information from one to another by hand.
You might need this if
- Someone on your team does by hand what software should be doing
- Your site or app breaks, and nobody can tell you why
- You have an idea for a product and no one to build it
- Your business has outgrown the tool it started on
How it runs
- 1
Walk through it
We sit with you and the people who will use it, and watch how the work gets done today.
- 2
Agree the first version
What it does on day one, what waits until later, and what it costs.
- 3
Build in the open
A working version to try every week, on a link you can share with your team.
- 4
Launch and look after it
We put it live, watch it closely through the first weeks, and keep looking after it from then on.
What you get
- Working software you can try every week, not one big reveal at the end
- Hosting, domain and email set up properly, in your name
- Everything written down, so a future hire can pick it up
- Us, still around after launch, running it and fixing what breaks




