Bending your business to fit software that was never built for it?
Built around how you run.
Web app development for when off-the-shelf software makes you bend your business to fit it. I build the thing that fits your business instead.
Being rolled out
A gym app for Imperial.
I built Imperial Grappling's members web app: classes, belt progress, notices, the coach's day and the check-in tablet at the door. It is being rolled out at Imperial now. These screens are on demo data, with names blurred.
- Household
- Classes
- Belt progress
- Notices
- Coach's day
At the door
The software almost fits.
Every business ends up with a process that no product quite supports. So it runs on a spreadsheet, a shared inbox, three apps that do not talk to each other, and one person who knows how it all fits together. It works until that person is on holiday. The gap between what the business does and what the software allows is where the time goes.
Shaped to the process
Build the part nothing else fits.
Off-the-shelf software is right most of the time, and when it fits I will tell you to buy it. I build when the workarounds cost more than the build: the spreadsheet, the shared inbox, and the one person who holds it all together.
The first version is a start, not a ceiling.
I build the smallest system that removes the biggest pain, get it in use quickly, and refine it with you using it. It works on a phone first and connects to what you already have.
You own the code. I host it, secure it and keep it running.
Web apps
Why I build web apps.
Everything I build like this is a web app. It runs in the browser, and people use it just like an app.
Runs just like an app
It opens full screen from its own icon, with its own name, on any phone.
Costs far less to build
One build instead of separate iPhone and Android apps, so it costs far less than a native app.
No app store wait
There is no Apple or Google approval to wait for, so it goes live the day it is ready.
Updates go live instantly
A change reaches everyone the next time they open it. Nobody has to update anything.
One build, every device
The same app works on iPhone, Android and a desktop computer.
On the home screen
People add it to their home screen and open it like any other app. On iPhone, notifications work once it has been added there.
What I build
A system shaped to the process.
I build web applications for the part of the business nothing off the shelf handles: a booking flow with your rules, a member web app for your gym, a job-tracking tool for your crew, a client portal that shows customers exactly what they need. Built on a modern, maintainable stack, hosted and secured by me, and designed so it works on a phone first. You own it, and it grows with the business.
- Scoped from your real process, not a feature list
- Works on a phone, a tablet and a desktop from day one
- Connects to the systems you already use rather than replacing them
- Hosted, secured, backed up and monitored as part of the service
- Built to extend: the first version is a start, not a ceiling
How it works
Four steps. The process first.
01
I understand the process
What happens, who does it, where it breaks. I write it down and you confirm it before anything is built.
02
I build the first version
The smallest system that removes the biggest pain, live and in use quickly rather than perfect and late.
03
I refine with you using it
Real use shows what matters. I adjust in short cycles until it fits like it was always there.
04
I run it
Hosting, security, updates and support. When the business changes, the system changes with it.
Asked before you did.
Often built alongside
Asked before you did.
Anything beyond a standard website that needs logins, data, rules and workflow. Booking systems, member management, internal job tracking, client portals, approval tools. If it is a process rather than a page, it is probably this.
Often, and if a product genuinely fits I will tell you to buy it. I build when the fit is poor enough that the workarounds are costing more than the build would.
Yes. The code is yours. I host and maintain it because that is the sensible arrangement, but you are not locked to me.
A first usable version is typically weeks, not months, because I build the core first and refine in use. Larger systems are staged so something is always live.
Yes. Accounting, CRM, calendars, payment systems, messaging. Most of what I build is the missing piece between things you already have.
That is normal. Describe what you are picturing and I scope it with you.
What you get back
You stop running the business on workarounds and start running it on a system built for it.
Got something specific in mind?
Describe it. If it can be built, and it usually can, I will tell you how and what it would take.