AI Consultancy
In development. Taking enquiries.
- ·The output is a written verdict: what to build, what to buy, what to leave alone, and the assumption that would change the answer.
- ·It is worth buying when a decision is expensive and reversing it is worse, not as a retainer that keeps opinions flowing.
| Becomes live when | One advisory artifact is published in an anonymised form, so a stranger can read the reasoning without reading the client. |
| Delivered by | · · ai-engineer · |
| Skills used | deep-research · spec-it |
What this involves
The output is a written verdict: what to build, what to buy, what to leave alone, and the assumption that would change the answer. The last part is the one that makes it useful a year later, because a recommendation with its assumptions attached can be re-checked when the assumptions move, and one without them can only be re-bought.
It is worth commissioning when a decision is expensive and reversing it is worse. It is not worth commissioning as a retainer that keeps opinions flowing, and a consultant who tells you otherwise is describing their own cash flow rather than your problem.
No advisory artifact is published yet, so there is nothing on this page to check. The nearest thing that can be opened is the reasoning published elsewhere on this site: the audit findings, the post-mortem on retiring a large piece of this project's own code, and the PROBLEMS panel that lists what is still broken.
How the work runs
1. Discovery
We agree what the project has to achieve, what it must not break, and how we will both know it worked, before any code is written.
2. Build
The work is built with an AI agent as the working partner and a human reviewing every change before it lands. You get commits you can read rather than a status update.
3. Review
You review running software at each milestone, not a screenshot of it, and the next milestone absorbs what you send back.
4. Launch
We deploy to production with checks in the pipeline and alerting that reaches a human, and you hold the repository and the infrastructure accounts.
Questions people actually ask
What does an engagement produce?
A written verdict on a specific decision, with the option that was rejected and why, and the assumption that would flip it. Not a maturity score, not a roadmap deck, and not a list of tools. A document whose recommendations cannot be argued with was not worth writing down.
Will the advice tell me not to build something?
Frequently, and that is the most valuable outcome available. The measurable cost of an AI project that should not have started is the whole budget; the cost of finding out early is a few days of somebody's attention.
Why is there nothing to read here yet?
Because advisory work is confidential by default, and publishing an anonymised version takes a client's agreement that has not been asked for yet. The page says so rather than filling the gap with a fabricated case study, which is the standard the rest of this site is held to.