Posts stop dying between the outline and the draft.
Most content pipelines lose posts in the gaps, an outline nobody reviewed, a draft waiting on an editor who never saw it land. This recipe closes every gap: an idea becomes an outline, the outline gets a decision, the draft gets written and reviewed, and only an approved post reaches your publication. Every stage has a named owner and nothing advances until they act.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Anyone on the team can pitch a post. Publishing it auto-creates the Blog Pipeline board that tracks every post from idea to publication. Each submission opens a row at the idea stage and routes it to the editor for topic approval.
Where writers submit the finished draft. Submission triggers the AI SEO review and the editor approval flow.
Logs a new idea into the pipeline and routes it to the editor for topic approval. Approved topics get an AI-generated outline, SEO keywords, and draft suggestions; rejected topics notify the writer and stop there.
Runs the AI SEO and readability review on a submitted draft, sends it to the editor for approval, then publishes approved posts and records the live URL. Revision requests flip the status and notify the writer to resubmit.
You connect your own accounts. Swap any app that offers an alternative at install.
Posts a new-idea alert to the editorial channel when the Blog Idea Submission form is submitted.
Sends the editor the secure approval link for each draft, announces publications, and notifies writers of requested changes. Swap for Telegram.
Publishes the approved post to the blog and returns the live URL. Swap for Medium or Notion.
Anyone pitches through the Blog Idea Submission form: title, angle, keyword, proposed author, content type, and target date. Publishing the form auto-creates its response sheet, which is the Blog Pipeline board; submitting opens a row there at the idea stage.
A Human-in-the-Loop step pauses the workflow before any writing happens. The editor gets a secure Approve / Reject link for the pitch. Rejected topics stop right here and the writer is notified, so nobody writes 1,500 words on a topic that was never wanted.
Once the topic is approved, a TinyGPT step generates an outline, SEO keyword suggestions, and concrete draft suggestions, flagging what needs researching rather than inventing sources. All three save to the pipeline record and the writer is notified it's ready to draft.
When the piece is written, the author submits it through the Draft Submission form: title, Markdown body, meta description, keyword, and an optional featured image. Submitting kicks off review.
A TinyGPT step scores SEO and readability, checks brand fit against your voice notes, and returns specific revision notes, flagging unverified claims rather than inventing sources. The draft and the notes both save to the pipeline record, so your editor opens a marked-up draft instead of a blank one.
A second Human-in-the-Loop step pauses the workflow. The editor gets the AI notes and a secure Approve / Request Revisions link. Requesting revisions sets the record to revision-requested and notifies the writer to revise and resubmit through the Draft Submission form, the piece never silently stalls.
On approval the post publishes to Ghost (swap for Medium or Notion), set the publish status to scheduled if you want to time the release. The live URL is recorded on the pipeline record, and the team, marketing included, is notified in the shared editorial channel.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
