aaron8.
  1. Home
  2. Custom software

Custom software, one senior pair of hands.

Internal tools, dashboards, APIs, integrations: the software your business needs that no product quite is. Before you take my word for anything, there is a complete platform build in a public repository you can compile, tests and infrastructure included. Few developers will show you that much before an interview.

Describe the tool you need See the finished thing Inspect the reference build

Live proof

This is the software you end up with.

A quotes-and-jobs tracker for a small operation, finished and running. Add a quote, move it along the stages, and watch the numbers at the top change. This is what a custom tool feels like when it fits the business instead of the other way around.

live demoA finished internal tool

This working build runs in your browser and needs scripts enabled. Everything on the page describes what it does; turn them on to use it.

Custom software is only worth it when it fits the way you actually work. The tracker above is the shape of what you get: your stages, your fields, your numbers, nobody else's subscription.

The work

Where custom earns its keep.

Internal tools

The job tracker, quoting screen or approvals flow your team fakes in spreadsheets today. Small, sharp and shaped to how you actually work, instead of a licence for a product you use a tenth of.

Dashboards and reporting

Numbers pulled from where they really live and shown so decisions get made: on-time rates, pipeline, exceptions. Derived from the record of what happened, so the dashboard cannot drift from the truth.

APIs and integrations

The connective tissue between your website, your CRM, your accounting and that one system nobody is allowed to replace. Built to fail loudly and recover cleanly, because integrations that fail silently cost the most.

The stack

.NET and C# or TypeScript and Node behind, React and Next.js in front, SQL written by hand where it matters, Azure or serverless underneath. Chosen per job, with reasons; the proof of fluency is public and compilable.

Proof, not promises

Compile it before you call.

Linehaul is a working platform slice I keep public precisely so a buyer can check the workmanship: a .NET 9 API with hand-written SQL, a typed React dashboard, Azure infrastructure as code, and a test suite that includes parsing every SQL statement with the database vendor's own parser.

52automated checks, all passing, all runnable by you
0compiler warnings tolerated, enforced in the build
2other tools live on the internet with public source
The build, explained The source

Fair questions

Before you ask.

How do I judge a developer before hiring them?
Ask for something you can check without trusting them: live software you can use, source code you can read, or a build you can run. My portfolio has all three. A developer who cannot show you any of those is asking you to buy on charm.
Agency or freelancer?
For most internal tools and integrations, one senior person who scopes and builds beats a chain of account manager, analyst and rotating developers, because nothing is lost in handovers. An agency makes sense when you need a whole team full-time, and I will tell you honestly if your job is that big.
What happens when you're not available?
Everything is built in your accounts, documented, and tested, so any competent developer can pick it up. I plan for my own absence on every job; software that only its author can run is a liability, not an asset.
Do you use AI to build?
Yes, the way a foreman uses a crew: written specifications, adversarial review, and independent checks before anything ships. It makes one senior person faster; it does not replace knowing what to build or noticing what is wrong. How, exactly, is public too.