Announcing o11's backing from Y Combinator.
Content Marketers: Scale Blog Production in Google Docs
Content marketing has a throughput problem. The strategy deck says publish three blog posts per week, two case studies per month, and a quarterly whitepaper. The reality is a two-person content team that spends Monday in a planning meeting, Tuesday through Thursday writing one blog post, and Friday formatting it for the CMS. The case studies are perpetually “in progress.” The whitepaper is a bullet-point outline that has not moved since Q3.
The bottleneck is not ideas or strategy. Most content teams have more topics in their backlog than they could publish in a year. The bottleneck is production: turning a content brief with target keywords and a rough angle into a finished, formatted draft that the editor approves and the designer can work with. Each piece requires research, outlining, drafting, editing, and formatting. Multiply that by the volume a modern SEO strategy demands, and you have a team that is always behind schedule.
o11 For Google Docs addresses the production bottleneck directly. It does not replace your content strategist or your editor. It compresses the gap between “approved brief” and “first draft ready for review” from days to minutes. And because it works inside Google Docs, the draft arrives in the same environment where your editor reviews it, your stakeholders comment on it, and your CMS plugin exports it.
Blog Post Drafts from Content Briefs and Keyword Research
A content brief typically includes a working title, target keywords, a brief angle or thesis, audience notes, and maybe a competitor reference. The writer’s job is to turn that brief into 1,500 words of original, well-structured content that hits the keywords naturally, follows the brand voice, and actually says something useful. That process takes a skilled writer three to five hours per post.
o11 compresses the drafting phase without removing the writer from the equation.
“Write a 1,500-word blog post based on this content brief. Target keyword is ‘financial reporting automation for mid-market CFOs.’ Hit the secondary keywords in H2 subheadings. Use our brand voice from the Style Guide doc in the Content Team folder. Include a practical example in each section.”
The output is not a generic SEO article stuffed with keywords. o11 reads your style guide from Google Drive and produces a draft that matches your brand’s tone, sentence structure, and formatting conventions. The target keywords appear in headings and body text at a natural density because the AI was given the brief’s intent, not just a keyword list.
“Pull the three most recent customer quotes from our Testimonials spreadsheet in Sheets. Work them into the blog post as supporting evidence in relevant sections. Format as blockquotes.”
This is where working inside Google Workspace matters. o11 reads directly from your Sheets data and places testimonials contextually, not just appended at the bottom but integrated into the sections where they support the argument. Your writer reviews a draft that already has real customer voices woven in, ready for editorial polish rather than structural assembly.
Case Study Documents from Customer Interview Notes
Case studies are the highest-value content most marketing teams produce, and also the hardest to finish. The raw material is usually a set of interview notes, a few metrics from the customer success team, and maybe a recorded call transcript. Turning that into a polished narrative with a clear problem-solution-result arc takes significant writing effort, which is why most teams have a backlog of “almost ready” case studies that never ship.
o11 handles the structural assembly that makes case studies so time-consuming.
“Create a case study draft from the customer interview notes in ‘Acme Corp Interview Notes’ in our Case Studies folder. Follow our standard case study template: Company Overview, Challenge, Solution, Results, What’s Next. Pull the ARR growth and time-savings metrics from the Customer Metrics spreadsheet in Sheets.”
o11 reads the interview notes, identifies the narrative arc, and assembles a structured draft that follows your template. The metrics from Sheets are placed in the Results section with appropriate context. The draft reads like a story, not a data dump, because the AI understands the case study format and organizes the raw material accordingly.
“The challenge section needs more specificity. Expand it using the pain points the customer mentioned about manual reporting in the interview notes. Keep the direct quotes but clean up any verbal filler.”
Iterative refinement inside the same Google Doc means your editor and the customer success manager can both comment on the draft in real time. There is no version management problem, no “which draft is current” confusion. The document lives in Docs from first draft to final approval, with full version history intact.
Whitepaper Creation from Research Outlines
Whitepapers are where content marketing meets thought leadership, and where production timelines go to die. A typical whitepaper starts as a research outline with section headings, key arguments, supporting data points, and source references. The outline might take a week. The actual writing takes three to six weeks, because whitepapers require sustained, structured argumentation that is difficult to produce in the interrupted workflow of a busy content team.
o11 does not write the whitepaper for you. It builds the scaffolding so your subject matter experts can focus on the ideas rather than the structure.
“Expand this research outline into a full whitepaper draft. Each section heading becomes a 400-word section. Use the data points listed under each heading as the foundation for the argument. Maintain an analytical, evidence-based tone. Pull the industry benchmark data from our Market Research spreadsheet in Sheets and cite it inline.”
The output is a 3,000-word first draft that follows the outline’s logic, incorporates the specified data, and maintains a consistent tone throughout. Your subject matter expert reviews a complete document rather than staring at an outline wondering where to start. They can focus their limited time on strengthening arguments, adding nuance, and inserting insights that only a human expert would know.
“Add an executive summary at the top. Summarize the three core arguments and the primary recommendation in under 200 words. Match the tone of the rest of the document.”
The executive summary is generated from the content o11 just wrote, ensuring it accurately reflects the document’s actual arguments rather than restating the original outline. This is a small detail that saves meaningful editing time: the summary and the body are always in sync.
Before and After: The Content Production Workflow
Before o11: A content brief is approved on Monday. The writer researches and outlines on Tuesday, drafts on Wednesday and Thursday, self-edits on Friday. The editor reviews next Monday, sends feedback Tuesday. Revisions happen Wednesday. The post publishes Thursday, eleven business days after the brief was approved. The team produces two posts per week at maximum capacity. Case studies take four to six weeks. The whitepaper is perpetually delayed.
After o11: The same content brief is approved Monday morning. The writer prompts o11 with the brief, style guide, and keyword targets. A structured first draft arrives in thirty minutes. The writer spends two hours refining voice, adding original insights, and polishing. The editor reviews Monday afternoon. The post publishes Tuesday, two business days after approval. The team produces four to five posts per week. Case studies take one to two weeks. The whitepaper gets finished.
Why o11 Instead of a Generic AI Writing Tool
ChatGPT, Jasper, and Copy.ai can all generate blog posts. The question is what happens after generation. With a standalone AI tool, the output arrives as plain text that you paste into Google Docs, reformat to match your style guide, manually insert data and quotes, and then share for review. The generation was fast, but the assembly work eats the time savings.
o11 eliminates the assembly step entirely. Your draft is generated inside Google Docs, formatted to match your existing templates, populated with data from your Sheets, and immediately available for collaborative editing. There is no copy-paste step. There is no reformatting. There is no “which version has the latest changes” problem.
For content teams that measure output in published pieces per week, this distinction is the difference between producing incrementally more content and doubling your publishing cadence without adding headcount.
