Working software by Friday.
We assess the team, teach the fundamentals, set up Claude inside your environment, then build with you for a day.
The program
One packaged engagement, delivered in a week. Every phase feeds the next, and the build day ships against your own priorities.
-
01
Assessment
An online read of how the team feels about the technology, what they use now and where the friction sits. It sets the use cases and tailors the engagement.
-
02
Education
90 minutes on fundamentals and concepts, so the team starts from the same baseline and the examples come from their own work.
-
03
Tooling
Claude and the harness stood up inside your environment: instructions, projects, connectors, memory and access.
-
04
Build day
A full working day building against your own priorities. What the team builds goes into production, not a pilot.
The four phases in full
Two weeks, four sessions. Choose a session for the detail.
What you keep stays with the team. Nothing is held in our accounts.
-
01
A capability baseline
Where your team sits today, and a ranked list of use cases with the reasoning behind the order.
-
02
A working environment
Claude and the harness configured, access sorted and guardrails agreed, which you keep running after we leave.
-
03
Live builds
The skills, workflows, artifacts and prototypes built on the day, running in production.
Track record
Eight programs since 2025, across finance, software vendors, retail and manufacturing.
-
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
Published, in AUD, excluding GST. Headcount does not change the fee.
- Phase 01 Assessment
- Phase 02 Education
- Phase 03 Tooling
- Phase 04 Build day
Questions
What sponsors ask before they book.
- Who should be in the room?
- The people whose week the builds will change. Past cohorts have ranged from the full C-suite to the whole company: heads of product, people, technology, operations and marketing, corporate functions, and individual contributors such as engineers, product managers and investment analysts.
- 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 Claude 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.
- Is anyone scored or ranked in the assessment?
- No. Nobody is scored or ranked, and we say so, which is why people answer honestly about what they can and cannot do. The assessment reads current usage and confidence, workflow friction, use case candidates, and environment constraints.
- What happens to the builds after the week?
- They stay with you. The skills, workflows, artifacts and prototypes run in your environment, in production, and every build names the steps a person reviews before the output is used. Nothing is held in our accounts.
- Can we book the education session on its own?
- Yes. Education covers phases 01 and 02 for $4,500. Build day covers phases 03 and 04 for $28,000. Committed together upfront, both are $30,000, excluding GST.
Book a call.
One call to check fit and set a date for the assessment.