Official sources reviewed
| Primary source | What it establishes | Review date |
|---|---|---|
| Microsoft Word Open XML documentation | Native Word document structure context used for the workflow discussion. | 2026-07-22 |
What this decision is actually about
The legal-tech opportunity is not just generating Word files. It is replacing the fragmented workflow where one system drafts, another compares, and a third handles accessibility or conversion.
Evaluation prompts—not a feature scorecard
| Alternative boundary | Confirm the supported input, deployment, and output behavior in the official source above using your current version. |
| PaperJSX boundary | Prove one real artifact locally first; local package behavior does not imply hosted access. |
| Delivery decision | Test the native file, recipient handoff, and release check that matter in your product. |
When PaperJSX is the better fit
PaperJSX is strongest when legal-tech teams want one programmable surface for document generation, comparison, tracked changes, accessibility, and downstream export instead of stitching multiple seat-based products together.
When fragmented legal-doc stacks is the better fit
If the organization only needs a narrow slice of document automation and has deeply entrenched review software, the existing stack may be sufficient for now.
Cost of choosing PaperJSX
PaperJSX is newer than dedicated legal-tech incumbents. Teams whose core requirement is specialized desktop legal review — not programmable document automation — may not need the platform yet.
Evaluate the file your customer receives.
Bring one real payload, its expected file, and the release check you cannot miss. Pro and Platform are self-serve; contact us when the evaluation requires Enterprise terms or architecture review.