Organic Social

Teams used to assume that having an account was most of the work. Follower count was treated as the size of the audience, and whoever ran the account reported how many posts went out that month.

Looking at the numbers is what broke that assumption. Reach is how many screens a post actually appeared on, and an account with 3,000 followers routinely reaches a couple of hundred people with a given post. What sets that fraction isn't the company but the platform's distribution rules, and when the rules change the same account's reach can halve in a month with nothing on your side having changed at all. "Twelve posts this month" met with "how many people saw them?" had no answer, and the report kept being filed anyway.

Organic social is the practice of running an account with that condition assumed. Reach is borrowed rather than owned, which means the response to each individual post, not the follower count, decides what the next post reaches. Everything else in the practice follows from that one fact about how distribution works.

Set the account's job, build a publishing rhythm, measure the response, and feed it back into what goes out next.

1. Write down in one sentence who this account is for and what it's meant to do. Introducing the product to people who have never heard of it and showing existing users more of what it does call for completely different posts. Mix both in one account and you get posts that suit neither: too inside for strangers, too familiar for users. Choosing one of the two is the cheapest decision available here.
2. Fix about three subject areas and a publishing rhythm. Product tips, customer stories, how the team works — divided up, with a count like three times a week against them. Without subjects decided in advance, every post starts with deciding what to post, and that deliberation is what stops the publishing. Set the rhythm at a level you can hold: twice a week sustained for six months beats five times a week abandoned after two, because reach responds to consistency more than to volume.
3. Make it in the form the platform favors. The same story spreads as a 40-second video in one place and as three screenshots with a paragraph in another, and the work of converting it is usually an hour rather than a rewrite. One artifact posted identically everywhere spreads nowhere, and it reads as something recycled rather than made.
4. Measure and choose. Watch reach, how many people it got to, alongside engagement rate, the share of those people who responded. Reach of 240 with 32 responses is 13 percent, and a post with a high ratio pulls more reach for the next one than a post with big raw numbers, because that ratio is the signal platforms use when deciding what to show more of.
5. Reuse what worked. Remake a high-response subject in another form, and occasionally put money behind an unusually strong post to extend how far it travels. From that moment, though, the traffic isn't organic, and it belongs in a different column of the report.

Day to day, one person runs it. At Pagedeck, Ravi handles the account alone — choosing subjects, publishing, checking responses. Splitting it across several people at a small scale makes the voice inconsistent, and one account starts reading like several. Consistency of voice is most of what makes an account worth following in the first place.

Other people come in at defined points rather than continuously. A designer builds reusable image templates; in a launch week, wording gets aligned with whoever owns the launch message. When user-generated content (UGC) — things users made and posted themselves — gets reshared, the person who made it gets asked first. That material reads better than anything the company produces about itself, so watching for it and moving it somewhere visible is part of the craft.

Timing splits three ways. First, the regular rhythm: holding the count you set is the baseline of this work. Second, launch weeks, when the rhythm changes and one subject repeats in several forms. Third, incidents. When the service is down this account is the first place people look, so what gets posted and how fast is decided in advance. A line saying you're looking into it, with no restoration time yet, beats silence by a wide margin.

Approval rules get settled up front too. Without a line between what can go out alone and what needs a check, an urgent moment produces either a late answer or an unchecked one. Both are worse than the rule that would have prevented them.

"We have 3,000 followers and this post reached 240."

Reporting that follower count and actual reach are different numbers entirely.

"It's launch week, so the publishing rhythm changes."

One subject takes the whole week instead of the usual spread of three.

"Let's put money behind the two that got the best response."

Spend only on the posts that organic distribution has already proved out.

Ravi changed how this work is judged the day he took post count out of the report. Twelve a month had been the number, and splitting reach from response showed three of the twelve producing most of the engagement. The other nine had cost the same amount of time to make.

After that the goal moved from volume to finding the subjects that get a response, which is a harder thing to report and a better thing to chase. Templates from Noa cut the production time, which let the same person test more subjects in the same hours — the same decision seen from another side.

The most common mistake is reading follower count as the result. It's the only number visible from outside, which makes the mistake natural. But followers only raise the ceiling on reach slightly, and the actual figure gets decided again for every post that goes out. Set follower growth as the target and the work drifts toward giveaways. Followers with no interest in the product then lower the response ratio, which lowers the next post's reach — the target works against itself.

Assuming no ad spend means no cost is the other one. No invoice arrives, so it reads that way. But publishing three times a week for six months is close to one person's job. Assign that time to nobody and publishing stops after about two months. A dormant account leaves a worse impression than no account at all, because it suggests a product nobody is tending.