Written example posts for founders and experts, each with the hook pulled out, the structure step by step, why it works, and a score from our free grader.
Each example shows the hook (the first line, the part people see before "see more"), the structure, why it works, and a score. The score is worked out on this page by the same grader you can use on your own drafts. Every post is a written example with made up names. None is a real person's post.
Story posts
01
The lost customer
100/ 100
Written example. Could be by: Founder of a 12 person design agency
The post
We lost our biggest client in March. It was 40% of our revenue.
They didn't leave because of bad work. They left because we stopped calling.
For two years we sent great designs and short emails. Their new marketing lead didn't know us. When budgets got tight, we were easy to cut.
So we changed one thing.
Every client now gets a 20 minute call each month. No deck. We ask what's hard and what's next.
It felt like a small fix. But in the six months since, we have not lost a single client. Two of them gave us more work.
Great work keeps a client for a year. A real relationship keeps them for five.
When did you last call your best client just to listen?
The hook (63 characters)
We lost our biggest client in March. It was 40% of our revenue.
Structure
Hook: a painful number and a loss
Twist: the reason was not the work
Turn: one small change
Result: what happened after
Close: a question for readers
Grader checks
Your first line fits above "see more" (63 characters).
The hook has a number, a question or "you".
Easy to read (about grade 1).
No stock phrases.
No hashtag clutter.
Why it works. It opens with a real cost, then gives one fix any agency owner can copy tomorrow. The closing question invites people to share their own habit.
Written example. Could be by: Founder of an early stage software company
The post
My first hire quit after 3 weeks. It was my fault.
I hired Ana to help with customer support. I was so busy that I gave her a login, a short doc and said, "Ask if you need anything."
She didn't ask. She was new and didn't want to bother me. She spent three weeks guessing.
On her last day she told me, "I never knew if I was doing it right."
That line stayed with me.
For our next hire, I blocked two full days. We answered tickets side by side. I wrote down every question she asked. That list became our onboarding guide.
That hire is still with us, two years later.
If you are about to make your first hire, clear your calendar for their first week. It's the best time you'll spend.
The hook (50 characters)
My first hire quit after 3 weeks. It was my fault.
Structure
Hook: a short failure with a number
Story: what went wrong and why
Quote: the line that hurt
Turn: what they did differently
Close: direct advice to the reader
Grader checks
Your first line fits above "see more" (50 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. Owning the mistake makes the author easy to trust. The quote gives readers a moment they can feel, and the advice is simple to act on.
Written example. Could be by: Freelance copywriter
The post
I sent 50 cold emails last year. One reply changed my business.
Most of my emails were polished. Nice intro, links to my work, a clear offer. Almost nobody wrote back.
Then I tried something different with one founder. I rewrote the first line of his homepage and sent it with one sentence: "Here's a free idea, no strings."
He replied in an hour. We worked together for 8 months. He introduced me to 3 other founders.
What changed?
I stopped asking for their time and started giving them something useful first.
Now every cold email I send includes one small piece of real work. My reply rate is much higher, and the calls are warmer because they already know what I do.
What's the smallest useful thing you could send a dream client this week?
The hook (63 characters)
I sent 50 cold emails last year. One reply changed my business.
Structure
Hook: a number and a surprise
Setup: what did not work
Turn: one different approach
Lesson: give before you ask
Close: a question that prompts action
Grader checks
Your first line fits above "see more" (63 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. The contrast between 49 ignored emails and one reply makes the lesson stick. The ending question turns the story into a small challenge.
Written example. Could be by: Independent operations consultant
The post
I doubled my prices in 2025. I lost 1 client and gained my weekends back.
For years I priced like a beginner. I was scared that a higher number would scare people off.
Here's what really happened when I raised my rate:
The clients who stayed took my advice more seriously.
The new clients who signed were further along and easier to help.
I had time to do better work, so results got better too.
The one client who left was already a bad fit. We both knew it.
The lesson I keep learning: low prices don't just cost you money. They cost you focus.
If you've been thinking about raising your prices, start with your next new client. You don't have to change everything at once.
The hook (73 characters)
I doubled my prices in 2025. I lost 1 client and gained my weekends back.
Structure
Hook: a bold change with a number
Fear: why they waited
Evidence: three short outcomes
Lesson: one clear sentence
Close: a small first step
Grader checks
Your first line fits above "see more" (73 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It turns a scary decision into a small, safe step. The short list makes the benefits easy to scan.
Written example. Could be by: Product manager at a software company
The post
Our biggest customer asked for a feature. We said no. Here's why you should too, sometimes.
They wanted a custom report just for their team. It would take 6 weeks to build.
I asked one question: how many other customers need this?
The answer was zero.
So I called them. I explained that building it would slow down fixes that all of our customers needed, including them. Then I offered a simple export they could use in a spreadsheet.
They were not happy at first. But a month later, their team lead said the export worked better than the report would have.
The lesson: a yes to one customer is often a no to everyone else.
Saying no well is not about being rigid. It's about being clear on who you serve.
How do you decide which requests to say yes to?
The hook (91 characters)
Our biggest customer asked for a feature. We said no. Here's why you should too, sometimes.
Structure
Hook: a surprising no and a nod to the reader
Setup: the request and its cost
Turn: one question that decided it
Result: a better outcome
Close: the lesson and a question
Grader checks
Your first line fits above "see more" (91 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It gives product people permission to push back and shows how to do it kindly. The question at the end invites readers to share their own rules.
For my first 6 months as a manager, I ran one on ones wrong.
I used them for status updates. What did you finish? What's blocked? When will it ship?
It felt productive. But my team stopped telling me things that mattered. I found out someone was unhappy only when they quit.
A mentor gave me one rule: never ask about status in a one on one. That's what standups are for.
So I changed my questions:
What's taking more energy than it should?
What would you change about how we work?
How can I help this week?
The first few meetings were awkward. Then people started opening up. I heard about problems weeks earlier.
Your one on ones belong to your team, not to you. Let them lead.
The hook (60 characters)
For my first 6 months as a manager, I ran one on ones wrong.
Structure
Hook: admitting a mistake with a time frame
Problem: what went wrong
Advice: a rule from a mentor
Change: three new questions
Close: a clear takeaway
Grader checks
Your first line fits above "see more" (60 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. New managers see themselves in the mistake. The three questions are something readers can copy into their next meeting.
Written example. Could be by: Career coach for mid career professionals
The post
Your LinkedIn About section can be written in 20 minutes. Here's the simple way.
1. Start with who you help and how. One sentence. "I help small clinics book more patients" beats "Passionate professional."
2. Name the problem. What keeps your ideal client or boss up at night?
3. Give one proof. A real project with a before and after.
4. Share how you work. Two or three short lines.
5. List what people come to you for. Keep it to four items.
6. End with a next step. "Message me" or your email.
That's it. Six parts, plain words.
Most people write their About section like a cover letter. Write it like a note to one person you want to help.
Save this for when you update your profile.
The hook (80 characters)
Your LinkedIn About section can be written in 20 minutes. Here's the simple way.
Structure
Hook: a time promise and 'your'
Steps: six numbered parts
Example: good vs weak line
Tip: write to one person
Close: a save prompt
Grader checks
Your first line fits above "see more" (80 characters).
The hook has a number, a question or "you".
Easy to read (about grade 1).
No stock phrases.
No hashtag clutter.
Why it works. A clear time promise makes the task feel doable, and the numbered steps are easy to follow. Each step is short enough to act on right away.
Written example. Could be by: Founder of a B2B software startup
The post
How to run a customer interview in 30 minutes, without leading the witness:
1. Ask about the last time. "Tell me about the last time you did your month end close." Real stories beat opinions.
2. Don't pitch. Not once. If you mention your product, they'll just be polite.
3. Ask what they tried. People who tried nothing don't have a real problem.
4. Ask what it cost. Time, money or stress. Get a number if you can.
5. Stay quiet. After they answer, wait 3 seconds. The best details come after the pause.
6. End with, "Who else should I talk to?"
I've run over 60 of these. The ones where I talked the least taught me the most.
What's your best interview question?
The hook (75 characters)
How to run a customer interview in 30 minutes, without leading the witness:
Structure
Hook: a time frame and a clear promise
Steps: six rules, each with a reason
Proof: the author's own experience
Close: a question for readers
Grader checks
Your first line fits above "see more" (75 characters).
The hook has a number, a question or "you".
Easy to read (about grade 1).
No stock phrases.
No hashtag clutter.
Why it works. Each step has a short reason, so readers learn the thinking and not just the rule. The ending question pulls in experienced founders to add their own.
Written example. Could be by: Account executive at a software company
The post
Your cold messages get ignored for one reason: they are about you.
Here's the simple format I use now:
Line 1: Something specific about them. A post they wrote, a hire they made, a product they launched.
Line 2: A problem you think they might have, stated as a question.
Line 3: One sentence on how you've helped someone like them.
Line 4: A small ask. "Worth a quick chat?" not "Can we book 45 minutes?"
Four lines. Under 60 words.
Before I switched, most of my messages got no reply. Now I get real conversations most weeks, and the people who reply already know why I reached out.
Try it on 5 people this week and see what happens.
The hook (66 characters)
Your cold messages get ignored for one reason: they are about you.
Structure
Hook: 'your' and a blunt diagnosis
Format: four lines, one job each
Rule: a word limit
Proof: the author's before and after
Close: a small challenge
Grader checks
Your first line fits above "see more" (66 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It names why messages fail before showing the fix. The format is short enough to copy into a note.
Written example. Could be by: B2B marketer at a small software company
The post
You don't need to post on LinkedIn every day.
I tried it for 3 months. My posts got worse. I was writing to fill a slot, not because I had something to say.
So I cut back to two posts a week. Each one took more thought. I used real stories from customer calls. I wrote a draft, waited a day, then cut it in half.
What happened: more comments from the people I wanted to reach. More messages from buyers. Less stress.
Posting often can work. But only if you have that much to say.
If posting feels like a chore, post less and make it better. Your readers will notice.
How often do you post, and why that number?
The hook (45 characters)
You don't need to post on LinkedIn every day.
Structure
Hook: 'you' and a claim that goes against advice
Proof: what happened when they tried
Change: fewer, better posts
Nuance: when the common advice works
Close: a question for readers
Grader checks
Your first line fits above "see more" (45 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. It pushes back on common advice while still being fair to it. The personal test makes the claim believable without any made up data.
Written example. Could be by: Recruiter for early stage startups
The post
Stop hiring for culture fit. Here are 3 reasons.
1. It usually means "someone like us." Same school, same jokes, same way of thinking. That feels comfortable. It also means blind spots.
2. Nobody can define it. Ask five people on your team what culture fit means and you'll get five answers.
3. It hides bias. When a hiring manager says "not a fit," there's often no real reason behind it.
What I ask founders to hire for instead: values fit.
Do they care about the same things you do? Honesty, pace, craft? Those can be tested with real questions.
Values fit gives you a team that agrees on what matters and disagrees on how to get there.
That's the team you want.
The hook (48 characters)
Stop hiring for culture fit. Here are 3 reasons.
Structure
Hook: a blunt instruction with a number
Reasons: three short points
Alternative: what to do instead
Close: the payoff in one line
Grader checks
Your first line fits above "see more" (48 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. It gives a strong opinion, backs it with clear reasons, then offers a better path. Readers leave with something to change, not just something to argue about.
Your niche is probably too broad. Mine was for 2 years.
I used to say, "I help small businesses with their finances." Everyone nodded. Nobody hired me.
Then I got specific: "I help consumer brands between 1 and 10 million in revenue plan their cash."
Fewer people fit. But the ones who did said, "That's exactly me."
Here's the fear that keeps most of us broad: we think narrow means fewer clients.
In my case, it meant more. Referrals got easier because people knew exactly who to send me. My content got sharper because I wrote for one kind of reader.
Narrow is scary for about a month. Then it's a relief.
What would your one sentence look like if you had to cut half your market?
The hook (55 characters)
Your niche is probably too broad. Mine was for 2 years.
Structure
Hook: 'your' plus a personal admission
Before: a vague line that did not work
After: a specific line that did
Fear: why people stay broad
Close: a question that makes readers try it
Grader checks
Your first line fits above "see more" (55 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. The before and after lines show the idea instead of explaining it. The closing question asks readers to do the exercise on the spot.
Written example. Could be by: Cofounder of a finance software startup
The post
42 customers asked us for the same thing this year. Today it's live.
You can now match receipts to card spend from your phone. Snap a photo, and it lands on the right expense.
Why did it take so long? Honestly, we got it wrong twice. The first version was too slow. The second one missed receipts from gas stations, which turned out to be half of what our customers buy.
Version three works. Our beta group used it for 6 weeks, and they've stopped emailing receipts to their finance team.
If you're a customer, it's in your app today. No setup needed.
If you're not, and your team still chases receipts at month end, message me. I'll show you in 10 minutes.
Thank you to everyone who kept asking. You made this better.
The hook (68 characters)
42 customers asked us for the same thing this year. Today it's live.
Structure
Hook: a number that shows demand
What: the feature in one line
Honesty: what went wrong first
Proof: the beta result
Close: two next steps and a thank you
Grader checks
Your first line fits above "see more" (68 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. It skips the hype and leads with customer demand. Admitting the failed versions makes the launch feel honest.
Written example. Could be by: Freelance brand designer
The post
After 3 years of custom projects, I'm opening a fixed price brand kit.
Here's why. Half the founders who contact me can't afford a full brand project yet. They need something good enough to launch, not perfect.
So here's what the kit includes:
A simple logo and a backup version
Two fonts and a color set
A one page guide on how to use them
Social and email templates
It takes two weeks. The price is on my site, and it doesn't change.
I tested it with 4 founders last month. All four launched on time, and two have already come back for more work.
If you're about to launch and need to look real without a big budget, message me. I'm taking 5 spots in November.
The hook (70 characters)
After 3 years of custom projects, I'm opening a fixed price brand kit.
Structure
Hook: a change with a number
Why: the problem it solves
What: a short list of what is included
Proof: a small test
Close: a clear offer with a limit
Grader checks
Your first line fits above "see more" (70 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. It explains who the offer is for before listing what's in it. The spot limit gives a reason to act without sounding pushy.
Written example. Could be by: Head of sales at a mid size software company
The post
I started a podcast because I was tired of sales advice from people who don't sell. Episode 1 is out today.
Every episode, I talk to one sales rep about one deal. Not a win story. The messy middle. What almost went wrong and how they saved it.
In the first episode, a rep named Carla walks through a 9 month deal with a hospital. Three buyers changed jobs during it. She tells us what she did each time.
No guests selling courses. No big theories. Just real deals.
It's 25 minutes, and you can finish it on a commute.
If you carry a quota, I think you'll get one idea you can use this week.
The link is in the first comment. And if you have a deal story, message me. I'd love to have you on.
The hook (107 characters)
I started a podcast because I was tired of sales advice from people who don't sell. Episode 1 is out today.
Structure
Hook: a reason for starting and a launch
Format: what each episode covers
Example: the first story
Promise: what listeners get
Close: a link and an invite to guests
Grader checks
Your first line fits above "see more" (107 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. It gives a clear reason the show exists and a taste of the first episode. The guest invite turns the launch into a conversation.
Written example. Could be by: Independent product designer
The post
One year ago I left my job to work for myself. Here are 5 things I didn't expect.
1. The work was the easy part. Finding it was hard.
2. My first 3 clients all came from old coworkers. My network was worth more than my portfolio.
3. I underpriced for 6 months. Then I stopped.
4. I missed having a team more than I missed a paycheck.
5. Saying no got easier after my first bad project.
The year was harder than I planned and better than I hoped.
Thank you to everyone who sent work my way, gave feedback or just checked in. It mattered.
If you're thinking about going solo, message me. I'm happy to share what I'd do differently.
The hook (81 characters)
One year ago I left my job to work for myself. Here are 5 things I didn't expect.
Structure
Hook: a time mark and a promise of surprises
List: five honest lessons
Reflection: one balanced line
Thanks: to the people who helped
Close: an offer to help others
Grader checks
Your first line fits above "see more" (81 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. It turns a personal milestone into lessons others can use. The offer at the end makes it generous instead of a brag.
Written example. Could be by: Founder of a scheduling tool for clinics
The post
We just signed our 100th customer. The first 10 took us a year.
I want to share how slow the start was, because most milestone posts skip that part.
Customer 1 was a friend's dental clinic. We set it up in person.
Customers 2 through 10 came from me calling clinics one by one.
Customers 11 through 50 came mostly from referrals.
Customers 51 through 100 came from a partner program with two clinic software vendors.
Each stage needed a different way to grow. What worked for the first 10 would never have gotten us to 100.
If you're stuck at your first 10, that's normal. It's the hardest part.
Thank you to every clinic that took a chance on a small team. We don't take it lightly.
The hook (63 characters)
We just signed our 100th customer. The first 10 took us a year.
Structure
Hook: a milestone number and the slow start
Setup: why share the slow part
Stages: how each group of customers came in
Lesson: each stage needs a new method
Close: encouragement and thanks
Grader checks
Your first line fits above "see more" (63 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It celebrates without bragging by showing the slow, honest path. Founders early on get comfort and a clear map.
Written example. Could be by: Newly promoted engineering manager
The post
Today is my first day as an engineering manager. 4 years ago I was a nervous junior engineer.
I didn't get here alone. A few people changed how I work:
Rafael, who taught me to ask for help before I was stuck for a week.
Sara, my manager, who let me lead a project before I felt ready.
Aisha, who reviewed my code with more patience than I deserved.
I'm nervous again, and that feels right. Managing people is a new skill, and I'll get some things wrong.
Here's my promise to my new team: I'll listen more than I talk, and I'll tell you the truth even when it's hard.
If you're a new manager too, what's one thing you wish you'd known in your first month?
The hook (93 characters)
Today is my first day as an engineering manager. 4 years ago I was a nervous junior engineer.
Structure
Hook: a new role and a then and now contrast
Credit: three people and what they taught
Honesty: admitting nerves
Promise: to the new team
Close: a question for peers
Grader checks
Your first line fits above "see more" (93 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. It shares credit in a specific way, which makes the thank you feel real. The closing question invites advice instead of congratulations.
Written example. Could be by: Technical cofounder of a 3 person startup
The post
We're hiring our first engineer. Here's what the job is really like, so you can decide fast.
The good:
You'll own real parts of the product from day one.
You'll talk to customers every week.
You'll have a big say in how we build.
The hard:
We're 3 people, so there's no one to hand the boring work to.
The product changes often.
Some weeks you'll do support.
What we're building: a tool that helps clinics answer missed calls. 30 clinics use it today.
What we need: someone who has shipped a web app end to end and likes working close to users.
Salary range and equity are in the job post. Remote, US time zones.
If this sounds like your kind of job, message me directly. I read every note.
The hook (92 characters)
We're hiring our first engineer. Here's what the job is really like, so you can decide fast.
Structure
Hook: the role and a promise of honesty
Good: three real upsides
Hard: three real downsides
Context: what the company does
Close: who fits and how to apply
Grader checks
Your first line fits above "see more" (92 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. Listing the hard parts helps the right people say yes and the wrong people pass. Sharing the pay range up front shows respect for applicants' time.
Written example. Could be by: Head of operations at a growing software company
The post
Do you love fixing customer problems more than closing tickets? We're hiring a support lead.
Our support team is 4 people. They're good, and they're tired. We need someone to help them work smarter, not just faster.
In your first 90 days you would:
Read a month of tickets and find the top 5 causes.
Work with product to fix at least 2 of them.
Build a simple weekly report the whole company reads.
You might be a fit if:
You've led a small support team before.
You write clear, kind emails.
You care about why problems happen, not just how fast they close.
Full time, remote. Pay range is in the post.
If you know someone who fits, please tag them. Referrals mean a lot to a small team like ours.
The hook (92 characters)
Do you love fixing customer problems more than closing tickets? We're hiring a support lead.
Structure
Hook: a question the right person says yes to
Context: the team and the need
First 90 days: three concrete goals
Fit: three traits
Close: ask for referrals
Grader checks
Your first line fits above "see more" (92 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. The opening question filters for the right candidate. Clear first 90 day goals help people picture the job.
Written example. Could be by: Data team lead at an online store
The post
We're hiring 2 data interns for next summer. No prior job needed.
What you'll do:
Answer real questions from our marketing and operations teams.
Write SQL every day, with help.
Present one project to our leadership team in August.
What we look for:
You're curious about why numbers change.
You've built something, even a class project.
You ask questions early.
What you'll get:
A paid 10 week internship.
A mentor who meets with you every week.
Real work that ships, not busy work.
Last year's intern found a bug in our returns report in week three. Our team still uses the fix.
Applications open next week. Students and career changers are both welcome. Message me with questions.
The hook (65 characters)
We're hiring 2 data interns for next summer. No prior job needed.
Structure
Hook: the role and a barrier removed
Do: what the work is
Look for: simple traits
Get: pay, mentor and real work
Proof: a past intern story
Close: when and how to apply
Grader checks
Your first line fits above "see more" (65 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. Removing the experience barrier in the first line widens the pool. A real story from a past intern shows the work matters.
I cancelled 7 software subscriptions this year. I don't miss any of them.
Here's what I cut:
1. A project tool. A shared doc with a checklist works for my size.
2. A second calendar app. The default one does enough.
3. A fancy invoice tool. My accounting software sends invoices too.
4. A social scheduling app. I post twice a week. I can do that by hand.
5. A stock photo plan. I use my own photos now.
6. A note app I never opened.
7. A course I bought and never started.
The savings are nice. But the bigger win is fewer logins and fewer places to check.
Most tools are built for teams. If you work alone, you probably need fewer than you think.
What's one subscription you could cancel today?
The hook (73 characters)
I cancelled 7 software subscriptions this year. I don't miss any of them.
Structure
Hook: a number and a surprising outcome
List: seven short items with reasons
Insight: the real win
Close: a question that prompts action
Grader checks
Your first line fits above "see more" (73 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. Each item is short and relatable, so readers check their own tools as they scroll. The ending question turns it into a small task.
Written example. Could be by: Recruiter for software companies
The post
5 questions you should ask at the end of every job interview:
1. "What does a great first 90 days look like?" It shows you're thinking about results.
2. "What's the hardest part of this job?" The honest answer tells you a lot.
3. "Why is this role open?" New role, or someone left? Both answers are useful.
4. "How does the team give feedback?" You'll learn if feedback is regular or rare.
5. "What would make you say yes to hiring me today?" Brave, but it gives you a chance to answer any doubts.
Most candidates ask about perks at the end. These questions show you're serious and help you decide if you want the job.
Save this for your next interview.
The hook (61 characters)
5 questions you should ask at the end of every job interview:
Structure
Hook: a number and 'you'
List: five questions, each with a reason
Contrast: what most people ask
Close: a save prompt
Grader checks
Your first line fits above "see more" (61 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. Each question comes with a short reason, so the list teaches and not just tells. It's easy to save and use later.
Written example. Could be by: Freelance marketing consultant
The post
Where my first 10 clients came from. None of them came from ads.
1. A former boss who needed help on a side project.
2. A friend of that boss.
3. A coworker who had moved to a new company.
4. Someone who read a post I wrote about email.
5. A reply to a question I answered in a forum.
6. A client referral from client 1.
7. A founder I met at a small local meetup.
8. A cold email where I sent a free idea first.
9. Another post, this time about pricing.
10. A referral from client 4.
The pattern: most came from people who already knew me or saw my work. Only one came from a truly cold message.
If you're starting out, tell every old coworker what you do now. It's awkward for a day and useful for years.
The hook (64 characters)
Where my first 10 clients came from. None of them came from ads.
Structure
Hook: a number and a surprise
List: ten real sources
Pattern: what most had in common
Close: one clear piece of advice
Grader checks
Your first line fits above "see more" (64 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. A full list feels honest and specific. The pattern at the end turns ten facts into one action.
Written example. Could be by: Founder of a B2B software startup
The post
Do you show prices on your website, or ask people to book a call?
We're debating this right now.
The case for showing prices: buyers want to know before they talk to anyone. It saves everyone time.
The case for hiding them: our deals vary a lot in size. A single price might scare off big buyers or confuse small ones.
Right now we show a starting price and a "talk to us" button for teams over 50 people. Half our team thinks that's the best of both. The other half thinks it's the worst.
I'd really like to hear from other founders and buyers.
If you're a buyer, what do you do when there's no price?
If you're a founder, what did you choose and what happened?
The hook (65 characters)
Do you show prices on your website, or ask people to book a call?
Structure
Hook: a direct question to the reader
Context: a live debate
Both sides: short and fair
Current state: what they do now
Close: two questions for two audiences
Grader checks
Your first line fits above "see more" (65 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. Real questions from a real decision invite honest answers. Splitting the ask by buyer and founder makes it easy for anyone to reply.
Written example. Could be by: Senior engineer about to become a manager
The post
What's one thing you wish you knew in your first month as a manager?
I start my first manager role in 2 weeks. I've read the books. I've talked to my own manager. But I want to hear from people who did it recently.
A few things I'm already worried about:
How to give hard feedback to someone who used to be my peer.
How to stop writing code without feeling useless.
How to run a one on one that isn't just a status update.
If you have one tip, even small, I'd be grateful.
I'll collect the best answers and share them in a follow up post for anyone else starting out.
The hook (68 characters)
What's one thing you wish you knew in your first month as a manager?
Structure
Hook: a direct question
Context: why they are asking now
Specifics: three worries
Ask: one small tip
Close: a promise to share back
Grader checks
Your first line fits above "see more" (68 characters).
The hook has a number, a question or "you".
Easy to read (about grade 4).
No stock phrases.
No hashtag clutter.
Why it works. Specific worries give people something easy to answer. The promise to share results makes replying feel useful to others too.
Written example. Could be by: Head of marketing at a small software company
The post
When do you find time to write? I have 3 half finished posts from last month.
My days are full of meetings and small fires. By the time I sit down to write, my brain is done.
Here's what I've tried:
Writing first thing in the morning. Worked for a week.
Blocking Friday afternoons. Always got booked over.
Writing on my phone. Too many typos, too little focus.
I know some people write every day before work. Others write in bursts once a month.
What actually works for you? Not the ideal, the real one.
I'll try the most common answer for a month and report back.
The hook (77 characters)
When do you find time to write? I have 3 half finished posts from last month.
Structure
Hook: a question plus a relatable number
Problem: why it is hard
Tried: three honest attempts
Ask: a real answer, not the ideal
Close: a promise to test and report
Grader checks
Your first line fits above "see more" (77 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. Sharing failed attempts makes readers want to help. The promise to test the top answer gives people a reason to reply.
Written example. Could be by: Founder of a missed call tool for clinics
The post
A two doctor clinic was losing 20 calls a week. Here's what changed for them.
Dr. Patel runs a small family clinic. Her front desk is one person, Linda, who also checks people in, handles insurance and answers the phone.
When Linda was busy, calls went to voicemail. Most people didn't leave a message. They just called the next clinic.
We set up a simple text reply for every missed call. "Sorry we missed you. Want to book a visit? Reply here."
In the first month, 31 people replied. Linda booked most of them in between check ins.
Dr. Patel told me the best part wasn't the new patients. It was that Linda stopped feeling like she was failing.
Sometimes the best tool is the one that takes pressure off one person.
The hook (77 characters)
A two doctor clinic was losing 20 calls a week. Here's what changed for them.
Structure
Hook: a number and a problem
People: who is involved
Problem: what really happened
Fix: one simple change
Result: numbers and a human moment
Close: the broader lesson
Grader checks
Your first line fits above "see more" (77 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It centers the customer, not the product. The human moment about Linda makes it more memorable than numbers alone.
Written example. Could be by: Owner of a packaging design studio
The post
A coffee brand was turned down by the same grocery buyer 3 times. The fourth time, she said yes.
The coffee was great. The team was great. But on the shelf, their bag looked like every other brown bag.
We didn't start with a logo. We started in the store. We stood in front of the coffee section with the founder and took photos.
Almost every bag was brown or black. So we made theirs a deep green with one big word on the front.
Two months after the new bags were printed, the founder went back to the buyer. She picked it up and said, "I can see this from the aisle."
They're in 40 stores now.
Your product might be fine. It might just be invisible.
The hook (96 characters)
A coffee brand was turned down by the same grocery buyer 3 times. The fourth time, she said yes.
Structure
Hook: a number of rejections and a win
Problem: invisible on the shelf
Method: start in the store
Change: one bold choice
Result: the buyer's quote
Close: a line aimed at the reader
Grader checks
Your first line fits above "see more" (96 characters).
The hook has a number, a question or "you".
Easy to read (about grade 2).
No stock phrases.
No hashtag clutter.
Why it works. The story puts the client's struggle first and the agency's method second. The buyer's quote does the selling without any claims.
Written example. Could be by: Operations consultant for service firms
The post
A 45 person firm was missing 1 in 5 client deadlines. The fix took 6 weeks.
Their founder, Maya, called me after losing a client she'd had for years. Her team was working late every night and still falling behind.
We didn't start with new software. We put every step of their client work on one wall with sticky notes. It took an afternoon.
What we found: 9 steps where work waited for someone's approval. Most of those approvals didn't need to happen.
We cut them. We moved status updates out of email and into one shared board.
Three months later, they missed 2 deadlines all quarter. Maya said the office felt quieter.
If your team is working hard and still behind, look for the waiting, not the work.
The hook (75 characters)
A 45 person firm was missing 1 in 5 client deadlines. The fix took 6 weeks.
Structure
Hook: a number and a time frame
People: the founder and the pain
Method: map every step
Finding: where work waited
Result: fewer misses and a quote
Close: a lesson aimed at the reader
Grader checks
Your first line fits above "see more" (75 characters).
The hook has a number, a question or "you".
Easy to read (about grade 3).
No stock phrases.
No hashtag clutter.
Why it works. It shows a simple method that readers can try without hiring anyone. The closing line is short enough to remember and repeat.
A first line that gives a reason to click "see more", one clear point, short sentences, and an ending that invites a reply. Every example here is annotated with how it does those things.
How is the score worked out?
It is the same free grader as on our home page, run on each example: does the hook fit above "see more", does it have a number, a question or "you", is it easy to read, does it avoid stock phrases, and does it keep hashtags to three or fewer.
Are these real posts that did well?
No. They were written for this page with made up names and details, to show each structure clearly. We make no claims about how any of them would perform.
Can I copy one?
Copy the structure, not the story. Press Grade it to load one into the grader, then rewrite it with your own details.