[DESIGN PARTNER PROGRAM]
Build evidence with customers, not on their behalf.
The program is for teams with a recurring native-document workflow and a representative fixture they can evaluate. Participation does not imply endorsement or permission to publish a case study.
NO PUBLIC LOGOS BY DEFAULTWRITTEN APPROVALCUSTOMER-VERIFIED OUTCOMES
Evaluation workflow.
- Define the baseline. Record the input, current process, review time, failure modes, and acceptance criteria before implementation.
- Run a bounded pilot. Use representative files and versioned PaperJSX artifacts. Keep customer data out of public fixtures unless explicitly approved.
- Capture observed evidence. Record dates, engine versions, sample size, validation method, exceptions, and the customer owner who can verify each result.
- Review the case-study draft. Separate measured facts from estimates and qualitative comments. Give the customer the complete draft and all proposed quotations.
- Publish only with written approval. Approval must cover company name, logo, quotes, metrics, artifacts, channels, and an expiry or revocation process.
Case-study evidence record.
| Field | Required capture |
|---|---|
| Workflow | Format, frequency, audience, current toolchain, and human-review boundary. |
| Baseline | Dated measurement method, sample size, exclusions, and source owner. |
| Intervention | PaperJSX versions, template/input scope, implementation effort, and other changes. |
| Outcome | Observed measurement with period and caveats; no extrapolated percentage presented as fact. |
| Approval | Named customer approver, approved copy/assets, channels, date, and withdrawal contact. |
Bring one representative workflow.
The first conversation establishes fit and evidence boundaries; it does not create a public customer claim.