Work Content Pipeline

Our Own Marketing,With Human Approval

Project
Content Pipeline
What It Is
The system behind Projecttt’s own social content
Status
In use for Projecttt’s own content

The Problem

Real work already contains things worth sharing. Turning it into posts is the repetitive part: finding the source again, checking what can be said publicly, writing it for each channel and keeping track of what was approved. Done by hand, all of it waits on one person.

Facts First

Drafts start from recorded facts about the work. A post cannot say more than those facts support.

  1. Real Evidence
  2. Checks
  3. Copy
  4. Owner Review
  5. Buffer Draft
Uses n8n, Google Sheets and Buffer

How One Post Moves

  1. Something real happens in Projecttt work.
  2. A draft is written from the recorded facts, not from memory.
  3. Every claim and the wording are checked before anyone sees the draft.
  4. The draft waits for the owner to approve, edit or reject it.
  5. Only the exact version the owner approved can go out. A changed post needs approval again.

Where a Person Decides

The owner’s part

Read the draft. Approve it, change it or stop it.

Gathering the source, checking claims and preparing the draft stay inside the workflow. Approving the wording and approving publication are separate decisions.

Time Given Back

The time in question is preparation time.

Finding the source again, checking it and drafting for each channel: the workflow is built to keep that preparation off the owner’s desk, so the owner’s part is the decision.

Current State

In use for Projecttt’s own content.

Repeated real runs have produced review-ready drafts, and running the same request again does not create a duplicate.

Built for Projecttt’s own marketing first. Visuals are still partly made by hand while reusable templates are calibrated against real posts.