Most of what is written about getting training signed off was written for a multi-week course, and it gives the same advice every time: tie it to a priority your manager already owns, name a concrete deliverable, agree a date to report back. The advice is right. It is also where the generic version stops, because a course that teaches a subject cannot tell you what your deliverable is going to be.
A build day can. The Oxford Agentic Bootcamp runs against one real task you bring from your own work, and you leave with a working agentic pipeline running against it. The three things the request needs - the task, the deliverable and the date - are not things you have to invent for the email. They are the format.
What is actually being decided
Rarely the fee on its own. Someone signing this off is deciding three things at once: whether a day out of your diary is worth it this month, whether anything comes back that they can see, and whether saying yes makes work for them afterwards. The fee is usually the smallest of the three and the easiest to attach, because pricing sits on each event booking page.
Write to those three and the request gets shorter, not longer.
Name the task, not the subject
“I would like to go on an AI course” is a request about a subject. “I would like to spend Thursday turning the weekly report into something that runs itself” is a request about a task, and it is the version that survives being forwarded.
The task is the one part nobody can supply for you. The published condition is that it has to be real: one task from your own work that currently costs you meaningful time, because the whole day runs against it. The programme’s own “Who is it not for?” answer is blunt about the alternative - without a real task you get a demonstration instead of an outcome. In Cohort 1 the tasks that surfaced in the room were lead generation, internal reporting and marketing content, one each, brought from sixteen people’s own work. Choosing yours is worth ten minutes before you write anything, because the rest of the request rests on it.
Promise the thing running, and no more than that
What you can honestly say you will come back with is published rather than implied:
- The workflow itself, built and running against the task you named.
- The pattern behind it - a step that gathers, a step that produces, a step that checks - which is what lets you build the second one without help.
- A clear sense of where the human judgement stays and where the grunt work goes.
Then offer to demonstrate it rather than write it up. “I will show you the thing running in the week after” is a promise that can be kept or visibly not kept, which is the kind that is easy to agree to.
What not to promise is a number. The temptation is to put a figure on the hours it saves, because that is the sentence that looks most like a business case. You will not have measured it yet, and effort moved around is not the same as time saved. Promise the artefact, measure afterwards, and bring the number to the next conversation once it is actually yours.
Nor should the request promise more than a day produces. One day produces one workflow on one task. What scales is the pattern, and saying that plainly is more convincing than the version that overreaches.
The four questions that come back
“Can you not watch something online instead?” The day is deliberately not recorded, which is an answer rather than a dodge: watching someone build is not building, and the friction that stops people is rarely the concept. It is the first stuck moment at their own desk with nobody there to unstick them. Why that is harder online is a separate argument, and already written.
“Is this a pitch for some tool?” No tool is being sold. The published “not for” list says so directly: anyone expecting a vendor or platform pitch should not come, and part of the day goes on where these workflows break and what you constrain so a bad run cannot do damage.
“What if the date stops working?” Places are not refundable, but a place transfers to a future cohort at no charge. A diary clash is not a lost fee, which is usually the risk inside the question.
“Can we pay properly rather than on a card?” An organisation can pay by invoice - email hello@oxfordagentic.com and it is arranged. That matters more than it sounds, because a request that needs a personal card and an expense claim is a request with a second approval hidden in it.
If you are the one who signs it off
Then the question is not approval but who goes, and the seat belongs to whoever owns the task rather than to the most senior person who would like a day in Oxford. If two of you go, bring the same task, so the same workflow goes back to work with both of you. And if it turns out several people want the day, whether to send them to a cohort or bring a day in-house is the question to settle first.
The short version
Four sentences, in this order: the task, the deliverable, the date, and the offer to demonstrate it. If the request runs longer than that, something in it is about the subject rather than about the task.
The next cohort is on Thursday 19 November at Worcester College, 09:00 to 17:00, and its booking page carries the figure to attach.