Managing social media for small business: week 4

Managing social media for a small business is a weekly loop: choose the week's material, draft the posts, adapt each one to the network it goes on, schedule, reply. It has been written up many times, including as six steps on this blog. It is not where management fails. It fails one step earlier, at the step no guide lists: on a specific morning, someone has to decide to start the loop. In July we changed who that someone is, for every account on ReadyToPost. Here is the decision, what forced it, and what we had to add to make an unasked week acceptable.

What managing social media involves at one to five people

Done by hand across five networks, the loop is about three hours a week. Thirty minutes per platform to adapt and schedule, plus finding something worth saying. Over a year that is the 156 hours we built the product around. Most of those hours are production: drafting captions, sorting photos, rewriting one message for five networks that do not read alike.

Software absorbed production, ours included. What no tool absorbed was the moment before production. A scheduler waits for you to fill the queue. A generator waits for you to press generate. A freelancer waits for your brief. Every one of them, until this summer, answered the question "who starts this week?" with the same word: you.

Why it breaks in week four, not week one

You can check this on any small-business account. Open the profile and read only the dates. Posts come in bursts: a run of them, a gap of three to five weeks, another run. Nobody decided to stop. The gap is not a decision. It is the absence of one.

The mechanism is short. Week one runs on setup: the accounts are freshly connected, the first week is free and generated right after, everything is in memory. Week two, the routine is still warm. Week three, the profile still looks alive, because last week's posts are the ones a visitor sees first, so skipping costs nothing you can see. Week four is the first week the gap shows on the profile. Restarting now means a cold decision on a Monday, with no momentum and a backlog. That is where the loop dies: not because the work is hard, but because the trigger is.

“

An option called "generate my week automatically" is itself the cold decision we were trying to remove.

”

The decision: the week starts without you

On 10 July we shipped automatic weekly generation as an option. You picked a weekday, "my week is ready on Wednesday". Two days ahead, the system chose the strongest theme suggestion for your brand, ran the same pipeline as a manual week, dropped the posts into your calendar, and emailed you at eight in the morning on the day. Behind it, someone on the team reviewed every generated week before that email went out.

Less than two weeks later, on 22 July, we turned it on for every account, with Wednesday as the default day, and removed the review.

The option had reproduced the problem it was built to solve. A toggle called "generate my week automatically" is itself a cold decision: you have to be in the app, find the setting and switch it on. The accounts that most needed a week to arrive unasked were, by construction, the ones not opening the app. An opt-in fix for a trigger problem is not a fix.

The review went for a plainer reason. It only gated the email; the week was already sitting in the calendar. It put a person between your posts and your inbox, and a human check on every week does not scale. We dropped it and moved the checking to the only place it belongs: your calendar, before anything publishes.

What an unasked week has to respect

A week that arrives without being asked for is either a relief or spam. What separates the two is a short list of rules, each one a line in the system rather than a promise.

Your week wins. If you planned that week yourself, the automatic one steps aside. Your plan is never overwritten.

It is built from your material. The theme is picked among suggestions built from your website, your photos and whatever you have added about your business, never from a blank prompt. An uninvited generic week is worse than no week: it fills the calendar with posts you will delete, and deleting is one more cold decision.

It skips quietly. No credits left for the week, no template to fill: it skips, records why, and sends no email about it.

It knows when you have left. If six weeks in a row were generated and announced and you did not visit once, it pauses. One login resumes it at the next cycle. We set this at two weeks first and raised it to six: a subscriber away for a month has not left. Past six, stopping preserves their credits for the day they return.

It never publishes on its own. The week lands in the calendar and waits for your approval. A fully unattended mode exists; we keep it off by default and switch it on by hand, per account, when someone asks for it.

How much time managing social media takes once the week starts itself

What remains is the part worth keeping. Twenty minutes of review: approving, swapping a photo, cutting a line that does not sound like you. Replies and comments, which no automation should touch first. And the exception week, when there is a launch or a new season to announce and you start the week yourself.

The weekly loop has not changed. What changed is that it no longer waits for a decision to begin. It starts on Wednesday whether or not you thought about it on Monday, and your job moves from starting it to answering it. A steady presence, for a business of one to five people, is exactly that: a loop that runs when nobody remembers to run it.

What we would decide again, and what is still open

The default is the decision we would make again. The trigger was the failure point, and a default is the only fix that reaches the accounts that need it.

Wednesday for everyone is the part we are less sure of. A restaurant's week is decided when the menu is; a hotel's a season ahead, which is where our guides for hotel owners start. One default day does not fit both, and we do not yet pick the day per trade. You can move it in settings, which is, we admit, a click.

The other open edge is the pick itself. When the suggestion chosen is not the one you would have chosen, you get a week to reject, and the cold decision comes back in a smaller form. Our answer so far is on the input side: each document, photo or link you add makes the next pick closer to the one you would have made.

If your last post is more than three weeks old, the question to settle this week is not what to post. It is who starts the next week when you don't.