Formstack Documents consulting and implementation for Salesforce teams

Six phases: discovery and current-state assessment, solution architecture, configuration and template build, Salesforce integration and automation, testing and training, then support and optimization. The work that decides whether it succeeds is the middle two — mapping merge fields to the right objects and relationships, and designing where generation is triggered from. Installing the managed package takes minutes; making it produce the right document from the right data is the project.

It is driven by three things: how many templates you need, how complex the conditional logic inside them is, and how clean the Salesforce data behind them is. A single document generated from one object is a short engagement. Thirty templates with jurisdiction-specific clauses, child-record tables and bulk generation is a different project entirely. We establish all three in phase one and quote against the actual inventory rather than an assumed one — which is also why we will not give a timeline before seeing your documents.

Configuration covers merge mapping from primary and child objects, conditional logic and formatting modifiers inside the template, looping over child records, and generating from a button, a Flow or a list view. Custom development starts when data selection goes beyond what point-and-click mapping can express and needs SOQL-based mappings, when several unrelated objects must be assembled into one package in a defined order, when thousands of documents run on a schedule with retry and alerting, or when routing depends on rules spanning multiple objects. We agree that boundary in writing before work starts.

That is a large share of the work we do. The common failures are template sprawl where conditional logic should have been used, merge mappings that break when a Salesforce field is renamed, trigger logic buried in places nobody can find, and no error handling when a merge fails silently. We audit the existing setup, consolidate the templates, repair and document the mappings, move trigger logic into Salesforce Flow where it belongs, and add error handling — usually without starting again.

Yes. The managed package includes buttons to generate documents from a Salesforce list view, and Formstack offers a High-Volume Generation mode built for large runs and complex mappings. It is not designed for the opposite case — a single document merging thousands of related records — and it does not support file retrieval, so a mapping that includes files falls back to standard batch processing. Designing which mode each use case runs in, and what happens when a run partially fails, is part of the implementation rather than an afterthought.

Formstack Documents fits well when business users need to maintain templates in Word, PDF, PowerPoint or Excel, when you need several output formats, and when documents must reach many destinations. A fully Salesforce-native tool is the better answer when data-residency or security rules require generation to happen inside your org, and a simple native build can be enough for a low-volume document whose layout never changes. We implement more than one of these and will say which fits your requirement, including when the answer is not Formstack Documents.

Intellistack is the company; Formstack Documents is the product. In June 2025 the company behind Formstack renamed itself Intellistack and relocated its headquarters to Denver, while keeping the Formstack product brand in place. The application you install from the Salesforce AppExchange is still Formstack Documents, and the Salesforce package is still Documents for Salesforce. If you have seen both names and assumed the product was discontinued or replaced, it was not.