Your AI licences, earning their keep

Hands-on workshops on Claude, Gemini, ChatGPT and Copilot, built around your team’s real work and skill levels. Your team leaves with working agentic workflows and the ability to keep building.

Book a call See the 4 phases

The program

Your team leaves with working tools in production and the ability to build more of them.

  1. 01 Assessment
  2. 02 Education
  3. 03 Tooling
  4. 04 Build day
  5. Optional Check-in

2 weeks, 4 sessions, and an optional check-in after. Choose one for the detail.

Week 1
Week 2
After

Phase 01 · Week 1 · Monday · Online

Capability assessment

Every participant completes an online assessment of current capability, and nobody is scored or ranked, so people answer honestly about what they can and cannot do.

It reads how the team feels about the technology, what they already use and where the friction sits, and the same answers set the use cases and priorities we build against on build day.

  • Current usage and confidence

    Where AI already sits in daily work

  • Workflow friction

    The tasks that take the longest each week

  • Use case candidates

    Ranked by value and feasibility

  • Environment and constraints

    What tooling set-up has to respect

Phase 02 · Week 1 · Thursday · Online · 90 minutes

Education session

90 minutes of fundamentals and concepts, built from what the assessment says about this team.

Examples come from your own use cases, so the session doubles as the brief for build day.

  • How the models work

    Capabilities, limits and failure modes

  • Context and prompting

    Giving the model the context it needs

  • Skills, agents and artifacts

    The building blocks used on build day

  • Judgement and review

    Which steps a person reviews before the output is used

Phase 03 · Week 2 · Tuesday · With the team

Tooling set-up

We sit with each team member and set their AI tools up for them: instructions, projects, connectors and memory, configured for the use cases the assessment found.

Everyone leaves logged in and working, so build day starts with building.

  • Accounts and access

    Every participant logged in before build day

  • Tool configuration

    Instructions, projects, connectors and memory

  • Guardrails

    Data handling and review expectations

  • Starter scaffolding

    Templates ready to build on

Phase 04 · Week 2 · Friday · A full working day

Build day

A full working day where teams build against the priorities the assessment ranked, and what they build goes live before they leave the room.

Every build names the steps a person reviews before the output is used, so each team knows where its own judgement sits in the workflow it built.

  • Skills

    Reusable capability for a recurring task

  • Workflows

    Multi-step processes wired end to end

  • Artifacts

    Documents, decks and assets teams reuse

  • Prototypes

    Working tools, shipped and in use

Optional · 2 to 3 weeks after build day · Online · 90 minutes

Check-in session

90 minutes 2 to 3 weeks after build day, once the builds have had real work put through them.

By then the team knows which builds earned a place in the week, so the session tunes those, retires the rest, and works through what has come up since.

  • What the team used

    Which builds earned a place in the week

  • Tuning

    Fixes to the builds carrying real work

  • Running cost

    Wasted spend cut from the prompts and context

  • Open questions

    What has come up since build day

What you keep

Everything from the program lives in your own accounts and your own environment, and it keeps running after we leave.

  1. 01

    A capability baseline

    Where your team sits today, and a ranked list of use cases with the reasoning behind the order.

  2. 02

    A working environment

    AI tools configured for each person, access sorted, and guardrails agreed with your IT and security teams.

  3. 03

    Live builds

    The skills, workflows, artifacts and prototypes built on the day, running in production.

Track record

8 programs in the past 12 months, across four industries and every level of the organisation.

  • 8

    Programs delivered since 2025

  • 100 +

    People through the education sessions

  • 86

    Prototypes shipped on build days

  • 4

    Sectors: finance, software vendors, retail, manufacturing

Who takes part

In the room

C-suite
CEO, CFO, CTO, CMO and managing directors
Middle management
Heads of product, people, technology, operations and marketing
Corporate functions
Finance, operations, legal, marketing, people and IT
Individual contributors
Software engineers, product managers, investment analysts

Pricing

Priced per cohort. Published prices in Australian dollars, excluding GST.

  1. Phase 01 Assessment
  2. Phase 02 Education
  3. Phase 03 Tooling
  4. Phase 04 Build day

Questions

What people ask before they book.

Which licences do we need?
Each participant needs a business seat on the AI tool you have chosen, whether that is Claude, Gemini, ChatGPT or Copilot, which you buy from the provider and which sits outside our fee. We confirm the tool and plan with you before tooling set-up, because the connectors and memory we configure depend on it.
How many people can take part?
Up to 12, and the cap applies to every phase, so the same group runs through the assessment, the education session, tooling set-up and build day. The fee is flat within that cap, and we agree the group on the first call.
Where does it run?
The assessment and the education session are online. Tooling set-up and build day run on site with the team, in Melbourne or wherever the team sits, and travel outside Melbourne is charged at cost.
Does anyone need a coding background?
No. The education session covers how the models work, context and prompting, and the building blocks used on build day. Everyone is logged in and set up before build day starts, so teams build in their own tools from the first hour.
What does IT need to agree to?
Access, permissions and data boundaries. We agree these with your IT and security teams before tooling set-up, along with data handling and review expectations, so nothing is blocked on build day.
How soon can we start?
Programs start 2 to 3 weeks after the first call, because the assessment needs a week to run before the education session and IT needs time to agree access.
What happens to the builds afterwards?
They stay with you. The skills, workflows, artifacts and prototypes run in your own environment and your own accounts, and your team keeps building on them after we leave.
Can we book the education session on its own?
Yes. Education is phases 01 and 02 for $4,500 and build day is phases 03 and 04 for $28,000. Booked together as the bundle, all 4 phases are $30,000, which is $2,500 less than booking them separately. Every price excludes GST.

Set the dates

One call to check fit and put the 4 sessions in the calendar.

Book a call