“Your team is growing. Growth creates complexity. Complexity kills duplication. One system fixes it.”

Start here - The shape of a launch

A launch is one call plus one workshop. The call is where your team decides. The workshop, the day after, is where they actually set SAGA up.

Both matter - a call without a workshop gives you signups that never turn into use.

The goal of the call is not signups. It is that SAGA becomes the normal daily way your team works. Keep that in mind and most of your decisions make themselves.

You can Download the complete launch Playbook here:

The four moves

The discount window stays open for 72 hours after the call. After that, the normal price applies.

What you are really doing

You are not introducing a tool. You are telling your team that from now on, this is where the work happens: onboarding, follow-up, content, CRM, communication. One home, one way of doing things, so the business duplicates.

Two things worth deciding now

1. Your date. Pick the call first, then put the workshop the very next day while the energy is still there.

2. Your three leaders. They need time to think about what they will say. Ask them early - this is the piece most launches leave too late.

The launch is delivered by your own leaders, not by an external speaker. The reason is substantive, not organizational. It is your system. If somebody from outside presents it, it becomes just another product that was sold to you.

The precondition is that every leader has internalized the system beforehand. Not looked at it. Used it. Leader gate.

Anyone who does not meet these four points does not speak at the launch:

• Own onboarding fully completed

• At least 30 of their own contacts in the systemmaintained and tagged

• At least one new partner already fully onboarded through SAGA

• At least one follow-up scheduled through the system, executed and closed out

That sounds harsh and it is meant to. A leader who speaks at the launch and is not in the system themselves by week 3 creates exactly the consistency gap that tips the whole process over. Teams watch behaviour, not speeches.

Your checklist

At least two weeks before

• Pick your call date and workshop date

• Request your launch and discount code

• Ask your three leaders and assign each a feature

• Start promoting the event (read more)

One week before

• Make your copy of the presentation and fill in details (read more)

• Send leaders the four-line template

• Brief your support person — give them link and code

The day before

• Run through the deck once out loud, especially the demo

• Check the signup link and code actually work

• Confirm all three leaders are still in — remind them: 60 seconds, one number

• Send a reminder with the workshop time already in it

Fifteen minutes before

• Signup link and code pasted in a note, ready to go

• Demo account open on a second screen with real data

• Follow-up message drafted, ready to send the moment you close

Keep it straight: The 72-hour deadline and the workshop are two different jobs. The deadline is for buying. The workshop is for setting up. Keep them separate on the call, or the deadline stops feeling urgent.

Part 1 - Before the call

Step 1: Request your launch and get your team code

Every team launch gets its own discount code. It is issued on request, so this has to happen before anything else - you cannot announce a price you do not have yet.

Step 2: Take your own copy of the presentation

The deck follows the structure below, section by section. Open the link and make a copy — that copy is yours to edit however you like. Here

Change these — Make it yours:

• Team name, logo and picture

• Your currency and price

• Your discount code (to be asked to the SAGA team)

• After launch training (workshop) date and time

• Your signup link

Download the deck here:

https://docs.google.com/presentation/d/1HwEKo0j5k_8-9Jd_OaGd7_fRJG7ihESP_mkEmgRbjNw/edit?usp=sharing

Leave these — Keep the structure:

• The order of the five sections

• The before/after demo pattern (this is what makes the call land)

Step 3: Ask three leaders to speak

Three short testimonials, one feature each, no overlap. Assign the features yourself in advance.

Under 60 seconds each, with a real number. “It helped a lot” convinces nobody. “I onboarded three people last week without a single extra call” does.

Send them this template:

The feature I love most is ___ Before SAGA, my problem was ___ Now, with this one feature, ___ It made my business simpler because ___

Step 4: Book the workshop and brief one support person

• Workshop: the day after the call. Frame it as hands-on setup, not technical training.

• Support person: one person on chat duty during the call, with the signup link and the code already copied, ready to paste the second the presenter says it. Not two people, not nobody.

Part 2 — Promoting the launch event

A launch that 30 percent of the organization attends is not a launch. It is a meeting. Promotion decides attendance, attendance decides the energy in the room, and the energy in the room decides everything that follows.

Two waves

Wave 1 → 2 weeks before: the invitation. Date, time, attendance framed as a matter of course. Deliberately thin on content. Something new is coming, it changes how this team works, be there. No product name, no screenshots, no feature list. Explain everything 14 days out and you have nothing left to say on launch day.

The invitation goes through every channel available: the WhatsApp main group, a personal message from each upline to their direct partners, an announcement on the next team call. The personal layer is what matters. A broadcast into a 500 person group produces around ten percent sign up. The same message, passed on individually by every leader to their people, produces a multiple of that.

Wave 2 →from 5 days before till day-1: the countdown. Five days, five posts, same time every day. The purpose is not information, it is presence. On launch day nobody in the team should be able to say they had not heard about it.

Between those waves there is deliberate silence. That gap is not an oversight. It builds the tension the countdown then releases.

The shape of the countdown

Each of the five days has a job. Templates in appendix C.

The hint on T-1 matters and has to stay vague. You announce that it is worth being there live without revealing the offer. Anyone who knows the offer in advance no longer needs to show up.

The pilot group as an amplifier

From T-14 the pilot group is no longer a secret, and that is an advantage. The participants get a clear instruction for these two weeks: show that you are working on something. Do not explain what it is.

Roughly, inside the team: "I am in a small group building something new right now. I am not allowed to say more yet, but on [date] you will see it." That creates curiosity no top down announcement can produce, because it comes from peers.

One thing to watch: the appeal of a visible small group has a flip side. People who are not in it can feel passed over. So when the invitation goes out to everyone, say once and clearly that there was a first test group, that it had to be small, and that on launch day everybody gets the same access.

Part 3 — The launch call (40 minutes)

The launch is not a vote. You are not asking whether the team would like a new system. You are also not in a sales conversation. You are painting a picture of how this organization works from now on, and you are radiating that you know where this is going.

People are there because of you and because of the trust they have in you. The system is one more piece of evidence that they are in the right team. What should form in that room is hope and confidence, because this business only works while both are present.

No launch opens with the product name. It opens with the outcome:

Over the next 30 days we are building our shared operating system for this organization. Everyone here sets up their contacts, their follow-ups and their customer journey in one place. At the end every member knows what to do daily, and every leader can support you specifically.

The product does not appear in that sentence. It sits in the background and does not need much discussion there either.

Run of show

Plus live Q&A at the end.

The five function rule

Show five functions at most, even if the system has thirty. The risk is real and it hits the people who know it best hardest. You are deep in the subject, you use familiar terms, and in doing so you lose the connection to the base. The moment somebody hears pipeline, automation, labels and drip campaigns in one sentence is the moment they check out internally.

Recommended selection, locked before the launch and identical for all speakers:

1. Adding contacts and finding them again

2. Pipeline: where each person currently stands

3. Scheduling a follow-up

4. Sending material from the library

5. Community: where questions go

Everything else is an accessory. What a partner needs is a short list: talk to people, do a follow-up, send material. If everybody did that daily, the goal is met.

Five rules that decide how it lands

1. Every demo beat is before and after. Never a feature on its own.

2. Your team is the star. SAGA is the vehicle.

3. One recommended path. Do not teach four price tiers on a live call.

4. One sharp ask. Buying is the ask; the workshop is the follow-through, not a competing action.

5. Nobody is excluded. Mention the free version so the whole team stays together.

How to present the offer

On launch day there is a 72 hour code on the annual plan. This is the only commercial moment in the entire process and it has to be placed cleanly, otherwise the character of the evening tips over.

• There is a free version — say it once, then move on.

• Recommend one paid path: the one with the full CRM, pipeline and follow-up.

• Show the yearly price, then the launch price with your team code. Name the saving out loud.

• The 14-day free trial starts today. The code locks the yearly plan.

• The window is 72 hours.

Why annual and not monthly. The hardest phase is not week 1, it is weeks 3 to 8. The first burst of enthusiasm has gone, the new habit has not formed yet, and on a monthly plan that is exactly when a cancellation decision comes up every single month. An annual plan takes that decision out of the critical phase. The partner stays long enough for the way of working to settle.

Why a 72 hour deadline. Without a deadline people do not decide, they postpone. The deadline moves the decision into the window where enthusiasm is highest. It also has a practical side effect. If the launch is on Sunday evening, the deadline falls on Wednesday evening, which is day three of the implementation sprint. Decision and first implementation coincide. Anyone who attended two workshops in those three days decides based on experience rather than on a promise.

How it gets placed. At the very end, after the proof and after the next steps. Not as a sales block but as information: these are the terms, this is the code, this is the deadline, here is the link. Six minutes, no persuasion, no repeating the same arguments. The evening was a direction setting decision by the leadership circle, not a sales conversation, and that must not flip at the end.

Non negotiable rules:

• The deadline is stated to the minute and posted in writing in the community.

• The deadline does not get extended. Not for individuals, not for special cases, not on request. A deadline extended once devalues every deadline you set for the next several years, and the team remembers that longer than they remember the offer.

• Everyone pays the same, leaders included. Say that out loud.

• No income claims in connection with the offer. The benefit is justified through way of working, not through earnings.

• Anyone who cannot or does not want to take it stays a full member of the team. If the non buyers feel second class on day 4, you have burned culture for short term revenue

The one ask, word for word

“Here is your one action, right now, while we are together. Click the link in the chat and create your SAGA account. That is it. Do not wait until later, because later is where good intentions go to die — and the 72-hour price goes with them. Create your account now, and tomorrow we set it up together in the workshop. Go ahead. I will wait.”

Part 4 — After the call

This is where the real work starts. Three days, one workshop each day, each workshop offered twice on the same day, once in the morning and once in the evening. The reason is mundane and important. Part of the team works during the day, another part is putting children to bed in the evening. Offer one slot and you predictably lose half of them.

Post-call message (send the moment the call ends)

Thank you for joining our SAGA launch today.

Your next steps:

1. Create your SAGA account today: [SIGNUP LINK]

2. Use this discount code for the yearly plan: [CODE] — 72 EUR / USD off, valid for 72 hours.

3. Join the hands-on setup workshop tomorrow at [TIME]: [WORKSHOP LINK]

4. Before the workshop, go through the onboarding inside SAGA.

5. Anything unclear? Reply here and we will help.

The homework

Everyone goes through the onboarding before the workshop. This is the small thing that decides whether the workshop works. People who have walked through onboarding arrive with real questions. People who have not arrive needing a demo, and you end up running the launch call twice.

Implementation sprint

Day 1: set up. Import or add contacts, understand the pipeline, schedule the first follow-up. Hands on, everyone does it live, no presentation.

Day 2: work. Use the library, send material, set up the keyboard app, install the app on the phone.

Day 3: community. One single welcome post gets pinned. Everyone introduces themselves in the comments under that post and greets two other people. Deliberately no individual posts, otherwise attention fragments immediately. This pattern becomes permanent: when a new partner starts in future, their upline introduces them under the welcome post.

Homework after day 3: complete onboarding in the system.

What to expect: questions at a level that will surprise you. Where do I find the app store. How do I download an app. My storage is full. That is normal with an audience that has no technical background and it is not a sign that something is going wrong.

How you handle it determines the culture of the next several months. Two things at once. Point consistently to the help pages in the system so people learn where help lives. And still answer kindly when somebody is stuck. Self reliance is the goal, but it does not get created by turning people away. A partner who feels stupid on their first attempt does not ask a second time.

On top of that, in the first days: 30 minutes of open power hour daily. No agenda, no presentation. Come in, use the system, ask questions. The only purpose is safety.

• Check who actually created an account — message the ones who did not.

• Follow up personally with anyone who was on the call but silent in the chat.

• Celebrate the first people who fill their pipeline, publicly. That is what makes the rest copy it.

FAQ — What your team will ask

How far ahead do we need to request the launch?

At least [X days] before your call, so your code is ready before you announce anything.

Does the code work on monthly plans?

No. Yearly plans only. That is deliberate — the launch is about committing to one system for the year, not trying it for a month.

Can someone start the free trial and still use the code?

Yes. Start the 14-day trial on the day of the call and lock the yearly plan with the code before the 72 hours close.

What if someone misses the 72 hours?

They can still join on the free version or the regular yearly price. The launch price does not come back, which is exactly why it works on the call.

Can we run the call in another language?

Yes. The deck is yours to translate once you have made your copy.

Can we run a second launch for a sub-team later?

Yes — request it the same way and you get a code for that launch.

Ready when you are

Pick your date, request your launch, and take your copy of the deck. Everything after that is just working through the checklist.

• Request your launch to the SAGA team (if you have not the contact write to support)

• Copy the presentation