Every question, answered before you ask it on a call.

Because teaching several people at once serves the confident and leaves everyone else where they started. When people learn together, the least fluent one stays quiet, never asks the question they actually have, and returns to their desk unchanged — while the pace is set by whoever spoke first. One to one removes that entirely: the whole session is spent on how that specific person works, at the speed they actually learn, on their own live files, tickets and documents. Nobody is asked to demonstrate what they do not yet know in front of a manager or a colleague. It is slower to deliver, and it is the only version that changes what happens on Monday morning.

It becomes twenty programmes rather than one event. First, a scoping conversation with the sponsor establishes what the organisation needs to be true in ninety days — which functions, which tools, which policies, and what counts as proficient. Then every named individual gets their own intake: what they actually do all day, which parts of it repeat, what they have already tried, and where their confidence stops. Each roadmap is built from that person’s own intake, so the accountant and the recruiter never sit through each other’s material. Delivery is one to one throughout, and the sponsor is reported to at the level of the organisation rather than the individual.

It runs as a sequence across the calendar rather than one date in the diary. Intakes are done first and move quickly, because they are short; sessions are then booked directly with each person around their own working week, in spaced blocks rather than one long day. A rollout across a whole department is measured in weeks, and the full schedule — who is booked when, in what order, which functions go first — is written down and agreed before the first session happens. Delivery capacity is capped deliberately, so the dates you are given survive contact with a bad week. If everyone has to be finished by a fixed date, say so at scoping: it changes the ordering, and occasionally it changes the answer.

Both are ordinary, and one to one is the format that handles them. Embarrassment tends to resolve in the first session, because there is nobody to be embarrassed in front of — the questions people will not ask in company get asked in the first ten minutes and answered without commentary. Resistance is treated as information rather than an attitude problem: it is often an accurate read that the tool being pushed does not fit the work, and the intake will say so in writing. Where someone simply does not want to take part, the sponsor is told that an allocated place is unused and why the pattern matters, without a name attached. At no point is anyone asked to demonstrate what they do not know in front of a manager or a colleague.

A Workflow Automation Sprint is ten working days, and an AI Agent Build is ten to fifteen. That clock starts from Access-Complete — the point at which credentials, a named client-side owner, test data and a signed definition of done are all in hand — not from the day you sign. Most of the delay in projects like this is waiting on access, which is the one part I do not control, so I do not price or promise around it.

Because a free audit is worth what it costs. The diagnostic is a paid, fixed-fee engagement that takes five business days and produces an 8–12 page written document: a process map, three to five ranked automation candidates, hours-saved estimates with the assumptions stated, a recommended stack and a 90-day sequence. It is credited in full against any build commissioned within thirty days, so if you go ahead it costs you nothing. If you do not, you keep a document you can hand to any engineer.

Twenty minutes of qualification, not consulting. I ask which process, how many hours a week it consumes and across how many people, what you have already tried, who else signs off on spend, and what you would do with the recovered time. If it is not a fit I will tell you on the call rather than sending a proposal. If it is, the next step is the diagnostic.

Yes — most engagements are with teams in the United States, the United Kingdom, Europe, the UAE, Singapore and Australia, delivered remotely with overlap into your working hours. International engagements are invoiced in US dollars and Indian engagements in rupees; each is quoted against its own market rather than converted from the other.

Yes, and it happens. Plenty of "AI problems" are actually a missing integration, an unenforced process, or a report nobody reads. The diagnostic ranks candidates by return and explicitly states which of them are not worth automating yet and why. Being told to fix something cheaply, or to do nothing, is a legitimate and common outcome — it is considerably cheaper than a build that solves the wrong problem.

The strongest fits are recruitment and staffing, B2B professional services — accounting, legal operations, insurance broking — and D2C and e-commerce operations, because all of them run on high-volume, rule-bearing back-office work: candidate pipelines, reconciliations, document review, order and inventory flows. But qualification is about the process, not the sector. If the work can be described in one sentence and counted in hours per week, it can be scoped — and if your industry is not on that list, the twenty-minute fit call is where we find out whether that matters. Individual professionals from any field can engage directly for one-to-one enablement.

Over video, one person and one instructor, scheduled directly with that person around their own working week in spaced blocks rather than one long day. Sessions are worked on the individual’s own live files, tickets and documents — not exercises — because the point is that Monday morning looks different, not that a course was completed. Delivery is remote by default, with calls scheduled to overlap US, European and Middle East working hours from India; on-site delivery is available by arrangement and quoted with travel. What is said in a session stays in it: sponsors receive aggregate progress, never a transcript.

You can buy it directly. A support professional who wants to close three times as many tickets without dropping quality, an accountant working through reconciliations, a lawyer summarising discovery, a recruiter writing outreach that does not read as machine-written — each of those is a legitimate engagement on its own terms, with no employer involved. The intake is identical to the enterprise version: your real work, your real files, a roadmap built for how you actually operate. Scope, format and timing are agreed in writing before anything begins, and the sessions are yours alone. Nothing you did not know at the start is reported to anyone, because there is nobody in the arrangement to report it to.

Progress at the level of the organisation, never a transcript of anyone’s session. The sponsor receives the agreed objectives, roadmap coverage across the people named in the engagement, completion against the written schedule, the themes that recurred — the tool nobody knew existed, the policy everyone was quietly working around — and the automation candidates the intakes surfaced. What the sponsor does not receive is who asked which basic question, who needed a second session, or who was slowest to start. That boundary is stated to everyone before their intake, because confidentiality is what makes an intake honest, and honest intakes are the only ones worth building a roadmap from.

The intakes are an unusually accurate automation diagnostic, and they feed straight into it. Sitting with people individually and watching them work surfaces the same task done a dozen different ways, the export nobody automated, and the three steps every one of them repeats by hand every morning — which is precisely the input a Workflow Automation Sprint or an AI Agent Build needs. Where something turns out to be worth building rather than teaching, it is written up as a ranked candidate with an hours-saved estimate and the assumptions stated, so you can challenge it. The two are quoted separately and neither is a condition of the other. Teaching a person to do a task faster is the wrong answer when the task should never have reached them.

Model and third-party SaaS costs are billed to your own accounts and are never resold through me — I do not want to carry token-price risk on your behalf and you should not pay a margin on it. Every AI build ships with a cost-per-conversation or cost-per-run projection so the monthly number is known before launch rather than discovered afterwards. Ongoing support is optional, quoted monthly against the tier you choose, and never bundled into the build price.

It is quoted per engagement rather than published, because the same brief can differ by a factor of three depending on your systems. Six things decide it: how many systems it touches, whether those systems have a usable API, how clean the data is, how much of the process is already written down, the corpus size and channel for an agent, and whether the output is customer-facing or internal. You get a fixed written price after a twenty-minute call, usually within twenty-four hours of it, and that price does not move afterwards — two revision rounds are included and anything outside the written scope caps is agreed before it happens.

Because a published number would have to be padded to cover the worst case, which means straightforward projects subsidise difficult ones. The alternative — advertising a low number and discovering the gap in week two — is how fixed-price projects turn into arguments. Instead the entire commercial structure is published: what drives the number, what is included at no extra charge, the payment milestones, the change-order rule, and the tax treatment. Only the amount waits for a short conversation about your actual situation.

Every enquiry gets a reply within one business day, from the person who would do the work rather than an automated sequence. After a twenty-minute fit call, a written fixed-price proposal typically follows within twenty-four hours, containing the scope caps, deliverables, timeline and payment schedule. There is no multi-week procurement dance, because there is no sales team to route it through.

That is the expected end state, and the build is structured for it. Everything is in version control with a runbook, prompts are versioned files rather than text pasted into a web interface, and the handover session is recorded. Your engineer can pick it up by reading the repository. There is no proprietary layer of mine in the middle that has to be replaced first.

Numeric caps written into the statement of work before you pay — how many processes, how many integrations, how many revision rounds, how many documents. Two revision rounds are included. Anything beyond the caps is a change order, quoted and agreed in writing before any work happens, at the rate stated in your statement of work. The fixed price does not move because the scope does not move quietly.

It is a fair question and the honest answer shapes how everything is built. Because the work lives in your infrastructure, in your version control, with a runbook and an evaluation suite, any competent engineer can take over without me — that is the point of building it this way rather than faster and looser. Delivery capacity is deliberately capped so schedules are not built on optimism, and for larger engagements I will name trusted subcontractors in advance rather than after a problem.

The centre of the practice is B2B services and B2B SaaS companies of roughly 10 to 200 people, with a named decision-maker and a manual operations bottleneck — large enough that a process eats real hours every week, small enough that one accountable engineer beats a vendor team. Individual professionals engage directly at one end, and larger organisations commission scoped rollouts one department at a time at the other. Where it is genuinely not a fit: pre-revenue startups looking for a technical co-founder, and open-ended "what can AI do for us" exploration with no process, no owner and no number attached.