Four ways to get an hour back.

Most common starting point

Automation & AI assistants

The unglamorous work that makes the biggest difference. If a person in your office is moving information from one place to another, that is a job for software.

Typically the smallest and fastest project on this page, and the one I recommend starting with. It is also the pattern behind most of the work I have done for larger companies. On how to tell which tasks qualify, see thoughts.

• Document generation: contracts, disclosures, quotes, and reports filled from records you already have
• Data that enters itself: pulling from county records, licensing databases, your CRM, or a supplier feed
• System-to-system plumbing: making the scheduler, the CRM, and the accounting package agree without a human retyping
• Drafting assistants: AI that writes the first version of a listing description, a follow-up email, or a summary, for a person to approve
• Reading messy input: turning PDFs, scans, and forwarded emails into structured data you can actually query

For teams and customers

Web applications

When several people need to see the same thing, or your customers need a way in, it belongs in a browser. Built to load fast on a phone in a parking lot, not just on the office desktop.

Hosted, monitored and kept patched on infrastructure I run, so there is no server for anyone on your team to look after.

• Internal dashboards: the numbers you currently rebuild in a spreadsheet every Monday
• Client portals: document delivery, status, and approvals, without another email thread
• Intake & booking: forms that validate properly and land directly in your systems
• Back-office tools: the small internal app that replaces a shared spreadsheet nobody trusts
• Accessible and mobile-first: because roughly half your visitors will be on a phone

For the field and the front desk

Mobile & desktop apps

Some work does not happen at a desk, and some data should never leave the building. Both are reasons to build something installed rather than something hosted.

Shipped as a properly signed installer or store listing, with the release and update process handled for you.

• Works offline: for job sites, canyons, and the stretch of I-17 with no bars
• Camera, GPS, and signatures: capture on site instead of writing it down and entering it twice
• Local-first by design: when the sensible architecture is one where your data never touches my servers, because there are none
• Windows and macOS: one codebase, both platforms, native installers
• Integrates with what is already installed: the CRM, the point of sale, the accounting package on the back-office machine

When something already exists

Fixing what you were handed

Not every project starts from nothing. Sometimes there is already an app, a site, or a spreadsheet doing far too much, and the person who built it is gone.

Starts with a short written assessment so you can decide with actual information. Inheriting other people’s code is most of what a decade of platform work teaches you.

• Inherited codebases: documented, stabilised, and made deployable again
• The spreadsheet that became load-bearing: turned into something that cannot be broken by a stray paste
• Sites that are slow or unusable on a phone: measured, fixed, and verified
• Honest triage: sometimes the recommendation is to keep it exactly as it is, and that is a valid outcome