Document automation software features, named for the buyer.
A feature list made for the buyer evaluating document automation software. Admin controls, template library, variable catalog, approval chain, e-signature, audit, open API, and the compliance posture mapped to the questions security review asks on week two of the evaluation.
Document automation evaluations miss the admin surface most often. Templates, variables, and signature grab the demo attention; the admin controls that keep the system working on day 500 get the one-slide fly-by. The nine features below are the ones that matter for the admin role and the ones most teams end up configuring in month three.
Template library
The catalog, with versioning.
The admin maintains a library of templates with explicit metadata: owner, version, status (draft, active, archived), description. The library is searchable, taggable (by document type, by region, by product line), and auditable. Templates have a lifecycle (draft, active, archived) parallel to the deal-lifecycle so retired templates do not sprawl.
Variable catalog
Every placeholder named and typed.
The variable catalog names every placeholder with an explicit type (text, currency, date, boolean, record reference). The catalog is tenant-wide so a variable called “effective_date” means the same thing across every template that references it. Rename is a tracked change with a one-step apply across all referencing templates.
Clause library
Reusable blocks of language.
The clause library stores reusable blocks (indemnity, governing law, data processing addendum) that templates reference by name. Edit a clause once and every referencing template picks up the change on the next generation. The pattern replaces the “find and replace across twelve templates” ritual that every legal team hates.
Approval chain config
The reviewer sequence, tenant-defined.
The admin configures the approval chain per template: who reviews, in what order, with what conditions. The chain supports sequential (legal, then CFO, then CEO), parallel (any two of three), and conditional (only CFO if deal value is above a threshold). The configuration is in the admin UI, not a settings JSON file, so the legal lead can tune it without filing a ticket.
Permission model
Who can edit, generate, send, sign.
Document permissions mirror the Strkr permission model. The admin defines who can edit templates, who can generate documents, who can send for signature, and who can sign. The role model is auditable and inherits from the tenant's standard role tree so a new user automatically gets the right document permissions based on their role assignment.
Audit log
Immutable, exportable, searchable.
Every edit, generation, approval, and signature logs with the actor, time, and before-after state. The log is immutable and exportable in standard formats (CSV, JSON) for compliance review. Audit retention is configurable per tenant to match regulatory requirements.
SLA config
How long each stage can sit.
The admin sets the SLA per stage per template. Internal legal review: 48 hours. Counterparty review: five business days. Signature: 72 hours. The clock runs on every document, surfaces yellow at 50 percent, red at 100 percent, and escalates on breach. The configuration is per-template so a renewal letter can run a tight SLA while an enterprise MSA runs a loose one.
Notification routing
Who gets notified, on what surface.
The admin configures the notification surface per reviewer: email for most, Slack for product teams on the native Slack integration, Teams for Microsoft shops, Strkr's notification center for everyone. The pattern prevents the “I did not know this was waiting for me” that stalls documents for days.
Delegation rules
Out-of-office handoffs, honored.
The admin configures the delegation pattern: automatic (based on each reviewer's OOO calendar) or explicit (reviewer sets their own substitute). The delegation is logged, the document keeps moving, and the audit trail is explicit about which reviewer actually approved what. The pattern prevents the “the senior counsel is on vacation and six contracts are stuck” problem.
The end-user feature set
What the person generating the document actually sees.
End-user features determine whether the system gets used. If generating a document takes six clicks, reps route around the system. If it takes two, adoption sticks. The seven features below are the ones that matter for the day-to-day user.
One-click generate
From a deal, in two clicks.
A rep opens a deal, clicks “generate document,” picks the template, and the document is ready. The variable substitution happens automatically from the deal and account data. For simple templates with no manual variables, the pattern takes under five seconds. For complex templates, the rep fills in the manual fields and clicks generate.
Smart defaults
The right template is pre-suggested.
When the rep opens the generate dialog, the system suggests the most likely template based on the deal stage, account segment, and recent template usage. A new-business deal in the current quarter suggests the current MSA. A renewal in the services arm suggests the services renewal. The pattern reduces template-browse time and prevents the wrong-template mistake.
Draft mode
Save a work-in-progress.
The rep can save a draft mid-process, come back the next day, and continue. The draft carries the current variable values and editor state. The pattern lets reps work complex deals across multiple sessions without starting from a blank template each morning.
Preview before send
A full-fidelity preview, one click.
Before send, the rep previews the final document (fully substituted, conditional logic applied, exhibits attached). The preview shows exactly what the counterparty will see. The pattern catches the mis-rendered dollar amount, the wrong exhibit, or the missing clause before the counterparty opens the attachment.
Status visibility
Where the document is, right now.
The rep sees the current stage of every open document on their deal: draft, internal review, counterparty review, redline, signature, archived. The surface is a stage pill on the deal and a status card in the user's own documents page. The pattern replaces the “where is my contract” email thread.
Shared link
A URL the counterparty opens.
The rep sends the document as a shared link rather than an email attachment. The link opens in the counterparty's browser, tracks every open, and shows the current version. The pattern replaces the “I think I sent them v3 last week” version drift that fragments contract negotiations across inboxes.
Mobile-friendly
Review and approve on the phone.
Reviewers can approve documents from the phone. The mobile view shows the full document with a prominent approve-or-request-changes button. The pattern catches the “I am traveling, I will approve when I get back” delay that stalls documents for days during conference season.
Comment thread
Clarifying questions, in-place.
Every document has a comment thread so reviewers can mark up specific sections without edit rights. The thread travels with the document into the signature stage. The pattern replaces the “download, mark up in Word, email back” cycle that fragments reviews across inboxes.
Templated email
The cover message, pre-filled.
When the rep sends the document for counterparty review or signature, the cover email pre-fills with a template that includes the signer name, the deal context, and the next-step ask. The pattern prevents the “I am sending you the contract” email that lacks any detail and extends the review time.
The integration feature set
What the system connects to, out of the box.
Document automation lives inside a larger stack. The integrations below are the ones that matter and the ones Strkr ships in the box rather than through a middleware vendor.
E-signature
DocuSign and PandaDoc, deeply.
Strkr integrates with DocuSign and PandaDoc for the signature leg. The integration passes the document, signer identity, and consent record into the signature vendor, retrieves the signed PDF with the signature certificate, and logs the signature event in the Strkr audit trail. Signatures captured this way are legally binding under the US ESIGN Act and the Uniform Electronic Transactions Act.
CRM data
The native Strkr CRM, no sync.
The document system reads CRM data (accounts, contacts, deals, products, custom fields) natively because it lives inside the same database as the CRM. There is no sync job, no middleware, no scheduled refresh. A deal update at 10 AM is reflected in the document generation at 10:01 AM.
Storage integration
SharePoint, Google Drive, S3.
Signed documents can route to a chosen storage destination: SharePoint folder for Microsoft shops, Google Drive for Google Workspace tenants, S3 bucket for teams running custom pipelines. The routing is per-template so a sales MSA archives to legal's folder while a renewal letter archives to the CSM team folder.
Billing integration
A signed order form triggers a Stripe invoice.
For teams running Stripe for billing, a signed order form can trigger an invoice automatically. The pattern eliminates the “finance has to transcribe the signed order into billing” step that extends the quote-to-cash cycle by a week. The integration respects the invoice approval chain so no auto-invoice ships without a human sign-off where policy requires.
Slack and Teams
Approval notifications where teams work.
Approval notifications land in Slack (via the native Strkr Slack integration) or Teams (via the Microsoft 365 integration) depending on the tenant's configuration. The reviewer can approve or request changes directly from the notification without opening the CRM. The pattern collapses the typical 15-minute review ritual into a 90-second tap.
Open API
Every surface in the public API.
Every feature in the admin and end-user surfaces is accessible through documented public API endpoints. A customer who wants to generate documents from a parallel system (billing engine, product app, custom portal) can do so with a documented call. The pattern is important for teams building a document-generation surface outside the CRM.
The compliance feature set
What security review will ask about.
Compliance review is where document automation evaluations stall. The posture below is explicit so the security lead can hand it to legal on day one.
HIPAA
Compliant, BAA available.
Strkr is HIPAA compliant and executes a Business Associate Agreement on request. Documents containing PHI respect the field-level mask on variables, the audit log retains access context for the regulated window, and generated PDFs stay inside the BAA scope.
SOC 2 Type II
In progress through 2026-Q4.
Strkr is actively pursuing SOC 2 Type II with report completion targeted through 2026-Q4. The template editor, generation pipeline, approval chain, signature integration, and audit log are all in scope. Interim artifacts are available under NDA.
GDPR
EU residency, SCCs on file.
Strkr is GDPR compliant with Standard Contractual Clauses in the standard contract and an EU-hosted path for EU tenants. Documents generated for EU tenants stay in the EU region, which honors the residency contract important for GDPR and sector-specific regulations.
CCPA
Consumer rights honored.
Strkr honors CCPA data-subject rights across the document surface. A deletion request removes the subject's data from generated documents (or scrubs the identifying variables, per tenant policy) within the regulatory window.
Signature validity
ESIGN and UETA compliant.
Electronic signatures captured through the Strkr integration are legally binding under the US ESIGN Act and the Uniform Electronic Transactions Act. The signature certificate includes the signer identity, timestamp, IP, consent record, and document hash. The pattern meets the legal bar in every US state.
Immutable audit
Nothing can be edited post-hoc.
The audit log is immutable: no admin, no engineer, nobody can edit a logged event. The retention is configurable per tenant (default seven years for regulated-industry tenants, three years for standard tenants). Compliance reviewers get the one-query reconstruction they need, which keeps the audit sampling ritual tractable.
The pricing feature
The honest line on what the software costs.
Document automation vendors routinely price features as separate SKUs. The posture below is explicit so the buyer can defend the budget line on day one.
Seat-priced
Included on every paid tier.
The document automation feature set ships on every paid Strkr tier. There is no “Documents Edition” or “Automation Pack” upsell. The seat price includes templates, variables, conditional logic, approvals, audit log, versioning, bulk generation, and the open API. Signature usage flows through DocuSign or PandaDoc under the tenant's own vendor contract.
No per-document cost
Generate as many as you need.
There is no per-document generation surcharge. A team generating ten documents a day costs the same as one generating a thousand. The pricing design encourages adoption rather than negotiating against it, which is the opposite of the per-document pricing some competitors ship.
Transparent pricing
The seat price on the public page.
The seat price for every tier is on the public pricing page. There is no “contact sales” opaque pricing for the document feature set. The number for the seat is the number for the documents feature. No bespoke pricing by company size and no willingness-to-pay bidding.
Open API included
No separate developer tier.
The open API is included in every paid tier. There is no “Developer Edition” or “API Premium” upsell. Teams building a document-generation surface outside the CRM pay the seat price for the admin who maintains the integration, not a separate API line.
No credit meter
No per-API-call surcharge.
API calls are not metered. A team running 100,000 generations per month through the API costs the same as one running 1,000. The design is intentional: metered pricing encourages architectural distortions to minimize cost, which is the wrong incentive for a document system.
No add-on signature
Signature via tenant's own vendor.
Strkr does not run a native e-signature SKU. Signature flows through the tenant's existing DocuSign or PandaDoc contract. The pattern lets teams keep the signature vendor they already standardized on without a parallel subscription from the CRM provider. For teams without a signature vendor, Strkr can refer the shortlist.
Admin, end-user, integration, compliance, pricing: the full software surface, inside the CRM.
Document automation ships on every paid Strkr tier. Templates, variables, conditional logic, approvals, e-signature integration, audit log, versioning, bulk generation, and open API are first-party. No per-document surcharge, no credit meter, no add-on SKU. Start a trial and configure your first template library before the end of the week.
What are the main features of Strkr's document automation software?
The admin surface ships a template library with versioning, a variable catalog with explicit types, a clause library of reusable language blocks, a configurable approval chain, a permission model that mirrors the CRM, an immutable audit log, per-stage SLA configuration, notification routing per surface, and delegation rules. The end-user surface ships one-click generation from the deal, smart template defaults, draft mode, full-fidelity preview, status visibility, shared-link counterparty review, mobile-friendly review, in-place comment thread, and templated cover email.
Does Strkr's document automation integrate with DocuSign or PandaDoc?
Yes. Strkr integrates with DocuSign and PandaDoc for the signature leg of the lifecycle. The integration passes the document, signer identity, and consent record into the signature vendor, retrieves the signed PDF with the signature certificate, and logs the signature event in the Strkr audit trail. Signatures captured this way are legally binding under the US ESIGN Act and the Uniform Electronic Transactions Act. Teams keep the signature vendor they already standardized on without a parallel subscription from the CRM provider.
Is there a per-document generation cost?
No. There is no per-document generation surcharge. A team generating ten documents a day costs the same as one generating a thousand. The pricing design encourages adoption rather than negotiating against it, which is the opposite of the per-document pricing some competitors ship. API calls are also not metered: a team running 100,000 generations per month through the API costs the same as one running 1,000.
How does the approval chain work for complex organizations?
The admin configures the approval chain per template with sequential (legal, then CFO, then CEO), parallel (any two of three), or conditional (only CFO if deal value is above a threshold) logic. Each reviewer gets a notification on the surface they use (email, Slack, Teams, Strkr's notification center) and can approve or request changes from the notification. Delegation handles out-of-office. Conditional reviewers route high-value documents to executive review automatically. The configuration is in the admin UI, not a settings file, so the legal lead can tune it without filing a ticket.
Is the document automation software HIPAA, SOC 2, and GDPR compliant?
Strkr is HIPAA compliant with a BAA available on request, GDPR compliant with Standard Contractual Clauses on file and an EU-hosted path for EU tenants, and actively pursuing SOC 2 Type II with report completion targeted through 2026-Q4. The template editor, generation pipeline, approval chain, signature integration, and audit log are all in scope. The audit log is immutable, and retention is configurable per tenant (default seven years for regulated-industry tenants, three years for standard tenants).
Can I generate documents from a system outside the CRM via the API?
Yes. Every surface (template editor, variable catalog, generation endpoint, approval event, signature event) is exposed through documented public API endpoints. A customer who wants to generate documents from a parallel system (billing engine, product app, custom portal) can do so with a documented call. The pattern is important for teams building a document-generation surface outside the CRM. The open API is included in every paid tier with no separate developer SKU and no per-call metering.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
