Prompting Is Not the Skill. Knowing When It Is Wrong Is.
Most AI training teaches prompting, and most people work that out on their own inside a fortnight. What they do not develop by themselves is the instinct for a confident answer that is false — because nothing in the output signals it. That instinct is the difference between a team AI makes faster and a team AI makes wrong faster, and it is teachable in an afternoon using your own work.
No credit card required · 30-minute call · No obligation to sign up
Six habits that make a team worse, not faster
None of these is anybody being careless. Each is a reasonable instinct that happens to be wrong for this particular tool.
- Trusting fluencyIt reads well · that is not evidence
- Asking it to check itselfIt agrees with itself, confidently
- Accepting a numberThe one output never to take on trust
- Pasting in what should not goClient detail, in a hurry
- Using it where they are the expertThe one place it adds least
- Not using it where it would helpBecause nobody said it was allowed
The last two rows are the same mistake pointing in opposite directions. People reach for it on the work they know best, where they could have done better themselves, and avoid it on the tedious task where it would genuinely help — usually because nobody has said that is fine. Teaching where it belongs is worth more than teaching how to use it, and it takes less time.
Generic examples teach nothing. Use their actual documents.
A session run on invented scenarios teaches people how the tool behaves on invented scenarios. Running it on your own briefs, your own client emails, your own reports produces the useful moments — the point where somebody says "that is wrong and I only know because I wrote the original". Those moments are the entire curriculum, and they cannot be manufactured with generic material.
The most useful exercise we run is deliberately uncomfortable: give people output that contains a confident error and ask them to approve or reject it. Some approve it. That is the lesson, it lands harder than any warning, and it does more in ten minutes than an hour of explaining hallucination as a concept. Nobody forgets having personally waved through something wrong.
The second half is the boundary, and it is short. Where it helps: first drafts, summarising, restructuring, generating options, the tedious formatting job. Where it does not: anything where they are the expert, anything where being wrong is expensive and hard to detect, anything involving a number they will not verify. Four or five lines, specific to what your team actually does.
And we should say plainly that we are not a training company. This is a half day attached to work we are doing, because a build handed to people who do not know when to distrust it is a build that produces confident mistakes at speed. If you want a training programme, buy one from somebody whose main business it is.
- ✓Use their real documents — Generic examples teach behaviour on generic examples.
- ✓Let them approve something wrong — It lands harder than any warning about hallucination.
- ✓Teach where, not how — People work out prompting. They do not work out placement.
- ✓They avoid it where it helps — Usually because nobody said it was allowed.
- ✓We are not a training company — This attaches to a build. Buy a programme elsewhere.
Some of them approve the wrong answer. That is the lesson, and nobody forgets having personally waved something through.
What a session actually covers
Six things, in half a day, on your own material.
Spotting the Confident Error
Run on real output containing real mistakes, where people approve or reject. Some approve. It is the exercise everything else in the session rests on.
Where It Belongs, and Where Not
Four or five lines specific to your work. Drafts and summaries yes; anything where they are the expert or a number matters, no. Placement rather than technique.
Your Own Documents Throughout
Real briefs, real emails, real reports. The moment somebody says "that is wrong and I only know because I wrote it" cannot be produced with invented material.
What Not to Paste In
Practised rather than stated, using examples from your actual work. The rules themselves belong to the strategy piece; this is whether people can apply them under time pressure.
Enough Technique, No More
Half an hour on the handful of things that genuinely help, because people work the rest out. A full day on prompting is a day sold rather than a day needed.
Somewhere to Ask Afterwards
A route for the awkward case that comes up three weeks later, answered within a day. Without it people decide for themselves and the session wears off.
What clients say
Real clients, quoted in their own words — published with their permission.
“It was a pleasure working with Ghalib and his team.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Team Training
The method doesn’t change by market. What it’s pointed at does.
Audit The Hours
Where time actually goes, task by task, scored on volume, repetition and the cost of getting it wrong. Ends in a ranked blueprint with estimated hours saved — yours to keep either way.
Design The Guardrails
Before any building: what the agent may touch, where a human must approve, what happens when it is unsure, and which data is never allowed near a third-party model.
Build & Evaluate
One workflow at a time, in your accounts, scored against real examples from your business before it touches live work. Shipped early so it meets reality while it is still cheap to change.
Run & Improve
Monitored for cost, failures and quality drift. Models change, your business changes, and an automation nobody tends becomes a liability rather than an asset.
Honest, No-Nonsense Commitment
If the audit concludes that a task is not worth automating, we will tell you and refund the difference rather than build it anyway. And if a workflow we built does not hit the outcome we agreed in the blueprint, we keep working on it at no extra cost until it does or we take it out.
AI Automation pricing for Team Training, in GBP
Priced as a half day, and normally attached to a build rather than sold alone — a system handed to people who do not know when to distrust it produces confident mistakes faster than the manual process ever did. If you want a full training programme, buy one from somebody whose main business that is.
One Team
Half a day, on your own material.
- The confident-error exercise, on real output
- Where it belongs, in four or five lines
- A route for questions afterwards
With a Build
The usual one. Training on what we built.
- Everything in One Team
- Run on the actual system we delivered
- Handover documentation walked through
Several Teams
Different functions, different boundaries.
- Per-team material and placement rules
- A shared standard across the business
- Refresher after three months
Every plan is scoped around your market — start with a free first look and we’ll recommend what fits, priced in GBP.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- The audit is credited, not sunkPay for the audit, and the full amount comes off the build if you proceed. If you don’t, the blueprint is still yours to hand to anyone else.
- A fixed build price after the auditQuoted once we know what we are building. If it takes longer than we estimated, that is our risk — the price only moves if you change the scope.
- You own everythingAccounts, API keys, workflows, prompts, evaluation sets, logs and documentation — all in your name from day one, and still yours if we never work together again.
- Running costs are yours and visibleAPI usage is billed by the provider directly to you. We never resell tokens or mark up usage, and you see the real number.
- The retainer is month to month30 days’ notice, no exit fee. Stop it and your automations keep running — you are simply maintaining them yourself.
- Human approval is the defaultAnything customer-facing or irreversible needs a person until the evaluation data justifies otherwise, and that decision is yours to make, not ours.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
Team Training AI Automation questions, answered
Related AI Automation pages
Same service, different angle — by market, by service and by industry.
Want them faster, not wrong faster?
Free 30-minute call · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.