A date and format do not make a slot ready. The team also needs an outcome, fact source, reviewer, status and learning field. Use the structure below in a spreadsheet or your existing workspace. Personalized slots and calendar planning inside Fabulica require signup.
Fabulica editorial resource · AI-assisted · examples are illustrative · reviewed
For a small software business, start with one audience and one task your product actually solves. The example below is an editorial exercise for a fictional scheduling app, not a customer case or a promise of results. Monday, Wednesday and Friday are a manageable starting rhythm, not universal best posting times.
Hook: ‘The meeting moved. Did everyone get the update?’ Describe one real scheduling problem in the audience’s words. Visual: a recreated example with invented names. Evidence needed: the exact workflow your product supports. CTA: read the checklist for changing a meeting.
Hook: ‘One changed date, shown step by step.’ Record the actual date-change workflow using demo data. Explain who can see the change and any notification limits. Avoid a polished mockup that implies a feature exists. CTA: try the same task in the demo, if a public demo is available.
Hook: ‘What happens if someone misses the update?’ Answer with verified product behavior and a clear limitation. Use one question from real support or label it as a question to test. CTA: view the relevant help page or product tour. Do not invent customer quotes.
Before writing, keep two approved examples beside the calendar. Note how you address the reader, sentence length, preferred terms and phrases to avoid. For this example: calm, practical, no hype; one specific action per post; no claims such as ‘never miss a meeting’. Change the evidence and format across the week while keeping these rules stable.
Before the week starts, check every source, demo screen and destination link. Assign one reviewer and leave uncertain posts as drafts. After publishing, save the actual post link; ‘accepted’ or ‘scheduled’ is not proof that it is live. At the end of the week, record useful replies, demo visits and completed demo tasks if you can measure them. Leave missing data unknown. Keep, revise or drop one topic based on that evidence.
In Fabulica, the weekly-plan settings let you choose three publication days, topics, audience, CTA and style. You can edit saved drafts and review image cards. Background preparation is currently limited to enrolled pilots. Scheduling needs a connected channel, suitable media and approval of the exact post; signup alone does not enable unattended publishing.
Record the outcome, audience and role in the editorial series. This can be one sentence. It should tell an editor which evidence the slot adds and why it belongs in this week.
Store topic, hook, key fact, format, required source material and CTA separately. Mark unverified facts explicitly. A polished draft must not turn an assumption into a claim.
Give every slot an owner, deadline, status and dependency such as photography, customer consent, current pricing or a connected channel. Status names should remain stable across the team.
After publishing, add the business signal, conclusion and decision: repeat the format, change the hook, test another audience or stop the series. A calendar becomes an asset when it stores learning as well as intent.
You can move this template into your own spreadsheet without Fabulica. Signup is required to store personalized slots, plan with brand context and use the product calendar. Automatic publishing availability depends on connected integrations, media and settings.
At minimum: idea, draft, review, scheduled, published and failed. Names should stay stable across the team.
After signup, the product supports content planning in a calendar and draft workflows.
No. It depends on the channel, connected integration, media and settings. The team should monitor status.
Add the actual business signal, a short conclusion and a next-cycle decision to the published slot.
Signup is required for Fabulica to use your supplied account context, brand memory and goals. You review every result.
Sign up and analyze my brand →