Formstack Consulting Services are advisory and delivery engagements that design, build and optimise processes on the Formstack Suite — Forms, Documents, Sign and Workflows — and connect them to the systems that already run your business. Twopir Consulting works as the architecture team on those programmes: we map the process first, choose the right product and deployment model second, and build so the result survives volume, audit and staff turnover.
Formstack consulting services cover the work of deciding how a process should run on the Formstack Suite, building it, connecting it to the systems of record around it, and keeping it healthy afterwards. That includes requirements and process mapping, choosing between Formstack's cloud products and its Salesforce-native packages, designing the form and data model, building document templates and signature routing, configuring approvals, wiring integrations through native connectors or the API, and setting the governance that stops the estate sprawling six months later.
It is distinct from Formstack support, which keeps an existing build running, and from licence resale. Twopir Consulting does not sell Formstack licences. We are the independent architecture and delivery team that makes the licences you already hold produce a working process.
On partner language. Twopir Consulting is a Salesforce Gold Partner and a HubSpot Gold Partner. We implement and support Formstack as an independent consultancy and do not describe ourselves as a Formstack or Intellistack partner. Where a page on this site states a vendor relationship, it states only the one we actually hold.
Formstack is easy to start with, and that is exactly why estates drift. These are the patterns we are called in to unpick — on programmes that have been live for six months and on programmes that have been live for six years.
Every team builds its own forms. Nobody owns naming, folders, field reuse or retirement. Two years later there are hundreds of forms, half of them unused, and no one can tell which one feeds the CRM field that finance reports on.
Formstack offers cloud products and Salesforce-native packages, and they behave differently — where data lives, how records are created, what governs access. Picking the wrong one is cheap to do and expensive to reverse once thousands of submissions exist.
The form is live, but somebody still copies the submission into Salesforce, retypes it into a contract, and emails the contract for signature. The tools were bought to remove that work and the process was never redesigned to actually remove it.
Merge templates accumulate conditional blocks and undocumented field names. One legal wording change becomes a two-week project because no one is sure which templates share the logic or what will break downstream.
Each connection was built by whoever needed it, with its own field mapping, its own error handling and no shared data contract. When a field is renamed upstream, three integrations fail silently and the first sign of it is a reporting gap.
The submission is captured properly and then stops. Approval happens in an inbox, the decision is never written back, and the audit trail ends at the point it starts to matter — which is the point a regulator or a customer asks about it.
Formstack supports HIPAA, GDPR, PCI and Section 508 requirements on the right plan and the right configuration. None of that is automatic. Teams routinely assume a capability is switched on because the platform is capable of it.
Leadership can see how many submissions arrived. They cannot see where people abandon the form, how long approvals sit, or how many documents needed a manual correction — the numbers that would tell them what to fix next.
Formstack is a capable platform with an unusually low barrier to entry. That combination is what creates the problem we are usually hired to solve: it is entirely possible to build a great deal of working functionality without anyone ever deciding what the process is supposed to be, who owns each decision, or where the data is meant to live.
We work in the other order. We start with the process — who submits, what has to be true before the next step runs, who approves, what document that produces, where the record of it belongs, and what leadership needs to see. Only then do we decide which Formstack product carries which part of it, and whether the Salesforce-native packages or the cloud products are the right fit. That decision is architectural, not a preference, and it is far cheaper to get right before the build than after.
The second principle is that nothing we build should depend on us. Field naming, template structure, integration contracts and error handling are documented as we go, and your team is trained on the build rather than handed a recording. The measure of a good engagement is that the internal team runs the next three changes without calling anyone.
Each of these is a discrete engagement with its own scope, deliverables and exit criteria. Most clients start with one and add others as the estate matures. Follow any link for the full detail on that engagement.
The left two columns describe the platform's native capability. The right column describes our work. Keeping those separate matters: nothing on this page should suggest Twopir built a Formstack feature.
| Product | What the platform does natively | Where design decisions are made | What Twopir delivers |
|---|---|---|---|
| Formstack Forms | Drag-and-drop form building, conditional logic, Save & Resume, Smart Lists, data routing, payment fields with PCI-compliant processors, form analytics and field bottleneck reporting. | Field and validation model, reuse across forms, routing rules, where submissions are stored, publishing surface. | Capture design, build, accessibility review, routing configuration and the naming and folder standard that stops sprawl. |
| Formstack Documents | Merges data into templates using {$fieldName} merge fields; supports the native builder plus Word, Fillable PDF, PPTX and Excel templates; outputs PDF, DOCX, XLSX, HTML, XML and more. | Template strategy, conditional content, how many templates exist, where the finished file is delivered and stored. | Template architecture, merge mapping, delivery routing, version control and a structure a non-developer can safely edit. |
| Formstack Sign | Collects legally binding eSignatures by email, text message or in person, with an audit trail, timestamps and signer metadata supporting ESIGN and UETA. | Signer order and roles, reminder cadence, what counts as complete, where the executed document and audit trail are retained. | Signature routing design, envelope and reminder configuration, and the retention and evidence trail your compliance team will be asked for. |
| Formstack Workflows | Visual builder that sequences form, document, signature and approval steps, with step logic, group approvals and a shared workspace for assigned work. | Where the process boundary sits between Formstack and the CRM, how exceptions are handled, who is accountable at each step. | Process design, step and approval configuration, exception paths, SLA instrumentation and the hand-off contract with Salesforce Flow. |
| Salesforce-native packages | Forms for Salesforce and Documents for Salesforce install from AppExchange as separate managed packages and run inside the Salesforce org, using Salesforce's own security model. | Native versus connected deployment, object and record-type mapping, prefill strategy, API consumption, Experience Cloud publishing. | The deployment decision itself, package configuration, mapping, prefill design, portal publishing and the API budget that keeps it inside platform limits. |
Platform capabilities, plan entitlements and published limits change. Everything in this table reflects Formstack's documentation as reviewed for this page; confirm the specifics against current Formstack documentation for your plan before you design against them.
Five stages, each with a named deliverable and a decision point. You can stop at the end of any stage with something useful in hand — that is deliberate, and it is what keeps a consulting engagement honest.
We inventory what exists — forms, templates, integrations, licences, volumes and failure points — and interview the people who actually run the process. The deliverable is a current-state map and a list of what is costing you time, money or risk right now.
Process design first, then the technical architecture: which product carries which step, native or connected deployment, the field and object model, integration contracts and the governance model. The deliverable is a design document your team signs off before anything is built.
Configuration and development in short cycles against the signed design, with a working demo at the end of each. Integrations are built with explicit error handling from the first iteration rather than added after the first outage.
User acceptance testing against the real process, volume and edge-case testing, data migration where relevant, and a documented cutover. Enablement is delivered to the people who will own the build, not just to the project sponsor.
Hypercare through the first cycle, then an agreed cadence of review: process metrics, failure rates, integration health, licence utilisation and the change backlog. This is where an estate stops drifting and starts compounding.
The organisations we help are rarely evaluating Formstack for the first time. They are usually running it already, at a scale where design decisions have started to have consequences.
Organisations where Salesforce is the system of record and Formstack is the capture and document layer in front of it. The work is usually about deployment model, mapping discipline and API budget.
Education, healthcare, financial services and government bodies that need accessibility, consent capture, retention rules and a defensible audit trail configured deliberately rather than assumed.
Teams generating contracts, agreements, statements of work, policy documents or onboarding packs at volume, where the cost of manual assembly and rework has become visible in headcount.
New CRM or operations leadership that has inherited a Formstack estate with no documentation, no owner and no reliable inventory — and needs to know what is safe to change.
Businesses running Formstack alongside a CRM, a finance system, cloud storage and a payment processor, where the integration layer is doing more work than anyone documented.
Groups that proved a process in one department or region and now need it to run consistently across many — where what worked informally stops working at the third repetition.
Twopir Consulting is a Salesforce Gold Partner and a HubSpot Gold Partner. Formstack work almost always terminates in a CRM, and the quality of that landing — object model, record types, sharing, reporting — is what determines whether the automation is actually useful. We design both sides.
Native or connected is the single most consequential choice on a Formstack-and-Salesforce programme, and it is routinely made by accident. We treat it as a documented architectural decision with stated trade-offs, so the reasoning survives the people who made it.
Most builds work on the happy path. Ours are designed around what happens when an integration times out, a required field arrives empty, a signer never responds, or a daily API quota is reached. Those paths are specified before the build, not discovered in production.
We do not resell Formstack and we have no commercial interest in you buying more of it. When the honest answer is that a step belongs in Salesforce Flow, in your iPaaS, or nowhere at all, that is the recommendation you get.
Naming standards, field dictionaries, template inventories, integration contracts and runbooks are deliverables, not afterthoughts. Our retention rate across long-running engagements is 98%, and it is not because clients are locked in.
Often yes, but for a narrower reason than people expect. A capable Salesforce admin can configure Formstack perfectly well. What is usually missing is the architectural decision layer — native versus connected deployment, where the process boundary sits between Formstack and Salesforce Flow, how the API budget is spent, and how the estate is governed as it grows. We are typically engaged for the design and the difficult integration work, with your admin owning day-to-day changes afterwards.
Twopir Consulting is a Salesforce Gold Partner and a HubSpot Gold Partner. We implement and support Formstack as an independent consultancy rather than as a Formstack or Intellistack partner, and we do not resell Formstack licences. In practice that means our recommendation on what to build in Formstack — and what to build somewhere else — carries no commercial bias.
The Salesforce-native packages — Forms for Salesforce and Documents for Salesforce — install from AppExchange and run inside your Salesforce org, so data is collected and stored against Salesforce's own security model. The cloud products run on Formstack's platform and connect to Salesforce through integrations, which means data travels to Formstack and back. Native is usually the right answer when Salesforce is the definitive system of record; connected is usually right when the same process must serve several systems, or when you need cloud-only capabilities. It is an architectural decision, and the two are covered in detail on our Formstack Salesforce integration page.
It depends on scope, and we size it after the assess stage rather than before. A focused audit of an existing estate is typically a matter of weeks. A single process built end to end across Forms, Documents and Sign is usually longer. A multi-process programme with data migration, portal publishing and several integrations is longer again. What we will not do is quote a duration before we have seen the current state, because the variable that actually drives timeline is the condition of the data and the number of stakeholders who need to agree on the process.
Yes, and it is a large share of our Formstack work. We start with an audit rather than a rebuild, because inherited estates almost always contain more working logic than they appear to. The output is an inventory, a list of what is genuinely broken versus merely undocumented, and a remediation roadmap sequenced so the highest-risk items are addressed first. Rebuilding is a recommendation we make only when the cost of remediation exceeds it.
Formstack documents support for HIPAA on its HIPAA plans, commitments to GDPR and PIPEDA, PCI compliance for payment handling, and Section 508 compliant forms. None of that is automatic on a given account — it depends on your plan, your configuration and, for HIPAA, the associated agreement being in place. Treat the platform's capability and your compliance position as two separate questions, and verify the current entitlements for your plan with Formstack directly. Configuring a build so it actually meets the obligation is part of what we do.
A first call is a working session, not a pitch. Come with the process that is costing you the most — the one with the rekeying, the email approvals or the integration nobody trusts — and we will tell you where the design problem actually is and what it would take to fix it.
Speak with a team that designs the process before it configures the platform — and that will tell you when the answer is not more Formstack.
