I build web applications, SaaS platforms, business systems and digital solutions that turn real requirements into usable products.
A selection of platforms and products I have designed and developed — each one solving a specific operational problem.
A property management platform that replaces spreadsheet-based rental workflows with one centralized system for units, tenants, contracts and payments.
An attendance and workforce platform covering kiosk check-in, schedules, leave and payroll-ready reporting, with an append-only audit trail throughout.
An online tutoring platform with real-time video classrooms, server-side recording, lesson booking, assignments and the administration around them.
A self-hosted file platform giving teams shared drives, versioning, expiring share links and granular permissions — with every action recorded.
A collaborative event camera platform: guests scan a QR code, shoot from their own phone, and every photo arrives in a shared, moderated gallery.
A self-hosted audio platform: upload a library, have it organised automatically from its own metadata, and play it anywhere through a web player.
Concepts, internal tools and client work that round out the picture.
Complete projects, not just the parts that are fun to build. The same sequence applies whether the result is a SaaS platform or an internal tool.
Work through the business problem and the real requirements before any code exists — including the workflows people already use and the ones they only think they use.
Plan the user experience and the system workflow together, so the data model and the interface are decided against the same set of constraints.
Develop the application and its core functionality in working increments, keeping something usable in front of you rather than saving it all for the end.
Exercise the workflows, integrations and edge cases — particularly the ones involving money, dates and permissions, where quiet errors are expensive.
Deploy, then iterate. Systems earn their value over time, so the work continues into maintenance, optimisation and extension.
Chosen per project rather than by habit — everything listed here is in active use in the systems shown on this site.
Interfaces people actually work in, all day.
The application logic and the APIs behind it.
Schemas designed to keep records correct over years.
Deploying and operating what gets built.
The harder parts: live video, audio and streams.
How the work gets done and kept maintainable.
My work connects business requirements to usable technology — the part where a described process becomes something people can actually operate.
That means the whole path, not one slice of it: understanding how a business really works, designing the data model and the interface against the same constraints, building it, and then deploying and maintaining it on real infrastructure. Most of the systems on this site I took from an empty repository to something running on a server.
The range is deliberate. Property management, workforce attendance, live video tutoring, file platforms, media applications and legacy modernization each demand something different, and the constraints of one regularly turn out to be the answer in another.
Let's turn it into a working digital solution — from the first conversation about the problem through to something running in production.