Finished Office documents. Straight from your data.
Offers, reports, contracts, letters — generated as native Word, Excel and PowerPoint files from your templates and your live data. Define the document once as a playbook; from then on the platform generates it — one at a time, in bulk, or on an assistant's request.
Not just text in a .docx — the full Word feature set.
Many tools can produce Office files, but use only a fraction of the format. Docs commands all of it: tracked changes, comments, charts, styles, headers and footers. And it doesn't just create new documents — it edits existing ones: “Flag every critical clause in this contract with a comment.”
- Tracked changes and comments — suggestions and annotations like a colleague would leave
- Edit existing documents: review, comment, revise — not just generate new ones
- Charts, tables and styles — real Word, Excel and PowerPoint elements
- Live data from the Index: prices, line items, master data — always current
- PDF output included when the document must be immutable
Define once. Generate forever.
A playbook describes how a document type is built: structure, data sources, text blocks, corporate design. Set it up once and it produces every offer, every report, every contract by the same rules — whether one or a thousand.
- Structure, data binding and branding per document type — maintained centrally
- Corporate design enforced: fonts, colors, logos, footers — no exceptions
- Bulk generation: one run across a whole record set, one document per record
- Change the playbook and every future document follows immediately
Documents are created where your processes run.
Docs is not an editor someone clicks around in — it is a building block of your workflows. Flows generate documents as a process step, assistants on request in chat, your own systems via the API.
- As a flow step: order created → order confirmation generated and sent
- From an assistant: “Build me the quarterly report as PowerPoint” — delivered in chat
- Via REST API from your own applications — using the same playbooks
- Scheduled in bulk: the nightly run across 248 customers, and nobody opens Word
The three formats your business runs on.
Word for contracts and letters, Excel for reports and price lists, PowerPoint for reviews and presentations — each one a native original.
Offers, contracts, cover letters, minutes — with live tables from your data and AI-written prose.
Price lists, analyses, reports — cells, formulas and formatting from the playbook, numbers from the Index.
Quarterly reports, project reviews, management summaries — slides on your master, content from your data.
Every format also ships as PDF — for sending, archiving and anything that must stay immutable.
Six capabilities that keep your documents under control.
Who may generate which documents, from which data, and who generated what when? Docs answers these questions out of the box — with the same platform governance as every other module.
Documents are built only from data the triggering user is allowed to see — inherited from your identity provider.
Fonts, colors, logos and footers come from the playbook — not from whoever hits generate. Every document is on brand.
Every generation is recorded: who, when, which playbook, which data. Every document is traceable.
Add a human review step where it matters: the document waits for sign-off before it leaves the building.
Generated documents land in the platform, structured — findable, linked to their case, searchable by assistants.
Playbooks, templates and documents separated per tenant — one platform, clean boundaries.
Use cases that run on Docs.
Dictate site documentation — finished, compliant reports as documents, every day.
See the use caseAnalyze hundreds of pages — and receive the findings as a finished document.
See the use caseKeep project files structured — and generate reports instead of copy-pasting them together.
See the use caseQuestions about Docs.
- What sets Docs apart from other tools that generate Office files?
- The depth and the direction: Docs commands the full format — tracked changes, comments, charts, styles — and edits existing documents instead of only generating new ones. Plus the platform behind it: live data from the Index, enforced corporate design, and generation from flows, assistants or the API.
- Can we keep using our existing templates?
- Yes. Your corporate templates are the starting point: Docs takes the layout, fonts, colors and footers from them and fills the content from your live data. You rebuild nothing — you define once where which data belongs.
- Where does the data in the documents come from?
- From the Index — the platform's data layer. Prices, line items, customer and master data are available there, current and permission-checked. A document pulls its content at generation time, not from a stale copy.
- What does the AI write — and what stays fixed?
- You decide in the playbook. Structure, tables and mandatory content are fixed and data-bound; prose like summaries or cover letters is written by the AI from the data at hand. Add a human review step before anything is sent, if you want one.
- How does bulk generation work?
- A flow runs across a record set — say 248 customer records — and generates one document per record from the same playbook: personalized, on brand, ready to send. Scheduled, event-driven or triggered manually.
- Can our own systems generate documents too?
- Yes, via the REST API. Your applications call the same playbooks as flows and assistants — one call, one finished document. Permissions and audit logging apply just the same.
Send us your most tedious template.
30 minutes, your document, live: we show you how it becomes a playbook — and generate it in front of you from real data.