[{"data":1,"prerenderedAt":1238},["ShallowReactive",2],{"blog:\u002Fblog\u002Flinkedin-ghostwriter-cost":3,"blog:related:\u002Fblog\u002Flinkedin-ghostwriter-cost":396},{"id":4,"title":5,"author":6,"body":7,"date":382,"description":383,"draft":384,"extension":385,"image":386,"meta":387,"navigation":388,"path":389,"seo":390,"stem":391,"tags":392,"updated":386,"__hash__":395},"blog\u002Fblog\u002Flinkedin-ghostwriter-cost.md","What a LinkedIn ghostwriter costs (and when one is worth it)","SelfSM",{"type":8,"value":9,"toc":371},"minimark",[10,14,17,22,25,32,38,44,47,51,57,60,82,85,88,92,95,98,130,133,137,140,151,157,168,172,299,303,306,333,337,343,349,355,365],[11,12,13],"p",{},"Founders ask this question in the wrong order. They ask what a ghostwriter costs, get a number, decide it's a lot, and go back to posting nothing. The number is only half the decision. The other half is what your own time costs and how much of it a ghostwriter actually saves, which is less than most people assume.",[11,15,16],{},"Here are the real ranges, the cost that never appears on the invoice, and the point where hiring stops being a luxury.",[18,19,21],"h2",{"id":20},"the-three-price-tiers","The three price tiers",[11,23,24],{},"Rates vary by market and by how much of the work is writing versus strategy, but ghostwriting offers cluster into three recognisable bands.",[11,26,27,31],{},[28,29,30],"strong",{},"$500–1,200\u002Fmonth — the drafting tier."," Usually a freelancer, often junior or offshore, writing 8–12 posts a month from material you give them. You supply the ideas, the stories and the facts. They turn your voice notes into posts. At this tier you are buying typing and structure, not judgment.",[11,33,34,37],{},[28,35,36],{},"$1,500–4,000\u002Fmonth — the standard tier."," This is where most experienced LinkedIn ghostwriters sit. You get a monthly interview call, 12–20 posts, some strategy on what to talk about, and edits. They will push back on weak angles. This is the band most founders mean when they say \"a ghostwriter.\"",[11,39,40,43],{},[28,41,42],{},"$5,000–15,000\u002Fmonth — the operator tier."," An agency or a senior writer running the whole presence: content, comments, DMs, sometimes lead handling. Common for founders raising, hiring at scale, or selling something with a long sales cycle where LinkedIn is the pipeline.",[11,45,46],{},"Per-post pricing exists too, typically $100–400 a post at the standard tier, but it tends to be worse value: the writer's cost is mostly in learning your voice, and per-post deals never let them amortise that.",[18,48,50],{"id":49},"the-cost-nobody-quotes-you-your-own-hours","The cost nobody quotes you: your own hours",[11,52,53,54],{},"The invoice is the visible cost. The invisible one is that ",[28,55,56],{},"a ghostwriter cannot write about your business without you.",[11,58,59],{},"Every good ghostwriting relationship needs roughly:",[61,62,63,70,76],"ul",{},[64,65,66,69],"li",{},[28,67,68],{},"A 45–60 minute interview call",", monthly at minimum, often weekly at the start.",[64,71,72,75],{},[28,73,74],{},"Voice notes or messages"," when something happens worth writing about — a customer result, a decision, a mistake.",[64,77,78,81],{},[28,79,80],{},"A review pass on every draft."," Not a rubber stamp: you are the only person who knows whether the number is right.",[11,83,84],{},"Call it 3–5 hours a month once the relationship is warm, and considerably more for the first two months. If your hour is worth $200, that is another $600–1,000 of real cost on top of the fee.",[11,86,87],{},"This is not an argument against hiring. It is an argument against the fantasy that hiring makes content someone else's problem. It never does. The founder is the only source of the material, and no arrangement changes that.",[18,89,91],{"id":90},"when-it-pays-for-itself","When it pays for itself",[11,93,94],{},"The honest test is not \"can I afford $2,000 a month.\" It is \"does one outcome from LinkedIn cover it.\"",[11,96,97],{},"Run the arithmetic on your own numbers:",[61,99,100,106,112,118],{},[64,101,102,105],{},[28,103,104],{},"If you sell something at $20k+ ACV",", one inbound conversation a quarter that closes pays for a year of ghostwriting. The bar is low and hiring is usually correct.",[64,107,108,111],{},[28,109,110],{},"If you're hiring",", one senior engineer sourced inbound saves a recruiter fee of $25–40k. Same conclusion.",[64,113,114,117],{},[28,115,116],{},"If you sell a $30\u002Fmonth product",", LinkedIn content almost never pays back as a direct acquisition channel at that price. It might still be worth it for hiring, fundraising or partnerships, but be honest that the payback is indirect.",[64,119,120,123,124,129],{},[28,121,122],{},"If you're pre-revenue",", the ghostwriter is being paid out of runway to build an asset with an unknown payoff. Usually the wrong call. See ",[125,126,128],"a",{"href":127},"\u002Fblog\u002Fwhat-to-post-before-launch","what to post before you have a product"," for the cheaper version.",[11,131,132],{},"The second test is consistency. A ghostwriter's real value is that posts go out in a week when your product is on fire. If you would have posted anyway, you are buying polish. If you would have gone dark, you are buying the channel's existence.",[18,134,136],{"id":135},"three-cheaper-setups-that-work","Three cheaper setups that work",[11,138,139],{},"Hiring is not the only way to solve \"I don't post.\"",[11,141,142,145,146,150],{},[28,143,144],{},"1. The 30-minute weekly block."," One recurring slot, four posts, batched. Most founders who \"don't have time\" have never actually tried the batched version — they have tried the write-something-every-morning version, which fails for everyone. The full method is in ",[125,147,149],{"href":148},"\u002Fblog\u002Ffounder-content-30-minutes-a-week","founder content in 30 minutes a week",".",[11,152,153,156],{},[28,154,155],{},"2. An editor instead of a writer."," You write badly and fast; someone else makes it publishable. Typically $300–800\u002Fmonth, and it keeps your voice because the words started as yours. Underrated, and much cheaper than full ghostwriting.",[11,158,159,162,163,167],{},[28,160,161],{},"3. A tool that starts from your material instead of a prompt."," The reason generic AI does not replace a ghostwriter is that it does not know your facts, so it invents them, in a register that reads as machine-written to anyone who has seen a few. What closes that gap is not a better prompt but a system that stores your voice and your confirmed facts and drafts from those. That is ",[125,164,166],{"href":165},"\u002Ffor\u002Ffounders","what SelfSM does",", at roughly a tenth of the standard ghostwriting tier.",[18,169,171],{"id":170},"the-comparison-plainly","The comparison, plainly",[173,174,175,195],"table",{},[176,177,178],"thead",{},[179,180,181,184,187,190,193],"tr",{},[182,183],"th",{},[182,185,186],{},"Ghostwriter",[182,188,189],{},"Editor",[182,191,192],{},"ChatGPT",[182,194,6],{},[196,197,198,216,233,250,267,284],"tbody",{},[179,199,200,204,207,210,213],{},[201,202,203],"td",{},"Monthly cost",[201,205,206],{},"$1,500–4,000",[201,208,209],{},"$300–800",[201,211,212],{},"~$20",[201,214,215],{},"$0–19",[179,217,218,221,224,227,230],{},[201,219,220],{},"Your hours per month",[201,222,223],{},"3–5",[201,225,226],{},"2–4",[201,228,229],{},"4–8",[201,231,232],{},"1–2",[179,234,235,238,241,244,247],{},[201,236,237],{},"Sounds like you",[201,239,240],{},"After 2–3 months",[201,242,243],{},"Yes, it's your text",[201,245,246],{},"Rarely",[201,248,249],{},"From your own posts",[179,251,252,255,258,261,264],{},[201,253,254],{},"Knows your facts",[201,256,257],{},"If you brief them",[201,259,260],{},"Yes",[201,262,263],{},"No — invents them",[201,265,266],{},"Stored per brand",[179,268,269,272,275,278,281],{},[201,270,271],{},"Decides what to post",[201,273,274],{},"They do",[201,276,277],{},"You do",[201,279,280],{},"You prompt it",[201,282,283],{},"Proposed weekly",[179,285,286,289,291,294,297],{},[201,287,288],{},"Survives a chaotic month",[201,290,260],{},[201,292,293],{},"Partly",[201,295,296],{},"No",[201,298,260],{},[18,300,302],{"id":301},"what-to-ask-before-you-hire","What to ask before you hire",[11,304,305],{},"If you do hire, four questions separate the good ones from the expensive ones:",[307,308,309,315,321,327],"ol",{},[64,310,311,314],{},[28,312,313],{},"\"Show me a client's posts from before and after you started.\""," Voice match is the whole job. If the after looks like the writer's own feed, walk.",[64,316,317,320],{},[28,318,319],{},"\"What happens when I go quiet for three weeks?\""," The honest answer is \"nothing gets written.\" Anyone promising otherwise is planning to invent your material.",[64,322,323,326],{},[28,324,325],{},"\"Who owns the archive?\""," You want the voice guide, the angles list and the post history when the engagement ends. Otherwise you restart from zero with the next person.",[64,328,329,332],{},[28,330,331],{},"\"What's the minimum I have to give you each week?\""," If they cannot answer in one sentence, the process is not real yet.",[18,334,336],{"id":335},"faq","FAQ",[11,338,339,342],{},[28,340,341],{},"How much does a LinkedIn ghostwriter charge per post?","\nTypically $100–400 per post at the standard tier, though monthly retainers of $1,500–4,000 are far more common and usually better value, because most of a writer's cost is learning your voice once rather than writing each post.",[11,344,345,348],{},[28,346,347],{},"Is a LinkedIn ghostwriter worth it for a founder?","\nIt depends almost entirely on deal size. At $20k+ ACV, one inbound deal a quarter covers a year of ghostwriting and the answer is usually yes. Below roughly $1k ACV, direct payback is rare, and the case has to come from hiring, fundraising or partnerships instead.",[11,350,351,354],{},[28,352,353],{},"Can AI replace a LinkedIn ghostwriter?","\nIt replaces the drafting, not the sourcing. A model has no access to your customer numbers, your decisions or your mistakes, so it fills the gap with plausible invention. What works is a system that stores your real facts and voice and drafts only from those — the writing stops being the bottleneck, but you still have to supply the material.",[11,356,357,360,361,150],{},[28,358,359],{},"How do I stop ghostwritten posts sounding generic?","\nInsist on one specific thing in every post that only you could have said: a number, a name, a decision you regret. Generic posts are almost always posts written without enough raw material. The patterns to strip are in ",[125,362,364],{"href":363},"\u002Fblog\u002Fai-writing-tells","the tells that make writing sound like AI",[11,366,367,370],{},[28,368,369],{},"How long before ghostwriting starts working?","\nTwo to three months for the voice to settle, and typically three to six before inbound is predictable enough to plan around. Anyone promising results in weeks is selling a different product.",{"title":372,"searchDepth":373,"depth":373,"links":374},"",2,[375,376,377,378,379,380,381],{"id":20,"depth":373,"text":21},{"id":49,"depth":373,"text":50},{"id":90,"depth":373,"text":91},{"id":135,"depth":373,"text":136},{"id":170,"depth":373,"text":171},{"id":301,"depth":373,"text":302},{"id":335,"depth":373,"text":336},"2026-08-19","Typical ghostwriter pricing tiers, the hidden cost nobody quotes you, the maths on when it pays for itself, and the three cheaper setups that work almost as well.",false,"md",null,{},true,"\u002Fblog\u002Flinkedin-ghostwriter-cost",{"title":5,"description":383},"blog\u002Flinkedin-ghostwriter-cost",[393,394],"founders","linkedin","hJwZRfT4-lH5xI1xcU_CPlVSXPJcD-RTMhK27jMub3s",[397,619,829],{"id":398,"title":399,"author":6,"body":400,"date":382,"description":612,"draft":384,"extension":385,"image":386,"meta":613,"navigation":388,"path":148,"seo":614,"stem":615,"tags":616,"updated":386,"__hash__":618},"blog\u002Fblog\u002Ffounder-content-30-minutes-a-week.md","Founder content in 30 minutes a week",{"type":8,"value":401,"toc":603},[402,405,408,411,415,418,424,430,433,437,440,446,452,462,465,469,472,498,501,505,511,522,528,539,543,546,552,558,562,565,571,573,579,585,591,597],[11,403,404],{},"Most founders who \"have no time for content\" have never tried the version that works. They have tried writing something every morning, which fails for everybody, then concluded the problem was time. The problem was the schedule.",[11,406,407],{},"Writing four posts in one sitting takes far less than four times writing one post, because the expensive part is not the typing. It is deciding what to say, getting into the register, and overcoming the blank page. Do that once a week instead of five times.",[11,409,410],{},"Here is the method, and the two places it breaks.",[18,412,414],{"id":413},"the-two-habits-not-one","The two habits, not one",[11,416,417],{},"This runs on a capture habit and a writing habit, and people who try to skip the first one always fail.",[11,419,420,423],{},[28,421,422],{},"Habit 1 — capture, 10 seconds, whenever."," One note, anywhere you will actually open. A customer said something. A number moved. You changed your mind about something you believed six months ago. You are not writing, you are dropping a line. \"Migration went 4h → 20m after the importer rewrite.\" That is enough.",[11,425,426,429],{},[28,427,428],{},"Habit 2 — write, 30 minutes, once a week."," Open the capture list, pick four, write four posts, done.",[11,431,432],{},"Without habit 1, habit 2 is just a blank page with a calendar invite attached. The whole thing lives or dies on whether you can produce raw material without it feeling like work.",[18,434,436],{"id":435},"what-actually-goes-in-the-30-minutes","What actually goes in the 30 minutes",[11,438,439],{},"Timeboxed, because the point is that it ends.",[11,441,442,445],{},[28,443,444],{},"Minutes 0–5: pick four."," Not the four best. The four you can write fastest, because you already know what you think. Anything requiring research goes back on the list.",[11,447,448,451],{},[28,449,450],{},"Minutes 5–25: write four drafts, five minutes each."," One pass, no editing, deliberately rough. Five minutes is short enough that you cannot polish, which is the point — polishing is where the hour goes.",[11,453,454,457,458,150],{},[28,455,456],{},"Minutes 25–30: one editing pass across all four."," Cut every first paragraph (it is almost always throat-clearing), replace the biggest adjective in each with a fact, and check each one has something only you could have written. The full pass is in ",[125,459,461],{"href":460},"\u002Fblog\u002Fhumanize-chatgpt-draft","how to edit a draft so it sounds like you",[11,463,464],{},"Then queue them. Do not schedule all four for the same channel on consecutive days if they are all the same shape — mix a short observation with a longer piece.",[18,466,468],{"id":467},"the-four-kinds-of-post-you-already-have-material-for","The four kinds of post you already have material for",[11,470,471],{},"The reason a founder's blank page is a lie: you generate publishable material every week and throw it away.",[307,473,474,480,486,492],{},[64,475,476,479],{},[28,477,478],{},"A number that moved, with the story behind it."," Not \"growth is up.\" What changed and why. Specific numbers are the single strongest thing a founder has and the thing they most often leave out.",[64,481,482,485],{},[28,483,484],{},"A decision and the alternative you rejected."," \"We chose X over Y because Z\" is more interesting than any framework, and only you can write it.",[64,487,488,491],{},[28,489,490],{},"Something a customer said, verbatim."," Half a sentence from a support ticket, with what you did about it.",[64,493,494,497],{},[28,495,496],{},"Something you were wrong about."," The highest-performing founder content is almost always this, and the most under-supplied.",[11,499,500],{},"Notice that none of these require an opinion about the industry. Founders default to industry takes because they feel safe and require no disclosure — and they are the most replaceable thing in the feed, because a thousand people can write them and only you can write the other four.",[18,502,504],{"id":503},"what-to-cut","What to cut",[11,506,507,510],{},[28,508,509],{},"Cut the daily target."," Two good posts a week beats five filler ones, and filler is what a daily target produces on week three.",[11,512,513,516,517,521],{},[28,514,515],{},"Cut the second channel until the first one works."," Most founders should run LinkedIn or X, not both. Cross-posting the same text to both is worse than picking one, because the formats reward different shapes: ",[125,518,520],{"href":519},"\u002Fblog\u002Fx-thread-structures","threads"," are not long LinkedIn posts.",[11,523,524,527],{},[28,525,526],{},"Cut comment-hour."," Engagement pods and reply-farming produce numbers that do not turn into anything. Reply when you have something to say.",[11,529,530,533,534,538],{},[28,531,532],{},"Cut the content calendar spreadsheet."," For one brand at this volume it is overhead pretending to be strategy. A capture list and a queue is the entire system you need. (Running several brands is genuinely different — that is where ",[125,535,537],{"href":536},"\u002Fblog\u002Fcontent-calendar-you-can-keep","a real calendar"," starts earning its keep.)",[18,540,542],{"id":541},"where-it-breaks","Where it breaks",[11,544,545],{},"Two failure modes, and they are predictable.",[11,547,548,551],{},[28,549,550],{},"The capture list runs dry."," Usually a sign you have stopped talking to customers, or that you are filtering too hard at capture time. Capture is not the place to judge whether something is interesting; write it down and decide later. If the list is genuinely empty for two weeks, that is information about your week, not your content.",[11,553,554,557],{},[28,555,556],{},"A brutal month eats the block."," Fundraising, an outage, a launch. This is the one thing a founder cannot solve with discipline, and it is exactly the moment going dark hurts most. Two defences: keep two posts in the queue as a buffer at all times, and lower the bar rather than skipping — one rough post beats a silent month.",[18,559,561],{"id":560},"when-30-minutes-stops-being-enough","When 30 minutes stops being enough",[11,563,564],{},"This method holds up well for one brand and one channel. It starts creaking when the constraint moves from writing to deciding: when you have three months of history to keep straight, a queue you cannot remember the contents of, and a growing list of things you already said. That is not a discipline problem, it is a memory problem, and it is the point where founders quietly stop.",[11,566,567,568,570],{},"That is the gap ",[125,569,6],{"href":165}," fills for founders: the capture list becomes a queue Chloe reads, she proposes what the week should say based on what you already covered and what facts you confirmed, and drafts in your voice from your own material rather than inventing around the gaps. The 30 minutes becomes ten minutes of approving instead of thirty of writing.",[18,572,336],{"id":335},[11,574,575,578],{},[28,576,577],{},"How often should a founder post on LinkedIn?","\nTwo to three times a week, sustained, beats daily posting that stops after a month. Consistency over months is what compounds; frequency inside a given week matters far less than most advice implies.",[11,580,581,584],{},[28,582,583],{},"What should a founder post about?","\nThings only you have access to: numbers that moved and why, decisions and the alternatives you rejected, verbatim customer feedback, and things you turned out to be wrong about. Industry commentary is the most replaceable content a founder can write.",[11,586,587,590],{},[28,588,589],{},"How long should it take to write a LinkedIn post?","\nFive to eight minutes for a draft if you already know what you think, which is why batching works — the expensive part is deciding and getting into register, and batching pays that cost once instead of four times.",[11,592,593,596],{},[28,594,595],{},"Is it better to batch content or write daily?","\nBatch. Daily writing means paying the blank-page cost five times a week and having no buffer when a bad week arrives. One 30-minute block plus a running capture list survives chaos in a way a daily habit does not.",[11,598,599,602],{},[28,600,601],{},"What if I have nothing to write about?","\nIt is almost always a capture problem, not a supply problem. Founders generate publishable material constantly and discard it because it does not feel significant in the moment. Start writing one line a day for two weeks before concluding the well is dry.",{"title":372,"searchDepth":373,"depth":373,"links":604},[605,606,607,608,609,610,611],{"id":413,"depth":373,"text":414},{"id":435,"depth":373,"text":436},{"id":467,"depth":373,"text":468},{"id":503,"depth":373,"text":504},{"id":541,"depth":373,"text":542},{"id":560,"depth":373,"text":561},{"id":335,"depth":373,"text":336},"A batched weekly method for founders who keep going dark: one capture habit, one 30-minute block, four posts. What to cut, what to keep, and where it breaks.",{},{"title":399,"description":612},"blog\u002Ffounder-content-30-minutes-a-week",[393,617],"workflow","c60V464WB1BI_vgU9XOGDOMBQj1HC-370I227cxxQkk",{"id":620,"title":621,"author":6,"body":622,"date":382,"description":822,"draft":384,"extension":385,"image":386,"meta":823,"navigation":388,"path":127,"seo":824,"stem":825,"tags":826,"updated":386,"__hash__":828},"blog\u002Fblog\u002Fwhat-to-post-before-launch.md","What to post before you have a product",{"type":8,"value":623,"toc":813},[624,627,630,633,637,640,666,673,677,683,689,695,701,707,713,719,722,726,729,732,738,744,748,751,758,762,765,768,772,775,781,783,789,795,801,807],[11,625,626],{},"The pre-launch founder has the hardest content problem and the best raw material, and almost always uses neither. No customers means no case studies, no numbers, no social proof — so most people fill the gap with industry takes that could have been written by anyone, or with traction language that is not quite true yet.",[11,628,629],{},"Both are worse than posting nothing. The takes are invisible; the inflated claims are remembered.",[11,631,632],{},"What you do have is the thing nobody with a mature product has any more: an unfinished decision, in public, in real time. That is the whole strategy.",[18,634,636],{"id":635},"the-claims-that-cost-you-later","The claims that cost you later",[11,638,639],{},"Start with what not to write, because pre-launch is where founders damage trust fastest and least deliberately.",[61,641,642,648,654,660],{},[64,643,644,647],{},[28,645,646],{},"\"Our customers are seeing…\""," when there are three design partners on a free tier. The plural is the lie, and someone will ask.",[64,649,650,653],{},[28,651,652],{},"\"We're growing fast\""," off a base of 40 signups. Not false, exactly, and everyone reads it as false.",[64,655,656,659],{},[28,657,658],{},"Invented specificity."," A generated post will happily produce \"teams save an average of 6 hours a week\" because it is the shape a post takes. If you did not measure it, that number becomes something you have to defend or quietly delete.",[64,661,662,665],{},[28,663,664],{},"Borrowed authority."," Writing about scaling when you have not scaled anything. Readers who have done it can tell in one paragraph.",[11,667,668,669,672],{},"The rule that survives all of these: ",[28,670,671],{},"never claim a scale you cannot name."," \"One beta customer cut migration from four hours to twenty minutes\" is stronger than \"customers save hours\" precisely because it is narrow. Specific and small beats vague and big, every time.",[18,674,676],{"id":675},"seven-angles-that-work-with-zero-customers","Seven angles that work with zero customers",[11,678,679,682],{},[28,680,681],{},"1. The problem, described better than your buyer can describe it."," If you can articulate the pain more precisely than the person living with it, you have earned attention without claiming anything. This is the single highest-value pre-launch post and most founders skip straight past it to the solution.",[11,684,685,688],{},[28,686,687],{},"2. The decision you are in the middle of."," Not \"here's what we built\" but \"here's the fork we're at and what we're weighing.\" Live decisions get replies from people who have made them. Finished decisions get likes.",[11,690,691,694],{},[28,692,693],{},"3. What you're building and why this way."," The architecture, the constraint you accepted, the thing you deliberately made worse. Technical honesty travels.",[11,696,697,700],{},[28,698,699],{},"4. What you were wrong about."," You have been wrong about something in the last month. That post is more interesting than your roadmap and costs you nothing, because pre-launch nobody expected you to be right yet.",[11,702,703,706],{},[28,704,705],{},"5. Research in public."," You are talking to potential users. Post what you are hearing, anonymised, without conclusions. \"Six of ten people we spoke to had already built a spreadsheet version of this\" is a fact you own.",[11,708,709,712],{},[28,710,711],{},"6. The thing you refuse to build."," Positioning stated as a boundary is memorable and commits you publicly, which is useful discipline.",[11,714,715,718],{},[28,716,717],{},"7. Work in progress with the seams showing."," A screenshot of something half-finished, a migration that broke, a metric that is bad. Build-in-public works when the \"in public\" part includes the parts that are not going well.",[11,720,721],{},"Notice that six of seven require no traction at all. They require you to be doing the work and willing to describe it accurately.",[18,723,725],{"id":724},"build-the-audience-the-launch-lands-on","Build the audience the launch lands on",[11,727,728],{},"The reason to post pre-launch is not the posts. It is that a launch to zero people is a press release into a void, and a launch to 800 people who have watched you reason for six months is an event.",[11,730,731],{},"Two things matter more than volume:",[11,733,734,737],{},[28,735,736],{},"Reply to people, individually, before you need anything."," Pre-launch is the only period where you have time for this, and it is the only distribution strategy that reliably works from a standing start. Twenty real conversations beat two hundred impressions.",[11,739,740,743],{},[28,741,742],{},"Say what you are building, repeatedly, in one sentence."," Not a pitch. A sentence people can repeat to someone else. If your audience cannot describe what you do, they cannot refer you at launch, and referral is most of what a launch is.",[18,745,747],{"id":746},"the-frequency-question","The frequency question",[11,749,750],{},"Lower than you think. Two posts a week for six months beats daily for five weeks and then silence, which is the standard pre-launch pattern: enthusiasm, exhaustion, disappearance a month before the thing you were building for.",[11,752,753,754,757],{},"Pre-launch is a stamina problem, not an intensity problem. The ",[125,755,756],{"href":148},"30-minutes-a-week method"," exists precisely because the pre-launch period is long and the founder's attention is not.",[18,759,761],{"id":760},"when-the-product-ships","When the product ships",[11,763,764],{},"Do not throw away the pre-launch archive. The decisions, the wrong turns and the research are the raw material for everything you write afterwards — a launch post that references six months of public reasoning is dramatically stronger than one that starts from \"today we're excited to announce.\"",[11,766,767],{},"This is also where most founders lose the plot: the voice that got attention pre-launch was specific, uncertain and technical, and the launch flips it to marketing register overnight. Readers notice the switch immediately. Whatever else changes, keep the register.",[18,769,771],{"id":770},"where-a-tool-helps-and-where-it-does-not","Where a tool helps and where it does not",[11,773,774],{},"No tool solves the pre-launch content problem, because the problem is that only you know what happened this week. What a tool can do is stop the two failure modes: going dark when the build gets hard, and letting a generated draft quietly invent traction you do not have.",[11,776,777,778,780],{},"That second one is why ",[125,779,6],{"href":165}," works the way it does — brand memory holds what is actually true, including \"customers: 0\", and a draft that would claim otherwise gets stopped rather than written. Pre-launch is exactly the situation where an AI writer is most dangerous and most tempting, because the gap between what you have and what a post wants is at its widest.",[18,782,336],{"id":335},[11,784,785,788],{},[28,786,787],{},"What should a startup post before launch?","\nThe problem stated more precisely than your buyer can state it, decisions you are currently weighing, what you are building and why this way, things you were wrong about, and anonymised findings from user research. All of these work with zero customers.",[11,790,791,794],{},[28,792,793],{},"How do I build an audience with no product?","\nPost twice a week for months rather than daily for weeks, and spend more time replying to individuals than writing posts. Pre-launch is the only period where you have time for one-to-one conversations, and they convert into a launch audience far better than impressions do.",[11,796,797,800],{},[28,798,799],{},"Should I build in public?","\nIt works when \"in public\" includes the parts going badly. Selective build-in-public that only shows wins reads as marketing and gets treated as such. If you are not willing to post the broken migration, the format is not for you.",[11,802,803,806],{},[28,804,805],{},"Is it bad to post about traction I don't have yet?","\nYes, and the damage is durable. Never claim a scale you cannot name. One named result stated narrowly is more persuasive than a vague plural, and it does not become something you have to defend later.",[11,808,809,812],{},[28,810,811],{},"How often should a pre-launch founder post?","\nTwo to three times a week, sustained. The pre-launch period is typically six to eighteen months, which is a stamina problem — the common failure is intense posting for a month followed by silence right before launch.",{"title":372,"searchDepth":373,"depth":373,"links":814},[815,816,817,818,819,820,821],{"id":635,"depth":373,"text":636},{"id":675,"depth":373,"text":676},{"id":724,"depth":373,"text":725},{"id":746,"depth":373,"text":747},{"id":760,"depth":373,"text":761},{"id":770,"depth":373,"text":771},{"id":335,"depth":373,"text":336},"Pre-launch content without fake traction: seven angles that work with zero customers, the claims that quietly destroy trust, and how to build an audience the launch can land on.",{},{"title":621,"description":822},"blog\u002Fwhat-to-post-before-launch",[393,827],"strategy","BSnR1nRUYwbsZ1GSrvhdK1ruP7msgCwyyzC96eDms3M",{"id":830,"title":831,"author":6,"body":832,"date":1229,"description":1230,"draft":384,"extension":385,"image":386,"meta":1231,"navigation":388,"path":1232,"seo":1233,"stem":1234,"tags":1235,"updated":386,"__hash__":1237},"blog\u002Fblog\u002Flinkedin-hooks.md","How to write LinkedIn hooks that earn the \"see more\" click",{"type":8,"value":833,"toc":1206},[834,837,841,844,847,851,854,858,863,866,874,877,881,884,892,895,899,902,910,913,917,920,928,931,935,938,946,949,953,956,960,977,981,998,1002,1019,1023,1040,1044,1061,1065,1113,1117,1128,1131,1135,1138,1155,1158,1162,1168,1174,1180,1186,1192],[11,835,836],{},"LinkedIn hides most of a longer post behind the \"…more\" cutoff. Your opening lines decide whether anyone taps to read the rest, so the hook does more work than the other 200 words combined. This is a guide to writing that opening: what a hook is, the types that work, a stack of examples by role, the mistakes that kill a post, and a checklist you can run before you publish.",[18,838,840],{"id":839},"what-a-linkedin-hook-actually-is","What a LinkedIn hook actually is",[11,842,843],{},"A hook is the first line or two of a post: the part visible in the feed before the reader taps \"…more.\" Its only job is to make stopping the scroll feel involuntary and make the tap feel worth it. It isn't a summary of the post and it isn't a headline. It's the smallest promise you can make that a reader can't comfortably ignore.",[11,845,846],{},"Good hooks share one property: they create a small gap the reader wants closed. A specific number they want explained. A story they need to see finish. A claim they want to argue with. Everything below is a different way to open that gap.",[18,848,850],{"id":849},"how-the-more-cutoff-works","How the \"…more\" cutoff works",[11,852,853],{},"LinkedIn shows a preview of a post and truncates the rest behind \"…more.\" Exactly how much shows varies by device, screen size, and formatting, so don't optimize for a specific line count. Optimize for the truth underneath it: the first sentence, sometimes two, is all most people ever see. Front-load the interesting part and put nothing before it. A line spent introducing the post (\"I've been thinking about hiring lately…\") is a line the reader never gets past.",[18,855,857],{"id":856},"five-hook-types-that-work","Five hook types that work",[859,860,862],"h3",{"id":861},"_1-start-mid-story","1. Start mid-story",[11,864,865],{},"Drop the reader into a moment instead of setting one up.",[61,867,868,871],{},[64,869,870],{},"Weak: \"I want to share some thoughts on hiring.\"",[64,872,873],{},"Strong: \"I rejected the most qualified candidate I've ever interviewed. Here's why.\"",[11,875,876],{},"The second one puts a question in the reader's head before they've decided to care. You don't announce that a story is coming; you start it.",[859,878,880],{"id":879},"_2-use-a-specific-result","2. Use a specific result",[11,882,883],{},"A concrete number reads as proof that something real is behind the post.",[61,885,886,889],{},[64,887,888],{},"\"We cut churn from 6% to 2% in one quarter.\"",[64,890,891],{},"\"I reviewed 200 cold emails last week. Four got a reply.\"",[11,893,894],{},"Vague beats nobody. \"We improved retention\" is a shrug; \"6% to 2%\" is a promise.",[859,896,898],{"id":897},"_3-take-a-defensible-position","3. Take a defensible position",[11,900,901],{},"If your first line could be posted by any account in your industry, it won't stop anyone. Say something a reasonable person could disagree with.",[61,903,904,907],{},[64,905,906],{},"\"Most 'thought leadership' is fear of saying anything disagreeable.\"",[64,908,909],{},"\"Your best hire will probably fail your interview.\"",[11,911,912],{},"You don't have to be inflammatory. You have to be specific enough that someone could push back.",[859,914,916],{"id":915},"_4-reveal-a-surprising-contrast","4. Reveal a surprising contrast",[11,918,919],{},"Set an expectation in the first half of the sentence and break it in the second.",[61,921,922,925],{},[64,923,924],{},"\"The best marketing hire we made had never worked in marketing.\"",[64,926,927],{},"\"Our worst-performing post last month took me four minutes to write.\"",[11,929,930],{},"The gap between the setup and the twist is the hook. The reader keeps going to resolve it.",[859,932,934],{"id":933},"_5-open-a-curiosity-loop","5. Open a curiosity loop",[11,936,937],{},"State that something happened, or that you learned something, without saying what.",[61,939,940,943],{},[64,941,942],{},"\"One sentence in our onboarding email doubled activation. It's not the one you'd guess.\"",[64,944,945],{},"\"I fired our biggest client on purpose. Best decision we made all year.\"",[11,947,948],{},"A half-told thing is a loop the brain wants closed. Just make sure you actually close it in the post; an open loop with no payoff burns the next post's trust.",[18,950,952],{"id":951},"_25-linkedin-hook-examples-by-role","25 LinkedIn hook examples by role",[11,954,955],{},"Use these as patterns, not scripts. Swap in your own specifics; a hook is only as strong as the real detail behind it.",[859,957,959],{"id":958},"for-founders","For founders",[61,961,962,965,968,971,974],{},[64,963,964],{},"\"We hit $1M ARR with no marketing team. Here's exactly how the pipeline actually worked.\"",[64,966,967],{},"\"I almost shut the company down in March. What changed in six weeks.\"",[64,969,970],{},"\"The feature everyone asked for is the one that nearly killed us.\"",[64,972,973],{},"\"We raised a round we didn't need. I regret it.\"",[64,975,976],{},"\"Three years in, here's the advice I'd give myself on day one.\"",[859,978,980],{"id":979},"for-recruiters-and-hiring","For recruiters and hiring",[61,982,983,986,989,992,995],{},[64,984,985],{},"\"I've read 10,000 resumes. The ones that get interviews do one thing.\"",[64,987,988],{},"\"The best candidate I ever hired had a two-line cover letter.\"",[64,990,991],{},"\"Stop asking 'what's your biggest weakness.' Here's what to ask instead.\"",[64,993,994],{},"\"We removed the take-home test. Our hiring got better.\"",[64,996,997],{},"\"A candidate ghosted us after the offer. Their reason was fair.\"",[859,999,1001],{"id":1000},"for-sales-and-b2b","For sales and B2B",[61,1003,1004,1007,1010,1013,1016],{},[64,1005,1006],{},"\"I lost a $40k deal on a single sentence. Here it is.\"",[64,1008,1009],{},"\"The best sales email I ever sent was four lines long.\"",[64,1011,1012],{},"\"Discovery calls don't fail at the demo. They fail in the first two minutes.\"",[64,1014,1015],{},"\"We stopped chasing 'decision makers.' Close rate went up.\"",[64,1017,1018],{},"\"A prospect told me exactly why we lost. I wrote it all down.\"",[859,1020,1022],{"id":1021},"for-product-updates","For product updates",[61,1024,1025,1028,1031,1034,1037],{},[64,1026,1027],{},"\"We shipped the smallest feature of the quarter. It's the most used one.\"",[64,1029,1030],{},"\"You asked for dark mode for two years. Today it's live, and here's why it took so long.\"",[64,1032,1033],{},"\"We deleted half the settings page. Support tickets dropped.\"",[64,1035,1036],{},"\"The update nobody noticed made everything 40% faster.\"",[64,1038,1039],{},"\"We rebuilt the thing you complained about most. Try it and tell me if we got it right.\"",[859,1041,1043],{"id":1042},"for-personal-stories","For personal stories",[61,1045,1046,1049,1052,1055,1058],{},[64,1047,1048],{},"\"I got laid off on a Friday. By Monday I'd learned something I wish I'd known years earlier.\"",[64,1050,1051],{},"\"The advice that changed my career came from someone I almost didn't call back.\"",[64,1053,1054],{},"\"I said no to a promotion. Here's what happened next.\"",[64,1056,1057],{},"\"For ten years I optimized the wrong number.\"",[64,1059,1060],{},"\"My first manager did one thing I still copy today.\"",[18,1062,1064],{"id":1063},"hooks-that-usually-fail-and-the-fix","Hooks that usually fail (and the fix)",[61,1066,1067,1077,1086,1095,1104],{},[64,1068,1069,1072,1073,1076],{},[28,1070,1071],{},"The rhetorical question."," \"Ever struggled with X?\" reads as a stall. ",[28,1074,1075],{},"Fix:"," make a statement the reader can't answer without reading on.",[64,1078,1079,1082,1083,1085],{},[28,1080,1081],{},"Announcing the format."," \"Thread 🧵\" or \"A quick post about…\" spends the hook on logistics. ",[28,1084,1075],{}," open with the content, not the container.",[64,1087,1088,1091,1092,1094],{},[28,1089,1090],{},"Warming up."," The good line is often your second or third sentence. ",[28,1093,1075],{}," cut everything above it.",[64,1096,1097,1100,1101,1103],{},[28,1098,1099],{},"The vague promise."," \"Here are some tips to improve your marketing.\" ",[28,1102,1075],{}," name the specific and the stakes: \"The one email change that doubled our reply rate.\"",[64,1105,1106,1109,1110,1112],{},[28,1107,1108],{},"Too clever to parse."," A pun or riddle the reader has to decode. ",[28,1111,1075],{}," clarity beats cleverness in the feed. Say the interesting thing plainly.",[18,1114,1116],{"id":1115},"before-and-after-rewrites","Before-and-after rewrites",[61,1118,1119,1122,1125],{},[64,1120,1121],{},"Before: \"Excited to share that we've launched a new feature!\" → After: \"We shipped the feature you've asked for since 2024. It took longer than it should have, and here's why.\"",[64,1123,1124],{},"Before: \"Some thoughts on remote work culture.\" → After: \"We went fully remote and our best people got worse. Here's what we changed.\"",[64,1126,1127],{},"Before: \"Here's how to write better cold emails.\" → After: \"I sent 200 cold emails last week. The four that got replies had one line in common.\"",[11,1129,1130],{},"Each rewrite does the same thing: replaces the setup with a specific, and replaces the announcement with a promise.",[18,1132,1134],{"id":1133},"a-5-point-hook-checklist","A 5-point hook checklist",[11,1136,1137],{},"Before you publish, read only your first two lines and check:",[307,1139,1140,1143,1146,1149,1152],{},[64,1141,1142],{},"Does it open with a specific (a number, a name, a moment), not a setup?",[64,1144,1145],{},"Is there a gap the reader wants closed?",[64,1147,1148],{},"Could someone disagree with it, or is it safe enough to ignore?",[64,1150,1151],{},"Did you cut the warm-up sentence above the good line?",[64,1153,1154],{},"If you saw only these two lines in the feed, would you tap \"…more\"?",[11,1156,1157],{},"If any answer is no, fix it before you touch the rest of the post. The hook is the only part most of your audience will read, so it's the part worth the most editing.",[18,1159,1161],{"id":1160},"frequently-asked-questions","Frequently asked questions",[11,1163,1164,1167],{},[28,1165,1166],{},"How long should a LinkedIn hook be?","\nShort enough to land before the cutoff. One strong sentence is usually plenty; two if the second one raises the stakes. If your hook needs three lines to work, the good line is probably buried in the middle.",[11,1169,1170,1173],{},[28,1171,1172],{},"Should I use emojis in the hook?","\nAn emoji won't save a weak line, and it can read as decoration. Lead with the words. If an emoji adds meaning, fine; if it's there to look lively, cut it.",[11,1175,1176,1179],{},[28,1177,1178],{},"What's the single best first line for a LinkedIn post?","\nThere isn't one. The best first line is the most specific true thing you have: the number, the moment, the opinion you'd defend. Specificity does the work, not a formula.",[11,1181,1182,1185],{},[28,1183,1184],{},"How many hooks should I write per post?","\nWrite three or four openers for the same post and pick the one you'd stop scrolling for. The first hook you think of is rarely the sharpest.",[11,1187,1188,1191],{},[28,1189,1190],{},"Why do my posts get impressions but no clicks to \"…more\"?","\nImpressions mean the feed showed your hook and people kept scrolling. That's a hook problem, not a reach problem. Rewrite the first two lines before you change anything else.",[11,1193,1194,1195,1199,1200,1203,1204,150],{},"If your openers keep coming out generic, the issue is usually voice, not format. SelfSM drafts in each brand's voice with the AI tells stripped, so the hook lands as a person's and not a prompt's, and Chloe helps sharpen the opener before it goes out. ",[125,1196,1198],{"href":1197},"\u002F","See how it works",". Threads on X follow the same logic; if that's your channel, see ",[125,1201,1202],{"href":519},"four X thread structures that get read","; for the craft underneath, start with ",[125,1205,364],{"href":363},{"title":372,"searchDepth":373,"depth":373,"links":1207},[1208,1209,1210,1218,1225,1226,1227,1228],{"id":839,"depth":373,"text":840},{"id":849,"depth":373,"text":850},{"id":856,"depth":373,"text":857,"children":1211},[1212,1214,1215,1216,1217],{"id":861,"depth":1213,"text":862},3,{"id":879,"depth":1213,"text":880},{"id":897,"depth":1213,"text":898},{"id":915,"depth":1213,"text":916},{"id":933,"depth":1213,"text":934},{"id":951,"depth":373,"text":952,"children":1219},[1220,1221,1222,1223,1224],{"id":958,"depth":1213,"text":959},{"id":979,"depth":1213,"text":980},{"id":1000,"depth":1213,"text":1001},{"id":1021,"depth":1213,"text":1022},{"id":1042,"depth":1213,"text":1043},{"id":1063,"depth":373,"text":1064},{"id":1115,"depth":373,"text":1116},{"id":1133,"depth":373,"text":1134},{"id":1160,"depth":373,"text":1161},"2026-07-28","A practical guide to LinkedIn hooks: five hook types, 25+ examples by role, before-and-after rewrites, the mistakes that kill a post, and a short checklist.",{},"\u002Fblog\u002Flinkedin-hooks",{"title":831,"description":1230},"blog\u002Flinkedin-hooks",[394,1236],"hooks","-ZWLORCx8cXFCCLKAEq6jqLLT3Rv9ZrDxrmqLP3DteI",1787133213522]