Documents, diagrams and tables for teams that work with AI
Delta Flow is a workspace for the documents a company runs on — processes, policies, price lists. You write like in Word, an AI agent drafts and edits beside you, and every change — yours, a colleague’s or the agent’s — stays marked in the text until someone accepts it. Nothing reaches the approved version unseen.
Policy_final_v7.docx
Versions travel by e-mail and nobody is quite sure which one is in force.
“What exactly did the AI rewrite?”
A chatbot hands back a whole new text. You look for the differences by eye, paragraph by paragraph.
“Who approved this — and why?”
The change stayed in the document. The reason for it got lost in somebody’s inbox.
What it does
Every picture below is the real application showing an example project — the documentation of Nordwind, a fictional chain of bicycle shops. Click a picture to see it full size.
01Editor
Headings, lists, tables, pictures and pages in A4 — with no syntax to learn. Underneath, every document is a plain Markdown file, so your documentation is never locked inside one program.
02Tracked changes
What was added is green, what was reworded is amber, what was removed is red. A card beside the paragraph shows the old wording and the new; one click accepts it, one rejects it.
03AI agent
Ask in plain words: shorten the deadlines to match the new policy, add the escalation step, draw the process. The agent reads the project, edits the documents and says what it did. Its edits arrive as tracked changes like anybody else’s — with a note on why.
04Approval
Work happens in a draft. The approved version is read-only and changes in exactly one way: a draft is reviewed and published into it. One list shows everything the draft changes, and a summary says it in words.
05Diagrams
BPMN process diagrams have an editor of their own; Mermaid diagrams live right inside a document. The agent can draw one from a description.
06Tables
A price list or a budget is a table with formulas — still part of the documentation, still under tracked changes. The same table opens as a full spreadsheet.
07History
Every saved state is kept. Open an earlier version, see what has changed since and who changed it, and restore it when needed.
08Notes
Attach a note to a sentence, reply, resolve. The agent leaves notes as well — its reasoning stays next to the change it made.
How it works
The approved version is the line everybody relies on. Changes happen beside it, in a draft, and come back only after somebody has looked at them.
Drop in Word and PDF files — they turn into editable documents, pictures included. Or start from an empty page.
One click. The draft is your working copy of the project; the approved version stays as it is, read-only, for everyone who relies on it.
You, your colleagues in the same document at the same moment, and the agent you ask for help. Everything saves itself.
Go through the changes where they happened. Accept, reject, add a note — or ask a colleague to approve.
The draft becomes the new approved version. The history remembers who changed what and why; export to Word whenever somebody needs a file.
Also inside
Several people in one document at once. You see each other’s cursors and nobody overwrites anybody.
Drag a .docx or .pdf in — text, tables and pictures come along as an editable document.
Company letterhead, fonts and styles, without reformatting by hand.
A read-only public link for a customer or an auditor. You can revoke it at any time.
Full text across the whole project — with or without diacritics — and find inside a document.
Authorship for every line of a document: who last changed it, and when.
Everywhere
Light and dark, ten colour schemes, and a layout made for the tablet and the phone — to read, review and approve away from the desk.
Under the hood
The tool software teams have trusted for twenty years to keep track of every change does the same job here for your documents — behind buttons named in plain words.
Markdown, BPMN, pictures — in a git repository per project. No proprietary format and nothing to migrate out of.
The words are everyday ones, the mechanics are the proven ones: a draft is a branch, the approved version is the main branch, publishing is a merge request.
Nobody edits it directly — not a person, not the agent. It changes only when a draft is published.
Accounts are created by invitation and see only the projects they have been given.
The agent runs on the AI account your company connects — OpenAI Codex, Claude or GitHub Copilot.
The service runs in a data centre in Frankfurt.
Pricing
There is no public price list. Write to me, tell me how many people will work with the documents, and I will send you an offer — and show you Delta Flow on your own documents.
Questions
No. You write in a visual editor and press buttons named in plain words — draft, accept, publish. Markdown and git are how the documents are stored, which matters on the day you want to take them somewhere else.
Only the draft it was asked to work in. Its edits appear as tracked changes that you accept or reject, and the approved version changes only when a person publishes the draft.
The agent runs through OpenAI Codex, Claude or GitHub Copilot, on an account your company connects. You choose which one for each conversation.
At any time. Export to Word (into your own template too), print to PDF, or take the whole git repository — it is plain files.
No. It suits anything that is mostly text and changes over time: policies, manuals, specifications, price lists, contract templates, meeting records.
Accounts are created by invitation. If your company already works in Delta Flow, sign in. If not, write to me and I will show you around.
