FIELD NOTE 01 · THE POST THAT GOT 17 VIEWS
I Wrote Like Customer Support on X. Then I Learned the First Line Is a Bet.
A product update got 17 views. The algorithm may not be the villain; the first line may simply give nobody a reason to stay.
7 min read
Written after the drafts failed, not before.
Joey Zhao · Founder of Finfold
Updated ·
Composite scenario · based on common indie-launch patterns, not a customer testimonial or Finfold traffic result.
At 11:47 p.m. I posted a product update I had polished for hours. It explained what we built, why we built it, and where to find it. Courteous, complete, and lifeless — a customer-support email wearing a social post as a costume.
The next morning it had 17 views. No replies, no reposts, not even a bot-like. Blaming the algorithm felt good for a minute. Reading it again felt worse: I had explained everything except why a stranger should stop.
The algorithm may be fine. You may just be too polite.
Product people often open an X post like they are knocking on a manager's door: ‘Thrilled to announce’ or ‘We have been working hard.’ Politeness is fine, but the feed does not hand out manners awards. A reader has half a second to ask: why should I care?
Skip the ceremony and put the tension on the table. ‘We spent three weeks building a feature nobody wanted.’ It is not elegant. It is alive — and it makes the next sentence necessary.
The feed does not reward good manners. Your first line is a bet, not a biography.
A hook is not hype. It makes the cost visible.
I now start with one of three things: a contradiction, a before-and-after, or a cost with a number attached. Not because formulas are magic, but because each forces me to answer what actually hurt.
‘Five content tips’ is a table of contents. ‘After posting for 30 days, our hardest-working habit turned out to be useless’ sounds like somebody climbed out of a hole with mud still on their shoes.
People remember an answer that somebody paid tuition to learn.
Links in the post or the reply? Run your own small bet.
Link folklore is endless. Your account, audience, and offer are not somebody else's. Publish two comparable ideas a few days apart: one with the link in the post, one with a self-contained post and the link in a reply.
Track impressions, clicks, reply quality, and real signups. Platforms change; your own ledger is still the least dishonest witness you have.
Without your own data, every ‘the platform always’ is bar-room gossip.
Stop begging for engagement with ‘thoughts?’
A useful question is narrow enough to answer without writing an essay: ‘Would you go deep on three channels or claim a spot on ten?’ Then stay for the answer. Ask a follow-up. Disagree like a person.
The durable asset on X is not one viral spike. It is a small group of people who know what you are building and are willing to argue with you about it.
Reach is foot traffic. A real back-and-forth starts to feel like neighbours.
SMALL BET, REAL SIGNAL
A 20-minute bet you can run tonight
01 / DIG
Find an ignored old post. Keep the fact; delete the ceremony.
02 / CUT TWICE
Rewrite line one once with conflict and once with cost.
03 / WATCH PEOPLE
Post the version you would actually say aloud. Track useful replies, not applause.
NOW MAKE A DRAFT
Let Finfold handle the X / Twitter structure. Keep your own point of view.
A generator can get you off the blank page. It should never erase the person who lived the story.
Try the free generator