Nothing We Write Goes Live Without Your Written Approval

The single question we are asked most often in sales calls is some version of: what stops you posting something I would hate?

The answer is a sequence of gates, and the client holds the last one.

The chain a deliverable passes through

1. The plan is approved first. Before anything is written, the Customer Manager builds a content plan from the organised client context: target subreddits and platforms, topic themes, posting schedule, tone and style notes, and the key messaging points. A Senior Manager reviews that plan for strategic alignment and feasibility. Only once it is approved does it become the blueprint for production.

2. The batch is drafted and self-reviewed. The CM produces the batch against the approved plan. AI does the drafting — that is what makes the pace possible — and the CM then reviews every output for accuracy, relevance, tone and factual correctness, and runs a self-review across the batch for anything that does not match the brief.

3. A Senior Manager reviews it internally. The batch goes up for review against quality, brand alignment, factual accuracy and our ethical standards. If it needs work, it comes back with specific feedback and the loop repeats until it passes. Content does not skip this step.

4. You review it. Only then does the batch reach the client, clearly marked as pending approval. Standard review turnaround is two to four business days.

5. You approve it in writing. Under no circumstances is anything posted before the client explicitly approves it. Approval has to be in writing — a message, an email, or a confirmation in whatever channel we agreed during onboarding.

What happens when you want changes

The deliverables are immediately marked as non-approved and posting is off the table. Before touching anything, the CM asks for the context behind the request, so the edit lands right the first time rather than after three rounds of guessing.

Then the revised work re-enters the full cycle: CM self-review, Senior Manager review, and back to the client. An edited deliverable does not get a shortcut to the front of the queue.

We accommodate as many rounds of edits as a client asks for. If the volume of edits starts causing real delays, that is escalated internally with a status report — because at that point something upstream is wrong, usually in the brief, and more rounds will not fix it.

And if the client goes quiet

Nothing is posted. That is the whole answer.

For the first five days the CM follows up through the agreed channel asking for approval or feedback. On day six the CM writes up a detailed report and the Senior Manager decides how to proceed. Approval is not implied by silence, and a deadline passing does not convert an unapproved draft into an approved one.

After it is live

Posting is not the end of the process either. Content is posted to fit the subreddit's rules and culture, and never as identical copies across multiple subreddits at once. Afterwards the CM checks the platform directly to confirm the post is actually live, visible and not sitting in a spam filter, and the live link gets logged.

None of this is a differentiator we invented for a landing page. It is the process, and the reason it exists is that the alternative — content going live that a client never saw — is the fastest way to lose one.