What I can build for you

Because every system here runs on a company’s live sales, stock and financial data, and I don’t put client data or client code on the public internet.

The screenshots are the genuine interfaces with sample figures substituted. On a call I’ll screen-share and walk through whichever system is closest to your problem, and answer any question about how it works. That’s the same discretion your data would get.

Yes, and here’s how I keep that true. I take one or two outside projects at a time, never more.

Before we start you get a scope, a milestone schedule, and what each milestone delivers — working software you can open, not a status update. If a week slips you hear it from me that week, not at the deadline. If your timeline needs full-time attention, I’ll tell you at the first conversation instead of taking the work and disappointing you.

Agreed, and that’s where most of the effort goes.

The systems I build don’t let the model produce a figure on its own. The data is fetched first by fixed, pre-approved queries. The model writes the sentence around it. Then every number in that sentence is extracted and checked against the data that was actually fetched — and if a figure appears that wasn’t in the results, the whole answer is thrown away and replaced by one built directly from the data.

In the newer system the model has no ability to write a database query at all, so there is nothing to go wrong in that direction. There’s a documented accuracy suite that has to pass before anything ships.

Then it doesn’t. One of the reconciliation systems here runs its entire AI layer on self-hosted models on the company’s own hardware — the questions, the data and the answers never touch an external service. That’s a real production deployment, not a plan.

If your situation allows a hosted model I’ll use one, because it’s cheaper and better. If it doesn’t, this is a solved problem.

Often you shouldn’t, and I’ll say so.

Build when the tool can’t express your business rules — a category-netted shortage calculation, a tiered incentive matrix, a recovery threshold cross-referenced against sales — or when the people who need the answer won’t open a BI tool.

One of the systems here replaced a Power BI report for exactly that reason: the numbers were right, but nobody looked at them, and the report couldn’t show a store manager their margin without also showing them the cost price. A purpose-built app could.

You get the source code, the database schema, deployment instructions and a written handover. That’s standard, not an extra.

These run on ordinary, widely known technology on purpose, so any competent developer can pick them up. I offer a support retainer if you want one, but the code is written so you’re not forced into it.

It depends on scope, and anyone who quotes before understanding the problem is guessing.

What I can tell you is the shape: a focused dashboard or reconciliation tool on data you already have is a matter of weeks. A full system with company sign-in, imports, scheduled jobs and an AI layer is a matter of months. I quote fixed-price per milestone wherever the scope allows it, so you’re never exposed to an open-ended bill.

No. The work here includes a contract and lease system with automatic renewal and rent-escalation reminders, a referral portal that screens résumés automatically, a staff incentive engine computing tiered payouts across six role types, an operations portal covering seven external platforms, and a physical stock audit system that implements a written company policy clause by clause.

Dashboards are the visible part. Most of the value is in the rules underneath them.