if your launch post starts with "excited to announce", read this
nobody is excited for you yet
they don't know you
before:
"excited to announce acme, an ai-powered platform for modern teams"
after:
"every friday i rewrote the same client report by hand. so i built a thing that writes it from the spreadsheet."
the second one names a pain people already have
sounds like a person, not a press release
and makes people ask "how"
announce the problem, not the product
1
1
19
one thing we got right building empyre
when the agents need something from you, you get one request
"action required"
it pauses that one task
everything else keeps moving
a lot of automation stalls the moment it needs you
and the founder becomes the bottleneck of their own system
if your automation needs you every hour, it's a to-do list with extra steps
1
2
29
"would you use this?" is the worst question you can ask a user
everyone says yes
it costs them nothing to be nice
ask these instead:
what did you try before this
what did it cost you when it broke
what would you pay to never deal with it again
compliments are free
answers to these aren't
29
most cold dms die in the first line
"hey! hope you're doing well" = archived
here's how i'd write one to someone who could actually use your product
1. open with something specific they posted, not a compliment
2. one sentence on the problem you think they have
3. ask a question they can answer in 5 words
4. no link, no pitch, no calendar invite
you're not selling in message 1
you're earning message 2
41
most of your churn happens before the user ever starts
they sign up
see an empty dashboard
close the tab
you counted them as a user
they never were
fix the first 60 seconds before anything else
- one clear first action
- something already done for them before they type
- a result they can see on screen 1
your signup page brought them in
your empty state sent them home
47
if your bio starts with "helping", read this
nobody follows a job description
they follow a result they want
"helping founders grow" says nothing
"i show solo founders how to get their first 100 users" says who it's for and what they get
who it's for
what they walk away with
one line of proof if you have it
rewrite it tonight. cheapest growth fix you'll make this week
1
1
56
building empyre in public, one rule we set early
if you leave, you take everything with you
your code lives in your own github
your customers pay into your own stripe
we take no cut of that
i don't want people staying because leaving is painful
i want them staying because it's still worth it every month
1
1
48
if i launched something this week and had no idea what to charge, here's how i'd figure it out
1. pick one price that feels slightly too high
2. say it to the first 10 people who show real interest
3. watch what they do, not what they say
4. if nobody pushes back, it's too low
5. if everyone walks, fix the offer before you touch the price
free users tell you what's interesting
paying users tell you what's valuable
37
your landing page isn't confusing because of the design
it's confusing because it lists features instead of the result
quick test
- show it to someone for 5 seconds
- close the tab
- ask what it does and who it's for
if they can't answer, rewrite the headline before you touch anything else
1
1
54
honest question for anyone building something right now
where did your first 10 users actually come from
- friends and people you already knew
- one post that took off
- cold dms
- a community you were already part of
- something else
most growth advice skips this part
curious what actually worked for you
1
1
44
building empyre in public, one design rule i care about a lot
if the agents need something from the founder, it comes as one request
not 12 notifications
not a dashboard full of red dots
one ask, and only that task pauses
everything else keeps moving
most tools interrupt you to look busy
the good ones only interrupt you when it actually matters
1
42
how i'd get the first 100 people to see a product with zero audience
1. pick one platform, not five
2. find 10 accounts your buyers already follow
3. leave a useful reply on their posts every day
4. post once a day about the problem, not the product
5. dm the people who reply to you twice
it's slow for 3 weeks
then the same names start showing up
27
sentinel.empyre.site one shottet with empyre.
1
21
if i had to launch something to people who don't know me yet, here's how i'd spend the first 14 days
day 1-3: write the one problem it solves in a sentence a stranger gets
day 4-7: find 20 people complaining about that problem and talk to them
day 8-10: show them the fix, ask what's missing
day 11-14: ask the ones who care to pay before building anything else
launch to people, not to a feed
1
22
building empyre in public from vienna, one thing i keep coming back to
most builder tools stop at "here's your code"
but launch day is day 1, not the finish line
after it someone still has to
- post every day
- answer support
- follow up with leads
- check the numbers
that's what we're building for: 8 agents that keep running the business after the first build
the code was never the hard part
1
26


