Use cases
Four shapesof the same job.
The mechanism does not change: writers, a plan, execution you approve, and a report on what went out. What changes is how many plans are running at once, how much of the year is predictable, and who reads the report at the end of the month.
Everything below is a description of how the same five jobs get used differently, not four different products. If your business is not one of these four, the useful question is which of them it resembles: are you running one plan or eleven, is your year shaped by seasons or by releases, and is the report for you or for somebody who is paying you.
Agencies
Several clients, each with their own plan, their own writers and their own report. The report is what the retainer is measured against, so it should not be assembled by hand on the last Friday of the month.
This is the case FABLS is strongest at, because the parts that are tedious at one client become impossible at eleven.
Local business
One person doing everything, no marketing department, and channels that have to look alive on a Tuesday in February. A bakery, a clinic, a fitting company, a garage.
The constraint here is approval time, not ideas. A plan sized to ten minutes a day is worth more than an ambitious one abandoned in March.
E-commerce
A catalogue is a content plan in disguise. Every category, every season and every restock is something to write about, and the blog reaches people who were not already searching for your name.
The channels split neatly: the blog for the people who have not found you yet, the socials for the ones who already have.
SaaS
You ship every fortnight and write about it twice a year. A roadmap becomes a plan; a release becomes three posts rather than a changelog entry nobody opens.
The hard part is not writing — your team can write. It is that writing is always the thing that gets dropped when the release is late.
Four kinds of company with the same empty Tuesday.
What they have in common
In all four cases the thing that fails is not the writing. It is the second month. Almost every business can produce a fortnight of good posts by force of will, and almost none can produce six months of them alongside the actual work.
What survives the second month is a plan somebody agreed to in advance, drafts that turn up before they are needed, and an approval step small enough to do between other things. That is the whole argument for this arrangement, and it applies identically to a bakery and to an agency running eleven of them.
The report is the second common thread. Whether it is going to you, to a client or to whoever signs the invoice, a month with no account of itself becomes a month nobody can defend.
- 1Set upA finished profile on every platform.
- 2PlanThree to six months of dated slots, themes and shares.
- 3CreateDrafted ahead, from scratch, from content or from a plan, and approved by a person.
- 4RunComments, messages and reviews in one queue, answered on time.
- 5LearnPlanned against published, and what it taught the next plan.
- ·What differsHow many plans, how the year is shaped, and who reads the report.
One accountOne mechanism
Where it fits badly
Two situations, said plainly, because finding out in month two is worse than reading it here.
If video on X, or WhatsApp, is the channel that matters to your business, this is not the right tool today — FABLS does not upload video to X, and WhatsApp is a separate business platform with its own charges for every conversation. The connected channels are a WordPress blog, a Facebook Page, Instagram, TikTok, X, LinkedIn, Pinterest, Threads, YouTube and a Google Business Profile.
And if nobody in the business is going to read a draft before it publishes, the value of the approval gate disappears and you are left with an expensive scheduler. The answer in that case is a smaller plan with a person who does read it, not a bigger plan on autopilot.
Agencies Local business