Content Studio AI workflow kit: One content process for every channel.

The ConvOps Content Studio kit gives your AI four workflows for a content team: Blog Post, Social Post, Newsletter Issue and Content Repurpose. Each starts from a brief, saves every draft as a task note, and holds at a gate until an explicit approval is given before anything is published or sent. A post becomes the source for the other three.

4 templates · 20 steps · 6 approvals · 4 loops back

kit · 4 workflowsreal steps
  1. 01Blog Post6 steps · 2 approvals
  2. 02Social Post4 steps · 1 approval
  3. 03Newsletter Issue5 steps · 1 approval
  4. 04Content Repurpose5 steps · 2 approvals

one chip per stored step · square chips wait for an explicit approval

the set

What's in the Content Studio kit?

Four Content Studio templates, installed together, each received by your AI one step at a time.

Four content workflows where an approved blog post becomes the source for repurposed versions, social posts and the next newsletter issue.

01 · 6 steps · 2 approvals

Blog Post

The long-form source of every Content Studio cycle, with the outline approved before a full draft exists.

  1. Brief
  2. Outline
  3. Draft
  4. Edit
  5. Final Review
  6. Complete
  • Write a product-announcement post from a one-line brief to a publish-ready draft
  • Turn a rough idea into a structured article with a working title and clear sections
every step of Blog Post →

02 · 4 steps · 1 approval

Social Post

Content Studio's single-platform post: three hooks drafted, one chosen and polished.

  1. Brief
  2. Draft Variants
  3. Polish
  4. Complete
  • Announce a feature on LinkedIn with three hook options to choose from
  • Turn a blog post into a short, on-brand social post
every step of Social Post →

03 · 5 steps · 1 approval

Newsletter Issue

The Content Studio issue to your list, themed and curated, with a pre-send check at Send Review.

  1. Theme
  2. Curate
  3. Draft
  4. Send Review
  5. Complete
  • Build a weekly issue around a single theme with curated links
  • Turn a launch into a newsletter that leads with the announcement
every step of Newsletter Issue →

04 · 5 steps · 2 approvals

Content Repurpose

Content Studio turns one approved source into a version per channel, each on an approved angle.

  1. Source Intake
  2. Angles
  3. Produce Versions
  4. Review
  5. Complete
  • Turn a blog post into a LinkedIn post, a thread, and a newsletter blurb
  • Break a webinar into a handful of short social posts
every step of Content Repurpose →

reach for it when

  • For a content team that publishes long-form work and spreads it across channels.
  • Briefs and approvals should look the same for every piece.
  • Every draft should be kept rather than overwritten.

something else fits when

  • You publish to a single channel.
  • Your content needs a regulated approval route outside the team.
  • You write now and then in chat: Chat Essentials pairs Blog Post with three everyday workflows.
example · global brandenterprise

One launch, five regional versions

Blog Post writes the launch announcement once. One Content Repurpose run per region turns it into local versions, each approved by that region's lead at Review, and every regional Newsletter Issue leads with the approved text.

Angles and Review gates per region

how it fits

How do the Content Studio workflows connect?

Blog Post produces the long-form source. Content Repurpose turns it into a version per channel, Social Post writes a single post with three hooks, and Newsletter Issue curates it into the next issue. Each runs on its own task with its own approvals, and each one's saved output is the next one's input.

FromToHow the work moves
Blog PostContent RepurposeThe approved draft is the source Content Repurpose captures at Source Intake.
Blog PostNewsletter IssueThe post becomes the lead story at Theme or one of the curated items.
Content RepurposeSocial PostBoth write social copy: Repurpose one version per channel, Social Post three hooks for one platform.

Each Content Studio template runs on its own task, and they connect through what a finished run leaves on record.

where approval is required

Where does the Content Studio kit wait for approval?

The six Content Studio approval gates, read from the stored workflows; each holds until an explicit approval is given.

TemplateStep with an approval gateIf you reject
Blog PostOutline step 2no rejection path; approve to continue
Final Review step 5back to Edit
Social PostPolish step 3back to Draft Variants
Newsletter IssueSend Review step 4back to Draft
Content RepurposeAngles step 2no rejection path; approve to continue
Review step 4back to Produce Versions
example

What does a week with the Content Studio kit look like?

An illustrative Content Studio run, labelled as an example, using the real Content Studio step names.

  1. 01

    The post

    Blog Post takes a brief, you approve the outline, the AI drafts and edits, and you approve the final read-through.

  2. 02

    The versions

    Content Repurpose proposes a LinkedIn angle and a thread angle. You approve the angles, it produces both, you approve the set.

  3. 03

    The announcement

    Social Post drafts three hooks for the launch. You pick the story variant; it polishes and you approve.

  4. 04

    The issue

    Newsletter Issue leads with the post, curates four items, and waits for your pre-send approval.

what you need

What do you need to run the Content Studio kit?

make it yours

How do you customize the Content Studio kit?

Once installed, each Content Studio template is a workflow in your workspace; ask your AI to change it in plain words.

ChatGPTexample

new chat

Add an SEO check step to Blog Post after Edit.
workflow_step_add · Content Studio
Done. Content Studio in your workspace now has the change, and every new run follows it.

more example prompts

  • "Add an SEO check step to Blog Post after Edit."
  • "Make every workflow in this kit load our brand voice guide at the brief."
  • "Schedule a Newsletter Issue every first Monday."
questions

Content Studio kit FAQ

What is the ConvOps Content Studio kit?

The ConvOps Content Studio kit gives your AI four workflows for a content team: Blog Post, Social Post, Newsletter Issue and Content Repurpose. Each starts from a brief, saves every draft as a task note, and holds at a gate until an explicit approval is given before anything is published or sent. A post becomes the source for the other three.

How many approvals does a full content cycle have?

Six across the ConvOps Content Studio kit. Blog Post has two (Outline and Final Review), Content Repurpose two (Angles and Review), Social Post one (Polish) and Newsletter Issue one (Send Review). Each holds its step until an explicit approval is given, recorded with the account that gave it. You can remove any once the team no longer needs it.

Does it publish to my CMS or social accounts?

No. Each ConvOps Content Studio workflow ends with approved, ready-to-publish copy saved as a task note: the post, the social variants, the per-channel versions, or the newsletter issue with its subject line and preview text. You or your AI client publish it with the tools you already use, and the approved version stays on the task.

What does Content Studio need beyond the Free plan?

One template more than Free allows. ConvOps Free includes 3 workflow templates and Content Studio has 4 (Blog Post, Social Post, Newsletter Issue and Content Repurpose), so the whole cycle from post to newsletter needs Pro or above. None of the four depends on another in the catalog, so on Free you can start with the three you publish most.

How does one piece of content move through the kit?

In ConvOps each template runs on its own task. A Blog Post run ends with the approved draft saved as a task note. That draft can be the source Content Repurpose captures at Source Intake, the brief for a Social Post, or the lead story or a curated item in a Newsletter Issue, each with its own approval.

Can every Content Studio template follow our brand rules?

Yes. In ConvOps, your brand rules can be a policy, which reaches the agent as guidance with the step it is on, in every Content Studio run. To make a check binding rather than advisory, bind a brand review report to Final Review or Review as required in enforce mode, and the step holds until the report is filed.