For owner-run firms that want AI to earn its keep.
I use AI to help other businesses optimise and grow.
Most AI help stops at the chat window. Better prompts, a wrapper around somebody else's service, a chatbot bolted onto your website. None of it changes how the work in your office actually gets done.
The gain is not in the chatting. It is in the jobs that quietly eat your week — the quoting, the chasing, the writing up, the same answer typed for the fortieth time. Hand those to a system that does them in minutes and the week comes back to you, which is the part that lets a firm take on more work without taking on more payroll.
The reason that stalls in a firm holding records that belong to someone else is simple: the obvious tools require the file to leave. So the growth and the confidentiality are the same problem, and I build for both rather than trading one against the other.
What decides whether your files stay yours sits underneath the chat window: the model, the machine it runs on, who is allowed to talk to it, and what it is allowed to see. That is the part I build.
What I will not tell you
The cheapest thing to check about anyone selling AI is what they refuse to do. Here is mine, in advance, so you can hold me to it later.
I will not tell you it is compliant. That determination belongs to your regulator, your insurer or your lawyer, and it is about your firm rather than my software. What I can tell you is where the data physically sits, who can reach it, and what is written down when they do — which is what those people are going to ask you anyway. Anyone using the word "compliant" about a system they built for you is describing a decision that was never theirs to make.
I will not tell you it does not make things up. It does. Every system I build starts from that assumption, so the design question is never whether it will be wrong. It is what it is permitted to do on the occasion that it is.
I will not tell you it replaces anybody. I will not put a number on your staff, because I do not know them and any figure I gave you would be a sales tactic wearing arithmetic.
I will not quote you a price before I have costed it. These systems have a real bill underneath them — hardware, electricity, or usage metered by the minute. A number given before that arithmetic is a guess, and a guess becomes the contract.
I will not tell you that you need this. Plenty of firms your size do not. If I look and the honest answer is that what you have is fine, that is the answer you will get, in writing, and you will owe me nothing for it.
What decides where a job runs
On my own setup, two things decide it: whether the machine in front of me can do the job at all, and what it costs if the answer comes back wrong.
The first is hardware. None of the models on that machine can look at an image, so anything with a picture in it doesn't start there — a limit, not a preference.
The second matters more. Local models are dependable at fetching and undependable at concluding: I tested three, and all three miscounted at least once. So the code does the arithmetic and the model only writes the sentence around it. Fetching work — reading files, sweeping logs, taking stock of what's running — stays on the machine. Judgement goes to the cloud, where being confidently wrong is expensive.
Twenty years of deciding where files actually sit
I did infrastructure for twenty years before any of this — infrastructure director and enterprise cloud architect, which means the machines, the networks and the unglamorous parts underneath other people's software.
NVIDIA-certified in AI infrastructure and operations. VMware VCP-Architect and vExpert.
That is the half almost nobody selling AI has, and it is the half that decides whether your files stay where you put them.
Four ways to do this. One of them does not involve me.
The only difference between them is how much of it I do. Prices are below rather than behind a phone call. You should be able to work out whether you can afford me without talking to me first.
Your machine, your account. I am not involved.
Free. The instructions are on this site — install the operating system, install the model, point it at your own files, and finish with something running on a machine you own. Nothing to sign up for, nothing owed, and I never see your files or your name. It is not a trial of anything. I write it because people who use it tell other people, and that is the entire return I am after.
I look at what you have, and tell you what to do about it.
$2,500, fixed. I look at what you actually have — the machines, the files, who touches what — and write you an answer: what could run on hardware you own, what should not, and what it would take. Yours to keep and act on, with me or without me. The conversation at the bottom of this page is free and stays free; this is the version where I come and look properly. If you want me on hand afterwards, you buy days rather than a monthly retainer, so there is never a month where you pay me for not needing me.
I come to your office and do it with you.
$3,500 a day. We set it up together, at your pace, and I will do the keystrokes if you would rather watch than type. This is the most expensive thing I sell and it should be — it is a whole day, not seven billable hours, and I cannot do anything else with it. That price is within about an hour of The Woodlands; further out, we work travel out before either of us picks a date.
I run it, and you use it over the web.
From $750 a month. Some firms are never going to buy a machine, and this is for them — I run it, keep your part of it walled off from every other client's, and you reach it from wherever you work. Training your staff is separate and charged by the hour, because how much of it anybody needs is not something I can guess in advance.
This is the one place on this page where the hardware is not yours, and I would rather say so than have you notice. It is not your machine. It is your space on mine, and I will tell you which machine, where it physically sits, and who can reach it. That is custody with an address on it — a real answer to the question your insurer is going to ask, and still not the same as owning the box. If owning the box is the point for you, it is one of the other three.
Those are the prices of my time and my hosting, and I know them. What your system costs is a different question, and I still will not answer that one before I have costed it.
You hire one person. Someone else always checks the work.
Whichever of those you pick, you deal with me, and I answer for all of it. I direct twenty AI specialists. They are agents rather than employees and I am not going to pretend otherwise. Each has one job and one thing it refuses to do, and nothing any of them produces reaches you unchecked.
What that buys you is not speed.
It is that the one who builds a thing is never the one who checks it, and the one who checks it is rewarded for finding it broken. The one who reviews the code cannot change the code. The one who tests logins tests them with the wrong password. The one who reads the numbers is not allowed to run the thing being measured.
Those are separate on purpose. The separation is the product. Your system gets built the same way.
Who this is not for
Saying this plainly is the only thing that makes the rest of the page believable.
Where this comes up
The same conversation, six different offices.
Five to fifty people. The owner makes the decision, and this is nobody's existing job.
Find out what AI could actually save you
Tell me what your firm does. That is enough to start.
I will tell you which parts of your week AI could take over, what that is worth in hours, and what could run on hardware you own instead. No charge for that, and nothing owed afterwards.
If the answer is that you are fine as you are, that is what you will hear.
Let's talk