INSIDE LETTING-GO MENTORING
Decide What AI Takes Over First
A composite client example.
You are pasting the same client history into another AI tool, because nobody else knows which CRM notes, playbook and case story belong together. Ivanka Menken uses the Step-Out Log inside Letting-Go Mentoring, a 6-month 1:1 programme at AUD $1,500 per month ex GST, to name which AI-linked work leaves your desk and which judgement stays with you. In a composite example, an agency founder had the tools connected and every exception still came back. You leave with one handover entry: the task, the owner, a 14-day test and the exception rule.
The Step-Out Log is a tool inside the programme, not a separate product.
AN EXAMPLE HANDOVER
One task. One owner. Fourteen days.
- THE TASKAI-linked, and it repeats every week1 task
- THE OWNERwho owns the exception, not you1 lead
- THE TESTno override, then review what came back14 days
THE RULE
“The tool does the drafting. The owner handles the gap. You hear about it after.”
A composite example, not a client result. Your task and owner will differ.
SOUND FAMILIAR?
The tools are new. The bottleneck is not.
- 01You are the only one who knows how the AI context fits together.
- 02Every automation still comes back to you for judgement.
- 03The team has tools but no clear owner for exceptions.
THE AI WORK, AS IT STANDS
- Tools: bought and connected to the CRM
- Context: assembled by the founder
- Prompt library: longer every month
- Exceptions: back to the founder
- Owner for a missing CRM note: nobody
A composite example. More context, the same bottleneck.
THE EXAMPLE CASE
One AI handover, read three ways
A composite client example.
01
THE MOMENT
AI tools in place, and every answer still routed through the founder
It is mid-morning and you are pasting a client’s history into another AI tool: the CRM notes, the playbook, the case story that fits. The team has the same tools and the same CRM connection. But when a note is missing or a client asks something new, the draft comes back to you. You bought the tools to get time back. You spend it assembling context only you know how to assemble.
02
WHAT THEY HAD TRIED
A longer prompt library
The founder wrote a longer prompt library: every client type, every tone, every edge case they could think of. It made the drafts better. It did not stop the team bringing exceptions back. Whenever a CRM note was missing or out of date, the team stopped, because nothing in the library said they were allowed to decide what to do next. The library grew; the founder’s week did not shrink.
03
WHAT IVANKA NOTICED
The team could use the tools, but nobody could handle the gap
Ivanka noticed that the team could use the tools perfectly well. What they lacked was authority. Nobody had been told they owned the moment a CRM note was missing. So every gap in the data became a question for the founder, and the AI tools simply made the gaps arrive faster.
THE DIAGNOSIS
Not more context. An owner for exceptions.
The real gap was not context volume. It was an owner for exceptions. More prompts give the tool more to work with; they do not give a person the right to decide when the tool runs out of information.
The reframe: AI does not remove the founder’s judgement. It exposes which judgement was never written down. The Step-Out Log names that judgement, hands the repeatable part to a system and a person, keeps the rest with the founder, and tests the handover for 14 days without override.
AI does not remove the founder’s judgement; it exposes which judgement was never written down.
THE COST OF STAYING STUCK
If every AI task still routes through the founder, the system adds tools without adding capacity. The subscriptions grow, and so does the queue at the founder’s desk.
THE TOOL
The Step-Out Log, for AI-linked work
The Step-Out Log is how Letting-Go Mentoring moves work off the founder: step out, log what still needed you, and hand it over in order. For AI-linked work, the log sorts each task three ways: what leaves your desk to a system and a named person, what goes to an exception owner, and what judgement stays with you.
A composite example. Tap a part. Your tasks and owner are yours.
Step-Out Log · a framework by Ivanka Menken
What it is
It is a one-page handover entry for one AI-linked task: the task, the owner, the exception rule and a 14-day test without override. Anything that comes back to you during the 14 days becomes the next session.
What it replaces
It replaces a growing prompt library, context only the founder can assemble, and exceptions that reach the founder’s desk faster than before the tools were bought.
It sits inside Letting-Go Mentoring, one handover each fortnight across the six months, with the Commitments-Kept Metric reviewed monthly. Ivanka does not build or configure your AI tools. There is no separate checkout.
THE LOG, FOR ONE AI-LINKED TASK
- 01Leaves your desk: the task that repeats every week without needing you
- 02The system: the AI tool and the CRM, doing the drafting
- 03The owner: one named person for the exception
- 04The exception rule: a missing or out-of-date CRM note goes to the owner
- 05Stays with you: the judgement call on a new kind of client
- 06The test: 14 days, no override, then review what came back
HOW IVANKA WORKED WITH THEM
One AI-linked handover, written down
In an example session, Ivanka asked three questions. Which task repeats every week without needing you? What would break if you heard about it afterwards? Who owns the exception? The founder picked client update drafts built from CRM notes. Together they wrote a one-page handover entry: the task, the owner, the 14-day test and the exception rule. Before the next session, the founder briefed one account lead, stopped checking the drafts, and logged anything that still came back.
THE HANDOVER ENTRY, AS WRITTEN
- The task
- Client updates drafted by the AI tool from CRM notes.
- The owner
- One named account lead, for every draft and every gap.
- What stays with you
- A judgement call on a new kind of client.
- The exception rule
- A missing or out-of-date CRM note goes to the owner, not you.
- Review
- 14 days out
A composite example. Your task and owner are yours.
THE FOUR-STEP LOOP
- 1The one thingThe AI-linked task that still comes back to you.
- 2The numbersHow often it repeats, and how often it comes back.
- 3The storyWhy letting the draft go without you feels risky.
- 4The commitmentOne Step-Out Log entry, and 14 days with no override.
THE QUESTIONS
- Which task repeats every week without needing you?
- What would break if you heard about it afterwards?
- Who owns the exception?
- What judgement stays with you, in one sentence?
- What will you stop checking?
Before the next session, the founder handed the client update drafts to one account lead and noted each thing that still came back. Those notes became the next session.
WHAT CHANGED
Tools that add capacity, not questions
By month six, at least one AI-linked handover is in the Step-Out Log, the founder has a written boundary for the judgement that stays with them, and the commitments-kept metric is reviewed monthly.
BEFORE
- The founder assembled every piece of context.
- The prompt library grew every month.
- Every exception came back to the founder.
- Nobody owned a missing CRM note.
BY MONTH 6
- One AI-linked handover in the Step-Out Log.
- A named owner for exceptions.
- A written boundary for the judgement that stays.
- The commitments-kept metric reviewed monthly.
THE 12 FORTNIGHTS
- 1Call
- 2Call
- 3Call
- 4Call
- 5Call
- 6Month 3
- 7Call
- 8Call
- 9Call
- 10Call
- 11Call
- 12Month 6
The programme is the container: 12 fortnightly 60-minute sessions, one handover each fortnight, and reviews at month 3 and month 6.
ILLUSTRATIVE RESULT
In this composite example, the founder logged one AI-linked handover, named an exception owner, and ran the 14-day test before changing the process again. Illustrative, not a client result.
WHAT THIS MEANS FOR YOU
Your next AI task is a handover decision
Ivanka Menken built Letting-Go Mentoring for founders of $500K to $3M businesses who became the bottleneck by being good at everything. She asks which work still ends at you, and keeps you to the handover you write down.
If your team has the AI tools and the work still comes back to you, the decision in front of you is who owns the gap. Name that person before you write another prompt.
“During our sessions Ivanka isn’t just talking theory. She is sharing her own lived experiences.”
Business owner
WHO IT IS FOR
It fits
- You run a $500K to $3M business with AI tools already in the work.
- You are the only one who knows how the context fits together.
- Exceptions still come back to you.
- You will name an owner and leave the handover alone for 14 days.
It does not fit
- You want open-ended coaching.
- You want a done-for-you AI build or someone to configure your tools.
- You want a prompt library written for you.
- You are not ready to hear about the work after it is done.
THE INVESTMENT
AUD $1,500
per month ex GST
6 months · 12 fortnightly sessions
The Step-Out Log is part of Letting-Go Mentoring, a 6-month 1:1 programme at AUD $1,500 per month ex GST. It is not sold separately.
- 12 fortnightly 60-minute sessions
- One handover each fortnight
- A monthly one-page scorecard
- Reviews at month 3 and month 6
Three founding places in total, shared across all 1:1 mentoring, are available at AUD $1,000/month ex GST, in return for honest monthly feedback and a testimonial, which can be anonymous. Claim a founding place.
The Step-Out Log is part of the programme. It is not sold separately.
FREQUENTLY ASKED
Questions about handing work to AI
Which work should move from me to an AI system?
The work that repeats every week without needing your judgement: drafting from known notes, pulling the right playbook, formatting a reply. Start with one task, not ten, and name the person who owns its exceptions. Ivanka Menken helps you pick it and write it into the Step-Out Log inside Letting-Go Mentoring, 6 months at AUD $1,500 per month ex GST.
What does the founder still own after automation?
The judgement that was never written down: a new kind of client, a change to price or terms, a call nobody has made before. The Step-Out Log writes that boundary down so the team knows what stays with you. Ivanka Menken draws it with you inside Letting-Go Mentoring, 6 months at AUD $1,500 per month ex GST.
How do I test a handover without overriding it?
Write the exception rule first, name the owner, then leave it for 14 days. You hear about the work afterwards, and anything that comes back is logged, not fixed on the spot. That log becomes the next session. Ivanka Menken keeps you to the 14 days inside Letting-Go Mentoring, 6 months at AUD $1,500 per month ex GST.
Is Letting-Go Mentoring a done-for-you AI build?
No. Ivanka Menken does not build, configure or choose your AI tools. Letting-Go Mentoring is 1:1 mentoring that decides which work leaves your desk, who owns the exceptions and what judgement stays with you. It runs 6 months at AUD $1,500 per month ex GST, with one handover each fortnight and reviews at month 3 and month 6.
Name the owner before the next prompt
If the AI tools are in place and the work still comes back to you, start with Letting-Go Mentoring. The Step-Out Log is inside it, and the 20-minute intro call is where you can see whether the programme fits.
Not open-ended coaching or a done-for-you AI build.