Announcing o11's backing from Y Combinator.
Government Agencies: AI Briefing Decks in Google Slides
Government agencies run on briefings. A deputy director needs a policy summary for the secretary by 3 PM. A program manager has to present quarterly performance metrics to an oversight committee next Tuesday. A regional office needs to brief headquarters on community feedback from last month’s public meetings. Every one of these requests ends with someone building a slide deck, usually under time pressure and with data scattered across multiple documents and spreadsheets.
The federal government alone produces an estimated 30,000 briefing presentations per week across its agencies. State and local governments add tens of thousands more. Most of these decks are built by analysts and program staff who are also responsible for the substantive policy work the presentations describe. The time they spend formatting slides and manually transferring data from reports into charts is time they are not spending on analysis, stakeholder engagement, or program improvement.
This is not a technology gap. Government agencies have adopted Google Workspace at scale. The data exists in Google Sheets. The reports exist in Google Docs. The templates exist in Google Slides. What is missing is the connection between these tools: a way to turn source material into a finished briefing without the manual assembly step that consumes hours of analyst time every week.
Policy Briefing Decks from Research Reports
Policy briefings are the core communication format in government. An analyst reads a 40-page research report, synthesizes the key findings, and distills them into 8 to 12 slides that a senior official can absorb in 15 minutes. The content needs to be accurate, the data needs to be sourced, and the format needs to follow the agency’s presentation standards.
o11 For Google Slides reads directly from Google Docs where policy research and reports are stored. Instead of manually extracting key points and rebuilding them in slide format, you describe the briefing’s purpose and audience.
“Build a 10-slide policy briefing from the ‘Water Infrastructure Assessment Q4’ Doc. Focus on the three highest-priority recommendations, include the cost estimates from Section 4, and add a map slide showing affected regions. Use the agency briefing template.”
o11 pulls the substance from the source document, structures it for a slide format, and applies the agency’s standard template. The analyst reviews for accuracy and policy nuance rather than spending two hours on layout and data entry.
“Add a slide summarizing the public comment period results. Pull the sentiment breakdown from the ‘Community Feedback Summary’ Doc and include the top 5 concerns by frequency.”
For agencies that produce weekly or monthly briefings on recurring topics, this workflow is particularly valuable. The structure stays consistent, the data updates automatically from source documents, and the analyst’s time goes toward analysis rather than formatting.
Budget Presentation Slides from Fiscal Data in Sheets
Budget season in government is a gauntlet of presentations. Program managers present to division directors, who present to agency heads, who present to legislative committees. At every level, the same fiscal data gets reformatted into a different slide deck with different emphasis. A single budget cycle can generate dozens of presentations from the same underlying spreadsheet.
o11 connects directly to the Google Sheets where fiscal data lives. This means budget presentations stay linked to their source data, and changes propagate without manual updates.
“Create a budget overview presentation for the FY2027 request. Pull appropriation figures from the ‘FY2027 Budget Justification’ Sheet, compare them to FY2026 enacted levels in column D, and highlight any program with a change greater than 10%. Use the CFO’s standard budget template.”
The resulting deck includes properly formatted comparison tables, variance highlights, and trend charts built from the actual spreadsheet data. When the budget office revises a number at 9 PM the night before a hearing, the presentation reflects the change without a rebuild.
“Generate a one-page spending summary slide for each of our 8 program offices. Pull obligations and outlays from the ‘Execution Tracker’ Sheet and include the burn rate percentage for each.”
For budget analysts who currently build these slides by hand, copying numbers from spreadsheets into table placeholders one cell at a time, this is the difference between a full day of formatting and an hour of review.
Public Meeting Presentations with Community Data
Public engagement is a growing requirement across government. Town halls, community advisory boards, environmental impact hearings, and public comment sessions all require presentations that make complex policy accessible to non-specialist audiences. These decks need to be clear, data-supported, and sensitive to community concerns.
Building public-facing presentations from internal data requires a different approach than internal briefings. The language needs to be plain. The charts need to be simple. The structure needs to guide a diverse audience through unfamiliar material.
“Build a 15-slide public meeting presentation on the proposed transit expansion. Pull ridership projections from the ‘Transit Data’ Sheet, route maps from the ‘Planning Assets’ folder, and community survey results from the ‘Public Input Summary’ Doc. Use plain language appropriate for a general audience.”
o11 adapts the content for the specified audience while maintaining data accuracy. It does not dumb down the analysis. It presents it in a format that a community member without a policy background can follow.
“Add a FAQ slide based on the top questions from last month’s public comment period. Pull from the ‘Comment Tracking’ Sheet and group by theme.”
For agencies managing multiple concurrent public engagement processes, the ability to generate audience-appropriate presentations from centralized data sources means more consistent messaging and fewer errors in public-facing materials.
Before and After: The Analyst’s Briefing Workflow
Before o11: A briefing request comes in at 10 AM for a 2 PM meeting. The analyst opens the source report in Docs, reads through it, identifies key points, opens Slides, searches for the correct template, and begins building. Data from Sheets gets copied into chart placeholders manually. Formatting eats an hour. A colleague reviews and catches a transposed number. The analyst fixes it, re-checks the source, and delivers the deck at 1:45 PM. Total time: nearly 4 hours of focused work for a 10-slide briefing.
After o11: The same request comes in. The analyst opens Slides, prompts o11 with the briefing requirements, and points it to the source Doc and relevant Sheets. A complete draft appears in minutes. The analyst spends 30 minutes reviewing for policy accuracy, adjusts the framing on two slides with follow-up prompts, and delivers at 11 AM. Total time: under an hour. The remaining three hours go back to the substantive work the analyst was hired to do.
The compounding effect matters. An analyst who saves three hours per briefing and produces four briefings a week recovers 12 hours of capacity. Across a division of 10 analysts, that is 120 hours a week returned to mission-critical work.
Why o11 Instead of a Generic AI Tool
Government presentations have requirements that generic AI tools cannot meet. Agency templates with specific formatting rules. Data that must trace back to authoritative sources. Language that follows plain-writing standards. Presentations that may become public records.
A generic AI tool can generate a slide deck about water infrastructure policy. It cannot pull the actual cost estimates from your agency’s budget Sheet, format them according to your CFO’s template standards, and maintain the data lineage that an inspector general might audit. That is the difference between a content generator and a workspace tool.
o11 also respects the separation between source data and presentation. It does not generate plausible-sounding numbers. It pulls real figures from real spreadsheets. For government work, where a misquoted statistic in a congressional briefing can become a headline, that fidelity is not optional.
The agencies adopting o11 are not replacing their analysts. They are giving their analysts back the time that manual slide construction was consuming, so those analysts can focus on the policy work that requires human judgment, institutional knowledge, and subject matter expertise.
