Word · .docx
Proposals, statements of work, contracts, HR letters, internal policy. Native Open XML output that opens cleanly in Microsoft Word and LibreOffice.
Product C · Document & Template Cloud
Every document, on brand, on policy, on demand.
Your sales proposals, statements of work, policy documents, board decks, and compliance forms — all generated from a single governed template library that Marketing, Legal, and IT actually agree on. Hand the finished document off to Agreements & E-Sign when it needs a signature.
Book a demoOne template library, every surface
PowerPoint · .pptx
Board decks, pitch decks, customer reviews. Slide masters and brand themes enforced; placeholder text replaced from your data.
Excel · .xlsx
Quote sheets, pricing calculators, audit-ready exports. Named ranges, formulas, and table styles preserved through the render.
Print-ready, accessibility-tagged PDF/A output for archive and submission. Optional PAdES-ready signature placeholders when the next step is e-sign.
What's in the box
Governed template library
A single authoritative source for every customer-facing or compliance-grade document your business produces. Versions, approvals, and audit logs on every change.
Brand & clause primitives
Logo, fonts, colours, voice. Pre-approved clause snippets with effective dates and per-jurisdiction variants. Templates draw from the same library that drives email signatures and signing UIs — no drift.
Office task-pane add-in
Authors work in Word, PowerPoint, and Excel where they already live. The tawqi3 task pane surfaces approved content, real-time validation, and one-click submit for review.
Programmatic render
A merge-data API renders documents from your CRM, ERP, or HR system. Idempotent, signed-URL retrieval, audit-anchored. Webhooks on completion.
Policy enforcement
Required sections, banned phrases, jurisdiction-specific footers, approval gates, classification labels. Policy is data, not a Word macro.
Hand-off to E-Sign
One click promotes a generated document into an Agreements & E-Sign envelope — with a correlation ID and audit record naming the source template. Hard A/B/C boundary preserved.
Why a third product, and not a feature inside the other two?
Generating a contract is fundamentally different from signing one. Different reviewers, different lifecycle, different storage. Different keys, different audit trail.
- Separate trust boundary. Templates and rendered documents have distinct encryption keys and distinct audit Merkle roots from completed agreements.
- Different audience. Marketing and Legal own the template library; Sales and HR consume it; Operations governs the change pipeline.
- Reusable surface. Both Email Signature Cloud (banner assets, clause snippets) and Agreements & E-Sign (template-driven envelopes) consume Product C as an upstream primitive.
- Predictable cost. Pay for what you generate, not for what you sign. Pick any non-empty subset of A, B, and C at signup.