Six decisions, and what each one cost me.

Every business I’ve worked inside had two versions of its process: the one in the handbook and the one that actually happens. The second one is the real one, and it’s usually held together by five or six things that don’t talk to each other. A scheduling spreadsheet. A shared inbox. A paper form somebody scans. A whiteboard. And one person keeping the rest of it in their head. None of that is bad management. Every one of those was a sensible decision at the time.

So the first part of this isn’t building anything. I come and watch the work, and ask a lot of dull questions. What gets typed twice? What does everybody quietly work around? Where does the week actually go? The answers are usually where the real system is.

How long that takes depends entirely on how big the operation is, and it isn’t something I’ll guess at down the phone. After the first visit I’ll tell you how long the watching runs, how long the build runs, and what the whole thing costs, as one fixed price.

Distance isn’t a filter. I’ll travel anywhere for this — Hillsboro is where I live, not the edge of the map. If you’re reading this from the other side of the state, or the other side of the country, you are still a customer.

What I write down is yours either way. If we do this part and you decide not to build anything — or to build it with somebody else — you keep it. It’s a description of how your own business actually works, and I was never selling you that.

Then I build one system for what I found, shaped to your trade rather than a software company’s idea of your trade. Your words on the screens. Your steps, in your order. Taking on a new customer, the schedule, the records, getting the invoices ready, and the numbers you keep having to ask somebody for. One place instead of five.

AI does the parts that are pure drudgery. The word gets used to mean anything, so here is exactly which parts:

One sign-in, one search, one straight answer, instead of four people checking four systems and hoping they agree. And when it’s live, I’m the one who keeps it running.

I’ve done this once, all the way through, and it has run the whole operation since 2023 — Pelican, the healthcare operations platform on the work page. That’s the whole track record: one, done properly, still running. I had an advantage there, and I’d rather say it than have you spot it: I worked inside that company, so nobody had to explain the day to me. For a client, that’s what the watching is for.

Pelican is also where I learned how careful the AI half has to be. It reads a referral document into the intake form. It drafts a care protocol from a plain description, for a nurse to correct. It turns “who deleted clients last week” into a filter an administrator can apply. It explains in ordinary words why somebody can or cannot do a thing, and shows what a proposed change to their access would reach before anybody makes it. And it takes dictation, so staff aren’t typing.

Not one of those acts on its own. It never runs the query — it hands the administrator a filter. It never changes anybody’s permissions — it shows what would change if you did. It writes the draft and a person signs it. In healthcare that restraint is the whole feature: anything clever enough to edit the record quietly is a liability, not a saving.

If you want to hear it from them rather than from me, ask on the call and I’ll arrange it — they’ll act as a reference on request. There’s no testimonial printed here, because I’m not going to write one on their behalf and put quote marks round it.

There isn’t a size of operation I’d turn away, and the one I run now is a whole company’s working day. What I do have is a queue rather than a ceiling: I’m one person, so I take one of these at a time, and what I can’t do is two at once. Ask me on the call where the queue is, and I’ll tell you before you book rather than in a month.

Every company I’ve worked in has at least one system that only works because one particular person knows how to make it work. When that person is on holiday, so is the system.

I’ve been that person. It’s a bad position for a company and a worse one for the person in it. You can’t take a week off without your phone, and every question comes to you because there’s nowhere else for it to go. I’m not willing to be that person for you, and I’m not willing to hand you software that needs one.

Building the thing is half the job. The other half is making sure the people using it understand it. Three things come with anything I build, and none of them are extras.

There’s a compliance reason too, and it’s the one that saves money. An inspector doesn’t only want the system to be right. They want the written procedure, and evidence that your staff were trained on it. If that already exists, that part of an inspection stops being a project and becomes a filing question.

And the honest test of whether I did this part properly is whether you could replace me. I’d rather you never wanted to. You should always be able to.

So who owns it? You do — the code, the data, the documentation, all of it, outright. You can hand the lot to another developer tomorrow and you don’t need my permission or my blessing to do it. It isn’t a licence and there’s nothing to renew.

That answer is for the bespoke operational software described here. The defined website package has its own source-export and monthly hosting terms, published before you book a call.

And if I’m ever not available, what stands behind you is people rather than paperwork. There are people I’d hand this to, and they’re people I know rather than a name in an escrow clause. The written version is what turns that handover into a week instead of a rebuild, which is the real reason I’m strict about keeping it current.