[{"data":1,"prerenderedAt":1191},["ShallowReactive",2],{"blog:\u002Fblog\u002Fwhat-to-post-before-launch":3,"blog:related:\u002Fblog\u002Fwhat-to-post-before-launch":234},{"id":4,"title":5,"author":6,"body":7,"date":220,"description":221,"draft":222,"extension":223,"image":224,"meta":225,"navigation":226,"path":227,"seo":228,"stem":229,"tags":230,"updated":224,"__hash__":233},"blog\u002Fblog\u002Fwhat-to-post-before-launch.md","What to post before you have a product","SelfSM",{"type":8,"value":9,"toc":209},"minimark",[10,14,17,20,25,28,57,64,68,74,80,86,92,98,104,110,113,117,120,123,129,135,139,142,151,155,158,161,165,168,175,179,185,191,197,203],[11,12,13],"p",{},"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,15,16],{},"Both are worse than posting nothing. The takes are invisible; the inflated claims are remembered.",[11,18,19],{},"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.",[21,22,24],"h2",{"id":23},"the-claims-that-cost-you-later","The claims that cost you later",[11,26,27],{},"Start with what not to write, because pre-launch is where founders damage trust fastest and least deliberately.",[29,30,31,39,45,51],"ul",{},[32,33,34,38],"li",{},[35,36,37],"strong",{},"\"Our customers are seeing…\""," when there are three design partners on a free tier. The plural is the lie, and someone will ask.",[32,40,41,44],{},[35,42,43],{},"\"We're growing fast\""," off a base of 40 signups. Not false, exactly, and everyone reads it as false.",[32,46,47,50],{},[35,48,49],{},"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.",[32,52,53,56],{},[35,54,55],{},"Borrowed authority."," Writing about scaling when you have not scaled anything. Readers who have done it can tell in one paragraph.",[11,58,59,60,63],{},"The rule that survives all of these: ",[35,61,62],{},"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.",[21,65,67],{"id":66},"seven-angles-that-work-with-zero-customers","Seven angles that work with zero customers",[11,69,70,73],{},[35,71,72],{},"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,75,76,79],{},[35,77,78],{},"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,81,82,85],{},[35,83,84],{},"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,87,88,91],{},[35,89,90],{},"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,93,94,97],{},[35,95,96],{},"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,99,100,103],{},[35,101,102],{},"6. The thing you refuse to build."," Positioning stated as a boundary is memorable and commits you publicly, which is useful discipline.",[11,105,106,109],{},[35,107,108],{},"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,111,112],{},"Notice that six of seven require no traction at all. They require you to be doing the work and willing to describe it accurately.",[21,114,116],{"id":115},"build-the-audience-the-launch-lands-on","Build the audience the launch lands on",[11,118,119],{},"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,121,122],{},"Two things matter more than volume:",[11,124,125,128],{},[35,126,127],{},"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,130,131,134],{},[35,132,133],{},"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.",[21,136,138],{"id":137},"the-frequency-question","The frequency question",[11,140,141],{},"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,143,144,145,150],{},"Pre-launch is a stamina problem, not an intensity problem. The ",[146,147,149],"a",{"href":148},"\u002Fblog\u002Ffounder-content-30-minutes-a-week","30-minutes-a-week method"," exists precisely because the pre-launch period is long and the founder's attention is not.",[21,152,154],{"id":153},"when-the-product-ships","When the product ships",[11,156,157],{},"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,159,160],{},"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.",[21,162,164],{"id":163},"where-a-tool-helps-and-where-it-does-not","Where a tool helps and where it does not",[11,166,167],{},"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,169,170,171,174],{},"That second one is why ",[146,172,6],{"href":173},"\u002Ffor\u002Ffounders"," 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.",[21,176,178],{"id":177},"faq","FAQ",[11,180,181,184],{},[35,182,183],{},"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,186,187,190],{},[35,188,189],{},"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,192,193,196],{},[35,194,195],{},"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,198,199,202],{},[35,200,201],{},"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,204,205,208],{},[35,206,207],{},"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":210,"searchDepth":211,"depth":211,"links":212},"",2,[213,214,215,216,217,218,219],{"id":23,"depth":211,"text":24},{"id":66,"depth":211,"text":67},{"id":115,"depth":211,"text":116},{"id":137,"depth":211,"text":138},{"id":153,"depth":211,"text":154},{"id":163,"depth":211,"text":164},{"id":177,"depth":211,"text":178},"2026-08-19","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.",false,"md",null,{},true,"\u002Fblog\u002Fwhat-to-post-before-launch",{"title":5,"description":221},"blog\u002Fwhat-to-post-before-launch",[231,232],"founders","strategy","BSnR1nRUYwbsZ1GSrvhdK1ruP7msgCwyyzC96eDms3M",[235,459,829],{"id":236,"title":237,"author":6,"body":238,"date":220,"description":452,"draft":222,"extension":223,"image":224,"meta":453,"navigation":226,"path":148,"seo":454,"stem":455,"tags":456,"updated":224,"__hash__":458},"blog\u002Fblog\u002Ffounder-content-30-minutes-a-week.md","Founder content in 30 minutes a week",{"type":8,"value":239,"toc":443},[240,243,246,249,253,256,262,268,271,275,278,284,290,301,304,308,311,338,341,345,351,362,368,379,383,386,392,398,402,405,411,413,419,425,431,437],[11,241,242],{},"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,244,245],{},"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,247,248],{},"Here is the method, and the two places it breaks.",[21,250,252],{"id":251},"the-two-habits-not-one","The two habits, not one",[11,254,255],{},"This runs on a capture habit and a writing habit, and people who try to skip the first one always fail.",[11,257,258,261],{},[35,259,260],{},"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,263,264,267],{},[35,265,266],{},"Habit 2 — write, 30 minutes, once a week."," Open the capture list, pick four, write four posts, done.",[11,269,270],{},"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.",[21,272,274],{"id":273},"what-actually-goes-in-the-30-minutes","What actually goes in the 30 minutes",[11,276,277],{},"Timeboxed, because the point is that it ends.",[11,279,280,283],{},[35,281,282],{},"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,285,286,289],{},[35,287,288],{},"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,291,292,295,296,300],{},[35,293,294],{},"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 ",[146,297,299],{"href":298},"\u002Fblog\u002Fhumanize-chatgpt-draft","how to edit a draft so it sounds like you",".",[11,302,303],{},"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.",[21,305,307],{"id":306},"the-four-kinds-of-post-you-already-have-material-for","The four kinds of post you already have material for",[11,309,310],{},"The reason a founder's blank page is a lie: you generate publishable material every week and throw it away.",[312,313,314,320,326,332],"ol",{},[32,315,316,319],{},[35,317,318],{},"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.",[32,321,322,325],{},[35,323,324],{},"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.",[32,327,328,331],{},[35,329,330],{},"Something a customer said, verbatim."," Half a sentence from a support ticket, with what you did about it.",[32,333,334,337],{},[35,335,336],{},"Something you were wrong about."," The highest-performing founder content is almost always this, and the most under-supplied.",[11,339,340],{},"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.",[21,342,344],{"id":343},"what-to-cut","What to cut",[11,346,347,350],{},[35,348,349],{},"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,352,353,356,357,361],{},[35,354,355],{},"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: ",[146,358,360],{"href":359},"\u002Fblog\u002Fx-thread-structures","threads"," are not long LinkedIn posts.",[11,363,364,367],{},[35,365,366],{},"Cut comment-hour."," Engagement pods and reply-farming produce numbers that do not turn into anything. Reply when you have something to say.",[11,369,370,373,374,378],{},[35,371,372],{},"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 ",[146,375,377],{"href":376},"\u002Fblog\u002Fcontent-calendar-you-can-keep","a real calendar"," starts earning its keep.)",[21,380,382],{"id":381},"where-it-breaks","Where it breaks",[11,384,385],{},"Two failure modes, and they are predictable.",[11,387,388,391],{},[35,389,390],{},"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,393,394,397],{},[35,395,396],{},"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.",[21,399,401],{"id":400},"when-30-minutes-stops-being-enough","When 30 minutes stops being enough",[11,403,404],{},"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,406,407,408,410],{},"That is the gap ",[146,409,6],{"href":173}," 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.",[21,412,178],{"id":177},[11,414,415,418],{},[35,416,417],{},"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,420,421,424],{},[35,422,423],{},"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,426,427,430],{},[35,428,429],{},"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,432,433,436],{},[35,434,435],{},"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,438,439,442],{},[35,440,441],{},"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":210,"searchDepth":211,"depth":211,"links":444},[445,446,447,448,449,450,451],{"id":251,"depth":211,"text":252},{"id":273,"depth":211,"text":274},{"id":306,"depth":211,"text":307},{"id":343,"depth":211,"text":344},{"id":381,"depth":211,"text":382},{"id":400,"depth":211,"text":401},{"id":177,"depth":211,"text":178},"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":237,"description":452},"blog\u002Ffounder-content-30-minutes-a-week",[231,457],"workflow","c60V464WB1BI_vgU9XOGDOMBQj1HC-370I227cxxQkk",{"id":460,"title":461,"author":6,"body":462,"date":220,"description":821,"draft":222,"extension":223,"image":224,"meta":822,"navigation":226,"path":823,"seo":824,"stem":825,"tags":826,"updated":224,"__hash__":828},"blog\u002Fblog\u002Flinkedin-ghostwriter-cost.md","What a LinkedIn ghostwriter costs (and when one is worth it)",{"type":8,"value":463,"toc":812},[464,467,470,474,477,483,489,495,498,502,508,511,531,534,537,541,544,547,577,580,584,587,596,602,612,616,743,747,750,776,778,784,790,796,806],[11,465,466],{},"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,468,469],{},"Here are the real ranges, the cost that never appears on the invoice, and the point where hiring stops being a luxury.",[21,471,473],{"id":472},"the-three-price-tiers","The three price tiers",[11,475,476],{},"Rates vary by market and by how much of the work is writing versus strategy, but ghostwriting offers cluster into three recognisable bands.",[11,478,479,482],{},[35,480,481],{},"$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,484,485,488],{},[35,486,487],{},"$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,490,491,494],{},[35,492,493],{},"$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,496,497],{},"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.",[21,499,501],{"id":500},"the-cost-nobody-quotes-you-your-own-hours","The cost nobody quotes you: your own hours",[11,503,504,505],{},"The invoice is the visible cost. The invisible one is that ",[35,506,507],{},"a ghostwriter cannot write about your business without you.",[11,509,510],{},"Every good ghostwriting relationship needs roughly:",[29,512,513,519,525],{},[32,514,515,518],{},[35,516,517],{},"A 45–60 minute interview call",", monthly at minimum, often weekly at the start.",[32,520,521,524],{},[35,522,523],{},"Voice notes or messages"," when something happens worth writing about — a customer result, a decision, a mistake.",[32,526,527,530],{},[35,528,529],{},"A review pass on every draft."," Not a rubber stamp: you are the only person who knows whether the number is right.",[11,532,533],{},"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,535,536],{},"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.",[21,538,540],{"id":539},"when-it-pays-for-itself","When it pays for itself",[11,542,543],{},"The honest test is not \"can I afford $2,000 a month.\" It is \"does one outcome from LinkedIn cover it.\"",[11,545,546],{},"Run the arithmetic on your own numbers:",[29,548,549,555,561,567],{},[32,550,551,554],{},[35,552,553],{},"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.",[32,556,557,560],{},[35,558,559],{},"If you're hiring",", one senior engineer sourced inbound saves a recruiter fee of $25–40k. Same conclusion.",[32,562,563,566],{},[35,564,565],{},"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.",[32,568,569,572,573,576],{},[35,570,571],{},"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 ",[146,574,575],{"href":227},"what to post before you have a product"," for the cheaper version.",[11,578,579],{},"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.",[21,581,583],{"id":582},"three-cheaper-setups-that-work","Three cheaper setups that work",[11,585,586],{},"Hiring is not the only way to solve \"I don't post.\"",[11,588,589,592,593,300],{},[35,590,591],{},"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 ",[146,594,595],{"href":148},"founder content in 30 minutes a week",[11,597,598,601],{},[35,599,600],{},"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,603,604,607,608,611],{},[35,605,606],{},"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 ",[146,609,610],{"href":173},"what SelfSM does",", at roughly a tenth of the standard ghostwriting tier.",[21,613,615],{"id":614},"the-comparison-plainly","The comparison, plainly",[617,618,619,639],"table",{},[620,621,622],"thead",{},[623,624,625,628,631,634,637],"tr",{},[626,627],"th",{},[626,629,630],{},"Ghostwriter",[626,632,633],{},"Editor",[626,635,636],{},"ChatGPT",[626,638,6],{},[640,641,642,660,677,694,711,728],"tbody",{},[623,643,644,648,651,654,657],{},[645,646,647],"td",{},"Monthly cost",[645,649,650],{},"$1,500–4,000",[645,652,653],{},"$300–800",[645,655,656],{},"~$20",[645,658,659],{},"$0–19",[623,661,662,665,668,671,674],{},[645,663,664],{},"Your hours per month",[645,666,667],{},"3–5",[645,669,670],{},"2–4",[645,672,673],{},"4–8",[645,675,676],{},"1–2",[623,678,679,682,685,688,691],{},[645,680,681],{},"Sounds like you",[645,683,684],{},"After 2–3 months",[645,686,687],{},"Yes, it's your text",[645,689,690],{},"Rarely",[645,692,693],{},"From your own posts",[623,695,696,699,702,705,708],{},[645,697,698],{},"Knows your facts",[645,700,701],{},"If you brief them",[645,703,704],{},"Yes",[645,706,707],{},"No — invents them",[645,709,710],{},"Stored per brand",[623,712,713,716,719,722,725],{},[645,714,715],{},"Decides what to post",[645,717,718],{},"They do",[645,720,721],{},"You do",[645,723,724],{},"You prompt it",[645,726,727],{},"Proposed weekly",[623,729,730,733,735,738,741],{},[645,731,732],{},"Survives a chaotic month",[645,734,704],{},[645,736,737],{},"Partly",[645,739,740],{},"No",[645,742,704],{},[21,744,746],{"id":745},"what-to-ask-before-you-hire","What to ask before you hire",[11,748,749],{},"If you do hire, four questions separate the good ones from the expensive ones:",[312,751,752,758,764,770],{},[32,753,754,757],{},[35,755,756],{},"\"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.",[32,759,760,763],{},[35,761,762],{},"\"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.",[32,765,766,769],{},[35,767,768],{},"\"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.",[32,771,772,775],{},[35,773,774],{},"\"What's the minimum I have to give you each week?\""," If they cannot answer in one sentence, the process is not real yet.",[21,777,178],{"id":177},[11,779,780,783],{},[35,781,782],{},"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,785,786,789],{},[35,787,788],{},"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,791,792,795],{},[35,793,794],{},"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,797,798,801,802,300],{},[35,799,800],{},"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 ",[146,803,805],{"href":804},"\u002Fblog\u002Fai-writing-tells","the tells that make writing sound like AI",[11,807,808,811],{},[35,809,810],{},"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":210,"searchDepth":211,"depth":211,"links":813},[814,815,816,817,818,819,820],{"id":472,"depth":211,"text":473},{"id":500,"depth":211,"text":501},{"id":539,"depth":211,"text":540},{"id":582,"depth":211,"text":583},{"id":614,"depth":211,"text":615},{"id":745,"depth":211,"text":746},{"id":177,"depth":211,"text":178},"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.",{},"\u002Fblog\u002Flinkedin-ghostwriter-cost",{"title":461,"description":821},"blog\u002Flinkedin-ghostwriter-cost",[231,827],"linkedin","hJwZRfT4-lH5xI1xcU_CPlVSXPJcD-RTMhK27jMub3s",{"id":830,"title":831,"author":6,"body":832,"date":1183,"description":1184,"draft":222,"extension":223,"image":224,"meta":1185,"navigation":226,"path":376,"seo":1186,"stem":1187,"tags":1188,"updated":224,"__hash__":1190},"blog\u002Fblog\u002Fcontent-calendar-you-can-keep.md","A 4-week content calendar you can actually keep",{"type":8,"value":833,"toc":1172},[834,842,846,853,856,860,863,899,902,906,909,1022,1025,1029,1032,1066,1069,1073,1076,1080,1083,1087,1090,1094,1097,1129,1133,1139,1149,1159,1169],[11,835,836,837,841],{},"Most content calendars collapse for one reason: \"post every day\" is a schedule, not a plan. Every morning becomes a decision, and decisions are where consistency goes to die. This is a calendar built to survive that. It decides the ",[838,839,840],"em",{},"kind"," of post ahead of time so that filling any given day is a small task instead of a blank page. You'll get the five buckets it runs on, a filled four-week example you can copy, notes for adapting it per platform, and a template to reuse each month.",[21,843,845],{"id":844},"what-a-content-calendar-actually-is","What a content calendar actually is",[11,847,848,849,852],{},"A content calendar is a plan that assigns each posting slot a ",[838,850,851],{},"job"," before you write a word. Not the exact caption, and not a rigid script. Just the type of post that goes there: a teaching post, a proof post, a personal one. The value isn't the grid. It's that you never sit down to \"do social\" and instead sit down to \"write today's proof post,\" which is a task small enough to actually finish.",[11,854,855],{},"A good calendar does three things: it stops you repeating the same note two days running, it removes the daily \"what do I post\" decision, and it leaves room to react when something real happens.",[21,857,859],{"id":858},"the-five-buckets","The five buckets",[11,861,862],{},"Rotate every post through five recurring types. Each does a different job for your audience.",[312,864,865,871,877,883,889],{},[32,866,867,870],{},[35,868,869],{},"Expertise & frameworks."," Teach one thing you know well. Example: \"The three questions I ask before taking on any client.\" These build authority.",[32,872,873,876],{},[35,874,875],{},"Industry take."," React to something happening in your field. Example: a short, opinionated post on a competitor's pricing change. Timely, and it shows you're paying attention.",[32,878,879,882],{},[35,880,881],{},"Proof."," A result, a case, a before-and-after. Example: \"How we took a client from 200 to 2,000 followers in eight weeks.\" This is what convinces buyers.",[32,884,885,888],{},[35,886,887],{},"Build in public."," What you're working on, what broke, what you learned this week. Example: \"We changed our onboarding and support tickets dropped by half.\" Honest and relatable.",[32,890,891,894,895,898],{},[35,892,893],{},"Human."," A moment, a story, something that isn't strictly business. Example: \"What running taught me about shipping work.\" This is what makes people remember ",[838,896,897],{},"you",", not just your feed.",[11,900,901],{},"Across four weeks you touch all five repeatedly without ever running two of the same in a row.",[21,903,905],{"id":904},"a-filled-example-four-weeks","A filled example: four weeks",[11,907,908],{},"Here's the rotation as a real grid, Monday to Friday. The bucket is the job; the note is a sample angle you'd swap for your own.",[617,910,911,932],{},[620,912,913],{},[623,914,915,917,920,923,926,929],{},[626,916],{},[626,918,919],{},"Mon",[626,921,922],{},"Tue",[626,924,925],{},"Wed",[626,927,928],{},"Thu",[626,930,931],{},"Fri",[640,933,934,956,978,1000],{},[623,935,936,941,944,947,950,953],{},[645,937,938],{},[35,939,940],{},"Week 1",[645,942,943],{},"Expertise: a framework you use",[645,945,946],{},"Industry: react to news",[645,948,949],{},"Proof: a recent result",[645,951,952],{},"Build: what you shipped",[645,954,955],{},"Human: a weekend story",[623,957,958,963,966,969,972,975],{},[645,959,960],{},[35,961,962],{},"Week 2",[645,964,965],{},"Proof: a client before\u002Fafter",[645,967,968],{},"Expertise: a common mistake",[645,970,971],{},"Human: a lesson from outside work",[645,973,974],{},"Industry: a hot take",[645,976,977],{},"Build: a work-in-progress",[623,979,980,985,988,991,994,997],{},[645,981,982],{},[35,983,984],{},"Week 3",[645,986,987],{},"Expertise: answer a FAQ",[645,989,990],{},"Build: a decision you made",[645,992,993],{},"Proof: a testimonial in context",[645,995,996],{},"Industry: a trend you disagree with",[645,998,999],{},"Human: something you changed your mind on",[623,1001,1002,1007,1010,1013,1016,1019],{},[645,1003,1004],{},[35,1005,1006],{},"Week 4",[645,1008,1009],{},"Industry: a prediction",[645,1011,1012],{},"Proof: a small win",[645,1014,1015],{},"Expertise: a step-by-step",[645,1017,1018],{},"Human: a personal update",[645,1020,1021],{},"Build: what's next",[11,1023,1024],{},"Twenty slots, five buckets, no two the same twice in a row. You can shift the order to fit your week; the point is that every day already has a job.",[21,1026,1028],{"id":1027},"adapt-it-per-platform","Adapt it per platform",[11,1030,1031],{},"The buckets stay the same across platforms; the format changes.",[29,1033,1034,1045,1054,1060],{},[32,1035,1036,1039,1040,1044],{},[35,1037,1038],{},"LinkedIn."," Longer posts work. Lean into Expertise, Proof, and Human, and open every one with a strong first line (",[146,1041,1043],{"href":1042},"\u002Fblog\u002Flinkedin-hooks","how to write a hook that earns the click",").",[32,1046,1047,1050,1051,1044],{},[35,1048,1049],{},"X (Twitter)."," Shorter and faster. Industry takes and Build-in-public fit best, and longer points become threads (",[146,1052,1053],{"href":359},"thread structures that get read",[32,1055,1056,1059],{},[35,1057,1058],{},"Instagram."," Visual-first. Proof (before\u002Fafter) and Human (behind-the-scenes) translate best to images and carousels.",[32,1061,1062,1065],{},[35,1063,1064],{},"Newsletter."," Depth. One Expertise or Proof piece a week, expanded, with the shorter social posts feeding it.",[11,1067,1068],{},"Run the same five-bucket rotation, and let each platform take the version of the bucket that suits it.",[21,1070,1072],{"id":1071},"map-the-month-in-one-sitting","Map the month in one sitting",[11,1074,1075],{},"Don't plan day by day. Sit down once, open the grid, and drop bucket labels across four weeks. You're not writing yet, just assigning jobs. That's twenty small decisions made together, when you have context, instead of twenty decisions made cold at 8am.",[21,1077,1079],{"id":1078},"batch-the-writing","Batch the writing",[11,1081,1082],{},"Once the slots have jobs, write in batches by bucket. Three \"proof\" posts back to back is far faster than one of each, because you stay in the same headspace and reuse the same raw material. Block an hour, pick a bucket, and draft everything of that type for the fortnight.",[21,1084,1086],{"id":1085},"leave-room-to-react","Leave room to react",[11,1088,1089],{},"Keep one or two slots a week loose. When something real happens (a launch, a news moment, a customer win), it goes there. A calendar that's 100% pre-planned can't respond to the present, and the present is usually your best material. The loose slots are where the calendar meets real life.",[21,1091,1093],{"id":1092},"a-reusable-template","A reusable template",[11,1095,1096],{},"Copy this and refill it each month:",[29,1098,1099,1105,1111,1117,1123],{},[32,1100,1101,1104],{},[35,1102,1103],{},"Buckets:"," Expertise, Industry, Proof, Build, Human.",[32,1106,1107,1110],{},[35,1108,1109],{},"Grid:"," 4 weeks × your posting days, one bucket per slot, no repeats back to back.",[32,1112,1113,1116],{},[35,1114,1115],{},"Loose slots:"," 1–2 per week, left open for reactive posts.",[32,1118,1119,1122],{},[35,1120,1121],{},"Batch blocks:"," one writing session per bucket, per fortnight.",[32,1124,1125,1128],{},[35,1126,1127],{},"Feed loop:"," at month's end, note which posts landed and make more of that bucket next month.",[21,1130,1132],{"id":1131},"frequently-asked-questions","Frequently asked questions",[11,1134,1135,1138],{},[35,1136,1137],{},"How many times a week should I post?","\nWhatever you can keep up without dropping quality. Five weekdays is a full rotation; three is fine and beats five you can't sustain. Consistency matters more than frequency.",[11,1140,1141,1144,1145,1148],{},[35,1142,1143],{},"How far ahead should I plan?","\nPlan the buckets for four weeks; write one to two weeks ahead. Planning the ",[838,1146,1147],{},"jobs"," far out is cheap and stabilizing; drafting the exact words too far ahead means rewriting when the moment shifts.",[11,1150,1151,1154,1155,300],{},[35,1152,1153],{},"What if I run out of ideas for a bucket?","\nThat's usually a capture problem, not a creativity one. Keep a running note of raw ideas as they hit you, and shaping a week's posts becomes selection instead of invention. See ",[146,1156,1158],{"href":1157},"\u002Fblog\u002Fidea-to-published-pipeline","the idea-to-published pipeline",[11,1160,1161,1164,1165,1168],{},[35,1162,1163],{},"Do I need a tool for this?","\nA spreadsheet and a notes app run it fine for one brand. Across several clients, each needing its own grid, buckets, and drafts, keeping it all straight becomes its own job. That's where ",[146,1166,6],{"href":1167},"\u002F"," takes over: it plans the month, drafts each slot in the brand's voice with the AI tells stripped, and ships the posts, with Chloe running the calendar alongside you like a brand manager.",[11,1170,1171],{},"The goal is simple: never face a blank page cold. Give each day a job, batch the work, and leave a little space for real life to interrupt.",{"title":210,"searchDepth":211,"depth":211,"links":1173},[1174,1175,1176,1177,1178,1179,1180,1181,1182],{"id":844,"depth":211,"text":845},{"id":858,"depth":211,"text":859},{"id":904,"depth":211,"text":905},{"id":1027,"depth":211,"text":1028},{"id":1071,"depth":211,"text":1072},{"id":1078,"depth":211,"text":1079},{"id":1085,"depth":211,"text":1086},{"id":1092,"depth":211,"text":1093},{"id":1131,"depth":211,"text":1132},"2026-07-20","A five-bucket content calendar that keeps you posting without a blank page every morning: what to post, a filled four-week example, per-platform notes, and a reusable template.",{},{"title":831,"description":1184},"blog\u002Fcontent-calendar-you-can-keep",[232,1189],"content calendar","eN-UW7Z51MqdV3_GT3y9Hp5saR1TaIgL7BNCblfsuFs",1787133213965]