The shift starts with recurring work
A single datasheet, brochure or catalogue page is not the issue. The issue is the same document logic, executed again and again: a new product variant, a price change, a market-specific version, a regulatory update. Each instance looks like a one-off task. Together, they form a pattern that manual production was never designed to carry.
That pattern is easy to miss from inside the work. A designer updates one file. A marketer copies a template. A local team adjusts a paragraph. None of these steps look like a bottleneck on their own. The bottleneck appears only once someone tries to trace how many times the same document has been rebuilt this quarter.
The shift begins when document creation stops being occasional work and becomes a recurring operating process.
Why templates stop being enough
Templates solve layout. They do not solve data, exceptions, review or distribution — the four things that actually determine how long a document takes to produce.
| Manual production | Configured flow | |
|---|---|---|
| Data | Copied and re-entered per document | Pulled from approved sources |
| Exceptions | Handled ad hoc, case by case | Defined once, applied consistently |
| Review | Repeated for every version | Built into the process |
| Distribution | Manual per market or channel | Routed according to configured rules |
A well-built template still needs someone to open it, populate it correctly and check the result. As the number of variants grows, that person becomes the constraint — regardless of how good the template is.
What changes when documents become system output
The shift is not about removing people from the process. It is about removing the parts of the process that depend on someone remembering the rules. Source data, templates, business rules, review steps and delivery destinations move from separate manual actions into a single configured flow. Someone still decides what the rules are and still reviews the output. What changes is that the same document no longer has to be rebuilt by hand every time the underlying data changes.
Where Pulse fits
2imagine Pulse connects approved data, templates, business rules, review steps and delivery destinations in a controlled document workflow. Pulse brings together relevant data and assets from PIM, ERP, DAM, CMS, Excel and CSV sources, and applies the configured templates, rules and workflow steps needed to produce and deliver the required documents.
Two things stay unchanged by design. Human review remains part of the process wherever the organisation wants it. And Pulse does not guarantee regulatory compliance on its own — configured rules and approved content reduce manual error, but the responsibility for what is legally correct still sits with the organisation.
Generation works within configured templates, mappings and rules. Structural changes to data, mappings or document logic may require configuration updates.
This is the same logic behind why catalogue production breaks at scale: a small number of connected steps replacing a growing number of manual ones. A short walkthrough of that idea in practice is available in 2imagine Pulse in 20 Seconds.
Identify where recurring document work should become a flow
Follow one recurring document from source update to final delivery. That shows which steps still depend on copying, manual layout, repeated checking or individual knowledge.
When the operating model needs to change
A few signals tend to appear before teams decide to act:
- The same document type is rebuilt from scratch for every market or language.
- Updates require touching several files that are supposed to stay in sync.
- No one can say with confidence which version is currently live.
- Review happens after production, not as part of it.
None of these signals mean the current process is wrong. They mean it has reached the volume of repetition it was not built to handle. At that point, the question is no longer whether to automate one more template — it is whether document creation should run as a configured flow instead.