Prompt Details
Model
Chat - (gpt-5.5)
Token size
314
Example input
[TOPIC]: Why hiring too early almost killed our startup
[PROFESSION]: SaaS Founder
[AUDIENCE]: Startup founders, operators, and early-stage entrepreneurs
[INSIGHT]: Premature scaling creates operational complexity before product-market fit exists
[TONE]: Direct/Blunt
Example output
✍️ LinkedIn Post
Hiring felt like progress.
Until payroll became our biggest problem.
At one point, we had 11 people on the team while still changing our product positioning every few weeks.
That sounds ridiculous now.
But when revenue started growing, hiring felt like the “grown-up” thing to do.
More sales calls?
Hire.
Need faster development?
Hire.
More customer requests?
Hire again.
The problem was we scaled headcount before we scaled clarity.
Within 6 months:
Burn increased 3.4x
Meetings exploded
Product decisions slowed down
Communication became messy
And nobody could clearly explain our core positioning anymore
(PAUSE FOR EFFECT)
What finally changed things wasn’t another hire.
It was simplification.
We cut projects.
Reduced meetings.
Focused on one ICP.
Fixed onboarding.
Improved retention.
Revenue grew faster after the team got smaller.
That experience completely changed how I think about scaling.
A lot of startups don’t fail because they move too slowly.
They fail because complexity grows faster than clarity.
Premature scaling feels productive in the short term.
But operational weight compounds quickly when fundamentals aren’t stable.
Which “growth decision” hurt your business most early on?
1 = Hiring too early
2 = Expanding too many offers
3 = Chasing too many channels
#Startups #SaaS #Entrepreneurship
By purchasing this prompt, you agree to our terms of service
GPT-5.5
High-performing LinkedIn post engineered to the exact format the 2025 algorithm rewards — scroll-stopping hook, correct paragraph structure, and engagement prompt.
...more
Added 2 weeks ago
