Studio is where a document gets its shape: you drag the fields onto the page and the template is done — no ticket, no release. From then on it is a token, and whoever needs the document asks for it: a Workflow step, an Intelligence agent, or a line of your own code. It also holds the OCR templates for the documents coming the other way, and those you set up by describing them out loud.
The work happens once, on the left, and there is a person doing it. Everything to the right of the token runs without anyone opening the template again — which is why one afternoon of dragging fields holds up at over two million pages a month.
The layout lives inside the code, so changing it is a change to the code: somebody writes the request, somebody else picks it up, it gets tested, it gets released. Moving a line two centimetres and adding a whole new clause cost the same — which is the part nobody believes until they ask for it.
The same page, with the fields dragged where they belong. You save it, and the next call already comes back with the new layout: there is nothing to deploy because nothing changed in the code. The person who knows what the document should say is the one who moves the line.
A document can be asked for by a process that reached that step, by an agent that has just finished writing it, by your own code, or by a service that runs at night. All four get the same document back, because all four are asking the same template — there is no such thing as the Workflow version.
Workflow and Intelligence are not calling in from outside: the integration is native, so a step or an agent picks the template off a list instead of carrying a token around.
Six pieces. Two of them write documents, one reads them, and the other three are what you end up needing once the first three are running at scale.
The canvas: the page exactly as it will print, with the fields dragged onto it. Whatever the call sends is what lands in each box.
The same thing for documents that have to stay editable after they come out. A contract somebody is still going to redline is not a PDF.
Every document that came out, with its token. You do not have to keep what you generated: ask for it again by token and it is there.
Templates for reading instead of writing. You describe out loud what the document has and where it is — Intelligence turns that into the template — and from then on it is another call to the service.
How many pages, from which template, asked by whom. At two million a month, an integration that went into a loop is not something you catch by eye.
The endpoints, the token and one call that works, to copy and paste. It lives here and not in a manual somewhere else because whoever is integrating is already logged in.
The policy, the certificate, the statement — the one where moving a line means opening a ticket. Send us the layout and we will draw it in Studio, and hand it back filled in the same meeting.
Talk to us