It finally came to a point where I felt an irresistible urge to join the program. And I remember I was on the landing page 10 minutes before the program closed.
1/ One of the best things I did in 2020 was to join a growth marketing program called @growclass
I’d seen it hover around online, I saw some friends talking about it. But I thought, wow, that looks great but it’s too expensive for me at the moment.
[continue thread ...]
It finally came to a point where I felt an irresistible urge to join the program. And I remember I was on the landing page 10 minutes before the program closed.
I was inspired by others to raise my prices significantly. Now my prices are triple what they were when I first started (and waaaay undercharging).
But the copywriting and website tear downs have made a big change for me.
It inspired me to build better resources for my programs.
As a solo founder, it’s extremely lonely, whether you’re seeing wins or struggles.
Not too many people in my life really “get it”
In my second, I had 10 students paying $400-525 each.
Today I’m about to close my next cohort starting on Saturday January 9th with 10 students paying $650-750 each.
Largely due to my shift in language and copywriting and how I talk about my programs (which is language I now use on my sales calls too).
You won’t regret it!
Feel free to DM me for any more info!
https://t.co/6eICrvoQcE
More from Marketing
eComm and D2C will be acutely impaired by the ATT opt-in mechanic coming to iOS (rumored made mandatory in March). ATT doesnt exclusively impact app advertisers, & in fact may disproportionately damage eComm and D2C. Some thoughts on how those advertisers should prepare (1/X)
2/ In the @MobileDevMemo 2020 mobile advertising predictions post, I posit that D2C ad spend may drop by as much as 50% in Q2 2020. FB revealed in December that app-to-web campaigns will be governed by ATT opt in, severely limiting campaign efficiency
3/ FB had only previously discussed ATT in terms of app campaign relevance. This new revelation likely stemmed from further instructions from Apple following FB's initial guidance
4/ FB affirmed in Dec that app-to-web campaigns will be: conversion event limited, aggregated at campaign level, and limited wrt attribution windows (default: 7-day click). This effectively replicates the privacy treatment of app campaigns on app-to-web campaigns
5/ Adam Lovallo from https://t.co/baV6VrUW7E describes 28-day click / 1-day view the "gold standard" for D2C. Why would FB change the default to 7-day? Because it is aggregating conversions at the campaign level -- universally, with what it is calling Aggregated Event Measurement
2/ In the @MobileDevMemo 2020 mobile advertising predictions post, I posit that D2C ad spend may drop by as much as 50% in Q2 2020. FB revealed in December that app-to-web campaigns will be governed by ATT opt in, severely limiting campaign efficiency
3/ FB had only previously discussed ATT in terms of app campaign relevance. This new revelation likely stemmed from further instructions from Apple following FB's initial guidance
4/ FB affirmed in Dec that app-to-web campaigns will be: conversion event limited, aggregated at campaign level, and limited wrt attribution windows (default: 7-day click). This effectively replicates the privacy treatment of app campaigns on app-to-web campaigns

5/ Adam Lovallo from https://t.co/baV6VrUW7E describes 28-day click / 1-day view the "gold standard" for D2C. Why would FB change the default to 7-day? Because it is aggregating conversions at the campaign level -- universally, with what it is calling Aggregated Event Measurement
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.