This post defines the features we score for Salesforce document generation apps, and how they add up. The shared method (the two axes, the confidence rules and the Enterprise Readiness items) is in How We Compare Salesforce Document Apps. Everything below applies to document generation only.
What counts as document generation
An app belongs in this arena when its main job is turning a template and Salesforce data into a finished document, one at a time or in bulk, and putting that document where it is needed. Forms that collect values for a document, and documents a recipient fills in with answers returned to Salesforce, are part of the job. Neighbouring jobs, such as storing and organising files, reading documents with AI, collecting signatures, approvals and contract lifecycle, are scored in their own arenas; where a generated document is handed to one of them, only the hand-off is scored here. Salesforce's own document generation is scored as an app like any other.
Templates, data, content logic, the output file and where it goes.
Document management, document AI, e-signature and contract lifecycle.
Salesforce's own document generation is scored like any other app.
How the Functionality score works here
Every product is rated on the same eighteen features. Each feature gets one rung on the five-rung ladder, from L1 Absent to L5 Extended, based on the public evidence we find. The Functionality score is the average of those eighteen rungs, weighted by each feature's Kano class: Dial 3, Delighter 2, Dealbreaker 1, Distractor 0. It runs from 1 to 5, like Enterprise Readiness. In this arena that is four Dials, ten Delighters, three Dealbreakers and one Distractor, 35 weight points in all.
The eighteen features follow one generated document from template to delivered file. Template covers how a template is built and kept. Data covers where its values come from. Content Logic covers what is done to that data. Output & Delivery covers the file, where it goes and the record of the run. Salesforce Support covers portals and mobile. Each capability is filed by what it is, not by what it touches, so it is scored once.
Three features matter so much that a product is hard to use without them: reaching the data, repeating line items, and producing a usable file. We check these first, and each must reach L4. A product that falls short is still placed on the matrix, and the gap is stated beside its score.
A product that misses one is still placed, and the gap is stated.
How the Automation score works here
Many teams want documents to generate by themselves when a record is created or changes. Seven features can be automated this way. We rate each on how far it runs through Flow, for admins, and Apex or an API, for developers, then average the seven into a separate score. A built-in trigger with no Flow or Apex route counts as a workaround, and a run started by an AI agent counts as an extra at the top rung.
How rungs are read
- Customer outcome decides the rung, not the mechanism. Logic an admin builds in Salesforce Flow with the app's documented actions counts as the app's capability.
- Workarounds are named and earn no higher rung. Custom Apex, Visualforce, formula fields added to objects, or data copied onto a record only so a template can read it, are workarounds.
- A limit that cuts into a rung's own criteria drops the rung. A limit is only noted when the rung's criteria are still fully met.
- Same-vendor products count. A capability delivered by the vendor's own companion product is scored; licences are noted, not rated.
Enterprise Readiness and Data Reliability here
Enterprise Readiness uses the same thirteen items and weights as every arena. Conference presence, partners and team mix are read at company level for every vendor, so a product sold by a large company is read the same way as one sold by a specialist. In this arena, Data Reliability averages two components, Coverage and Precision, across every item behind the scores.
The features
Grouped into the five categories above. Each card gives the definition, the Kano class and why the feature has it, and whether automation is rated.
Template
Template Authoring Kano · Dial
Building a template: in a familiar editor such as Word, Excel or PowerPoint, in a builder inside Salesforce, or by uploading an existing file, and how easily merge fields are placed. It covers layout elements such as headers, page breaks, tables of contents, hyperlinks and watermarks, starter galleries, and AI that drafts the template itself. Ease of setup is scored here and nowhere else.
- L1 · AbsentNo way to build a template; documents are fixed layouts.
- L2 · WorkaroundTemplates written in code or markup, or built by the vendor as a service.
- L3 · LimitedOne authoring format; or fields, tables and conditions typed as syntax by hand; or only the vendor's own editor, with no add-in for Word, Excel or PowerPoint.
- L4 · CompleteAn add-in inside at least one Office tool that inserts fields, tables and conditions point-and-click across the data model.
- L5 · ExtendedComplete, plus several formats, live preview with real record data, or AI-assisted drafting.
Why a Dial: Every step saved in building and changing templates compounds across the whole library.
Automation: not rated for this feature.
Template Management Kano · Delighter
Keeping the template library in order: folders, versions, cloning, who may edit or use which template, and moving templates between sandbox and production.
- L1 · AbsentTemplates are loose files with no management.
- L2 · WorkaroundManaged only by naming conventions or outside the app.
- L3 · LimitedSome of folders, versions or access control, but not all.
- L4 · CompleteFolders, version history, and access by user, profile or role.
- L5 · ExtendedDeployment between orgs, approval before a template is published, or usage reports.
Why a Delighter: Small teams cope with loose templates; a governed library is valued at scale.
Automation: not rated for this feature.
Data
Data Sources Kano · Dealbreaker
How far from the triggering record a template can reach: its own fields, related and child records, any object by query, and systems outside Salesforce. Data that a customer must first copy onto a record, just so the template can read it, is a workaround and earns no higher rung.
- L1 · AbsentOnly the triggering record's own fields.
- L2 · WorkaroundOther data only by copying it into fields first, through formulas or code.
- L3 · LimitedRelated records one level deep, or a fixed set of objects.
- L4 · CompleteAny standard or custom object, related at several levels, by path or query.
- L5 · ExtendedData from outside Salesforce merged into the same run without first being stored on a record, by any route: connector, Flow, Apex or API.
Why a Dealbreaker: A document that cannot reach the data it needs cannot be generated.
Automation: rated on whether Flow and Apex can pass records, collections or outside data into a run.
Runtime Input Kano · Delighter
Values supplied when a document is generated rather than stored beforehand: a choice of template, options, recipients or typed text, from the person running it or from an outside person through a form that feeds the document.
- L1 · AbsentNo input at run time; every value must already be stored.
- L2 · WorkaroundThe user edits fields on the record before generating.
- L3 · LimitedA fixed prompt, such as template choice only.
- L4 · CompleteConfigurable prompts for values, options and template choice.
- L5 · ExtendedGuided wizards with validation and conditional questions, or forms for outside people whose answers generate the document.
Why a Delighter: Storing values first works; asking at run time saves steps.
Automation: rated on whether Flow and Apex can supply the same inputs with no user.
Content Logic
Conditional Logic Kano · Dial
Showing, hiding or choosing content based on data: sections, clauses, rows and images. A whole template chosen by data is filed here; a template chosen by the user is Runtime Input.
- L1 · AbsentEvery document shows the same content.
- L2 · WorkaroundA separate template for each case.
- L3 · LimitedSimple show or hide on one field.
- L4 · CompleteNested conditions on any field, with AND/OR logic, for any content: text, tables, images, sections.
- L5 · ExtendedComplete, plus conditions on related records, whole templates or documents included by data, or rule sets reused across templates.
Why a Dial: Each extra condition removes a template the team would otherwise maintain.
Automation: not rated for this feature.
Repeating Content Kano · Dealbreaker
Repeating table rows or whole sections for each related record, such as line items, contacts or products. Sorting, filtering and grouping the repeated records live here.
- L1 · AbsentNo repeating content.
- L2 · WorkaroundA fixed number of rows filled from separate fields.
- L3 · LimitedOne table level, with no sorting, filtering or grouping.
- L4 · CompleteTables over any related list, with sorting and filtering.
- L5 · ExtendedNested tables, grouping with subtotals, or whole repeated sections and pages.
Why a Dealbreaker: Quotes, invoices and orders are lists of items; without this there is no document.
Automation: not rated for this feature.
Calculations & Formatting Kano · Dial
Deriving and presenting values: totals and formulas, and number, date, currency and language formatting.
- L1 · AbsentValues printed exactly as stored.
- L2 · WorkaroundCalculated and formatted in formula fields before generating.
- L3 · LimitedBasic formatting, or totals only.
- L4 · CompleteFormulas and totals in the template, with formatting that follows the locale.
- L5 · ExtendedMulti-language templates, translation, or custom functions.
Why a Dial: Every calculation done in the template is one less formula field in the org.
Automation: not rated for this feature.
Rich Media Kano · Delighter
Turning data into visuals: images from records or links, charts, barcodes and QR codes.
- L1 · AbsentText only.
- L2 · WorkaroundStatic images placed in the template.
- L3 · LimitedOne kind of dynamic visual, such as images only.
- L4 · CompleteDynamic images and charts from record data.
- L5 · ExtendedBarcodes, QR codes, signatures or maps as well.
Why a Delighter: Plain documents work; visuals lift the brand and make documents easier to read.
Automation: not rated for this feature.
Output & Delivery
Output Formats Kano · Dealbreaker
The file types produced, and the finishing applied to them. Template features are rated on Word, the main format; gaps in other formats are noted rather than marked down.
- L1 · AbsentNo usable file; output is on screen only.
- L2 · WorkaroundOne format, converted by hand or by another tool.
- L3 · LimitedPDF or Word only.
- L4 · CompletePDF plus the main Office formats, chosen per template or per run.
- L5 · ExtendedPDF extras such as flattened fields, bookmarks or password protection, or HTML and email-body output.
Why a Dealbreaker: A document in a format the recipient can't use has not been delivered.
Automation: rated on whether the output format can be set from Flow and Apex.
Fillable Documents Kano · Delighter
Generated documents that contain fields a recipient fills in, such as text boxes, checkboxes and dropdowns, and whether the answers flow back into Salesforce. Fields a signer fills in inside an e-signature tool are scored in the e-signature arena.
- L1 · AbsentOutput is read-only.
- L2 · WorkaroundFields added afterwards in a PDF editor; answers retyped by hand.
- L3 · LimitedFillable PDF fields, but the answers stay in the file.
- L4 · CompleteFillable fields placed from the template and prefilled from data, with answers written back to Salesforce fields.
- L5 · ExtendedValidation and conditional fields, several fillable formats, or a web-form view of the document.
Why a Delighter: Most documents are read-only; returning answers to Salesforce removes retyping.
Automation: not rated for this feature.
Document Packets Kano · Delighter
Several documents from one run: generated outputs and existing files combined into one file, or delivered together as a set. Which documents join is Conditional Logic; joining them is here.
- L1 · AbsentOne template, one file, always.
- L2 · WorkaroundMerged by hand after generating.
- L3 · LimitedSeveral templates merged, but existing files can't be added.
- L4 · CompleteSeveral templates and existing record files combined in a chosen order.
- L5 · ExtendedConditional packet contents, a table of contents, or page numbers across the whole bundle.
Why a Delighter: Single documents cover most needs; packets win proposals and onboarding.
Automation: rated on whether packets can be assembled from Flow and Apex.
Bulk Generation Kano · Delighter
Generating documents for many records in one run.
- L1 · AbsentOne record at a time.
- L2 · WorkaroundRepeated single runs, or a custom script.
- L3 · LimitedBatches from a list view, with low caps or no progress view.
- L4 · CompleteLarge batches from list views or reports, with progress and error reports.
- L5 · ExtendedScheduled batches, or one merged file across records.
Why a Delighter: Many teams generate one at a time; month-end runs and mailings need batches.
Automation: rated on whether batches can be started and scheduled from Flow and Apex.
Preview & Edit Kano · Dial
Seeing and adjusting a generated document before it is final.
- L1 · AbsentThe file is final as soon as it is made.
- L2 · WorkaroundDownload, edit and upload again.
- L3 · LimitedPreview only, with no editing.
- L4 · CompletePreview and edit inside Salesforce before saving or sending.
- L5 · ExtendedEdits limited to allowed sections, or edits tracked against the template.
Why a Dial: Each fix made in place, rather than by generating again, saves time on every document.
Automation: not rated for this feature.
Save & Write-back Kano · Delighter
Where the finished file is kept, under what name, and what is written back to the record. Managing the storage itself is scored in the document management arena.
- L1 · AbsentDownload only; nothing is saved.
- L2 · WorkaroundThe user attaches the file to the record by hand.
- L3 · LimitedSaved to the record, with no choice of place or name.
- L4 · CompleteSaved to the record or Salesforce Files with naming rules, plus field updates.
- L5 · ExtendedSaved to external storage, or full status written back, such as generated date and version.
Why a Delighter: Download and attach works; automatic filing keeps records complete.
Automation: rated on whether the save location and write-back can be set from Flow and Apex.
Send & Hand-off Kano · Delighter
Sending the finished document on: by email or SMS, to an e-signature tool, to print and post, or to a later workflow. Only the hand-off is scored; signing is its own arena.
- L1 · AbsentThe user sends the file themselves.
- L2 · WorkaroundDownload, then send or upload elsewhere.
- L3 · LimitedEmail only, or one e-signature tool.
- L4 · CompleteEmail with templates, and a choice of e-signature tools.
- L5 · ExtendedSigner fields placed from the template, other channels such as SMS or print and post, or later workflows.
Why a Delighter: Sending by hand works; one-step hand-off is felt every day.
Automation: rated on whether sending can be triggered from Flow and Apex.
Run History Kano · Delighter
The record of what was generated: who ran it, when, for which records and with what result, plus usage reports and error logs.
- L1 · AbsentNo record of runs beyond the files themselves.
- L2 · WorkaroundInferred from file dates or Salesforce debug logs.
- L3 · LimitedA status on batch jobs only, or errors only.
- L4 · CompleteA log of every run with user, record, template, result and error detail.
- L5 · ExtendedUsage dashboards, exportable audit reports, or retry from the log.
Why a Delighter: Teams get by on the files themselves; a run log is valued for audits and support.
Automation: not rated for this feature.
Salesforce Support
Experience Cloud Support Kano · Delighter
Whether portal users can generate documents, and how much they can do. Licences are noted, not rated.
- L1 · AbsentInternal users only.
- L2 · WorkaroundDocuments generated internally and shared to the portal.
- L3 · LimitedPortal generation with limited templates, access or features.
- L4 · CompletePortal users generate and download from allowed templates.
- L5 · ExtendedPortal users also choose options, preview, or send for signature.
Why a Delighter: Portals open uses the core job doesn't cover.
Automation: not rated for this feature.
Mobile Compatibility Kano · Distractor
Whether documents can be generated in the Salesforce mobile app, on a layout built for phones. Where the documentation says nothing about mobile, the feature is rated Absent.
- L1 · AbsentNothing appears in the Salesforce mobile app.
- L2 · WorkaroundGenerated only through a browser or another app.
- L3 · LimitedAppears but reduced: a layout not built for mobile, or only some actions.
- L4 · CompleteGenerate, preview and save on a layout built for mobile.
- L5 · ExtendedMobile-only extras such as camera input, offline drafts or bulk actions.
Why a Distractor: Few teams generate documents on a phone, so it rarely changes a choice.
Automation: not rated for this feature.
When this list changes
Features are added or reclassified through the same Kano test, and every change is dated here. The current list of eighteen was set on 4 November 2026.