Restaurants
Stock, food cost, purchasing, staff and sales across one or many branches — in one system instead of a stack of spreadsheets.
See how it works →What I build
Custom business software that takes the manual work off your team.
Bookings, stock, staff, invoices, reports — the jobs done by hand or in a spreadsheet today, turned into one simple system built around how your business already works.
Four things I build
Business management software
A private system your team logs into to run the day — built around your process instead of forcing your process into someone else’s software.
Booking & scheduling
Take bookings without the phone calls and the double-bookings. Availability, staff schedules and reminders all handled in one system.
Workflow automation
The steps somebody currently does by hand every week — copying numbers between tools, chasing approvals, writing the same report — done automatically.
Customer-facing apps
The part your customers see — on the web or on their phone — connected to the same system your team uses, so nothing has to be re-entered.
Built around your industry
Pick the one closest to your business — each page shows the real workflow and what the software handles.
Salons & beauty
Appointments, customer history, staff schedules, commissions, memberships and stock — one system your front desk can run the day from.
See how it works →Car rental & fleet
One platform that manages vehicles, drivers, hours, maintenance and money internally, while giving customers a simple way to book.
See how it works →Service businesses
Cleaning, repair, maintenance, field service, contractors and agencies — leads, jobs, staff assignment, invoices and payments in one chain.
See how it works →Not listed? The work is the same — a messy manual process turned into something simple. Tell me about your business →
How it works
- 01
Understand
You walk me through a normal week — who does what, where the information lives, what gets written down twice. No technical vocabulary needed.
- 02
Identify
Not everything should be software. I point at the repetitive, manual or scattered parts where a system would genuinely save time, and say so when it would not.
- 03
Design
You get a plan in plain English: what the system does, what it costs, how long it takes. One document, fixed price where the scope allows it.
- 04
Build
I build it in pieces you can look at and react to — not a silent three months followed by a big reveal. Changing your mind stays cheap.
- 05
Launch
I put it live, help your team move onto it, and stay reachable for the fixes and additions you think of once it is in daily use.
What it costs
The first conversation is free — we work out together whether custom software is even worth it for you. After that you get one written estimate with a real number, fixed where the scope allows it. No rate card, because no two businesses have the same workflow.
Questions people ask first
I am not sure custom software is what I need. Is that a problem?
No — that is usually the right starting point. Tell me what you are doing today and where it hurts, and I will tell you honestly whether software helps, whether an off-the-shelf tool would do the job for less, or whether the problem is not a software problem at all.
What does a project usually cost?
It depends on the workflow, and anyone who quotes you before understanding it is guessing. As a rough guide, one focused process automated is a few thousand dollars; a full internal system with a customer-facing side is considerably more. After our first conversation I send a written estimate with a real number, fixed where the scope allows it.
How long will it take?
Most projects reach a first usable version in one to four months. I would rather get something small and genuinely useful into your team’s hands quickly and improve it, than disappear for six months building everything at once.
I am not technical. Is that a problem?
No — most of the people I work with are not. You are the expert on your business, which is the part I cannot work out on my own. My job is to turn that into software and explain what I am doing in language you already use.
Will my team actually use it?
That is the part most projects get wrong, so it is the part I design around. If a system takes longer than the spreadsheet did, people go back to the spreadsheet. I build for the person doing the job at 4pm on a busy day.
Can it replace the tools we already pay for?
Often, yes — and sometimes it should not. If a tool you already have does one job well, I would rather connect to it than rebuild it. What I replace is the gap between tools, which is usually where the manual work lives.
Do you work with businesses outside your timezone?
Yes — nearly all of my work is remote. Past clients have been across Europe, the UK, the United States and Australia, so timezones are well-practised territory. I keep hours that overlap with yours for calls and keep you updated in writing in between.
Who owns the software you build?
You do, completely. It lives in your accounts under your control, and you are free to take it to another developer at any time. I do not hold anything hostage.
Have something you need built?
Tell me the problem in plain English. I will tell you honestly whether I can help, and what it would take. No obligation.
Prefer email? immilon27@gmail.com