Nebo · tutorial 06 · win customers

Publish consistently without a content team

A week of on-brand posts queued and waiting for your nod, plus something watching for mentions you should answer personally.

TimeAbout an hour
Rolessocial-media-manager, social-calendar, reputation-manager
Triggerschedule, watch

Consistency beats brilliance in content, and consistency is exactly what a person running a business cannot sustain. This recipe produces a full week in one sitting, so the bottleneck becomes your approval rather than your inspiration.

It is also the recipe with the most reputational downside, so the gates matter more here than anywhere except money.

Steps

1

Hire the calendar and the watcher separately

Two employees, deliberately. social-calendar plans and drafts on a schedule. reputation-manager watches mentions continuously. They fail differently and should be gated differently, so keep them apart.

2

Write the brand rules as refusals

Positive style guidance produces bland output. Refusals produce a voice. Put both in the persona, weighted toward what it must not do.

Never use: "excited to announce", "game changer", "in today's fast-paced world", rhetorical questions as openers, or emoji as bullet points. Never describe us as innovative, passionate, or leading. Never post about a topic we have no standing in. Do: write like one person talking to one person. Lead with the specific thing. If a post has no specific thing in it, do not write it.
3

Demand native drafts, not one post reformatted

The single biggest quality difference. Say it explicitly or you will get the same sentence with different character limits.

Draft each post for its channel specifically. A LinkedIn post is not a longer tweet and a tweet is not a truncated LinkedIn post. If an idea only works on one channel, put it on one channel and leave the others alone that day.
4

Feed it what already worked

Ask it to pull the previous month's performance before drafting, and to say which angle each new post is derived from. This converts posting from guessing into iterating, and it gives you something to argue with when a draft is weak.

5

Schedule the calendar, watch the mentions

// social-calendar "trigger": { "type": "schedule", "cron": "0 15 * * 5" } // reputation-manager "trigger": { "type": "watch", "plugin": "...", "event": "mention" }

Friday afternoon for next week's calendar, so you approve while the week is still fresh and you are not doing it on Monday morning.

6

Set the gates, and make one of them absolute

Stays human

Publishing stays at approval. Public replies to criticism should be blocked outright, not gated. The difference matters: a gate can be approved in a hurry on a phone, and the one reply you must never send quickly is the one to an angry customer. Let it draft a suggested response and hand it to a person.

Reputation damage is not reversible by an approval that arrives afterwards, and a deleted post is a screenshot.

Verify

  • Read a full week of drafts and count how many you would actually post unedited
  • Confirm each channel's draft reads natively, not converted
  • Post a negative mention from a test account and confirm it routes to you rather than replying
  • Confirm nothing published without approval over a full cycle

When it goes wrong

Everything sounds like a press release

Your refusal list is too short. Add the specific phrases you are seeing, verbatim. Ten banned phrases will do more than a paragraph about tone.

It writes about things you have no business writing about

Give it a topic boundary in the persona: the three or four subjects you actually have standing in, and an instruction to skip a slot rather than reach outside them.

The watcher is noisy

Have it classify before it notifies, and only surface mentions that are negative, from a real account, or ask a direct question. Everything else goes in a weekly digest.