How it worksthe long version

A Praximedes is an operator built out of your own knowledge.

1. 01 · inYour knowledgewhat you decided, what went wrong, how you work
2. 02 · the operatorYour Praximedesreads it all, plans the work, does what it may
3. 03 · the gateYou decidemoney · sending · publishing · deleting
4. 04 · outYour workruns without you, until the next thing only you can decide

every decision goes back into the record · that is how it grows you

Using AI and having one are different jobs.

Prompting is piecework. You describe the task, you check the answer, you carry the context between one message and the next. Get better at it and you are still the one doing the carrying.

An operator is a different object. It holds the context, it works while you are not watching, and it stops at the points where stopping matters. The skill is no longer writing the prompt. It is deciding what may run unattended and what must wait for you, and being able to prove, afterwards, which was which.

That is the work this practice teaches, because it is the work that will still be yours when the prompting is worth nothing.

The work that will still be yours when the prompting is worth nothing.

It is not a folder of prompts with a nice name. Every piece of it either runs or it does not ship.

It stops at the points where stopping matters.

Every action your business takes, sorted into two piles. Reversible, which an agent does without asking. Irreversible, which waits for one named person to say yes at the moment it becomes irreversible: money, data, passwords and logins, anything public, anything deleted. This is the piece that makes speed safe, and almost nobody has it written down.

Not “we use AI”. Not a chatbot. Work that agents pick up, do and finish, where a person approves the plan once instead of approving every step, and where nothing irreversible happens without a named human.

It is not agents without gates. Speed with nothing holding it is how people get hurt, and it is the failure I am hired to prevent.

Speed with nothing holding it is how people get hurt.

I have run my own company this way for months. A team of named agents, one yes on the plan instead of a yes on every step, a board that updates itself, automatic checks that have caught genuinely expensive things, and a hard rule that agents stop before anything that cannot be undone. The proof is not a case study. It is that the operation exists and I can show it working.

It runs on your machine and your data stays yours.

The context belongs to the person who grew it, so it does not walk out the door with anyone.

Not a software licence. You own what is built.

One thing, three ways in.

Techne, the build log: watch it happen. Methodos, opening soon: take the route or the machinery and build it yourself. Praxis: have me in it, as ten guided sessions or the engagement. Every one of them ends in the same place: an operator of your own, running real work. What changes is how much of the build is yours, and how much of it I can hand over rather than perform.

Show me it is realTechne, the build log

Craft, shown in the making. The build log is free and stays free, because watching someone grow one does not hand it to you.

The build log · anyone who wants to see it happen

One person going from zero to an operator that runs real work, written down as it happens, with the failures in front of the wins.

You are not buying anything here. You are watching whether this is real before you decide it is for you.

I want to build it myselfMethodos, opening soon

The part that can be written down and handed over, so you can run it without me. That is what is being built now, in the open, and building it is what makes my hours unnecessary.

The route · you are building it, and you want the way through

Not a course. Real projects you build and ship yourself, with an operator that grows out of the work as you do it.

It is being shaped in the open, and it opens first to people who subscribe to Techne.

The machinery · you want the working system, not a blank page

The working system behind my operation, the gates, the rules and the routines, shaped to run inside your own work.

The difference from the route is the difference between being told where the road goes and being handed the map I drew while walking it.

Being handed the map I drew while walking it.

I want you in itPraxis

Doing. My hours, inside your build. It cannot be handed over, only performed, which is why there is not much of it and why it costs the most.

Ten guided sessions · you are building it and you are stuck

Ten hours, one at a time. Your build, your decisions, inside my experience.

For the point where you are already building and you hit something you cannot get past alone. You still own it. You just stop losing weeks to a thing I have already solved.

One hour, guided. We take your business and your questions and work them through against what I have actually done. It is a conversation with an agenda. You bring the problem; I bring the sequence it should be decided in. You can spend the ten on ten different problems or on one, and change your mind halfway.

• It is not implementation. I am not building the thing between sessions.
• It is not delivery. Nothing of yours ships because a session happened; you ship it.
• It is not a retainer. There is a fixed number of hours and it does not renew on its own.
• It is not a course in prompting. If a better prompt would fix it, you do not need me.

In a session we work your problem through together. Between sessions I am not building, reviewing, or on call. The ten hours are the whole of it, and the work stays yours.

Either of us can cancel a session. A cancelled session does not consume one of the ten.

The engagement · you do not want to build it. You want it built.

I build the operator inside your business and hand it to your people. Agents doing real work, a human gate at exactly the points that matter, and proof of what the agents did.

The end of the ladder, where none of the build is yours. You get the operation, and your people get taught to run it before I leave.

Your team runs real work through AI agents, with a human gate at exactly the points that matter, and you can prove what the agents did.

Five things, and each is a thing rather than a document.

A map of where it stops and asks

Every action your business takes, sorted into two piles. Reversible, which an agent does without asking. Irreversible, which waits for one named person to say yes at the moment it becomes irreversible: money, data, passwords and logins, anything public, anything deleted. This is the piece that makes speed safe, and almost nobody has it written down.

A board that updates itself

Work lives in one place, and its status is read from wherever your work really lives: your inbox, your spreadsheets, your project tool. Reaching a conclusion and recording it become the same action. Nobody updates a tracker by hand.

Agents with named jobs, and a clear way to give them work

Not one do-everything chatbot. Each agent has a named job and clear limits, works on its own piece without touching the rest, and hands back something you can check. Plus the rule that keeps it safe: work nobody planned cannot give itself permission to start.

Early warnings

Automatic checks that warn you before something quietly breaks, while it still costs nothing. A login that expired without telling anyone, a service you rely on that was switched off, a setting that no longer matches how things actually run. Each of these exists because it caught something real here.

Spending limits, a record of every action, and an off switch

A spending limit that really stops an agent when nobody is watching. Every action traced back to the decision that allowed it. One switch that stops everything.

The ninety days

What it is not

• Not a chatbot set-up, an AI tool rolled out to everyone, or prompt training.
• Not staff augmentation. I am not doing your work; I am building the thing that does it.
• Not a software licence. You own what is built.
• Not a pilot. Three months to something running for real, or it has not worked.

What I need from you

One decision-maker

Someone who can agree the rule for where it stops and asks. Without that, the engagement produces a document instead of an operation.

One real piece of work

Not a trial run. A map of where it stops is only useful against work that has consequences.

Access to where your work really lives

Your inbox, your spreadsheets, your project tool: wherever the real record is kept.

A three-month transformation engagement ends with a deck and a pilot. This ends with a running operation your people own, still running after the engagement closes.

Fifteen years in growth. Then I became the person I build for.

I spent them in mobile growth. A ten-country blueprint that returned 550% year on year, and five consecutive years over target.

Then AI arrived, and I was where I had always been: the most technical person in a room full of non-technical people. We are in the middle.

The most technical person in a room full of non-technical people. We are in the middle.

That is who I build for: people who run their own business or team, already use AI here and there, and have nothing of their own to show for it. You do not leave with a certificate. You leave with a dated record of the work you rebuilt, the points where it stops and asks you, and what now runs without you. That is evidence anyone can check.

This is not an application. It is a conversation.

Tell me what the work actually is, where it currently breaks, and what changed that made this the week you wrote. Three sentences beats three paragraphs.

I read every one of these myself. If it is not a fit I will say so plainly, and point you at whoever is better placed.