Textio
Monthly Performance Report
July 1 to July 31, 2026
LinkedIn · Josh Potter

At a glance

Impressions
11.5K
across 5 posts
Engagements
72
likes, comments, shares, saves, sends
New Followers
+36
▲ 3.1% · 1,153 to 1,189
Posts Shipped
5
≈ 1.2 posts/week
Saves
4
high-intent signal

Performance overview

Follower growth

+36 net new followers, a 3.1% gain and a clear improvement on June's +7. The curve stepped up mid-month around the July 14 event invite and the interview-practices post. More consistent cadence would compound this faster.

Impressions by post

One event promo (the Seattle Talent on Tap invite) drove 66% of the month's reach. The interview-practices how-to was the top organic content post. The other three stayed small.

Top performing posts

What broke through this month

With 5 posts, the picture is stark: the biggest reach came from an event invite, not from content. That matters because the event post earned 7.6K impressions but just 1 save, while the how-to posts earn saves at a far higher rate on much smaller reach. Reach this month was event-driven; intent was how-to-driven. Those are two different levers, and only one of them compounds week over week.

🏆 By impressions (reach)

Who got seen the most.

1
Seattle Talent on Tap invite
Event promoImage · Jul 14
7.6Kimpressions
2
2.1Kimpressions
3
816impressions
4
566impressions
5
402impressions

💾 By saves (high intent)

B2B's strongest signal. Readers bookmarking to revisit. Four posts tied at 1 save; the anniversary essay earned none.

1
1save
2
1save
3
1save
4
Seattle Talent on Tap invite
Event promoImage · Jul 14
1save
5
0saves

Format analysis

Four text posts, one image (the event)

Josh's content is still almost entirely long-form text (4 of 5). The one image post, the Seattle event invite, drove the month's highest reach at 7.6K, but that is event mechanics (location, tagged attendees, a shared company push) more than a repeatable format lesson. The text how-to posts averaged 1,026 impressions. The most valuable format experiment for August is still a carousel or image version of the candidate how-to content that already earns saves.

Content pattern analysis

What we posted, and what each pattern returned

Across 5 posts, three jobs emerged: practical candidate and interview how-to, personal reflection on Josh's own workplace, and one event invite. The how-to lane is the one that both reaches and saves consistently; the event drove a reach spike but almost no intent.

Pattern breakdown

Three content patterns observed across 5 published posts. Small sample, read as directional.

Pattern Posts Total imp. Avg imp./post Total saves Top performer
Candidate / interview how-to 3 3,079 1,026 3 Two interview practices I'd ban (2.1K imp)
Event promo 1 7,596 7,596 1 Seattle Talent on Tap invite (7.6K imp)
Personal / reflection 1 816 816 0 Why we celebrate work anniversaries (816 imp)
📌 How-to content is still Josh's save engine, but volume dropped

The three candidate/interview how-to posts drove all 3 of the month's content saves and hold the best save-per-impression ratio on the account. This is the proven lane from June. The problem this month is quantity: only 3 how-to posts in the whole month, down from the cadence needed to compound. The engine works; it is not being fed.

📌 The event post reached far but converted almost nothing

The Seattle Talent on Tap invite hit 7.6K impressions (66% of reach) on the strength of a tagged, shared company event, but earned just 1 save and 0.13 saves per 1,000 views. Events are worth posting for turnout, but they do not build the saved, high-intent audience that how-to content does. Do not read the 7.6K as a content win.

📌 Personal reflection connects but does not get saved

The work-anniversary post pulled warm engagement (10 likes, 3 comments) but 0 saves and stayed at 816 impressions. As in June, personal stories tied to Josh's specific workplace work as connection, not as saveable utility. Keep them occasional and always anchor them to a takeaway.

Hook analysis

What the strongest content hook did right

Setting the event aside (its reach came from mechanics, not its opening line), the best content post was "Two interview practices I'd ban." Its hook does four things the weakest post, the late-month resume how-to that stalled at 402, does not.

1
Credibility number up front

"I've spent 7 years recruiting" establishes authority in the first five words. The reader immediately knows why Josh's opinion on interviews is worth reading.

2
A specific, curiosity-opening claim

"There are two interview practices I'd ban tomorrow if I could" creates an open loop with a number attached. The reader has to keep going to learn which two. The weaker resume post opened on an abstract observation ("AI made it effortless to create a resume") that describes a problem rather than promising a payoff.

3
A clear reader benefit

Hiring managers and candidates both know instantly this post will make their process better, so they engage and save. Reflection posts and problem-framing openers give the reader less to act on, so they get fewer saves.

4
First person and concrete

"I've seen companies loop 7 or 8 people into a single hire." Short, personal, specific, with a "three and three" rule the reader can copy. The winning cadence across both Textio accounts. Note this post also ended with a question ("what would you ban?"), which pulled 4 comments.

What didn't work

The weakest post and why

5 of 5
Standing out when every resume looks perfect
402 impressions · 1 save · 0 likes · Jul 30
Hypothesis: strong content, weak opener, no early engagement

This was genuinely useful how-to (build a story bank, highlight the pivot, create public proof), the exact lane that works for Josh. But it opened by describing the problem ("AI made it effortless to create a resume that perfectly matches the job description") instead of leading with Josh's credibility and a curiosity gap the way the interview-practices post did. It drew 0 likes and 0 comments in its early window, so the algorithm never pushed it. Same author, same topic family, roughly one fifth the reach of the interview post. The lesson is to open with authority and an open loop, not with the problem statement.

🛑 Common failure modes to watch in August

1. Low cadence: 5 posts in a month is not enough for how-to content to compound into follower growth.
2. Leaning on events for reach: the 7.6K event spike is not repeatable content and earned almost no saves.
3. Opening how-to posts with a problem statement instead of a credibility hook and an open loop (the resume post stalled at 402 with 0 likes).
4. Personal essays without a reader takeaway (the anniversary post connected but earned 0 saves).

What to do next month

Playbook for August

Five moves to turn a promising but thin month into a compounding account.

1
Raise cadence to 3 posts per week

Volume is still the single biggest constraint. Five posts, only three of them content, is not enough for the algorithm to learn the account or for followers to compound. Target 3 posts per week in August on fixed weekday slots so there is real signal to analyze next month.

Evidence: +36 followers on 5 posts, up from +7 on 4; the trend is right, the volume is not there yet.
2
Make candidate and interview how-to the core: 2 per week

This lane earned all 3 content saves and the best organic reach (the interview-practices post at 2.1K). Ship 2 how-to posts a week aimed at candidates and hiring managers ("the 3-and-3 interview rule," "how to build a story bank before you job hunt," "what a strong debrief documents"). This is Josh's proven save engine and it is currently underfed.

Evidence: 3 how-to posts = 3,079 impressions and all 3 content saves; the interview post alone hit 2.1K.
3
Open every how-to with credibility, then an open loop

The interview-practices post led with "I've spent 7 years recruiting" and a numbered claim, and hit 2.1K with 4 comments. The resume post led with the problem and stalled at 402 with 0 likes. Same lane, five times the reach. Make the credibility-plus-curiosity opener the template for the top of every post.

Evidence: interview post (2.1K, credibility hook) vs resume post (402, problem-statement hook), same author, same week-family.
4
Treat events as turnout tools, not reach strategy

The Seattle invite reached 7.6K but earned 1 save and does not build a saved audience. Keep one event post when there is a real event, but do not count on events for growth. The compounding audience comes from weekly how-to, not from invites.

Evidence: event post 7.6K impressions / 1 save / 0.13 saves per 1K vs how-to lane at roughly 1 save per 1K.
5
Keep personal posts, but anchor each to a takeaway

The anniversary post connected but gave the reader nothing to do, so it earned 0 saves. When posting personally, end with the lesson the reader can apply to their own team. Ratio: roughly 1 personal post for every 2 how-to posts.

Evidence: anniversary post (816 impressions, 10 likes, 0 saves) connected but did not spread or get bookmarked.