Report and data pulls
Scheduled services that sign in to a web system, run the exports people download by hand, and file them, with retries, run history and a small dashboard.
I build internal tools, client portals, booking systems, dashboards and automation around how your organization already works. You own the code, and it runs where you control the data. Four of my projects are public on GitHub, each with a live demo below.
Why “Daemon”? In computing, a daemon is a program that runs quietly in the background and keeps things working. That’s the job.
A minimal CSS library for calm, readable interfaces. One stylesheet with design tokens, a real dark mode and accessible components. Every page of this site is built with it.
Press Tab to see the focus states.
Desk booking for hybrid teams. Staff book a desk on an interactive floor map; admins manage locations, layouts, people and booking rules.
Pick a free desk to book it. Striped desks are taken.
A self-hosted IT service desk for teams that want proper service management without the enterprise price tag. One application, no queue workers, no build step to deploy.
SLA clocks are live. Resolve a ticket before it breaches.
Uptime monitoring and public status pages you host yourself, so your team keeps full control of the infrastructure that reports on your infrastructure.
Reports someone downloads by hand every morning, forms re-keyed from one system into another, old scripts nobody dares touch: that work can run on its own. I use Claude Code to build the automation quickly without cutting corners: work out how a system behaves, prototype against it the same day, then harden the prototype into something people can rely on.
Sample data only: made-up jobs and numbers, not a real system. It shows the kind of dashboard I build: scheduled runs, retries, a re-login when a session expires, and a live log.
Scheduled services that sign in to a web system, run the exports people download by hand, and file them, with retries, run history and a small dashboard.
Scripts that fill in the forms people re-key every day, with a log of every change.
Old background jobs nobody can maintain, documented from what’s running and rebuilt as small, supported services.
The same approach goes into client work: plain, durable technology, careful interfaces, and code you own outright. Tell me what's slowing your team down.
Requests, approvals, case tracking and scheduling, shaped around your process.
A secure place for customers or members to submit, track and download.
Your numbers in one place, updated automatically and exportable.
Rooms, people, vehicles or equipment, with your rules built in.
Connect the tools you already pay for, and script the downloads, uploads and re-keying people do by hand.
Replace paper and PDF forms with ones that check themselves and route to the right person.
For a new app
Discovery, a written spec and one agreed price for the first release. Later phases are quoted the same way, so the budget doesn't drift.
For apps already running
A monthly plan covering fixes, security updates, small features and questions, with a set response time.
For inherited or ageing apps
An audit first, then a plan to stabilise, secure and document what you have, whoever built it.