THOUGHTFOXRECEIPT 000 · YOUR TEAM’S HOURS
- Hours back, after checking
- to agree
- Time went to
- to agree
- Decided by
- to agree
- Date
- to agree
** EVERY HOUR GOES SOMEWHERE **
000 06 0000AI Adoption: You’ve paid for the licences. Now put them to work.
For businesses whose people have AI licences but use them like a search box. In 90 days, one team learns to hand AI real work, its strongest become super users, and one weekly task runs a new way, measured before and after. Fixed scope, fixed price.
Not ready to talk? Take the 5-minute AI readiness check
Sound familiar?
“We rolled out the licences. Use peaked in the first fortnight.”
“We ran a training day. A month later, nothing had changed.”
“A few people are flying. The rest are waiting for someone to show them.”
What you get
From one-off questions to real work.
We teach the foundations of working with AI on people’s own work, within your rules and whatever the tool, so the skills hold when the tools change. With AI, the value moves from doing the work to what goes in and what comes out: a clear brief with the right context and examples, and a sharp eye on whether the result is right.
Everyone using AI within the rules.
Training opens with safe use, and you keep the training record the EU AI Act expects.
A tool each person built and reuses.
Within two weeks of the training day, everyone builds one thing for their own work, and shows it.
Super users, found and ready.
The people who take to it fastest, helping colleagues now and ready to start your champion network.
One piece of work running a new way.
A weekly workflow redesigned with AI, measured before and after, and handed to an owner of yours.
Managers who back it.
Their own session first, on what changes and how to handle pushback. We do the rest.
Hours back, and where they went.
Measured after time spent checking AI’s work, shown by team, and put where a named person in your business decides.
A real brief, a real catch
Brief it well. Then judge what comes back.
The same task, briefed two ways. A clear brief gets a far more useful answer. Even a good answer can carry a mistake that sounds right, so everyone learns to check before they use it.
Example written by ThoughtFox to show the idea.
The brief
“I’m preparing a one-page summary of October’s customer complaints for Thursday’s operations meeting. Use only the attached log. Group the complaints by cause, with a count for each, and put anything about safety first. Suggest three actions. If something in the log is unclear, say so rather than guessing.”
- Purpose: covered
- Source: covered
- Shape: covered
- Priority: covered
- Say if unsure: covered
AI outputDraft · not yet checked
Safety: 2 complaints about damaged packaging with sharp edges.
Late delivery: 31, most on the Cork route.
Wrong item sent: 12. Billing errors: 9.
Complaints are up 40% on September.
Actions: review the Cork route schedule, check packing at station 3, add a billing check before invoices go out.
Unclear: 4 entries have no cause recorded.
Useful, and ready for the meeting. Or is it?
Proof
At Emydex, we started with one engineering team, redesigning how they build software with AI, and trained the leadership team alongside. One team first, then the next step.
Packages
Two packages. The 90-day programme, then AI in Your Core Work.
The 90-day adoption programme starts with one team and one workflow. AI in Your Core Work then takes it further: more workflows in that team, then more teams, each building on what the last one taught.
Before you start: your AI rules are set once at the top, by your leadership team or at group level. Need the rules in place, or want everyone trained first? Safe AI Use →
The 90-day adoption programme
For one team, with licences in place and an approved tool.
Set up: leaders, managers and a starting point.
Weeks 1 to 2. Your sponsor agrees what good looks like and makes time to practise. Managers get their own session, and we measure a likely workflow as it runs today.
Train and build.
Weeks 3 to 4. A training day on real work, then each person builds one tool and shows it.
Redesign one workflow.
Weeks 5 to 12. Super users and the manager redesign one workflow with us, including how roles change, then roll it out to the team.
- Time:
- 90 days, fixed scope and fixed price
- You leave with:
- one workflow redesigned and measured before and after, super users ready to start a champion network, the training record the EU AI Act expects, and an owner of your own who runs it.
AI in Your Core Work
Rollout across teams. For organisations that have proved it with one team and want to take it further. See the full page →
More workflows, more teams.
Leadership signs off each stage on the results so far. What worked becomes your standard approach, and a champion network grows from the first team’s super users.
A monthly clinic and a managers’ group.
Questions answered, the next build agreed, and managers comparing what’s working. New starters get the same training.
Report and review.
A one-page report to your sponsor each month, and a review of the plan each quarter.
- Time:
- Scoped and quoted for your organisation, and scaled back when you’re ready to run it yourselves
- You leave with:
- more of your work running a new way, a champion network, and an owner of your own who carries it on.
Your 90 days, from people to team.
- Weeks 1–2Set up
Leaders sign off, the manager goes first, and we measure a likely workflow as it runs today.
- Weeks 3–4 · Day 30Train and build
The training day, then everyone builds one tool and shows it.
- Weeks 5–6 · Team’s workRedesign
Super users and their manager redesign one team workflow with us, and how each role changes.
- Weeks 7–8 · Day 60 · Team’s workPilot
The new way runs on real work, checked every week.
- Weeks 9–10 · Team’s workRoll out
Super users teach the rest of the team.
- Weeks 11–12 · Day 90 · Team’s workHand over
Written down, with a named owner of your own.
- Next stepRollout across teams
We turn what worked into your standard approach, build a champion network, and take the results to leadership to sign off the next teams. Scoped and quoted.
AI in Your Core Work →
Approximate timings, set with you.
Why teams stall
Every team stalls somewhere. We find where, and fix it.
A team can stall anywhere between knowing why AI matters and using it on real work. A short report at day 30, 60 and 90, and a weekly look at what people build, shows where. We agree the fix with the manager, whose part is about 15 minutes a month. Pick a checkpoint to follow one team.
Who leads this
Led by people who make change stick.
Edel Churchill
Co-founder, AI Adoption & Change Lead. Created PRIME, ThoughtFox’s method for redesigning work around AI and guiding teams through the change. A Prosci Certified Change Practitioner with a focus on AI adoption, and holds a Diploma in Advanced AI for Business from UCD Professional Academy.
Marie Toft
Co-founder, AI Governance & Literacy Lead. Leads AI literacy training for ThoughtFox clients, and has taken organisations such as Workday and Fidelity Investments through AI executive leadership training.
JV Fennelly
Co-founder, Value & Product Lead. A serial entrepreneur since 2008, who rebuilt his own digital commerce business around AI. Leads how we measure and prove the return. Holds an Executive MBA from Trinity College Dublin, with a thesis on AI transformation at Jaguar Land Rover.
Questions people ask
Before you book the call.
We’ve already done AI training. Why would this be different?
A training day on its own fades within weeks. This one uses people’s own work, everyone builds something straight after, and managers back it.
Microsoft already offers free training. Why pay you?
Use it. You pay us for what it can’t do: your work, your rules, managers who lead it, and proof it’s paying off.
Can I start with just my team?
Yes. That’s what the 90-day programme is. We’ll need a sponsor above you to sign off the time.
How much of our people’s time does it take?
Most of it falls in the first month: about ten hours each for the training day and building a tool, and about two hours for your sponsor. After that, the small group redesigning the workflow gives two to four hours a week, and everyone else very little.
Our most experienced people are the most sceptical.
That’s common, and the team follows them. With AI their judgement counts for more: setting the brief and spotting what’s wrong. We bring them in early and show how their role grows.
We’re part of a group with several businesses.
We start in one business unit. Your group sets the shared rules once, and what works in one business is reused in the next.
Find out how deeply your people use AI.
Start with a call, or take the AI readiness check. Either way, you’ll know where your people stand and what a sensible first step looks like.
Our approach to change draws on Prosci’s methods, including ADKAR. Our approach to AI fluency draws on the AI Fluency framework from Anthropic and University College Cork.