We just shipped Sheets, a spreadsheet grid inside the platform where each column can run an AI instruction across every row at once. You bring the rows - prompts, URLs, keywords, product names, competitor pages - and Sheets runs the same brief, rewrite or research task across all of them. It's aimed at content, SEO and growth teams who currently do bulk work one item at a time.
Most AI content tools are built around a single task: one prompt, one brief, one page. That's fine for a flagship article and painful for the other 300 URLs on your list. Sheets exists to close that gap without asking you to learn a new interface.
What is Sheets?
Sheets is a bulk AI workspace inside WriteWorks that looks and behaves like a spreadsheet, where columns hold AI instructions and rows hold the items you want to run them against. Instead of pasting one prompt at a time into a chat window and copying the answer back into a document, you define the instruction once at column level and it runs down the whole sheet.
The grid itself is deliberately familiar. Cells, columns, headers, copy and paste, import and export - the mechanics work the way you already expect a spreadsheet to work, so the only new thing to learn is what an AI column does.
How Sheets works
Each AI column carries an instruction that can reference other cells in the same row, so the output is specific to that row rather than generic. A column might take the URL in column A and the target prompt in column B, then produce a brief outline, a meta description, a rewritten intro, or a classification such as "informational / commercial".
Runs are processed row by row against the model you choose, and you can review, edit and re-run individual cells without re-running the whole sheet. Because model selection is already exposed elsewhere in the platform - see the update on choosing your AI model per run with cost shown up front - you keep the same control over which engine handles a bulk job.
Two limits worth stating plainly. Sheets generates and transforms text; it is not a ranking system, and it does not decide on its own which pages matter most. And AI output at volume still needs human review - a bulk run gives you 300 solid first drafts, not 300 finished assets.
Who Sheets is for
It's especially useful if you:
- Produce or refresh content at volume - category pages, product descriptions, location pages, help-centre articles.
- Run keyword or prompt lists through the same classification, clustering or intent-labelling step every month.
- Need briefs for a large batch of topics rather than one hero piece, building on the same logic as content briefs built from the prompts AI engines answer.
- Manage several brands or clients and repeat an identical process for each one.
- Audit a large URL set and want a consistent, structured output per page.
Advanced users benefit too: if you already write precise prompts, Sheets is simply the fastest way to apply one of them several hundred times with row-level variables.
What Sheets changes
The practical shift is that bulk content work becomes a single reviewable artefact instead of a queue of tabs. You can see every input and every output side by side, spot the rows where the model went off-brief, fix those, and export the rest.
That also changes how you brief the work. Because instructions live at column level, the improvement loop is "sharpen the instruction, re-run the column" rather than "re-prompt 40 times". It's the same discipline behind good AI content optimisation - get the instruction right once, then apply it consistently.
How to run your first bulk job in Sheets
1. Open Sheets from the WriteWorks navigation and create a new sheet.
2. Add your rows - paste them in, or import a CSV of URLs, keywords or prompts.
3. Add an AI column and write the instruction, referencing the cells it should use for each row.
4. Choose the model for the run.
5. Run the column, review the first handful of outputs, and adjust the instruction if the pattern is wrong.
6. Re-run, then export the sheet or pass the outputs into your content workflow.
Tips for a better result
- Test on ten rows before running hundreds. Instruction problems show up immediately and cost far less to fix early.
- Give the column a format, not just a task: "three H2 headings, each under 60 characters" beats "write some headings".
- Keep one job per column. Separate columns for outline, meta description and internal-link suggestions are easier to review than one column doing all three.
- Feed the sheet from real demand data - the prompts and volumes surfaced in prompt research make far better rows than a brainstormed keyword list.
- Remember what the output is for. Google's own guidance on how content performs in its AI experiences still points at unique, people-first pages, so bulk drafting should raise your floor, not flatten your quality.
Availability and requirements
Sheets is available in the WriteWorks platform now. Placeholder: confirm release date and which plan tiers include Sheets - see [WriteWorks pricing.]
Frequently asked questions
What is WriteWorks Sheets?
Sheets is a bulk AI workspace inside WriteWorks laid out as a spreadsheet. Rows hold your items - URLs, keywords, prompts, product names - and AI columns hold instructions that run against every row. It is designed for content and research jobs that would otherwise be done one at a time in a chat interface.
How is Sheets different from using a chat assistant?
A chat assistant handles one task per conversation and leaves you to copy results into a document. Sheets applies one instruction across an entire list, keeps inputs and outputs together in a reviewable grid, and lets you re-run individual cells or a whole column after you sharpen the instruction.
Can I import my own data into Sheets?
Yes. You can paste rows directly into the grid or import a CSV, which is the usual route for URL lists, keyword exports and prompt sets. Outputs can be exported again once you've reviewed them, so Sheets fits between your existing data sources and your CMS or editorial workflow.
Does Sheets replace briefs and optimisation elsewhere in WriteWorks?
No. Sheets is the bulk layer. Single-page work is still better served by the dedicated brief and optimisation tools, and repeatable multi-step processes belong in agentic workflows. Many teams use Sheets to produce the batch, then finish high-value pieces individually.
