What this usually looks like
If one of these sounds like the thing you keep meaning to sort out, it's probably a two to four week project rather than the six-month rebuild you've been dreading.
Client and member portals
Somewhere your customers log in to see their own documents, invoices, bookings or progress — instead of emailing you to ask.
Dashboards
Your numbers in one place, pulled from wherever they live, so you stop assembling the same spreadsheet every month.
Booking and intake
When the standard booking app doesn't match how you actually work: multi-step intake, deposits, different rules per service, routing to the right person.
Replacing a spreadsheet
The workbook everything runs on that only one person understands and nobody dares change. It becomes a proper tool with real records and permissions.
Integrations and automations
Getting the systems you already pay for to talk to each other, so the same information stops being typed in three times.
Calculators and quoting tools
Someone answers a few questions and gets a number. You get their details and a qualified enquiry instead of a blank contact form.
How a project runs
- 1
Talk it through
Fifteen minutes on what should happen and who it's for. Not how to build it — that's my problem.
- 2
Scope and quote
A written scope with a fixed price, agreed before anything starts. Staged payments on bigger projects.
- 3
Build and review
You see it working early and often, so course corrections are cheap instead of painful.
- 4
Launch and hand over
Live, tested with real data, and walked through with you so you know what you can safely change yourself.
One thing most people miss
Applications built this way often serve search engines and AI assistants a blank page, because the content only appears once the visitor's browser has done its work. If anyone is meant to find your tool through Google or ChatGPT, that has to be handled deliberately — it doesn't come free.
How to test your own appCommon questions
Is this a website or software?
Software. A website presents information; this does work — logins, records, approvals, schedules. Plenty of businesses need both, and they can share one design and one domain.
How long does it take?
Small tools land in a couple of weeks. Anything with logins, payments or another system on the far end takes longer, and I'll give you a range with the quote rather than an optimistic single number.
What does it cost to run afterwards?
Far less than most people expect, and I'll tell you the real figure before you commit rather than after.
Can I change it myself later?
The content usually, the logic usually not. I'm specific about which is which at handover so you're never guessing, and small changes are quick to come back for.
What if I already started building something?
Bring it. Finishing a stalled build is a large share of what I do, and it's often cheaper than starting over.