independent software practice — accepting new commissions
haphzrd is an independent practice building web, mobile and home-automation systems — tools that get out of the way, automate the boring, and give the day back to you.
01 — manifesto
The world doesn’t slow down. Schedules slip, bills pile up, devices argue, inboxes overflow. Most software adds to the noise.
The work here goes the other way. Systems that earn their place by not breaking. Interfaces that disappear into the task. Automations that close the gap between intention and outcome — so people can get back to the parts of life that aren’t a problem to solve.
02 — practice
Different surfaces, same craft. Each one a system you can lean on — built end‑to‑end and made to outlast the brief.
Marketing sites, customer platforms, and the operational tooling that holds them up. Architecture that doesn't unravel. Performance you can feel.
Sensors, schedules, voice — and the glue that makes them speak the same language. Homes that anticipate, not just react.
Native and cross-platform mobile, built to feel at home on the device. Tuned to the hardware. Useful when the network isn't.
03 — work
Builds that go all the way down — interface, services, infrastructure — threaded with the API integrations that connect the moving parts. Past engagements have covered AI bots, booking platforms, inventory tracking, and the websites that hold them together.
Builds that go all the way down — interface, services, infrastructure. They scale by being well-made, not by being clever.
Conversational layers woven into existing flows, with retrieval, tool-use, and guardrails that don’t undo the rest of the product.
Calendars, availability, payments — and the awkward edge cases nobody mentions in the brief.
Dashboards that show the actual state of the business, not yesterday’s spreadsheet.
iOS, Android and cross-platform — tuned to the device, the network, and the moment of use.
Automations the household stops noticing — because they don’t break.
The connecting tissue. Stitching services, devices and partners together — most of the bugs in a product live here, so it’s where I spend the time.
05 — approach
A solution that survives users, scratchy networks, and ordinary Tuesdays. Resilience over novelty.
The seam between interface and infrastructure is where most products fail. So I work both sides.
Less surface area. Fewer prompts. Slower animations. Smaller defaults. Tools that earn the second visit.
A modest version in working use beats a generous version in a slide deck. Iterate against use, not opinion.
04 — in development · code names
Each one answers a daily friction — the kind that doesn’t make headlines but costs people their evenings. They’re built slowly, on purpose.
End-to-end commerce for a precision-instrument line. Catalogue, stock, checkout and dispatch — one stack from product page to packed box.
Marketing and booking for a learning practice. Site, intake, scheduling and follow-up — one funnel from first enquiry to enrolled student.
A training app that counts what actually happened. Sets, reps, time under tension — measured by the device, not estimated by the eye.
A modern identification layer for fashion. A printed mark that gives a piece its passport — maker, story, a history that can be checked.
A catalogue for serious collections. Provenance, condition and edition kept with the same care as the objects themselves.
A weekly planner shaped around the gap between intention and reality. Plan less, notice more, reschedule without guilt.
06 — bespoke
based in london — working worldwide