Audit your last five LinkedIn posts and rewrite them
For the first hundred users, a founder post should be so tied to real customers, dates, and numbers that no one else could write it.
The feed is punishing generic founder posts
You are trying to find your first users, not build a content engine. Before you post on LinkedIn again, run the First Hundred Slop Test on your last five posts.
A user-facing 'Seems Like AI slop' reporting button appeared in LinkedIn's feed on 30 July 2026. The July 30 update also swapped LinkedIn's Enhance your post tool for a proofreader that preserves a member's voice. In a review of about 57,000 items, Pangram Labs reported that 41% of long-form public posts on LinkedIn and 30% of public comments were fully machine-written from April through June.
New classifiers would identify posts as AI slop or other low-quality content and, with user feedback, control how far a post travels outside the author's network. User reports would provide signal for tuning LinkedIn's AI models to better identify slop.
The reporting and detection changes had reduced the view count of AI-slop-labeled content by 40% in recent weeks. LinkedIn now stops hundreds of thousands of automated comment attempts each day.
For a founder with no distribution yet, the job is to find the first people who will use the product, tell you what is broken, and come back. A post is a way to show that you have real users and a real problem.
Run the First Hundred Slop Test on your last five posts
Take your last five posts. For each one, ask the same question: could anyone else have written this word for word? If three or more could, stop. Rewrite them with customer names, dates, and numbers before the next post.
The test works because generic founder content is now a crowded lane. A post about building in public, learning from customers, or shipping fast can be written by a template, a peer, or a model. The reader cannot tell whether it came from your actual week. Specificity is the proof that you were there.
Run these checks on each post:
- Name the customer, the role, or the exact problem they had.
- Put a date on the first conversation, first sale, first fix, or first complaint.
- Include one number you can defend: time saved, price paid, tickets closed, days to value.
- State what you did manually: the call, the email, the spreadsheet, the support thread.
- Name the next step you asked for and the result.
- Ask whether a competitor, a peer, or a template writer could post it word for word.
The customer, date, and number items are the core: a customer name or role makes the post about a person, not a theme; a date makes the story verifiable in your own memory and harder to imitate; a number gives the reader a concrete reason to believe the product changed something.
The manual step matters because early users are usually found through unscalable work. You did the outreach, the hand-holding, the follow-up. If the post hides that work, it reads like advice from someone who has not done it. If it shows the work, it becomes a proof point.
The final item is the gate. If the answer is yes, the post is too generic. It may be true, but it is not yours. Rewrite it with the customer, the date, and the number, then post the version only you could have written.
Specificity is the distribution tactic for the first hundred
Early-stage founders often treat the feed as a reach channel. They post lessons, frameworks, and milestones, then wonder why it does not return users. The problem is interchangeable content, not the algorithm.
For the first hundred users, distribution depends on relevance, not volume. A post that names a customer, a date, and a number can be shared by the customer, quoted by a peer, or saved by a prospect. It gives the reader a reason to reply or ask a question.
LinkedIn is curbing how often generic posts appear in recommendations without deleting them outright. A post that could be written by anyone is exactly what that filtering is meant to catch. Make the post impossible to copy.
The first users are already in your notes, your calendar, and your support inbox. Put the customer, the date, and the number in the post, then ask for the next step.
