Custom Software That Fits Your Business

There is a category of work that no off-the-shelf product handles well: the thing your office does that is specific to you. The dispatch board on a whiteboard. The intake form that is really three forms and a phone call. The tracking spreadsheet that only one person understands. For years the answer was to live with it, because custom software cost more than the problem.

That is no longer true. With AI-assisted development, one experienced engineer can build and ship a focused business application in weeks, with real testing and a deployment pipeline, for a fraction of what it cost even three years ago. This is the third of three things I do, and it is the one that replaces the workaround for good.

What I Have Built

For a regional clinical laboratory, I built a real-time dispatch app that replaced phone-tree and radio dispatch for about thirty field staff across two cities. Urgent requests arrive from a shared mailbox, push to every phone, and are read aloud even on a silenced device. One tap claims the job, and every status change is broadcast live to the office. Time-to-claim went from unknowable to a number on a dashboard. It passed Apple's app review and is installed through the company's device management.

For the same lab, I built a temperature-monitoring appliance that reads a few dozen sensors across refrigerators, freezers, and transport coolers, alerts on excursions and power loss, and generates the regulated records on demand. It replaced paper logs. The inspector approved it on site. Read the full case study.

Both were built by one person, with AI-assisted development, in months, including automated tests and a release pipeline that cannot ship untested code.

What It Looks Like for You

The pattern is the same whether you run a brokerage, a clinic, a contractor's office, or a logistics yard. Something arrives, someone has to claim it, its status changes, and someone else needs to see that. Or a record has to exist for an inspector, and today it exists on paper.

• Dispatch and job boards: requests in, claim, status, done, with a live view for the office
• Intake and request forms that go straight into a tracked queue instead of an inbox
• Compliance and inspection records generated by the system, not written up afterward
• Dashboards built from data you already have but cannot see
• Mobile apps for field staff, installed through the device management you already use
• Integrations with Microsoft 365, Google Workspace, and the tools you already pay for

How I Build

I do not start with code. I start by mapping the process with the people who run it, because the map is the specification. Then I build the smallest tool that removes the paper, put it in front of two or three users, and change it based on what they do rather than what they said they would do.

• Boring, proven technology: PostgreSQL, TypeScript, Docker. Nothing you will struggle to find support for later
• Sign-in with the Microsoft or Google accounts your staff already have
• Automated tests and a release process with a health check and automatic rollback
• Hosted where you choose, with backups that are proven by restoring them
• Documentation and an operator guide, so your team is not dependent on me
• You own the code

How This Usually Starts

With a fixed-price discovery sprint. Two weeks, ending in a clickable prototype and a firm quote for the real thing. If the prototype does not convince you, you have spent very little finding that out.