How to Run Your Company's Content Production In-House With Claude or ChatGPT (2026): 8 Steps, No Agency

Key Takeaways

• Storyflow is the board an in-house team's plan lives on when Claude or ChatGPT does the planning: its connector lets the assistant build the strategy, the dated monthly plan, the briefs and a kanban on one board, then read what changed in the last week and who changed it.
• An agency sells six things: strategy, a monthly plan, briefs, production, review and publishing. An assistant carries most of the first three. People still make, judge and approve the work.
• The loop that replaces a retainer is six stages run on a fixed rhythm: a quarterly strategy, a monthly plan, a brief per piece, weekly production, a review clock, and a publishing queue.
• Four roles cover it, and a team of two can hold all four: owner, maker, reviewer and publisher. The owner is the only role that cannot be shared.
• The software for a team of three costs about $132 a month before design software, at list prices checked on 10 October 2026. WebFX's 2026 survey puts content marketing retainers at $1,000 to $20,000 a month. The real cost of in-house is your team's hours, not the tools.
• Storyflow does not publish posts, has no month grid and has no approve button. Pair it with Buffer for the queue, and keep Asana or Notion if formal approvals or a database are what you need most.
• Do not cancel the agency on day one. Run a 30-day overlap in which the agency delivers this month while your team plans next month on the board.

What an Agency Retainer Actually Buys (and What an Assistant Can Carry)

You are probably not unhappy with the agency's work. You are unhappy that every small change takes three emails, that the monthly plan arrives as a PDF you cannot edit, and that the invoice is the same whether the month was busy or quiet. Before you replace any of that, split the retainer into its jobs. A retainer is not one service. It is six jobs on one invoice, and they are not equally hard to bring home.

The planning jobs are the ones that quietly stop

When a retainer ends, design does not stop. Someone opens Canva. What stops is the thinking nobody saw: the strategy deck that told you which topics to skip, the plan that arrived on the 25th, the brief that reached the designer before the request did. None of your execution tools does those jobs, so a team that goes in-house can end up shipping more posts and saying less.

An assistant drafts fast and forgets fast

Claude and ChatGPT are good at exactly those planning jobs. Give either one your positioning, three customer calls and last quarter's numbers, and it drafts pillars, a month of topics and a set of briefs in one working session. The weakness is storage. A chat thread is not a plan: nobody else on the team can see it, it has no owners or dates you can update, and next week the assistant starts from whatever you remember to paste back in.

The fix is a board the assistant can write to and read from

That is the gap a connector closes. Storyflow's MCP server, launched in October 2026, lets the assistant put its output straight onto a board your team shares (notes, tables, documents, a kanban, slide decks) and read the same board back later. The plan stops living in one person's chat history. It lives where the designer, the founder and the next conversation can all find it.

How We Chose Where the Plan Lives: Criteria and Weighting

Every tool below is good at something. The question this guide answers is narrower: when the planning is done in Claude or ChatGPT, where should the output land so that a team of two to four can run on it for months? We scored that job on five criteria and published the weights so you can disagree with them.

Why the connector carries 30%

Without a write-capable connector, the assistant's plan has to be copied by hand into the tool, and copied back out for every update. That copy step is where in-house plans go stale. A connector that only searches your files helps the assistant answer questions. It does not let the assistant maintain the plan.

What we did not score

We did not score publishing, design or video editing, because no planning tool should be judged on jobs it hands off. We also did not score formal approvals. If a legal or compliance sign-off with an audit trail is your main requirement, that is a different weighting, and Storyflow would not lead it.

Full disclosure: Storyflow is our product. It ranks first here because this weighting rewards an assistant building and reading the whole plan on one visual board, which is what Storyflow's connector does. It has no publishing, no month grid, no formal approvals and no native apps. On a weighting where scheduling and sign-off carried half the score, Buffer and Asana would rank above it.

Where Each Tool Sits in an In-House Content Operation

This table places the six tools in the stack by the job each one does. Connector details and prices come from each vendor's own pages, linked in the tool notes further down.

Read the table by column two. Only one of these tools is a place for the plan behind the work, and four are places where the work gets made or shipped. That is the shape of the stack: one hub, several hands.

How to Run Content Production In-House With Claude or ChatGPT in 8 Steps

The eight steps below are the operating loop. Steps 1 and 2 happen once a quarter, step 3 once a month, steps 4 to 7 every week, and step 8 at month end. Each step names what you ask the assistant to do, what lands on the board, and what a person has to decide.

Step 1: Name One Owner and Set Up the Board

An agency gave you one thing a tool never will: a named person who was accountable for the month. Replace that first. One person owns content production, which means they decide what gets made, what gets cut and what ships. On a team of two that is the marketer. In a founder-led company with no marketer, it is the founder, for two hours a week.

Then the owner creates one Storyflow project called Content, with one board per quarter, and connects their assistant to it. Scope the connection to that one project at sign-in and allow changes.

Ask the assistant to lay out the board in five sections: Strategy, This Month, Briefs, Production and Results. Over the connector, sections of notes and tables and the kanban are built with the build_section tool, and the assistant places each one on the board where it belongs. Open the board while it works: what the assistant adds appears live.

Step 2: Write a One-Page Strategy With the Assistant

Most in-house teams skip this step and go straight to topics. Then every week starts with "what should we post?", which is the most expensive question in content.

Give the assistant four inputs: who buys from you and why, the three questions sales hears most, what you sold last quarter, and what you refuse to talk about. Ask for three to five content pillars, the two or three channels you can run with the people you have, one measurable goal for the quarter, and a short list of things you will not do. Ask it to write that as a one-page document in the Strategy section of the board.

Then cut. An assistant given no constraint proposes five channels and daily posting. Your job is to delete until the plan fits the hours you have. A strategy for an in-house team is mostly a list of what you are not going to make.

The decision that stays human: the pillars. An assistant can propose ten plausible ones. Only you know which three the company can speak about with authority.

Step 3: Build the Monthly Plan as a Dated Table

On the 20th of each month, plan the next one. Ask the assistant to read the Strategy section and last month's Results section, then build a table in This Month with one row per piece: publish date, title, pillar, format, channel, owner and status. Tell it your capacity in pieces, not hours, for example "one anchor piece, four articles and twelve social posts".

Plan around one anchor piece a month: a customer story video, a webinar, a research piece or a long guide. Then ask the assistant to list the derivatives each anchor will produce (clips, quotes, a newsletter section, a carousel) and add them as rows. Derivatives planned before the anchor is made are cheaper than derivatives invented afterward, because the recording is set up to produce them.

Two honest limits. Storyflow has no month grid, and the canvas cannot sort a table, so ask the assistant to keep the rows in date order when it builds and updates them. If your team must see the month on a grid, look at the scheduled posts in your scheduler's calendar and keep the plan behind them on the board.

Step 4: Turn Every Row Into a Brief Before Anyone Makes Anything

A request is not a brief. "We need a post about the new integration" is a request. The agency's account manager turned requests into briefs for you, and that translation is the first thing an in-house team forgets to replace.

For each row in the month's table, ask the assistant to write a brief as a document in the Briefs section: the one reader, the one thing they should believe afterward, the proof, the format and length, the call to action, the deadline and the reviewer. Seven fields, one page. Briefs for derivatives can be three lines that point at the anchor's brief.

The owner reads every brief before production starts and either approves it or rewrites the angle. This is the least expensive review point in the whole loop: changing a sentence in a brief is quick, and changing a finished video can mean a re-edit. For a longer walk-through of the brief itself, see how to write a campaign brief with ChatGPT or Claude.

Step 5: Run Production Off a Kanban, Not a Chat

Once briefs are approved, ask the assistant to build a kanban in the Production section: a row of column walls named Briefed, In Progress, In Review, Approved and Published, with one ticket per piece carrying its owner and date. In Storyflow a kanban is a row of column walls holding tickets, and the connector builds it in one request.

Makers then work in their own tools. The writer drafts in a Storyflow document or in Notion. The designer works in Canva. Whoever edits video works in Descript. The assistant helps inside production too: first drafts from the brief, a script outline from a transcript, five headline options, a caption per channel. Each maker moves their own ticket when the state changes.

Keep the references on the board. Brand examples, screenshots, the competitor post you want to beat and the product images go beside the brief, where the designer sees them without asking. Over the connector the assistant can add pictures to the board from web addresses, and for a picture on your computer it gives you an upload link, because a photo attached in the chat does not reach Storyflow.

Step 6: Put Review on a Clock

Unbounded review is why in-house content ships late. An agency enforced rounds because rounds cost it money. You need the same rule without the invoice.

Write the rule on the board: one reviewer per piece, named in the brief; 48 hours to respond; two rounds at most; silence after 48 hours counts as approval for anything that is not a legal or pricing claim. Before a piece goes to the reviewer, ask the assistant to check the draft against its brief and list every place the draft drifts from the reader, the claim or the call to action. That catches the avoidable round.

For stakeholders outside the team, share the board with a view-only link. They open it with no account, and they sign in to comment. Two limits to plan around: Storyflow has no approve button or versioned sign-off, so approval is a ticket moved to the Approved wall by the named reviewer. And the connector cannot read comment threads, so the owner reads comments on the board and tells the assistant what changed.

Step 7: Publish From a Queue

Publishing is the job to automate hardest and think about least. Storyflow does not publish or schedule posts, so finished pieces leave the board here.

When a ticket reaches Approved, the publisher loads the post into Buffer. Buffer's MCP page says access is included on every plan, including Free, and that posts an assistant creates land in your queue as drafts or scheduled posts for you to review before they go out. In practice, an assistant with both connectors can read the approved rows on the Storyflow board and create matching drafts in Buffer. A person still checks each draft and confirms the schedule.

Blog posts, newsletters and videos go out through whatever you already use: your CMS, your email tool, YouTube. The rule is the same for all of them: nothing is published that is not on the Approved wall, and the ticket moves to Published the same day with the live link added.

Step 8: Review the Month in One Hour

The agency's monthly report was 20 slides you skimmed. Replace it with one hour and two questions: what worked, and how healthy was the process.

The assistant cannot see your analytics through Storyflow, so paste in the numbers that matter (per piece: views or reads, clicks, replies, leads) or export them from your scheduler and analytics tools. Ask the assistant to add them to a table in the Results section, chart the top five pieces, and write three observations and two changes for next month. Then ask it what changed on the board in the last month and who changed it, and use that to see where pieces sat longest.

The owner keeps two numbers from that hour: the share of planned pieces that shipped on time, and the one result tied to the quarterly goal. Those two numbers feed step 3 for the following month, which closes the loop.

The Four Roles, for a Team of Two, Three or Four

You do not need four people. You need four roles with one name against each, so that nobody waits for "the team" to decide.

The owner is the only role you cannot split

Two owners means two plans. If the founder and the marketer both decide what ships, the board fills with half-approved work. Give one person the veto and the other a named review slot.

Makers should not also review their own work

On a team of two this is the hardest rule to keep. The fix is small: the person who did not make the piece gets ten minutes with the brief and the draft side by side, and the assistant's brief check from step 6 does the first pass.

Subject experts are reviewers, not writers

Your head of product knows the feature. That does not mean they should write the post. Have the assistant draft 6 to 8 interview questions from the brief, record a 20-minute call, and write from the transcript. The expert then reviews for accuracy only, inside the 48-hour clock.

The Rhythm That Replaces the Account Manager

An account manager's real product was cadence: things happened on set days because someone chased them. In-house, the calendar invitation does the chasing.

The Monday meeting is the one that matters most. Open the board on a shared screen and walk the kanban from right to left: what published, what is approved and unscheduled, what is stuck in review, what is in progress, and what has not started. The assistant's change summary, built with the connector's board-changes tool, tells you what moved in the last week and who moved it before anyone has to remember. That tool reads fixed windows only (the last day, the last week or the last month), which happens to match this rhythm.

14 Prompts to Copy, by Stage

Each prompt assumes your assistant is connected to Storyflow and scoped to your Content project. Replace the bracketed parts. Run them one at a time: a single prompt asking for strategy, plan and briefs at once produces a thinner version of all three.

The publishing prompt needs Buffer's connector as well as Storyflow's. If you run only Storyflow's, ask the assistant to format each approved post for its channel and paste them into your scheduler yourself.

A Worked Example: One Month for a Team of Three

This is an illustrative example, not a measured case. The company, the counts and the hours are invented to show the loop at a realistic size.

Picture a 45-person company that sells scheduling software to dental clinics. It has paid an agency for 18 months and wants the work in-house. The team is three people: a marketing lead who owns content, a content marketer who writes and publishes, and a designer who also edits video two days a week. The founder reviews anything that makes a product claim.

The setup week

The marketing lead connects Claude to a Storyflow project called Content and asks for the five-section board. They paste in notes from six sales calls and last quarter's numbers. The assistant proposes five pillars. The team keeps three: front-desk time saved, no-show reduction and multi-location reporting. They pick two channels they can sustain (LinkedIn and a fortnightly newsletter) plus the blog, and one goal: 40 demo requests from content in the quarter.

The month on the board

On the 20th, the assistant builds November's table from the strategy document. The team sets capacity first, then lets the assistant fill it.

The assistant writes 26 briefs: full pages for the video and the four articles, three-line briefs for the 21 derivatives. The marketing lead rewrites the angle on two of them and approves the rest in one sitting. The kanban gets 26 tickets.

What the assistant did, and what the people did

In this example, the assistant builds the board, drafts the strategy page, builds the month's table, writes every brief, drafts the four articles from briefs and transcripts, writes the 12 LinkedIn posts, checks each draft against its brief and prepares the Monday summaries. The people choose the pillars, set capacity, run the interview, record and edit the video, design the carousel, rewrite the drafts into the company's voice, review, approve and publish.

Two things go wrong, as they would. The founder misses the 48-hour clock on the anchor video, so the six clips slip four days and two LinkedIn posts move to December. And one article draft makes a claim about no-show rates that the brief check flags as unsupported; it slips into the first week of December and ships with a customer's own number in it. The month closes with 23 of 26 pieces published. On the last working day the marketing lead pastes in the numbers, and the observation that changes December's plan is that the six clips out-performed all four articles on demo requests.

How to Connect Claude or ChatGPT to Storyflow

Connecting takes one address: https://mcp.storyflow.so/mcp. The full walk-through is in the help article on connecting AI assistants.

Connect Claude

In Claude, open Customize, then Connectors, choose Add, then Add custom connector. Name it Storyflow, paste the address, choose Continue, pick Sign in now, choose Add, and sign in to Storyflow. Anthropic's custom connector guide says custom connectors are available on Free, Pro, Max, Team and Enterprise, with Free limited to one custom connector. On Claude Team, an owner adds the connector for the organisation. Our step-by-step version is in how to connect Claude to your project board.

Connect ChatGPT

Custom connectors in ChatGPT need ChatGPT Plus or above with Developer mode. On the web, open Settings, then Security and login, and turn Developer mode on (on Business and Enterprise an admin does this). Go to chatgpt.com/plugins, choose the plus button, name it Storyflow, choose Public endpoint, paste the address, create it and sign in. OpenAI documents the feature in its developer mode article. The longer guide is how to connect ChatGPT to your project board.

The permissions to pick at sign-in

At sign-in you choose three things: which projects the assistant may use (all, or ones you pick), whether it may make changes or only read, and whether it may use documents outside projects. For a content operation, pick the Content project only and allow changes. Connections expire after 30 days, and you can disconnect in Settings under Connected apps, with access ending within a minute.

Each teammate connects their own assistant with their own Storyflow account. On Plus, Pro and Max the connector has no action limit. A teammate on a free account (today, that means one invited by a paid member) gets 25 actions a week, with every read and every change counting as one, reset on Monday UTC. The connector runs on your assistant's own model, so it does not spend Storyflow AI credits.

If you would rather not use an outside assistant at all, Storyflow's built-in AI agent runs the same planning jobs inside the app, with workflows for a content plan, a social media plan, a campaign brief and a marketing plan. It reads the current board plus up to five attached documents and up to three other boards.

Where Notion, Asana, Canva, Descript and Buffer Fit

An in-house operation is a stack, and most of the stack is not Storyflow. Here is where each of the other five earns its place, with what its connector does, checked on each vendor's own page on 10 October 2026.

Notion: the wiki and the long-form drafts

Keep Notion if your company's knowledge already lives there and your content is mostly writing. Notion's help page says Notion MCP lets AI apps read and write your pages, with project pages, databases and task lists among its listed uses, and notes that connected tools act with your full Notion permissions. Notion's pricing is per member: Plus is $10 per member a month billed annually ($12 monthly) and Business is $20 ($24 monthly). Notion places below Storyflow on this guide's weighting because the assistant builds pages and database rows rather than a visual plan with references beside it.

Asana: tasks and approvals across departments

Keep Asana if content is one workstream among several and other departments already assign work there. Asana's developer documentation describes an MCP server that lets assistants create and manage tasks and projects and generate reports, with Asana apps in Claude and ChatGPT. Asana's pricing page lists Personal as free for up to 2 users, Starter at $10.99 per user a month billed annually and Advanced at $24.99. Asana holds tasks well and holds briefs, references and strategy poorly, which is why it sits beside the plan rather than under it.

Canva: design for people who are not designers

Canva is where a marketer makes the carousel, the thumbnail and the event banner. Anthropic's Canva connector page says Claude can browse, summarise, autofill and generate Canva designs, export them and organise folders. The useful pattern is to hand the assistant the brief from the board and ask for a first design to edit, not a finished one. For plans and prices, see Canva's pricing page.

Descript: video and podcast editing by transcript

Descript is the editor for a team without an editor: you cut video by deleting words in the transcript. Descript's help article on connecting to Claude says the connector can import media, edit, manage projects and publish from a chat, and that imports and edits through it use your media minutes and AI credits. Descript's pricing page lists a Free plan with 1 media hour a month, Hobbyist at $16 a month billed annually with 10 hours, Creator at $24 per person with 30 hours, and Business at $50 with 40 hours. For a weekly video cadence, Creator is the realistic starting point.

Buffer: the publishing queue

Buffer is the last step. Buffer's pricing page lists Free for up to 3 channels and 1 user, Essentials at $5 per channel a month, and Buffer's Team tier at $10 per channel a month with unlimited users and approval workflows. Its MCP access is on every plan. If your reviewer wants to approve the exact post before it is scheduled, Buffer's Team tier is where that approval belongs, not the planning board.

One tool we left out of the core stack: Frame.io, which is the stronger choice for frame-accurate video review. Frame.io's pricing page lists a free tier for up to 2 members and Pro at $15 per member a month. Add it when video review, not planning, becomes your bottleneck.

What It Costs Against an Agency Retainer

The software is the small number. Prices below are list prices from each vendor's page on 10 October 2026, in US dollars. Canva is left out because we could not confirm its prices on its own page; add your Canva plan to the total. Retainer and hours figures are estimates.

Now the honest half. The same WebFX survey puts in-house content teams at $5,000 to $25,000 or more a month, because the cost of in-house is salaries. If your three people already exist and content is part of their job, the marginal cost of dropping the retainer is the software plus the hours you move. If you would have to hire to do it, compare the retainer with a salary, not with $132.

As a planning estimate, the loop in this guide asks the owner for about six hours a week (planning, briefs, review, the three meetings) on top of the makers' production time. If nobody has those hours, the plan goes stale, and keeping a smaller retainer for strategy and planning is the better trade.

Decision Rules: Which Setup Fits Your Company

Pick by the constraint that binds first, not by the feature list.

Whatever you choose, keep these jobs with freelancers or a specialist at any size: a brand film, paid media buying, a website rebuild and anything that needs a crew. In-house works for the weekly rhythm. It does not have to cover the once-a-year project.

Common Mistakes When You Replace an Agency With an Assistant

Each of these looks like progress in week one and costs you in week six.

Mistake 1: Asking for the whole month in one prompt

One prompt that asks for strategy, a calendar and 30 posts returns a generic version of each. Run the stages in order, and approve each before the next: pillars, then the table, then briefs, then drafts.

Mistake 2: Leaving the plan in the chat

A plan in a thread has no owners, no dates anyone else can change and no history. If the assistant has a connector to your board, every planning prompt should end with where the output goes.

Mistake 3: Publishing the assistant's first draft

A first draft from a brief is on topic and voiceless. Readers can tell. Budget rewriting time for every piece, and put the proof (a customer number, a screenshot, a quote from a recorded call) in the brief so the draft has something real to stand on.

Mistake 4: Planning for the hours you wish you had

An assistant will happily plan 60 pieces. State capacity in pieces before you ask for a plan, and cut a quarter of what comes back. A plan that ships 18 of 20 pieces on time does more for the team than one that ships 20 of 50 late.

Mistake 5: Letting two people own it

When the founder and the marketer both decide what ships, nothing ships on time. One owner, one veto, one named review slot for everyone else.

Mistake 6: Connecting every project

Scope the connector to the Content project. An assistant that can read and change everything will, sooner or later, put a brief on the wrong board. Narrow access also keeps weekly summaries about content only.

Mistake 7: Cancelling the agency before the first in-house month ships

The first month in-house usually ships less than planned. Overlap for 30 days, as in the handover plan below, so the gap never reaches your audience.

When Storyflow Is Not the Right Choice

If you are weighing a hub for a marketing team, our page on Storyflow for in-house content production and the one for marketing teams show the board in use. Storyflow is the right hub when the plan is visual, the planning is done with an assistant, and stakeholders need to look without a seat. It is the wrong hub in these cases.

• You need the tool to publish. Storyflow does not schedule or post anywhere. Every setup in this guide pairs it with Buffer or another scheduler.
• You need a month grid. There is no calendar tool on the board. Dates live in table date cells and on tickets, and the canvas cannot sort a table. If your team thinks in a grid, plan in Notion or look at the grid in your scheduler.
• You need formal approvals. There is no approve button, no versioned proofing and no audit trail. Regulated industries should run sign-off in Asana, Buffer's Team tier or a proofing tool.
• You need the assistant to read feedback. The connector cannot read comment threads. A person reads comments on the board and relays the decision.
• You need generated images from the chat. The connector has no image-generation tool. Image generation is in Storyflow's built-in agent on Pro and Max; over the connector the assistant adds existing pictures or gives you an upload link.
• You need it free today. Storyflow is paid-only during early access. Its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now.
• Your team works offline or on phones. Storyflow runs in the browser only, with no native mobile or desktop apps.
• Your content is all long-form text in an existing wiki. A Notion workspace your company already maintains will serve that better than a canvas.

The In-House Content Board: A Template to Copy

Build this once per quarter. The first prompt in the table above creates the shell; the rest of the loop fills it.

The one-page brief has seven fields: reader, what they should believe afterward, proof, format and length, call to action, deadline, reviewer. The review rule has four parts: one named reviewer, 48 hours, two rounds, and silence counts as approval except for legal and pricing claims. Write both on the board where every maker sees them.

A 30-Day Handover From Agency to In-House

Give notice last, not first. This plan runs your first in-house month in the shadow of the agency's last one.

Three items people forget to collect: the source files (not only exports), ownership of the ad and social accounts, and the list of freelancers the agency used. Ask for all three in writing in the first week.

The Bottom Line

An agency retainer bought you a plan, a cadence and a pair of hands. The hands were never the hard part to replace: Canva, Descript and Buffer are built for teams without specialists. The plan and the cadence were. Claude or ChatGPT can now write the plan, and a board the assistant can build on and read back keeps it alive between conversations.

So the answer to "how do I run this without an agency" is not a tool. It is one owner, a six-stage loop, a Monday meeting, and a Storyflow board where the strategy, the month, the briefs and the status sit together. Connect your assistant to Storyflow, ask for the five-section board, and plan one month at half the agency's volume while the retainer still runs. Check Storyflow's pricing before you start; one paid seat and invited teammates is enough to test the loop.

This article was published in October 2026. Prices and connector details were checked on each vendor's own pages on 10 October 2026.