Frank doesn’t hand out courses. It builds programs: a set of stories your team practices by voice over a few weeks, where the counterpart arrives at each session carrying what happened in the last one. This is how one is built, and what a four-week pilot looks like from the inside.
Each one contains the next. The leader sets up the program for the coming weeks. Each story is a situation that moves forward chapter by chapter. Each session is a voice conversation, start to finish.
The team leader, from a template or from scratch.
Two to four weeks.
Frank proposes it from your documents. You correct it and approve it.
Two to four sessions.
The person, alone, from the browser.
Five to ten minutes.
What happens inside a session and what the report measures is in how Frank works.
When each session ends, Frank records what was settled: whether you held the price, gave up margin, or the counterpart ended the meeting. The next session starts from there. Two people in the same program can reach the third week with different conversations, because they resolved things differently.
Procurement opens asking 18% off the closed price.
Second meeting. Procurement comes back to the discount with a competitor’s quote in hand.
If you held the price: technical close. Procurement accepts the number and now argues payment terms and warranties.
If you gave up margin: win the term back. Procurement takes the discount for granted and asks to extend it to the whole contract.
Twelve-month renewal. The counterpart remembers what happened in the third session and opens from there.
A template brings the structure, not the scenarios: it defines what kind of situation and what nature goes in each week. When you clone it, each week is filled with a scenario written from your documents and approved by you.
So a newly promoted leader can hold hard conversations without burning out the team.
A newly promoted leader, before their first formal feedback cycle.
Routine feedback to one team member. The baseline is set.
Another person, another topic. Settling the pattern.
A conflict between two team members, with emotional load.
Defending an unpopular decision in front of peers.
Giving clear negative feedback without breaking the relationship.
A manager before their quarterly or annual review cycle.
The structure of the message, with someone who listens.
Someone who questions the review or gets defensive.
Hard feedback to someone with a history of conflict.
Sharpening negotiation when there’s a number at stake.
A sales team in the weeks before the quarter cutoff.
Negotiation with limited time and technical objections.
The client threatening to leave.
For someone who had a hard conversation go wrong and needs to recalibrate.
One person after a real conversation that went badly.
Rebuilding confidence with a case that carries little emotional load.
Back to the kind of conversation that went wrong, this time at no cost.
No template is mandatory. A program can also be built from scratch, story by story.
This is exactly what happens, step by step, with a small group and a scenario co-designed with you. Week 0 is preparation: the four weeks of practice start with the baseline.
Documents and approval
You hand over the documents you already have. Frank proposes the scenarios; you correct them and approve the ones that go in. The confidentiality agreement is signed before the first session.
Baseline
Each person does their first session. That’s where their baseline comes from: how they sound speaking under normal conditions, before practicing. It’s the reference everything that follows is compared against, and it’s theirs, not an average.
Practice
The program’s stories. The counterpart arrives at each session carrying what happened in the last one, and the story branches according to what each person resolves. Every report is private to the person who did it.
Reassessment and report
Each person does a session on a comparable scenario they haven’t seen: same situation and same nature, different content, so what gets measured is the conversation and not the memory of the script. Then an aggregate report for the organization with the group’s progress against its own baseline.
The aggregate report doesn’t rank people or compare them against an ideal. Individual reports stay in each person’s hands.
The pilot seen from the inside, with the detail of each week, is in case studies. That page has the full method and what the organization gets at the close.
You leave the demo with at least one scenario written for your company and a clear idea of which template to use.
What each plan includes and how it’s billed is in pricing.