AI Capacity

AI use is not AI capacity.

Your team can use ChatGPT, Claude, Copilot, agents and automations every day — while the same important work still comes back to the same people.

Because making individuals faster is not the same as making the organisation more capable. AI becomes capacity when human expertise, well-designed work, systems and AI combine so valuable work can move reliably to standard.

AI Capacity is the ability to use human expertise, work design, systems and AI to increase what the organisation can reliably get done.
The important question is not

How much AI are we using?

It is

What can the business do now that it couldn’t reliably do before?

Lots of AI. Same bottlenecks?

Everyone has AI. Why are the same jobs still coming back?

Your team may already be using AI well. Documents arrive faster. Research that took hours takes minutes. Meetings summarise themselves. Someone has built an agent. There may even be a respectable little zoo of automations quietly doing useful things in the background.

And yet…

Proposals
The proposal is faster to write.

You still add the client context that makes it right.

Reporting
The report gets produced.

You still decide what matters, what looks wrong and what happens next.

Agents
The agent completes most of the task.

You are still the person who knows whether the result is good enough.

Everywhere
Your productivity has gone through the roof.

The firm’s capacity hasn’t followed it.

That’s not a failure of AI.It’s a clue.

The real dependency sits somewhere else.

What AI exposes

AI didn’t create the dependency. It exposed the invisible job specification.

Imagine the process says: Prepare the monthly client report.

It sounds perfectly clear. Until someone else — human or AI — actually tries to do it.

For years, you may have supplied the missing answers almost without noticing. That’s the invisible job specification. The process described the task. You supplied the judgement that made the task work.

Fig. 01 — The invisible job specification · drag the task upwards to reveal what the job actually depends on
Where the specification lives
5 with the founder · 0 explicit in the firm
The missing information was never a better prompt.It was the context, standards, judgement and decision boundaries.

Nobody had needed to make them explicit while the founder was quietly supplying them. So before asking “What can we automate?” ask “What does this job actually require?”

Transfer is more than documentation

Four things have to move.

A folder full of SOPs can be useful. It can also become a beautifully organised record of everything the founder still needs to approve. Real transfer involves four things.

01 · Knowledge
What do I know?
  • Facts
  • History
  • Client context
  • Examples
  • Patterns
  • Sources
02 · Judgement
How do I decide?
  • What changes the answer?
  • What makes me suspicious?
  • When does the usual rule stop applying?
  • Which trade-off matters most?
03 · Standards
What does good look like?
  • What would make me reject the work?
  • What tone sounds like us?
  • Which examples represent the standard?
  • Where is the line between acceptable and excellent?
04 · Responsibility
Who can get this done without me?
  • Who owns it?
  • What can they decide?
  • Where does AI fit?
  • What gets checked?
  • What genuinely comes back?
A beautifully documented founder who still approves every exception is simply a better documented bottleneck.

Documentation matters. Ownership matters more.

Enough theory

What might Transfer actually look like?

These are examples of the kinds of recurring jobs where the distinction becomes obvious.

01Meetings into action
Before

The meeting happens. AI produces immaculate notes. Then everyone gets busy. A week later: “What did we actually decide?” The founder becomes the memory system.

Towards transfer

The workflow turns the meeting into:

decisionsactionsownersdeadlinesfollow-upescalation

AI helps extract the work. A named person owns what happens next.

What changed

The output stopped being meeting notes. It became an owned job.

02The weekly firm brief
Before

The information exists everywhere. Email. CRM. Projects. Messages. People’s heads. So the founder reconstructs the state of the business from six conversations and a strong cup of coffee.

Towards transfer

Agreed information feeds a consistent brief. AI prepares the synthesis. A named person checks it against defined standards. The founder sees the few things that genuinely require attention.

What changed

Information became usable operating context.

03Proposals
Before

The team creates 80%. Then the founder adds the client context, commercial nuance and the bit that makes it sound like the firm rather than a competent stranger.

Towards transfer

Relevant context, strong examples, quality criteria and decision boundaries become part of the workflow. Routine correction disappears. Commercial exceptions still escalate.

What changed

The team gained access to more of the judgement behind the work.

04Management reporting
Before

Someone produces the numbers. The founder explains what they mean and tells everyone what to do.

Towards transfer

The workflow includes interpretation criteria, thresholds, exception triggers, ownership, decision rights and escalation. AI can surface patterns. People remain responsible for decisions.

What changed

The work moved from reporting information to supporting action.

Read those examples and immediately think, “I’ve got three of those”?

You probably do.

The work-first approach

Design the job before you design the technology.

01
Identify

Choose recurring work worth moving.

02
Extract

Capture the context, judgement, standards, examples, exceptions and red flags it actually depends on.

03
Design

Decide ownership, human/AI roles, decision rights, boundaries and escalation.

04
Build

Use the simplest useful combination of people, AI, automation, knowledge and tools.

05
Test

Run real work. Find the failures. Fix the design.

06
Transfer

Move ownership beyond the founder and check whether it holds.

Use the least complicated system that reliably transfers the job.

A three-agent orchestra is not automatically better than one well-designed workflow and one competent human. No medals are awarded for unnecessary orchestration.

Explore Workflow Redesign & Implementation

Human-in-the-loop

Put the right human in the right loop.

Responsible AI does not mean letting software wander around the business like a Labrador with the office keys. It also doesn’t mean the founder approves everything forever. That just recreates the original problem with nicer technology.

Pattern one
AI performs

For bounded, repeatable work with clear standards and controlled risk. A person remains accountable for the system. They don’t need to inspect every routine output.

Pattern two
AI prepares · human decides

Where judgement, relationships, interpretation or meaningful commercial risk remains. AI removes preparation work. A person owns the decision.

Pattern three
Human owns

Where the situation is highly sensitive, genuinely novel or consequential. Leadership. Culture. Critical relationships. Material commercial or reputational decisions.

Angela Sedran
Why this isn’t an AI side quest

AI changed the instrument. It didn’t remove the need to design the work.

I came to AI from the organisational side. For more than 25 years, I’ve worked with strategy, leadership, decisions, accountability and execution across organisations including BHP, Microsoft, Vodafone and LexisNexis and with founder-led businesses.

The technology is new. The questions underneath it aren’t:

  • Who has the context?
  • Who owns the work?
  • Who can decide?
  • What does good look like?
  • Where should judgement sit?
  • Why does everything unusual come back to the same person?

AI makes those gaps dramatically more visible. And when the work is designed well, it gives us a powerful new instrument for addressing them.

AI is the instrument. Your expertise is the advantage.

I’m not interested in getting your business to use more AI for the sake of it. I’m interested in what the business can genuinely do better because AI is there.

“Genuinely seeks to understand and design processes that suit the client’s business — not a one-size-fits-all approach like so many other consultants.”
Troy McDonald
Former Asset President, BHP / Illawarra Coal · Founder, Torqn
Where do you start?

That depends on the work.

Not every company needs an “AI transformation”. Thank heavens. There are two practical routes.

Route one
AI Capacity Sprint™

Three recurring jobs become firm-owned in four weeks. For established founder-led firms with three suitable recurring jobs that still rely too heavily on founder context, judgement or correction.

Real work. Real owners. Live testing. A 30-day durability check.

Founding cohort starts
Tuesday 8 September 2026
Applications close
5pm Wed 2 September 2026
Investment
AU$2,500 per firm
Route two
AI Workflow Redesign & Implementation

Redesign the work. Then implement the AI. For a more complex workflow or broader implementation challenge.

This can involve workflow redesign, knowledge architecture, agents, automation, integrations, permissions, testing, handover and adoption. The scope depends on the work. But the philosophy does not:

Start with the work. Choose the technology second.

Not sure which applies? Tell me what work keeps coming back

Build capacity, not just AI activity
What could your business do without continually coming back to you?
See the AI Capacity Sprint

If three recurring jobs immediately spring to mind.