Formstack by Intellistack collects the data, generates the document and routes it for signature without anyone re-keying a field. Twopir Consulting implements it, configures it around your object model, and builds the custom pieces its declarative surface does not reach. Native inside your Salesforce org, or standalone and integrated.
Trusted by 500+ organizations building document and intake workflows on Salesforce and HubSpot.
Most teams that come to us do not have a data problem. They have a disconnected-tools problem. Forms live in one place, documents are assembled by hand in another, and signatures happen over email. These are the five failures that show up in almost every assessment.
Submissions land in an inbox instead of a record. Someone re-keys the data into Salesforce by hand, introducing typos, delays and duplicate contacts along the way.
Contracts, invoices and proposals assembled manually from templates in a word processor. Every document is a fresh chance for a copy-paste error or an outdated clause.
Agreements sent as attachments, printed, signed, scanned and re-uploaded — or routed through a tool whose cost climbs with every envelope once volume is real.
Intake form, contract and CRM record each ask for the same client details separately. Nothing prefills, nothing stays in sync, and every re-entry is another chance to be wrong.
Generic form builders and eSignature apps bolted on with brittle integrations, custom glue code or middleware that breaks every time a field changes.
Consent, retention and audit evidence tracked in a spreadsheet next to the tool rather than inside it — which is exactly what fails when someone asks for the trail.
Formstack is a no-code suite of three connected products — Forms, Documents and Sign — that takes a workflow from data collection to a finished, signed document without leaving one platform. Two of those products also ship as Salesforce-native applications, Forms for Salesforce and Documents for Salesforce, which run inside your own org rather than syncing into it from outside.
The vendor is Intellistack, which was called Formstack until it rebranded in June 2025. The products kept the Formstack name, so both names are current: the company is Intellistack, the software is Formstack. Vendor documentation for the Salesforce products lives at formstack.com.
To be clear about who does what: Formstack provides the platform capability. Twopir Consulting designs the workflow, implements and configures the products against your object model, and builds anything the declarative surface cannot express. The client outcome is a single pass from intake to executed agreement with no re-keying in between.
A no-code form builder with conditional logic, multi-step workflows, group approvals and prefill, so a returning contact never fills in a field you already hold. Available standalone or as the Salesforce-native Forms for Salesforce.
Turns your own DOCX, PPTX, PDF or CSV templates into data-populated documents drawn from form submissions or live CRM records, with conditional sections that personalise each one and the ability to combine or split output files.
Routes contracts, invoices and agreements for signature by email or SMS with multi-participant signing, automatic reminders, reusable templates and an audit trail recorded against every signed document.
These are three different services with three different buyers, and collapsing them into "we work with Formstack" loses all three. Twopir offers all three. Which one you need depends on whether the product already does what you want, needs shaping, or has to be extended past its declarative surface.
Standing the products up from nothing: installing the managed packages into your org, setting security and sharing, provisioning users, and migrating the templates you already use so nothing is rebuilt by hand.
Shaping the products around how your team actually works — all of it inside the declarative surface, so your admins can maintain it after we leave without writing code.
Custom development where the product stops. This is Apex, Lightning Web Components and API work that extends Formstack rather than reconfiguring it — and it is a different engagement, scoped and estimated separately.
| The requirement | Configuration | Custom development |
|---|---|---|
| Mapping a form to your objects | Yes — field mapping is declarative, including custom objects and lookups. | Only if the target record has to be resolved by logic the mapping cannot express. |
| Branching a document by deal type | Yes — conditional sections and merge rules cover it. | Not needed. |
| Generating on a record trigger | Yes — Flow can call generation without code. | When the trigger depends on state Flow cannot evaluate, or must run in bulk. |
| Producing hundreds of documents at once | Not reliably — declarative generation is built around one record at a time. | Yes — batch Apex, queued and monitored. |
| Embedding a form in a custom UI | Standard placements only. | Yes — a Lightning Web Component hosting the form in your own screen. |
| Pushing a signed document elsewhere | Yes, where a supported connector exists. | Yes — API integration when it does not. |
The Salesforce-native products run inside your org rather than as an external tool that syncs over. Each of these is configured against your object model and your security setup, not a default template.
Native data capture: submissions are collected, processed and stored directly in your org, with no separate login and no field-mapping layer to maintain between systems.
Contracts, quotes and invoices generated from record data with field-level mapping, one-click buttons on the record page, and generation triggered from Flow.
Routing rules, multi-participant ordering, reminder cadence and the audit trail, wired so the executed document lands back on the right record automatically.
Dynamic prefill so returning contacts never re-enter data you already hold, with records verified and updated in place rather than duplicated across systems.
Approval routing, conditional logic and status-triggered document generation, configured around your object relationships rather than a generic out-of-the-box process.
Formstack states support for HIPAA, GDPR, PCI and Section 508 requirements. We configure those controls, plus retention and audit settings, against the obligations you actually carry — the capability is the vendor's, the fit is the work.
The native products do not "integrate" with Salesforce in the usual sense — they run inside it. What still has to be designed is which data moves where, when, and which team consumes it on the other side.
Connects intake with the customer record so sales, service and operations work from one version of the client's details instead of an inbox and a CRM that disagree. A submission creates or updates the Contact, Account and any related custom record in a single pass, and prefill pushes known values back out to the form so returning contacts confirm rather than retype.
Submission in · Prefill values out
Connects live record data with the paperwork that data produces, so finance and sales stop rebuilding contracts and invoices by hand. Field values, related records and line items are read out of the record at generation time; the finished file is written back and attached to the record it came from, which is what makes the document auditable later.
Record data out · Generated file back
Connects signature status with the pipeline so a rep sees an agreement stall before the renewal call rather than after it. The signature request carries the record context outward; signer events, completion status and the executed document flow back in, which is what lets a stage change or a renewal task fire automatically on execution.
Request out · Status and signed file back
Connects the form that collects the commitment with the system that collects the money, so finance is not reconciling two lists by hand. Payment fields capture the transaction at submission time through the processor, and the payment reference and status land on the same record as the submission — so the intake, the document and the payment share one audit trail.
Payment captured · Reference filed to record
A rollout that gets adopted looks nothing like one that gets ignored after week two. We run discovery before touching a single form field. A focused implementation — core forms, a handful of document templates and a signature workflow — typically runs four to eight weeks. Deep Salesforce automation, many document types or complex approval logic take longer, and we scope that before work begins rather than after.
We map the intake-to-signature process you actually run — who submits, who approves, what gets produced and where it has to land — before any configuration decision is made.
Forms, Documents and Sign configured standalone or native to Salesforce, including security settings, field mapping and migration of the templates you already use.
Object-level configuration for the native products, Flow-triggered generation and signature routing, plus any custom development the declarative surface cannot cover.
Sandbox validation first, then a staged production rollout with hands-on training — plus support after go-live as volume and use cases grow.
A law firm needed a folder structure organised by matter type, with files and documents imported through Salesforce into the right folder, and an email and document management platform that let the team search and retrieve work files from outside the office. Twopir built automation that generates the client, the matter and the related workspace, so documents uploaded from Salesforce are stored in iManage and reachable from anywhere. It is the same problem shape as a Formstack rollout — the document has to end up filed against the record that produced it, not in someone's downloads folder.
Read the case studyMore delivery work across industries sits in our case studies and recent projects.
We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. Formstack scales from a team running a handful of forms to an organization processing high document and signature volume, so the question is rarely size — it is whether the workflow is worth designing.
Consent, intake and onboarding packets that carry compliance obligations and cannot live in a general-purpose form tool sitting outside the record.
Engagement letters, agreements and client onboarding where the document has to be generated from CRM data and filed back against the client record.
Applications, donations and alumni engagement spread across several point tools that should be one interoperable system on Salesforce.
Teams already carrying a generic form builder and a separate eSignature tool held together by brittle integrations, looking to consolidate.
Groups whose current manual process works today and visibly will not at three times the volume — the right time to design rather than patch.
If you need one simple public form and nothing else, this is more platform than the problem needs. We will say so on the call rather than scope an engagement around it.
Before a single form is built we map how your team collects data, produces documents and gets things signed. The system reflects your actual process, not a default.
You know before we start which parts are declarative and maintainable by your admins, and which parts are custom development with their own scope and cost.
Collection, generation, signature and CRM sync are not four projects. We design them as one path through your Salesforce org.
Salesforce and document infrastructure across healthcare, financial services, education and professional services — so the edge cases are not new to us.
The configuration holds up as form count, document types and signer counts grow. What you launch should be the foundation for the next stage, not a rebuild.
Both are valid. If your team lives in Salesforce and wants data captured directly into the org with no separate login, Forms for Salesforce and Documents for Salesforce are the right fit. If you need a form and document platform that also serves systems outside Salesforce, the core Formstack products connect in through integrations instead. We assess your org and your workflow before recommending which path fits — the answer usually turns on how much of your data already lives in Salesforce.
Configuration ends where the product's declarative surface ends. Field mapping, conditional logic, prefill, document templates, approval routing and Flow-triggered generation are all configuration — your admins can maintain them without writing code. Custom development starts when you need behaviour the product does not express: bulk or scheduled generation across many records, a form embedded in a custom Lightning screen, or an API integration to a system Formstack does not reach natively. We scope those separately so the boundary is visible in the estimate rather than discovered halfway through.
Scope determines timeline. A focused implementation — core forms, a handful of document templates and a signature workflow — typically runs four to eight weeks. Engagements that include deep Salesforce automation, many document types or complex approval logic take longer. We scope delivery against your actual requirements before work begins, and the custom development portion is estimated on its own.
Often, yes. Documents and Sign handle contracts, invoices, proposals and other revenue documents end to end, and Formstack's plans include unlimited eSignatures and unlimited senders rather than charging per signature — though envelope allowances do vary by plan tier, so check the tier against your real volume. The migration question matters more than the feature question: we move existing templates and workflows across so nothing breaks during the switch.
Yes. The company rebranded from Formstack to Intellistack in June 2025 and moved its headquarters to Denver, but the products kept the Formstack name — Formstack Forms, Formstack Documents and Formstack Sign, plus the Salesforce-native Forms for Salesforce and Documents for Salesforce. So both names are correct and current: Intellistack is the company, Formstack is the software. Nothing about an existing deployment changes because of the rebrand.
Formstack states support for HIPAA, GDPR, PCI and Section 508 requirements, with encryption and audit trails, and the Salesforce-native products operate inside your org's existing security model rather than beside it. That is the platform capability. The work is fitting it to the obligations you actually carry: we configure the security, consent, retention and audit settings as part of implementation, and confirm the controls against your compliance requirements before go-live rather than after.
Implementation-only partners optimise for turning the tool on. We optimise for whether the workflow it powers improves how your team operates. In practice that means the engagement starts earlier, with process mapping, includes the custom development most implementation partners hand off, and continues past go-live with adoption support and room to scale.
Talk to a Twopir Formstack architect. We will review your current setup, identify the gaps, and tell you what a well-configured Formstack environment looks like for your team — including which parts are configuration and which are custom development — before any engagement begins.
Salesforce · Formstack by Intellistack · Document automation
Related: Formstack solutions · Formstack Documents · Formstack Sign · Salesforce AppExchange work · Salesforce support · Salesforce for professional services · Contact us
