SAGA · Team Launch Preparation Guide
Everything you need to run a launch call that makes SAGA the way your team works — not just another tool they signed up for. Read this once, then work through it in order. It takes about two weeks of light preparation.
Last updated About 3 hours ago
“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.
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
Your date. Pick the call first, then put the workshop the very next day while the energy is still there.
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.
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.
Change these — Make it yours:
Team name, presenter name
Your currency and price
Your discount code (to be asked to the SAGA team)
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.
Your checklist
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
One week before
[ ] Make your copy of the presentation and fill in details
[ ] Send leaders the four-line template
[ ] Announce the call to your team — date, time, and that it matters
[ ] 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 2 — The call (40 minutes)
Five sections
Plus live Q&A at the end.
Five rules that decide how it lands
Every demo beat is before and after. Never a feature on its own.
Your team is the star. SAGA is the vehicle.
One recommended path. Do not teach four price tiers on a live call.
One sharp ask. Buying is the ask; the workshop is the follow-through, not a competing action.
Nobody is excluded. Mention the free version so the whole team stays together.
How to present the offer
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.
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 3 — After the call
Post-call message (send the moment the call ends)
Thank you for joining our SAGA launch today.
Your next steps:
Create your SAGA account today: [SIGNUP LINK]
Use this discount code for the yearly plan: [CODE] — 72 EUR / USD off, valid for 72 hours.
Join the hands-on setup workshop tomorrow at [TIME]: [WORKSHOP LINK]
Before the workshop, go through the onboarding inside SAGA.
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.
In the week after
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)