Session 8 of 9

FSM Training

The 80% Method

How to deliver 80% of the value so founders own 100% of the outcome.

80% us. 20% them.
100% theirs.

Identity

What We Are vs. What We Are Not

What We Are

A system installation team
Expert guides who accelerate results
Builders of founder-owned assets
Temporary scaffolding for permanent growth

What We Are Not

An agency doing work for them
Freelancers taking revision requests
A service they depend on forever
A support desk for unlimited changes

Analogy

The Tailor Analogy

Think of yourself as a master tailor. You take the measurements (brand deep dive), you select the fabric (their unique positioning), and you create a bespoke suit (their system). The founder does not tell the tailor how to cut the fabric. They trust the tailor's expertise. When the suit is done, they own it. They wear it. It fits only them.

We measure before we cut. Every deliverable is built from their specific data.
We make adjustments on the spot. Not after the fitting. During it.
The end product belongs to them. They walk out wearing it, ready for the world.

Language

Say This / Not That

Say This	Not That
✓ "What resonated most?"	× "What feels off?"
✓ "Does that make sense?"	× "What didn't work?"
✓ "Let me update that right now"	× "I'll fix that after the call"
✓ "Your system"	× "Our module"
✓ "Installation"	× "Course"
✓ "We built this from your brand deep dive"	× "AI generated this"
✓ "Your team can use this"	× "We'll do revisions"

Objection Handling

When Founders Push Back

1

Listen fully. Do not interrupt. Let them finish their concern completely.

2

Acknowledge the feeling. "I hear you. That is a valid concern."

3

Reframe with data. "Here is what we have seen work across our top-performing founders..."

4

Offer to amend live. "Let me adjust that right now so it feels right for you."

5

Confirm alignment. "Does that feel better? Is this closer to what you envisioned?"

120 founders per FSM.
Zero revision cycles.

Live Amendments

Amend on the Call

The revision cycle is dead. If a founder requests a change, make it live. This is faster, builds trust, and eliminates the back-and-forth that kills scale.

Small changes happen now. Wording tweaks, tone adjustments, content swaps. Do them live.
Structural changes get scoped. "That is a bigger shift. Let me map that out and we will review it on our next call."
Never promise revisions via email. That creates a ticket queue. You are not a support desk.
Document what you changed. Note every live amendment so the system stays updated.

Non-Negotiable

Automatic Fails

These behaviors are career-limiting. One instance gets flagged. Repeated instances get escalated.

×

Telling a founder the deliverable was "AI generated" or "auto-created"

×

Deferring a simple change to "after the call" or "next session"

×

Using the word "course" or "module" instead of "system" or "installation"

×

Showing up unprepared without reviewing the founder's brand deep dive

×

Ending a call without a clear roadmap, homework, or next session booked

×

Asking "What didn't work?" instead of "What resonated most?"

What We Stand For

The Founder OS Values

Insanely Simple

Obsessing Over Quality

Finding Innovative Solutions

Engineering the Future

Elevating the Design

Dazzling Founders

Someone who deeply understands
my business created this with
extraordinary care.

The Standard

What the Founder Should Feel

"This was made for me." Not a template. Not a generic output. Theirs.
"They actually listened." Every detail from the brand deep dive is reflected.
"I can see myself using this." Practical. Implementable. Not theoretical.
"I own this now." It is their system, their brand, their future.

Scale

How 80% Method Enables Scale

120 founders per FSM. That is the target. You can only hit it if every call is efficient.
Zero revision cycles. Amend on the call. No email threads. No back-and-forth.
Same quality at scale. The system produces the deliverable. You present it with conviction and amend live.
Your time is the bottleneck. Every minute spent on revisions is a minute stolen from another founder.

Language Toolkit

Phrases That Build Ownership

"This is your content machine." Not ours. Theirs.
"Your team can run this without you." System, not dependency.
"We built this from everything you shared in your brand deep dive." Personal. Custom. Theirs.
"Let me update that right now." Instant trust. Zero delay.
"What resonated most?" Positive framing. Always.

Self-Assessment

80% Method Checklist

I use ownership language: "your system," "your brand," "installation"

I never reference AI or automation to founders

I amend deliverables live on the call, not via email

I ask "What resonated most?" not "What feels off?"

I can handle pushback with the 5-step framework

I know all six automatic fails and avoid them

Your Progress

Training Journey

Deck 8 of 9

The 80% Method

Next up: Leadership Blueprint

The 80% Method

80% us. 20% them.100% theirs.

What We Are vs. What We Are Not

What We Are

What We Are Not

The Tailor Analogy

Say This / Not That

When Founders Push Back

120 founders per FSM.Zero revision cycles.

Amend on the Call

Automatic Fails

The Founder OS Values

Someone who deeply understandsmy business created this withextraordinary care.

What the Founder Should Feel

How 80% Method Enables Scale

Phrases That Build Ownership

80% Method Checklist

Training Journey

80% us. 20% them.
100% theirs.

120 founders per FSM.
Zero revision cycles.

Someone who deeply understands
my business created this with
extraordinary care.