Programmes and workshops — Aifluencypath

Half-day

Fluency Clinic

The clinic is for teams that already have licences and have tried a few tools, yet still treat them as a novelty. People paste a sentence, accept the first reply, and then spend as long cleaning it up as they would have spent writing it. We use four concentrated hours to replace that habit with a short, repeatable sequence: state the task, add context and constraints, generate, then check the result against source material before anything leaves the room.

We open with a brief task audit so the group is working on real items, not invented examples. Typical clinic work includes drafting a customer reply from a ticket, rewriting a policy paragraph in plainer English, summarising a meeting note, or pulling a first cut of a table from a messy export. Facilitators work in a pair: one leads the room, the other unblocks people at their own screens. Nobody sits through two hours of slides. Each concept is followed by supervised practice on a file the participant brought that day.

We also cover the parts that usually get skipped. Participants practise spotting fabricated citations, invented numbers and quotations that sound plausible. We walk through what should never be pasted into a general tool, using your existing confidentiality rules rather than a generic poster. By the end of the afternoon the group has a small set of working instructions, a nine-point review checklist, and a shared language for when the model is confidently wrong. The clinic does not replace a longer programme; it gives a team enough structure to decide whether a cohort or sprint is worth the time.

Core programme

Six-Week Cohort

The six-week cohort is the programme we run most often. Eight to fourteen people from the same organisation meet for two live hours each week and practise between sessions on one recurring task they have named in week one. We keep the group small so that every person can be watched while they work, and so that the written routine at the end actually belongs to that team rather than to a generic playbook.

Week themes follow the work, not a vendor feature list. We start with a task audit and sort the group’s recurring jobs into three piles: safe to hand over with review, worth assisting but not delegating, and not suitable for AI at all. We then move through drafting and rewriting; working with your own documents rather than the open web; structured data and tables; building a repeatable routine; and finally review, documentation and handover. Participants keep the same live task across the six weeks, so the improvement is visible in a file they already own. Between sessions we set short practice, not homework theatre: one output, checked, brought back.

By week six the group has usually shortened or structured that recurring task, written the steps down, and agreed who reviews what. The handover pack includes an adapted prompt library tied to their document types, an output review checklist, the team’s written routine, and a short list of work we recommend they do not automate. A thirty-day follow-up session is part of the format, so we can see whether the routine is still in use and patch the bits that drifted. We deliver on-site in Singapore or online for regional teams; recordings are by agreement with the sponsor, never as a substitute for live practice.

Two weeks, one team

Embedded Sprint

An embedded sprint is for a single function that already knows which outputs eat the week: monthly commentary, bid drafts, escalation notes, variance narratives, handbook answers. For two weeks we sit with that team. On-site days are spent mapping the recurring work, rebuilding three to five of those outputs with AI assistance, and writing the steps while people are still at their desks. Between those days we offer async support so drafts do not stall overnight.

We begin with the same three-pile sort we use in the cohort, because the most useful result of a sprint is often a clear list of work that should stay human. The rebuild itself is practical. If the team writes monthly commentary from spreadsheet exports, we design the extract, the instruction, the check against the numbers, and the sign-off. If they answer customers, we tie instructions to their macro categories and put tone and escalation rules in writing. Facilitators still work in a pair so that no one is left staring at a half-finished prompt while the rest of the room moves on.

The deliverable is a documented workflow pack: the mapped outputs, the adapted instructions, the review steps, and the list of tasks we recommend leaving alone. We do not build software, and we do not leave you with a tool you did not already licence. The pack is written so a new joiner can follow it, and so the sponsor can see exactly what changed. Sprints suit groups of about five to ten in one function. Larger mixed groups belong in a clinic or a cohort, where the teaching load is shared across roles rather than concentrated on one production line.

Ninety minutes

Leadership Briefing

Managers are often asked to approve tools, budgets and usage rules before anyone in the organisation has a shared picture of what the tools actually do. The briefing is a ninety-minute working session for that group, up to twenty-five people. We do not demonstrate every product on the market. We walk through what current general assistants, document-grounded search, spreadsheet helpers and meeting tools genuinely handle well, and where quality risk sits when the output looks finished.

The middle of the session is policy, in plain language. We look at how to set an internal usage note in an afternoon: what may be pasted, what must stay in a private environment, who reviews outbound work, and how a pilot should be judged. We treat a pilot as a test of a named task with a named review step, not as a mood. Sponsors leave knowing which questions to ask a vendor and which questions only their own team can answer, because only they know the documents and the duty of care.

The briefing is often paired with a Fluency Clinic for the people who will actually sit at the keyboard. That pairing keeps the policy conversation honest: leaders hear what the tools can do, and the working group immediately tests those claims on live files. We can run the briefing on-site or online. It is not a substitute for practice, and we will say so in the room. If you need people to change how they draft, check and file work, you will still want a clinic, a cohort or a sprint after the decision is made.

Tooling we teach with

We are tool-agnostic. We teach with whatever your organisation already licences: a general assistant, document-grounded search, spreadsheet helpers, meeting notes, the suite your IT team has already approved. The skill we care about is the same across products. Your people need to state a task with context and constraints, ground the answer in a source they trust, and write a review step that still happens after we leave.

We do not sell licences, we do not resell seats, and we do not take referral arrangements from vendors. If a tool is a poor fit for a given task, we say so, even when that tool is already on your desktop. If a task should not go near a general model at all, it goes on the do-not-automate list. That independence is part of the method: the programme is organised around your work, not around a partner’s feature release.

When a team uses more than one tool, we still keep a single routine. People should not have to remember a different ritual for each window. The written handover names the tools you actually use, shows a worked example on your own file types, and records the checks that apply no matter which product produced the draft. If your licences change later, the routine still holds because it is built around the task, the source and the review, not around a brand name.

Pricing approach

We quote per programme after a short scoping call. Price depends on group size, number of live sessions, whether we are on-site in Singapore or online, and how much documentation you want written into the handover. A clinic is a single afternoon. A cohort runs six weeks plus a follow-up. A sprint occupies two weeks of calendar time with on-site days inside it. A briefing is ninety minutes and is often booked with a clinic in the same week.

There is no per-seat licence resale in our invoices, because we are not selling you software. If you want us to write a fuller internal guide than the standard pack, we price that writing as part of the engagement rather than as an add-on catalogue. Travel within Singapore is included in on-site delivery; regional online delivery is priced on the same session rates. We send a written proposal with format, dates and price before anything is booked, and we do not start work without a named sponsor and a list of representative tasks.

Outcomes depend on your team’s context. The examples on this site describe our delivery format: cohort size, hours, number of workflows documented. They are not guaranteed results. If you write to us, tell us the function, the approximate group size, what you currently use, and what is blocking people. We reply within one working day, Monday to Friday, and we will say plainly which format fits before we talk numbers.

Ask for a quote See case blocks