--- title: "How a Marketing Team Built a Content Operating System — Kylon Use Case" description: "A shared workspace for briefs, source material, brand assets, review notes, publishing decisions, and the work that follows." url: "https://kylon.io/use-cases/content-operating-system" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>[Content production](https://kylon.io/use-cases/topics/content-production)\>How a Marketing Team Built a Content Operating System Use Case7 min read # How a Marketing Team Built a Content Operating System A shared workspace for briefs, source material, brand assets, review notes, publishing decisions, and the work that follows. [Start in Kylon](https://app.kylon.io/launch/content-operating-system) [Book a call](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) What you'll connect - Gmail - Google Drive - Slackoptional - Outlookoptional Your agent asks for each one in the Room. Nothing is sent or written until a person approves it. Kylon TeamProduct August 6, 2026 How we make our videos · 40 s[See every step](https://kylon.io/use-cases/how-we-run-content) Step by step ## From a scattered signal to a published piece. One card per step. The agent prepares, and a named person decides. 1. 01 ### Capture the signal Today Ideas sit in sales threads and chat and never reach the editorial calendar. In Kylon The agent opens a content record linking the request, source material, audience, owner and deadline. Who decides The content owner confirms the record. 2. 02 ### Draft from shared context Today Each draft starts from an isolated prompt and scattered documents. In Kylon An outline, social copy or image brief is prepared from the approved brief, prior decisions and brand guidance. Who decides The reviewer checks the draft. 3. 03 ### Keep outbound email reviewed Today Teams ask who has the latest version before anything goes out. In Kylon Invitations, partner updates and customer emails are drafted in the linked record. Who decides The content owner checks recipient, claims and tone, then sends. 4. 04 ### Repeat the rhythm Today Each campaign is rebuilt from documents scattered across inboxes and drives. In Kylon A workflow opens records from approved requests, prompts the next reviewer and prepares the publishing checklist. Who decides The reviewer gives final approval before anything publishes. What it works with ## The tools you already use. - Connection Gmail Carries the requests that start content work, with every external email drafted for a person to send. - Connection Google Drive Keeps the briefs, source documents and brand guidance each draft is written from. - Optional Slack Is where requests and ideas surface in chat threads. - Optional Outlook Carries email if your team works from Outlook instead. Set it up ## Start with one repeated content workflow. 1. 1\. Start in Kylon A new Room opens in your workspace with this prompt. 2. 2\. Connect what it lists Gmail, Google Drive, from the card in the Room. 3. 3\. Give it your rules Your agent asks one at a time and writes them into the Room's guideline. Set-up prompt Set up our content operating system in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail and Google Drive first, since the first run needs them. Tell me which ones still need connecting. Slack and Outlook can wait until a step uses them. 2. Ask me who drafts content, who reviews it and who gives final approval, and help me invite them to this Room. 3. Build a Content App with one record per piece: the original signal and its source owner, audience, format, proposed angle, owner, reviewer, stage, evidence, deadline, distribution plan, next review date and decision history. 4. Read this week's requests in email and chat and create a record for each one, linked to its source material. Show me the records, and flag any missing evidence or reviewer, before you save them. 5. For the record I pick, draft an outline, social copy or launch email from the approved brief, the linked documents and our brand guidance. Hold any invitation, partner update or customer email in Gmail for a person to check the recipient, claims and tone, and send. 6. Copy our formats, review stages and what needs approval into this Room's guideline. 7. After one clean campaign, offer to turn reviewer prompts, missing-evidence requests and the publishing checklist into an Automation. Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time. [Start in Kylon](https://app.kylon.io/launch/content-operating-system) Rolling this out with a team? ## How it works in detail ## A request should become a working record A webinar idea, product change, customer question, or campaign request often starts in an email or chat thread. The team creates one content record that links the request, its source material, the intended audience, owner, deadline, and decision history. ## Use shared context for every draft The agent can read the approved brief, relevant documents, prior campaign decisions, and brand guidance in the same workspace. It prepares an outline, launch email draft, social copy, or image brief from that context instead of from an isolated prompt. [A creator's next episode: a Kylon demo with sample data](https://static.purework.app/files/5f4900f037a80ff766e91884638ac119/demo-creator-next-episode.mp4) Demo · sample data. One message at night: the creator's own agents make thumbnails, a description and chapters overnight, and in the morning the editor's pick updates the content calendar record. ## Build an editorial app the team can use A database app gives the team a current view of topics, assets, drafts, reviewers, publishing status, and follow-up work. It is useful because the same record carries the latest source material and the reason behind each edit. ## Keep external communication under review When a campaign needs an invitation, partner update, or customer email, the agent prepares a draft in the linked record. A person checks the recipient, claims, and tone, then explicitly confirms before anything is sent. ## Make the rhythm repeatable A workflow can create a content record from an approved request, prompt the next reviewer, and prepare a publishing checklist. The team keeps improving one shared process instead of rebuilding a campaign from scattered documents. ## Turn scattered content signals into an operating record Content work rarely begins with a blank page. It begins with customer feedback in a sales thread, a recurring question from a creator, a product decision in a planning room, or a useful observation that never reaches the editorial calendar. Kylon gives those signals a shared operating record. A workspace database app can hold the source, audience, proposed angle, owner, stage, evidence, distribution plan, and next review date. The record is not a replacement for judgment. It makes the judgment trail visible, so a team can see why an idea was selected, what evidence supports it, and what still needs review. A workflow can collect submissions from agreed rooms, flag incomplete briefs, and remind the assigned owner when a decision is waiting. Editors can then compare opportunities in one place rather than reconstructing context from separate conversations. This is especially useful when product marketing, sales, and creator programs all contribute material but work to different cadences. ### Build a brief that remains useful after publication A durable content brief connects the first signal to the work that follows. For a customer-feedback pattern, the brief can capture the problem in the customer’s own language, the affected workflow, supporting examples, the intended reader, and the product detail that needs validation. For creator outreach, it can record the proposed audience, the collaboration rationale, the review owner, and the approved talking points without treating outreach as an automatic send. For go-to-market planning, it can connect a launch theme to source material, priority distribution surfaces, review milestones, and a measurement question. Each person sees the same current record, while discussion remains attached to the decision rather than lost in a long chat history. This gives writers a clearer starting point and gives reviewers enough context to approve, revise, defer, or decline a request. It also preserves a reusable record when a similar question returns several months later. - Capture the original signal with a link or short excerpt, a source owner, and a note on why it may matter. - Classify the request by audience, business question, funnel stage, and format such as article, customer story, creator brief, or sales enablement asset. - Assign a content owner and a reviewer separately. The separation makes it clearer who is drafting and who is accountable for a decision. - Use a workflow to request missing evidence, move items into a review queue, and send internal reminders when dates approach. - Keep editorial comments, factual checks, legal or brand notes, and final approval in the same workspace context as the brief. - Record the distribution plan and learning question after approval, then review the record when results or qualitative feedback are available. > ““The useful change was not more ideas. It was being able to trace a proposed article from the customer question that prompted it, through review, to the next experiment. The team could decide with context instead of asking who had the latest version.”” ## Use workflows for coordination, not unattended publishing ## What the team keeps in the internal system The exact fields differ by workflow, but the system keeps the source context, current status, accountable owner, decision history, related documents, relevant email thread, next internal action, and review date together. That structure gives people and agents a reliable starting point whenever work changes hands. ## Start with one repeated workflow Teams do not need to replace every tool at once. Start with the repeated work that currently requires people to copy information between conversations, inboxes, documents, and spreadsheets. Build a shared record, connect the people who own it, and use a workflow to support the review rhythm. The system becomes more useful as its context and decisions accumulate. See how Kylon can help your team turn recurring work into a shared operating system. [Talk to Kylon](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) ## More Use Cases [View all](https://kylon.io/use-cases) [ Before: 1,000 to email today, Re: group rates?, call notes: who?, hot lead, unread, OOO reply x40. With Kylon: 12 meetings booked from one send. Scored 214 replies by intent. Workflow tools: Gmail, Outlook, Fathom. ### How a US Hospitality Firm Built an AI Sales Pipeline with Kylon Agents run 1,000-contact outreach, score replies and route leads. - ![HubSpot](https://kylon.io/v2/integrations/small/hubspot-com.webp) - ![Apollo](https://kylon.io/v2/integrations/apollo.png) - ![Cloudbeds](https://kylon.io/v2/integrations/small/cloudbeds-com.webp) - ![Fathom](https://kylon.io/v2/integrations/small/fathom-video.webp) - ![Calendly](https://kylon.io/v2/integrations/small/calendly-com.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/ai-sales-pipeline)[ Before: resume\_final2.pdf, Re: still keen?, interview: TBD, 47 unread applicants, which role is this?. With Kylon: 12 interviews booked this week. Scored 47 resumes vs roles. Workflow tools: Gmail, Outlook, Google Calendar. ### How an AI Startup Automated Talent Sourcing with Kylon Resumes parsed, candidates scored and outreach managed from one room. - ![Greenhouse](https://kylon.io/v2/integrations/small/greenhouse-io.webp) - ![LinkedIn](https://kylon.io/v2/integrations/small/linkedin-com.webp) - ![Airtable](https://kylon.io/v2/integrations/small/airtable-com.webp) - ![Google Calendar](https://kylon.io/v2/integrations/small/google-calendar.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/talent-sourcing)