Developers
Built to scale with Salesforce.
Keep business context in Salesforce and run document rendering in dedicated services. Connect standard and custom objects, scale generation capacity independently, and return document status and links to the records your teams use.
- Proposals
- Agreements
- Statements of work
- Schedules
- Renewal packages
A clear path from CRM data to document
Separate business rules, rendering, and storage so each part can scale with its workload.
Start in Salesforce
Use record actions, automation, or scheduled runs to initiate generation. Salesforce supplies customer, product, and project context and determines the configured document set.
Assemble the data
Map standard and custom objects, related records, and assets into the template. Each data table’s SOQL query runs once per generation, with results reused during rendering.
Render outside the CRM
Dedicated generation services merge data, evaluate conditional content, and render documents concurrently. Rendering capacity can grow independently of Salesforce resources.
Store and synchronize
Store generated files in customer-managed object storage, including Amazon S3. Write document metadata, links, and status back to Salesforce for the next workflow step.
Design for the production workload
One published customer deployment processes 21,500+ documents a day with a 1.1-second average generation time. Use your templates and data to establish your own baseline.
- Evaluate individual request latency and concurrent throughput separately
- Test related-record counts, images, conditional content, and package size
- Plan rendering capacity and storage for peak demand
Give each team clear ownership
Keep integration and deployment decisions with engineering while template authors maintain document language.
- Map Salesforce objects, queries, triggers, and downstream workflows
- Define storage access, region, encryption, and retention for the deployment
- Let authors update Word templates and preview against Salesforce records
Common questions
Explore the tools behind your workflow.
Does rendering run inside Salesforce?
Document rendering runs in dedicated services outside Salesforce. Salesforce holds the business context, initiates configured workflows, and receives document metadata and status. CRM queries and automation still need to be designed around the limits of your Salesforce environment.
Can we use custom objects and related records?
Yes. Templates can use standard and custom Salesforce objects, related-record tables, and conditional content. Map the queries and record relationships to your data model, then preview with representative records before rollout.
What affects generation performance?
Performance depends on data retrieval, document length, images, conditional content, package size, and concurrency. The published customer figures describe that deployment, not a universal latency guarantee. Benchmark your own workload and distinguish rendering time from the full request-to-delivery cycle.
What should we review before production?
Review the data model, generation triggers, expected peak volume, storage configuration, and Salesforce status updates. Agree on failure handling, monitoring, and downstream handoffs for your integration, then validate representative documents and concurrent requests.
Walk through your architecture
Bring your Salesforce data model, a template, and expected volume. We’ll review the generation flow and plan a representative performance test.