[{"data":1,"prerenderedAt":1030},["ShallowReactive",2],{"blog:\u002Fblog\u002Ffounder-content-30-minutes-a-week":3,"blog:related:\u002Fblog\u002Ffounder-content-30-minutes-a-week":246},{"id":4,"title":5,"author":6,"body":7,"date":232,"description":233,"draft":234,"extension":235,"image":236,"meta":237,"navigation":238,"path":239,"seo":240,"stem":241,"tags":242,"updated":236,"__hash__":245},"blog\u002Fblog\u002Ffounder-content-30-minutes-a-week.md","Founder content in 30 minutes a week","SelfSM",{"type":8,"value":9,"toc":221},"minimark",[10,14,17,20,25,28,35,41,44,48,51,57,63,75,78,82,85,113,116,120,126,137,143,154,158,161,167,173,177,180,187,191,197,203,209,215],[11,12,13],"p",{},"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,15,16],{},"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,18,19],{},"Here is the method, and the two places it breaks.",[21,22,24],"h2",{"id":23},"the-two-habits-not-one","The two habits, not one",[11,26,27],{},"This runs on a capture habit and a writing habit, and people who try to skip the first one always fail.",[11,29,30,34],{},[31,32,33],"strong",{},"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,36,37,40],{},[31,38,39],{},"Habit 2 — write, 30 minutes, once a week."," Open the capture list, pick four, write four posts, done.",[11,42,43],{},"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,45,47],{"id":46},"what-actually-goes-in-the-30-minutes","What actually goes in the 30 minutes",[11,49,50],{},"Timeboxed, because the point is that it ends.",[11,52,53,56],{},[31,54,55],{},"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,58,59,62],{},[31,60,61],{},"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,64,65,68,69,74],{},[31,66,67],{},"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 ",[70,71,73],"a",{"href":72},"\u002Fblog\u002Fhumanize-chatgpt-draft","how to edit a draft so it sounds like you",".",[11,76,77],{},"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,79,81],{"id":80},"the-four-kinds-of-post-you-already-have-material-for","The four kinds of post you already have material for",[11,83,84],{},"The reason a founder's blank page is a lie: you generate publishable material every week and throw it away.",[86,87,88,95,101,107],"ol",{},[89,90,91,94],"li",{},[31,92,93],{},"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.",[89,96,97,100],{},[31,98,99],{},"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.",[89,102,103,106],{},[31,104,105],{},"Something a customer said, verbatim."," Half a sentence from a support ticket, with what you did about it.",[89,108,109,112],{},[31,110,111],{},"Something you were wrong about."," The highest-performing founder content is almost always this, and the most under-supplied.",[11,114,115],{},"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,117,119],{"id":118},"what-to-cut","What to cut",[11,121,122,125],{},[31,123,124],{},"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,127,128,131,132,136],{},[31,129,130],{},"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: ",[70,133,135],{"href":134},"\u002Fblog\u002Fx-thread-structures","threads"," are not long LinkedIn posts.",[11,138,139,142],{},[31,140,141],{},"Cut comment-hour."," Engagement pods and reply-farming produce numbers that do not turn into anything. Reply when you have something to say.",[11,144,145,148,149,153],{},[31,146,147],{},"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 ",[70,150,152],{"href":151},"\u002Fblog\u002Fcontent-calendar-you-can-keep","a real calendar"," starts earning its keep.)",[21,155,157],{"id":156},"where-it-breaks","Where it breaks",[11,159,160],{},"Two failure modes, and they are predictable.",[11,162,163,166],{},[31,164,165],{},"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,168,169,172],{},[31,170,171],{},"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,174,176],{"id":175},"when-30-minutes-stops-being-enough","When 30 minutes stops being enough",[11,178,179],{},"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,181,182,183,186],{},"That is the gap ",[70,184,6],{"href":185},"\u002Ffor\u002Ffounders"," 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,188,190],{"id":189},"faq","FAQ",[11,192,193,196],{},[31,194,195],{},"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,198,199,202],{},[31,200,201],{},"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,204,205,208],{},[31,206,207],{},"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,210,211,214],{},[31,212,213],{},"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,216,217,220],{},[31,218,219],{},"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":222,"searchDepth":223,"depth":223,"links":224},"",2,[225,226,227,228,229,230,231],{"id":23,"depth":223,"text":24},{"id":46,"depth":223,"text":47},{"id":80,"depth":223,"text":81},{"id":118,"depth":223,"text":119},{"id":156,"depth":223,"text":157},{"id":175,"depth":223,"text":176},{"id":189,"depth":223,"text":190},"2026-08-19","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.",false,"md",null,{},true,"\u002Fblog\u002Ffounder-content-30-minutes-a-week",{"title":5,"description":233},"blog\u002Ffounder-content-30-minutes-a-week",[243,244],"founders","workflow","c60V464WB1BI_vgU9XOGDOMBQj1HC-370I227cxxQkk",[247,538,811],{"id":248,"title":249,"author":6,"body":250,"date":232,"description":530,"draft":234,"extension":235,"image":236,"meta":531,"navigation":238,"path":532,"seo":533,"stem":534,"tags":535,"updated":236,"__hash__":537},"blog\u002Fblog\u002Fagency-roles-for-social-content.md","Agency roles for social content: who drafts, who approves, who releases",{"type":8,"value":251,"toc":521},[252,255,262,266,269,275,281,287,293,300,304,307,313,319,325,332,336,339,406,414,418,421,424,427,442,446,452,458,464,470,474,477,489,491,497,503,509,515],[11,253,254],{},"Small agencies run on one person per account. That person writes, decides, sends to the client and publishes, and it works beautifully right up to the point where they are on holiday, or leave, or make one mistake at scale.",[11,256,257,258,261],{},"The fix is not more process. It is separating four things that are usually one thing: ",[31,259,260],{},"drafting, internal approval, client release, and publishing",". Once they are separate permissions rather than stages in one person's head, juniors can do real work, seniors stop being a bottleneck on every post, and no single mistake reaches a client feed unaccompanied.",[21,263,265],{"id":264},"the-four-permissions","The four permissions",[11,267,268],{},"They are worth naming precisely because most tools and most agencies collapse them into two.",[11,270,271,274],{},[31,272,273],{},"Draft."," Create and edit content. The permission a junior or a freelancer should have on day one, on real accounts. There is no faster way to train someone and no reason to withhold it, because drafting is reversible.",[11,276,277,280],{},[31,278,279],{},"Approve internally."," Assert that this is good enough to show the client: on brand, factually sourced, within scope. This is a quality and risk judgment and it belongs to whoever is accountable for the account, not to whoever wrote it.",[11,282,283,286],{},[31,284,285],{},"Release to client."," Send it out of the agency. Separate from internal approval because it is the moment work becomes visible to someone who is paying, and because the person who should own client communication is often not the person who owns editorial quality.",[11,288,289,292],{},[31,290,291],{},"Publish."," Put it on the account. The narrowest permission, and the one most agencies hand out most casually.",[11,294,295,296,299],{},"The important claim: ",[31,297,298],{},"approve and publish must not be the same permission."," A post can be approved on Tuesday and correct, and publishing it on Thursday can still be wrong because the client announced a layoff on Wednesday. Someone has to own the moment, not just the artefact.",[21,301,303],{"id":302},"the-three-roles-this-produces","The three roles this produces",[11,305,306],{},"Map the permissions onto people and you get a shape that works from three people to thirty.",[11,308,309,312],{},[31,310,311],{},"Writer"," — drafts. Junior, freelancer, or a senior on a client they know well. Has access to that brand's voice definition, fact file and forbidden list, and nothing else. Cannot release, cannot publish.",[11,314,315,318],{},[31,316,317],{},"Account lead"," — approves internally and releases to the client. Accountable for the account: the editorial standard, the factual sourcing, the client relationship. One named person per client, always, including holiday cover assigned in advance.",[11,320,321,324],{},[31,322,323],{},"Publisher"," — publishes on schedule. Often the same person as the account lead in a small agency, and that is fine. What matters is that it is a distinct act with its own check, not a side effect of approval. On larger books this is genuinely a separate role with a daily pre-publish sweep.",[11,326,327,328,74],{},"Plus the client, who approves what the account lead released. That flow is a different problem with its own failure modes — see ",[70,329,331],{"href":330},"\u002Fblog\u002Fcontent-approval-workflow","the approval workflow that doesn't lose the client",[21,333,335],{"id":334},"what-each-stage-actually-checks","What each stage actually checks",[11,337,338],{},"Roles without checks are just job titles. Each gate is looking for something specific, and the specificity is what makes it fast.",[340,341,342,358],"table",{},[343,344,345],"thead",{},[346,347,348,352,355],"tr",{},[349,350,351],"th",{},"Stage",[349,353,354],{},"The question",[349,356,357],{},"Blocks on",[359,360,361,373,384,395],"tbody",{},[346,362,363,367,370],{},[364,365,366],"td",{},"Draft",[364,368,369],{},"Does this say something, in this brand's voice?",[364,371,372],{},"Generic content, wrong register",[346,374,375,378,381],{},[364,376,377],{},"Internal approve",[364,379,380],{},"Is every factual claim sourced and in scope?",[364,382,383],{},"Unsourced numbers, over-generalised claims",[346,385,386,389,392],{},[364,387,388],{},"Release",[364,390,391],{},"Is this the right thing to send this client this week?",[364,393,394],{},"Bad timing, scope creep, tone against context",[346,396,397,400,403],{},[364,398,399],{},"Publish",[364,401,402],{},"Has anything changed since approval?",[364,404,405],{},"News events, client announcements, live incidents",[11,407,408,409,413],{},"The internal approval gate is where ",[70,410,412],{"href":411},"\u002Fblog\u002Fwho-is-responsible-for-a-wrong-claim","wrong claims"," get caught, and it is the gate most often skipped when the account lead is busy. If one gate has to be defended, defend that one.",[21,415,417],{"id":416},"give-juniors-real-work-not-fake-work","Give juniors real work, not fake work",[11,419,420],{},"The common failure is over-correcting: juniors get research and scheduling, seniors write everything, and the agency has a capacity ceiling equal to its senior headcount plus a training programme that produces nobody.",[11,422,423],{},"A permission model makes the safe version possible. A junior drafting on a live account with no release permission cannot cause an incident, so there is no reason to hold them back from the work that actually teaches — writing in someone else's voice against real constraints and getting edited.",[11,425,426],{},"Two things make this work in practice:",[428,429,430,436],"ul",{},[89,431,432,435],{},[31,433,434],{},"Edits go back with reasons."," \"Cut this, it's puffery\" teaches; a silently rewritten draft teaches nothing and is the most common way agencies fail to develop people.",[89,437,438,441],{},[31,439,440],{},"The voice definition and fact file are accessible to the writer."," If the standard lives only in the account lead's head, the junior cannot hit it and the feedback loop is arbitrary. Writing it down is what makes delegation possible at all.",[21,443,445],{"id":444},"where-the-model-breaks","Where the model breaks",[11,447,448,451],{},[31,449,450],{},"One person is every role on eight accounts."," Common, and usually described as being busy. It is a single point of failure with no holiday cover and no second read on any claim. The first fix is not hiring — it is assigning a named second approver per client, even if that person only reads.",[11,453,454,457],{},[31,455,456],{},"The gates exist but everyone has every permission."," Then the model is documentation, not a control. Permissions that are not enforced are conventions, and conventions collapse exactly when the week is bad.",[11,459,460,463],{},[31,461,462],{},"Approval lives in chat."," The gates ran, the record did not. Six weeks later nobody can say who approved what, which is the state you are in during precisely the conversation where it matters. Approvals belong attached to the post.",[11,465,466,469],{},[31,467,468],{},"Nobody owns publish."," So it happens automatically at the scheduled time, including the morning of a client's outage. Automation is fine for the mechanics; someone still has to own the last look.",[21,471,473],{"id":472},"scaling-it-across-a-book","Scaling it across a book",[11,475,476],{},"At three clients the model is a shared understanding. At fifteen it needs to be enforced by something, because the number of people-times-brands combinations exceeds what anyone tracks reliably, and the failure is silent — nobody notices a missing gate until an incident.",[11,478,479,480,483,484,488],{},"What that requires is per-brand scoping rather than agency-wide roles: a writer added to two accounts sees two accounts, and permissions travel with the brand rather than with a job title. That is how ",[70,481,6],{"href":482},"\u002Ffor\u002Fagencies"," models it — draft, approve and client release are separate per-brand permissions, and every transition is recorded against the post itself, so the trail exists without anyone maintaining it. When ",[70,485,487],{"href":486},"\u002Fblog\u002Fhanding-over-a-social-account","an account changes hands",", that record is most of what makes the handover survivable.",[21,490,190],{"id":189},[11,492,493,496],{},[31,494,495],{},"What roles does an agency need for social media content?","\nAt minimum three: a writer who drafts, an account lead who approves internally and releases to the client, and someone who owns publishing. In small agencies the last two are the same person, but they should remain distinct acts with distinct checks.",[11,498,499,502],{},[31,500,501],{},"Should approval and publishing be the same permission?","\nNo. A post can be approved and correct on Tuesday and wrong to publish on Thursday because circumstances changed. Someone has to own the moment of publishing, not just the approval of the artefact.",[11,504,505,508],{},[31,506,507],{},"Can juniors draft on live client accounts?","\nYes, and they should. Drafting is reversible and it is the only thing that actually trains someone. What juniors should not have is release or publish permission — that separation is what makes real delegation safe.",[11,510,511,514],{},[31,512,513],{},"How do you stop client approvals from living in Slack?","\nAttach approvals to the post rather than to a conversation. The gate running is not enough; if the record is in chat, nobody can reconstruct who approved what six weeks later, which is exactly when it is asked.",[11,516,517,520],{},[31,518,519],{},"How many approvers should a client have?","\nOne named approver with a defined tiebreak, plus assigned cover for absence. Two peers who can both comment and disagree with no stated precedence is the most common cause of stalled approvals.",{"title":222,"searchDepth":223,"depth":223,"links":522},[523,524,525,526,527,528,529],{"id":264,"depth":223,"text":265},{"id":302,"depth":223,"text":303},{"id":334,"depth":223,"text":335},{"id":416,"depth":223,"text":417},{"id":444,"depth":223,"text":445},{"id":472,"depth":223,"text":473},{"id":189,"depth":223,"text":190},"The three-role split that lets juniors do real work without release risk, why approval and release are different permissions, and how to scale it across a book of clients.",{},"\u002Fblog\u002Fagency-roles-for-social-content",{"title":249,"description":530},"blog\u002Fagency-roles-for-social-content",[536,244],"agencies","eyiBKklu-EKdbjB8AgAXGqewqg7Cmv5JK7FEY6Z0SsY",{"id":539,"title":540,"author":6,"body":541,"date":232,"description":804,"draft":234,"extension":235,"image":236,"meta":805,"navigation":238,"path":806,"seo":807,"stem":808,"tags":809,"updated":236,"__hash__":810},"blog\u002Fblog\u002Fclient-reporting-that-gets-read.md","The client report that actually gets read",{"type":8,"value":542,"toc":795},[543,546,549,552,556,562,565,571,574,578,581,587,593,599,605,611,615,618,623,655,660,686,690,693,696,702,708,714,721,725,731,737,743,747,750,757,763,765,771,777,783,789],[11,544,545],{},"The monthly report is the most-produced and least-read artefact in social media work. Twelve slides of charts, an impressions number nobody can act on, and a client who skims for the one line that says whether this is working.",[11,547,548],{},"That skim is the whole document. Everything else is you demonstrating effort, which is a bad thing to be paid for and a worse thing to be judged on. A report is not evidence of work; it is an instrument for making the next month's decisions.",[11,550,551],{},"Here is the version that gets read, and the parts to delete.",[21,553,555],{"id":554},"start-with-the-answer","Start with the answer",[11,557,558,559],{},"The first line of the report answers the question the client actually has: ",[31,560,561],{},"is this working, and what are we changing?",[11,563,564],{},"Not \"here's what we did in March.\" Something like:",[566,567,568],"blockquote",{},[11,569,570],{},"March: the customer-story posts outperformed everything else by a wide margin, so April shifts to two of those a month and drops the industry-commentary slot. One post drove 14 profile visits and 3 inbound messages — the highest of the year.",[11,572,573],{},"Everything after that first paragraph is support for a claim already made. If a client reads only the top of the page, they have the answer, and they will trust the rest more for not having to hunt for it.",[21,575,577],{"id":576},"the-one-page-structure","The one-page structure",[11,579,580],{},"Five blocks, one page, same order every month. Consistency matters more than completeness — a report whose shape changes each month cannot be compared with the last one, which is most of what a report is for.",[11,582,583,586],{},[31,584,585],{},"1. The verdict."," Two or three sentences. Working, not working, what changes.",[11,588,589,592],{},[31,590,591],{},"2. What went out."," Volume and mix, stated plainly. \"11 posts: 4 customer stories, 3 product, 2 opinion, 2 hiring.\" This is the only place effort belongs, and one line is enough.",[11,594,595,598],{},[31,596,597],{},"3. What worked, with the actual post."," Not a chart — the top two posts, embedded or quoted, with one sentence on why you think each landed. Clients engage with their own content far more than with any metric about it, and \"why it landed\" is the part they cannot get from a dashboard.",[11,600,601,604],{},[31,602,603],{},"4. What did not, and the hypothesis."," The block most people delete, and the one that builds the most trust. A named underperformer with a specific reading — \"the two product posts led with the feature rather than the problem\" — proves you are reading results rather than collecting them.",[11,606,607,610],{},[31,608,609],{},"5. Next month, and what you need."," Three to five bullets of what you will do, plus an explicit list of what you need from them and by when. This is where the report stops being a rearview mirror and starts causing something.",[21,612,614],{"id":613},"which-metrics-to-keep","Which metrics to keep",[11,616,617],{},"Report metrics the client can act on and that are plausibly caused by the work.",[11,619,620],{},[31,621,622],{},"Keep:",[428,624,625,631,637,643,649],{},[89,626,627,630],{},[31,628,629],{},"Reach or impressions",", as context only, one number, no chart.",[89,632,633,636],{},[31,634,635],{},"Engagement rate",", because it is comparable across post sizes in a way raw likes are not.",[89,638,639,642],{},[31,640,641],{},"Profile visits and follows from content"," — the nearest honest proxy for \"people wanted more.\"",[89,644,645,648],{},[31,646,647],{},"Anything countable that touches pipeline:"," inbound messages, demo requests, link clicks to the page that matters, applications for an open role.",[89,650,651,654],{},[31,652,653],{},"A qualitative line."," Who engaged, not how many. \"Two heads of engineering at target accounts commented\" outranks a thousand impressions and no report format captures it automatically.",[11,656,657],{},[31,658,659],{},"Drop:",[428,661,662,668,674,680],{},[89,663,664,667],{},[31,665,666],{},"Follower count as a headline."," It moves slowly, it is easy to game and it rarely causes anything.",[89,669,670,673],{},[31,671,672],{},"Every chart with fewer than three months of data."," Two points is not a trend; presenting it as one trains the client to over-react to noise.",[89,675,676,679],{},[31,677,678],{},"Platform-native \"engagement scores.\""," Different definitions per platform and not comparable.",[89,681,682,685],{},[31,683,684],{},"Anything you cannot explain the cause of."," If you cannot say why it moved, it is decoration.",[21,687,689],{"id":688},"reporting-a-bad-month","Reporting a bad month",[11,691,692],{},"Every account has them, and how you report the third bad month determines whether there is a fourth.",[11,694,695],{},"Three rules:",[11,697,698,701],{},[31,699,700],{},"Say it in the first line."," Burying a bad month in slide nine reads as concealment when it is discovered, and it always is. Leading with it reads as control.",[11,703,704,707],{},[31,705,706],{},"Distinguish the two kinds of bad."," \"The content underperformed\" and \"we published four posts instead of eleven because material never arrived\" are entirely different problems with different owners. Conflating them is either taking blame you do not deserve or hiding a dependency that needs fixing. Say which one it was, without editorialising.",[11,709,710,713],{},[31,711,712],{},"Bring a change, not a reassurance."," \"We'll keep at it\" is what a client hears as nothing. One specific alteration, with what you expect it to do, is what keeps the next month funded.",[11,715,716,717,720],{},"The failure mode worth naming: smoothing a bad month by finding a metric that happened to go up. Everyone can tell, and it costs more credibility than the bad month did. If the data is thin, say the data is thin — ",[70,718,719],{"href":482},"honest measurement"," survives a quarter of noise far better than a curated one does.",[21,722,724],{"id":723},"frequency-and-format","Frequency and format",[11,726,727,730],{},[31,728,729],{},"Monthly, not weekly."," Weekly reporting on social is mostly noise and turns into a treadmill that consumes bucket-four time you are not being paid for.",[11,732,733,736],{},[31,734,735],{},"One page, in the body of an email or a shared doc."," Not a PDF attachment, not a slide deck, not a dashboard link. The report should be readable on a phone in ninety seconds without a login. Dashboards fail as reports for one reason: a dashboard shows numbers, and a report makes an argument.",[11,738,739,742],{},[31,740,741],{},"Quarterly, go longer."," Once every three months there is enough data for an actual trend, and that is the meeting where you discuss strategy, scope and rate. The monthly one-pager is not the place for that conversation.",[21,744,746],{"id":745},"the-compounding-benefit","The compounding benefit",[11,748,749],{},"There is a second reason to write reports this way, and it shows up months later.",[11,751,752,753,756],{},"A year of one-page reports that each name a hypothesis and a result is an argument for your rate that no proposal can match. It is also the record that settles disagreements about what was agreed, which is the same reason ",[70,754,755],{"href":330},"approvals need a trail",". Reports written as decisions accumulate into evidence; reports written as dashboards accumulate into nothing.",[11,758,759,760,762],{},"Across a book of clients this is exactly the part that decays under load — the fifth client's report gets written at 11pm and quietly becomes a metrics dump. ",[70,761,6],{"href":482}," keeps what was published, what was approved and what it produced attached to each brand, so the monthly report is assembled from a record rather than reconstructed from memory.",[21,764,190],{"id":189},[11,766,767,770],{},[31,768,769],{},"What should be in a social media report for a client?","\nA verdict in the first two sentences, what went out, the top posts with why they worked, what underperformed and your hypothesis, and next month's plan with what you need from the client. One page, same structure every month.",[11,772,773,776],{},[31,774,775],{},"Which social media metrics actually matter to clients?","\nEngagement rate, profile visits and follows from content, and anything countable that touches pipeline — inbound messages, demo requests, relevant link clicks. Follower count and raw impressions are context at best and misleading as headlines.",[11,778,779,782],{},[31,780,781],{},"How often should I report to a social media client?","\nMonthly for the one-pager, quarterly for the longer strategic review. Weekly reporting on social is mostly noise and consumes unbilled time without improving decisions.",[11,784,785,788],{},[31,786,787],{},"How do I tell a client a month went badly?","\nIn the first line, distinguishing content that underperformed from work that could not happen because material never arrived, and paired with one specific change you are making. Burying it reads as concealment; leading with it reads as control.",[11,790,791,794],{},[31,792,793],{},"Should I send a dashboard link instead of a report?","\nNo. A dashboard shows numbers; a report makes an argument about what to do next. Clients who receive dashboard links stop opening them within about two months.",{"title":222,"searchDepth":223,"depth":223,"links":796},[797,798,799,800,801,802,803],{"id":554,"depth":223,"text":555},{"id":576,"depth":223,"text":577},{"id":613,"depth":223,"text":614},{"id":688,"depth":223,"text":689},{"id":723,"depth":223,"text":724},{"id":745,"depth":223,"text":746},{"id":189,"depth":223,"text":190},"Most social media reports are dashboards nobody opens. A one-page structure built around decisions, which metrics to drop, and how to report a bad month without losing the account.",{},"\u002Fblog\u002Fclient-reporting-that-gets-read",{"title":540,"description":804},"blog\u002Fclient-reporting-that-gets-read",[244,536],"CrLO_ehJZApOOOzw8VupnuRkE2sS4yfJ_xh4qMLQZ-I",{"id":812,"title":813,"author":6,"body":814,"date":232,"description":1024,"draft":234,"extension":235,"image":236,"meta":1025,"navigation":238,"path":486,"seo":1026,"stem":1027,"tags":1028,"updated":236,"__hash__":1029},"blog\u002Fblog\u002Fhanding-over-a-social-account.md","Handing over a social account without losing the voice",{"type":8,"value":815,"toc":1016},[816,819,822,825,829,832,838,844,853,859,862,866,869,872,902,905,909,912,918,924,930,936,942,946,949,959,965,968,972,975,981,984,986,992,998,1004,1010],[11,817,818],{},"An account changes hands. The new strategist reads the last three months of posts, the brand doc if there is one, and starts writing. Nothing obviously breaks. Six weeks later the client says something vague about the posts not feeling like them lately, and cannot point at a single one.",[11,820,821],{},"They are right, and the cause is structural. Reading published posts teaches you the output, not the reasoning: which angles were rejected, which words are banned, what the client reacted badly to in March, why the account stopped doing the Friday format. All of that lived with the person who left.",[11,823,824],{},"Voice does not survive a handover by default. It survives because someone captured the part that was never written down.",[21,826,828],{"id":827},"what-is-actually-lost","What is actually lost",[11,830,831],{},"Four categories, in rough order of how much damage their loss causes.",[11,833,834,837],{},[31,835,836],{},"1. Rejections."," The single most valuable and least recorded artefact. Every angle the client killed, every phrasing that came back marked up, every topic that turned out to be sensitive. The published archive shows what passed; it says nothing about what was tried. A new writer without the rejection history will re-propose the same rejected ideas within a month, which is what a client experiences as \"they don't know us.\"",[11,839,840,843],{},[31,841,842],{},"2. The forbidden list."," Claims they cannot legally make, competitors they will not name, words banned internally. Usually held in memory after the first time someone got told off.",[11,845,846,849,850,74],{},[31,847,848],{},"3. Fact provenance."," Which numbers are current, which were true in March, which need legal review. Undated facts in an old post are how a stale claim gets recycled into a new one — the second-order version of ",[70,851,852],{"href":411},"publishing a wrong claim",[11,854,855,858],{},[31,856,857],{},"4. Relationship texture."," Who actually approves versus who comments, how blunt you can be, whether they want to be consulted or informed. Not voice exactly, but it determines how much friction the next three months carry.",[11,860,861],{},"The published posts capture none of these. That is why \"read the last quarter and you'll pick it up\" fails reliably.",[21,863,865],{"id":864},"capture-it-before-you-need-it","Capture it before you need it",[11,867,868],{},"The only version of this that works is continuous. A handover document written during a handover is written by someone already mentally gone, under time pressure, from memory that is already degrading.",[11,870,871],{},"Four artefacts, maintained per account as a matter of course:",[428,873,874,884,890,896],{},[89,875,876,879,880,74],{},[31,877,878],{},"The voice definition",", concrete enough that two writers produce similar posts from it. Three real sample posts beat any list of adjectives — the standard is in ",[70,881,883],{"href":882},"\u002Fblog\u002Fmanaging-multiple-brand-voices","keeping several brand voices straight",[89,885,886,889],{},[31,887,888],{},"The fact file",", with dates. Every citable number, when it was true, where it came from.",[89,891,892,895],{},[31,893,894],{},"The forbidden list."," Claims, comparisons, words, customers who may not be named.",[89,897,898,901],{},[31,899,900],{},"The rejection log."," One line per killed angle, with the reason. This is the one nobody keeps and the one that matters most. It costs ten seconds at the moment of rejection and is unreconstructable afterwards.",[11,903,904],{},"If these exist, a handover is a week. If they do not, it is a quarter, and the client pays for the difference in quality without being told.",[21,906,908],{"id":907},"the-two-week-handover","The two-week handover",[11,910,911],{},"Assuming the outgoing person is still available. Compress it if they are not, and accept a worse result.",[11,913,914,917],{},[31,915,916],{},"Days 1–2 — Written transfer."," The four artefacts above, updated to current. Plus one page the outgoing strategist writes from memory: what the client actually cares about, what they say they care about, and where those differ. That page is worth more than the rest combined.",[11,919,920,923],{},[31,921,922],{},"Days 3–4 — The walkthrough."," Go through the last quarter's posts together, outgoing person narrating: why this angle, what got cut, what the client said. Record it. This is the reasoning layer that the archive does not contain, and an hour of it saves a month.",[11,925,926,929],{},[31,927,928],{},"Days 5–8 — Shadow drafting."," The incoming writer drafts; the outgoing one edits with reasons attached. Nobody sends anything new to the client yet. Three or four rounds is usually enough for the register to transfer, and the edits themselves become additions to the voice definition.",[11,931,932,935],{},[31,933,934],{},"Days 9–10 — Introduce, deliberately."," Tell the client, before they notice. Frame it as continuity with a name and a date, not as an apology. Clients handle a planned handover well and an unannounced one badly, and the difference is entirely in whether they found out from you.",[11,937,938,941],{},[31,939,940],{},"Days 11–14 — Supervised solo."," Incoming writer runs the account; outgoing person reviews before release. Then stop.",[21,943,945],{"id":944},"the-drift-check","The drift check",[11,947,948],{},"The failure is gradual, which is why it is caught late. Two cheap checks catch it inside a month.",[11,950,951,954,955,958],{},[31,952,953],{},"The blind test."," Take three new posts, strip the logo and any product names, and ask someone who knows the brand which client they belong to. If the answer is \"could be any of them,\" the voice has already flattened toward the writer's default. This is the same check that catches ",[70,956,957],{"href":882},"voice bleed across clients",", and it works for the same reason.",[11,960,961,964],{},[31,962,963],{},"The rejection replay."," Pull five angles from the rejection log and ask the new writer whether they would propose them. If they would propose three, the reasoning did not transfer, and the client is about to feel it.",[11,966,967],{},"Run both at week two and week six. After that, drift is usually the normal kind that any account has, not handover damage.",[21,969,971],{"id":970},"why-this-keeps-happening","Why this keeps happening",[11,973,974],{},"Because the artefacts live in the wrong place. A brand doc in a shared drive gets updated during onboarding and never again; a rejection log in someone's notes app leaves with them; the fact file is a spreadsheet three versions behind whatever the client last confirmed.",[11,976,977,978,980],{},"The structural fix is that brand knowledge should live attached to the brand rather than to the person, and it should be updated as a side effect of the work rather than as a separate chore nobody does. That is what ",[70,979,6],{"href":482}," holds per brand: voice profile, confirmed facts with their history, constraints, and the record of what was proposed, edited and rejected. The next strategist inherits the account rather than reverse-engineering it from published posts.",[11,982,983],{},"It also removes the incentive that quietly damages agencies — when knowledge lives with a person, the account is hostage to their retention, and everyone knows it.",[21,985,190],{"id":189},[11,987,988,991],{},[31,989,990],{},"How do you hand over a social media account to a new manager?","\nTransfer four written artefacts first — voice definition, dated fact file, forbidden list and rejection log — then walk through the last quarter's posts with the outgoing person narrating why each angle was chosen, then shadow-draft for a week before the new writer sends anything to the client.",[11,993,994,997],{},[31,995,996],{},"Why does a brand's voice change when the writer changes?","\nBecause published posts show the output, not the reasoning. A new writer cannot see which angles were rejected, which words are banned or what the client reacted badly to, so they default toward their own register within a few weeks.",[11,999,1000,1003],{},[31,1001,1002],{},"What is a rejection log and why does it matter?","\nA one-line record of every angle a client killed and why. It is the most valuable handover artefact and the least commonly kept — without it, a new strategist re-proposes rejected ideas within a month, which clients experience as not being understood.",[11,1005,1006,1009],{},[31,1007,1008],{},"Should you tell the client the account is changing hands?","\nYes, before they notice, framed as planned continuity with a name and a date. Clients handle announced handovers well and unannounced ones badly, and the difference is almost entirely in who told them first.",[11,1011,1012,1015],{},[31,1013,1014],{},"How long should a social media account handover take?","\nAbout two weeks with the outgoing person available: two days of written transfer, two of walkthrough, four of shadow drafting, then a supervised solo period. If the brand artefacts were maintained continuously it is closer to a week; if they were not, expect a quarter of degraded quality.",{"title":222,"searchDepth":223,"depth":223,"links":1017},[1018,1019,1020,1021,1022,1023],{"id":827,"depth":223,"text":828},{"id":864,"depth":223,"text":865},{"id":907,"depth":223,"text":908},{"id":944,"depth":223,"text":945},{"id":970,"depth":223,"text":971},{"id":189,"depth":223,"text":190},"When the strategist who ran an account leaves, the voice resets to whoever writes next. What to capture before it happens, a two-week handover plan, and the drift check that catches it early.",{},{"title":813,"description":1024},"blog\u002Fhanding-over-a-social-account",[536,244],"4-PllwzsnCCa4EsTMXRWOcblfK2h5kKGj7ee3GcEeGQ",1787133213392]