postpulse scored my post 88. the weakest part wasn’t the idea. it was the opening.
hook lab gave me eight openings for the same idea, ranked. i took one and left the rest of the post alone. it rescored 97.
published it. 73 impressions, 8 engagements. that's about 11% engagement against my median of 3.95%.
the score doesn't tell you how many people will see a post. it tells you whether it lands with the people who do. this one landed almost 3x better than my usual.
built postpulse solo. $29/mo, and the free scan of your last 20 posts is in the reply
6
19
566
i built a thing that reads your last 20 posts and tells you how you sound.
ran it on myself. it came back with:
"your own work's autopsy, with the next move."
not "visionary founder." not "compelling storyteller." an autopsy report.
i sat with that for a while. then i realised it's right. i post about what broke, what i tried, and what i'm doing next. that's the whole timeline.
most tools tell you your voice is great. mine told me the truth on the first try, and i'm the one who built it.
link in the first reply.
3
7
111
try it on your own handle, no sign-in: postpulse.app/read
2
44
same post scored 72, then 91. the only difference was one extra line pasted above the first sentence.
it was my nov 2 post about the localStorage bug. with that line sitting on top, the hook row came back "unsure / couldn't verify" with no score at all, and the total dropped with it. took the line out, rescored, and the opening got read as a hook. 63 on the hook, 91 overall.
first time i've seen the hook come back unsure. most of that 19 point gap was a missing hook score. the sentence itself was fine.
before you rewrite a post that scored low, check what's actually sitting above your first line
3
5
130
went looking for a draft i wrote a week ago in postpulse. my history showed one post.
turns out my dev only ever stored draft and score history in the browser's localStorage. nothing server-side. clear your browser, switch devices or open it on your phone, and every draft and score is gone. no error, no warning.
nobody files a bug for that. they just decide the tool doesn't keep anything and stop coming back.
and the whole point of postpulse is that your score gets measured against your own posts over time. that doesn't work if the history vanishes when you switch browsers.
fixed it sunday morning. history lives server-side now, keyed to the user. opened the app in incognito to make sure it wasn't still reading local, and everything was there.
if someone else wrote your code, open your app in incognito today
2
6
165
hook lab only touches the first line. here's what it gave me for that post:
"the score doesn't predict views. i backtested postpulse on my last 20 posts yesterday."
claim first, setup second. same post, same data, rescored 97.
scan your own last 20, free: postpulse.app
12
spent a week rewriting my pinned post, the one meant to show what postpulse does. checked the analytics yesterday.
43 impressions. 8 engagements. 3 replies, 1 like, 0 reposts.
0 profile visits.
a pin only gets seen by people who land on your profile. nobody landed. i was rewriting the copy on a page nobody was visiting.
for context, my ordinary posts do 70 to 170 impressions. the pin did less than those.
so the copy was never the problem. there's no traffic, and my own feed is the ceiling. the next two weeks go into getting in front of other people's audiences instead of tuning my own page.
2
3
120
a draft of mine scored 88. i ran it through the hook lab, took one of the new openings, and it rescored at 97.
i posted the 97. it did an 11% engagement rate. my median is 3.95%. my best before that was 7.2%.
that's what postpulse is for. it reads your last 20 posts and works out how you actually write (mine came back lowercase, contrast moves, open endings. fair.). then it scores a draft before you post it, so you know whether it's going to land with the people who see it, and the hook lab gives you better openings when it won't.
screenshots of the 88 and the 97 with the breakdown are below.
to try it: free scan of your last 20 posts. $29/mo if you want to score every draft.
link in the reply
3
4
153
i called 6.2% on this post. it did 9.7%.
269 impressions, 26 engagements. i was more than three points low.
and i read this at 83 impressions a few hours after posting. it's at 269 now. so the number you see an hour in is half the story.
same thing on the 98: i called 8.1%, it did 11%. my median is 3.95%.
the 60s and 70s posts did 5.4, 5.9 and 7.2. so the score gets the order right. it just squishes at the top. 79 and 98 are 19 points apart and only 1.3 points apart in reality.
so no more decimals. postpulse is going to tell you if a draft looks below your median, around it, or above it. that's what the data actually supports.
honest caveat: this is 20 posts. i need about 20 logged before i trust the top of the scale.




