The SAT Launch Identity Framework
Launch bigger by becoming a scientist, an athlete, and a technician
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 7
- Confidence
- 85%
SAT is a three-part identity framework for anyone launching a product or offer. As a Scientist, you treat every launch as an experiment: you name the variables (page build time, funnel structure, email sequence, offer stack), change one at a time, and read the outcome instead of internalising it as fear or embarrassment. As an Athlete, you accept the training horizon: the people whose results inspire you practised for a decade or more before the visible win, so you commit to repetition in the dark rather than expecting a trophy from a first attempt. As a Technician, you accept that you are the doer: you build the lead pages, funnels, sequences, and webinars yourself, because learning the work is what generates the revenue and the competence to hire it out later. Adopt all three or the launch collapses under the weight of one bad result.
Origin
Jasmine Star built the framework after hosting a mastermind of six- and seven-figure entrepreneurs and later sitting in a venture-backed executive cohort, discovering that her launch methodology, refined over eight years of bootstrapped launches, was not common practice in either room.
Core principles
- 01A launch is a test, not a verdict on your worth.
- 02The goal is not to launch fast, it is to launch often.
- 03Small tweaks to single variables compound over many launches.
- 04Visible success is preceded by years of invisible practice.
- 05Nobody comes to save you until you have saved yourself.
- 06Doing the work yourself is what earns you the right to delegate it.
How to run it
- 1
Ship the hypothesis into the wild
Treat your first launch as an untested hypothesis that must reach real buyers before it can teach you anything. Getting the offer out is the entry price for data.
Pro tip Expect the first build to take absurdly longer than planned; that duration is itself a variable worth recording.
Watch out Perfecting the product before launch delays the only feedback that improves it.
- 2
Name your variables
List every element of the launch you could change to produce a different outcome: the lead page, the email sequence, the funnel, the upsell, the downsell, the VIP tier.
Pro tip Write the list immediately after cart close while friction is still fresh in memory.
- 3
Change one variable per launch
Run each launch as a single test rather than a full rebuild, so you can attribute any change in result to a specific cause.
Pro tip Track the same handful of numbers every time: leads, conversion, cash on hand, projected revenue, lifetime value.
Watch out Changing everything at once destroys attribution and teaches you nothing.
- 4
Convert launching into a lifestyle, not an event
Replace the goal of launching fast with the goal of launching often. Frequency is what produces the compounding improvements.
Pro tip Put the next launch on the calendar before the current one closes.
Watch out Treating a launch as a one-off makes a poor result feel terminal.
- 5
Adopt the athlete's training horizon
Accept that the people whose results inspire you trained for well over a decade before the visible win, and commit to practice that is unglamorous and unwitnessed.
Pro tip Judge yourself on reps completed this quarter, not on the trophy you have not won yet.
Watch out Comparing your year one to someone's year fourteen is the fastest route to quitting.
- 6
Do the technician work yourself
Build the funnels, sequences, webinars, and pages with your own hands at least once so you understand every moving part of your own machine.
Pro tip Research gaps as they appear rather than waiting for a course to teach you everything first.
Watch out Do not treat 'do the work' as licence to burn your health or your holidays; it is a decision about sequence, not sacrifice.
- 7
Hire out of earned revenue
Once a launch produces real money, use it to bring in help for the parts you now understand well enough to delegate and to judge.
Pro tip Delegate the task you have personally done the most times first.
Watch out Hiring before you understand the work means you cannot evaluate the hire.
In the wild
Launching her first Instagram-for-business course, Jasmine and her husband ran the entire launch themselves with no team. Setting up a single lead acquisition page and connecting it to their email service provider consumed six hours, one item on a very long build list. Rather than reading that as evidence of incompetence, she logged the duration as a variable: something known, measurable, and reducible on the next launch once the process had been learned once.
→ The build time became a tracked variable to compress on subsequent launches rather than a reason to abandon the launch model.
Planning her first ever launch during a trip meant to be a rest, Jasmine sat in a hotel lobby with twenty funnel emails still unwritten and no one available to help. She wrote all of them in a single day. The sequence was, by her own account, not particularly good, but it existed, and building it herself taught her the mechanics she later hired a team to run.
→ The funnel shipped, and the technician-level knowledge became the basis for later delegating launch execution.
Common mistakes
Reading one weak launch as a final verdict
Founders internalise a disappointing first launch as fear, failure, and embarrassment, then refuse to relaunch. The result is that the only mechanism that would have improved the offer, repetition, is switched off.
Optimising for speed instead of frequency
Chasing a single fast, perfect launch removes the ability to isolate and test variables. Frequent launches with small tweaks outperform rare, heavily engineered ones.
Skipping the technician phase
Waiting for a team before building funnels and sequences leaves you unable to specify, evaluate, or fix the work once you can afford to hire it out.
Is it for you?
Best for
Bootstrapped creators and service providers launching their first few digital products or memberships.
Not ideal for
Venture-backed teams with staff and budget who can buy their way past the manual execution phase.
From the transcript
“S you need to be a scientist. A you need to be an athlete, and t you need to be a technician.”
“A variable is a thing you can change to create a different outcome.”
“your objective is not to launch fast. Your objective is to launch often and make small tweaks.”
From the episode
How to Avoid Self-Sabotaging Your Launch