The template library grows faster than anyone can own it
Each rep who needs a variation makes a copy. Six months in there are sixty templates, nobody knows which is current, and a customer has just received last year's terms.
Document Automation · Implementation Buying PandaDoc is a decision.
Buying PandaDoc is a decision.
Landing it is a project.
Most PandaDoc rollouts stall in the same place: the licences are live, two enthusiasts build templates, and four months later half the team is still attaching PDFs to email. Implementation is not installation — it is deciding what a document is in your business, who owns it, what has to be true before it goes out, and what happens when it comes back signed. We build that, then we make sure people use it.
5
8 wks
14
1
Trusted by 500+ organizations — including revenue, sales operations and legal teams running document generation, quoting and e-signature on Salesforce and HubSpot with Twopir Consulting.
Built for Document-Heavy Teams
- Salesforce Partner
- HubSpot Partner
- Template Architecture
- Approval Workflows
- E-Signature
- Content Library
- User Adoption
- Admin Handover
Why PandaDoc rollouts quietly fail
None of these is a product problem. Every one is a decision nobody made before the licences went live. They are all cheaper to fix before launch than after.
Nobody owns the system
It was bought by sales, configured by an admin who has since moved on, and paid for by finance. When something breaks, three teams each assume it belongs to one of the others.
Variables were never mapped to the CRM
Templates get built with typed-in placeholders because the field mapping was 'a later phase'. The team is now doing manual data entry inside an automation tool.
Approval exists as a policy, not a workflow
Discounts are supposed to be approved. Nothing in the system enforces it, so approval is a message someone sends when they remember, and a gap in the audit trail when they do not.
Go-live happened without a parallel run
The first real test is a live customer deal at quarter-end. Every defect is now discovered by someone under pressure, and confidence in the system never recovers.
No baseline, so nobody can prove it worked
If you did not measure how long a proposal took before, you cannot show the improvement after — which makes the renewal conversation harder than it should be.
What Implementation Is
Implementation is the decisions, not the installation
A PandaDoc implementation is the work of turning a licensed platform into your document operating model. It covers workspace and folder structure, role and permission design, the template architecture, the variables and roles that pull data in, the Content Library of reusable clauses, the approval workflows, the connection to your CRM, and the training and governance that keep it correct after launch. Installing the software is an afternoon; the rest is the project.
Three distinct things, stated plainly. PandaDoc supplies the platform — templates, variables, roles, Content Library, pricing tables, approval workflows, e-signature, analytics and an API. Your CRM stays the system of record for the customer and the deal. Twopir designs the model and builds it, then hands it to a named owner on your side with the documentation to run it. We implement PandaDoc; we are not PandaDoc, and we do not resell it.
This page covers the rollout itself. If your first question is specifically how PandaDoc should sit inside Salesforce or HubSpot, those pages go deeper on the CRM architecture and the two-way sync. Most engagements are this page plus one of those.
We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. A PandaDoc implementation is worth doing properly once your document volume is high enough that inconsistency costs real money — usually somewhere past a few hundred documents a month, or earlier if the documents are contracts.
Implement, configure, or build past the platform
Buyers arrive wanting one of three things and often use the same word for all three. This is the split we work to.
Implement
The full rollout: from an empty workspace to a team that has sent real documents and would object if you took it away.
- Workspace, folder and branding setup
- Role, permission and ownership design
- Template architecture from your real documents
- Variables and roles mapped to your CRM fields
- Content Library for reusable clauses and terms
- Training, parallel run and a documented handover
Configure
Refining a live workspace so it expresses the way your business actually sells and approves.
- Conditional content so one template covers many cases
- Approval routing on value, discount or document type
- Pricing tables and quote configuration
- Identity verification appropriate to the risk
- Reporting on cycle time, stalls and completion
- Template consolidation and change control
Build On
Where the platform's own surfaces stop and software development begins.
- Generation from objects the CRM connector does not expose
- REST API and webhook services
- Bulk and scheduled document runs
- Embedded signing inside your own product
- Custom integrations to ERP, billing or storage
- Data transformation the template engine cannot do
| Scope item | Included in implementation | Separate engagement |
|---|---|---|
| Workspace, roles and branding | Yes | — |
| Template architecture and build | Yes — your core document set | Additional document families |
| Variable and role mapping to the CRM | Yes | — |
| Approval workflow design | Yes — your primary approval path | Multi-entity or multi-region matrices |
| CRM two-way sync architecture | Connection and validation | Deep CPQ and line-item design |
| Migrating historical documents | — | Yes — see PandaDoc Migration |
| Custom-object or API generation | — | Yes — see PandaDoc API development |
| Ongoing template governance | Handover and documentation | Yes — managed services |
We quote the right-hand column separately rather than folding it into an implementation price and discovering the overrun halfway through.
The boundary, in one sentence: implementation covers everything you can build inside PandaDoc's own surfaces plus the standard CRM connection — and stops at historical data migration, custom-object generation and anything requiring the REST API. Those are real projects with their own scope, and we price them as such.
The six things that decide whether a rollout survives its first quarter
Each of these is a deliverable with a named owner at handover, not a workshop output.
Workspace & Role Architecture
The structure everything else lives in. Get it wrong and every later decision fights it.
- Workspace and folder structure matched to the business
- Roles mapped to real job functions, not job titles
- Permission model for create, send, approve and admin
- Multi-team or multi-brand separation where needed
- A named owner with documented responsibilities
Template & Content Architecture
The difference between a template library and a document system is whether one template can serve many cases without being copied.
- Document families defined from your real output
- Conditional content blocks driven by deal attributes
- Content Library for clauses, terms and standard sections
- Brand lock so layouts survive rep editing
- Naming, versioning and retirement conventions
Variables, Roles & CRM Mapping
Where documents stop being retyped. Every field that appears in a document should come from the record, not a person.
- Field-by-field mapping from CRM objects to variables
- Role design for signers, approvers and counter-signers
- Transformation plan for picklists, formulas and lookups
- Fallback behaviour when a source field is empty
- Validation against real records before go-live
Approval & Signing Workflow
Approvals configured on the template so the policy applies to every document, not the ones someone remembered to route.
- Approval paths by value, discount or document type
- Multi-step routing across sales, finance and legal
- Signing order and counter-signature flows
- Identity verification matched to the risk
- Audit trail that stands up to a finance review
Adoption & Enablement
The part most implementations under-fund, and the reason most of them under-deliver.
- Role-specific training, not one generic session
- A parallel run before the system carries live deals
- Quick-reference material people will actually open
- Champion identification inside each team
- First-cycle floor support when questions are highest
Baseline, Measurement & Handover
We measure the before so you can prove the after — and hand over a system somebody internal can run.
- Baseline capture of cycle time and manual effort
- Dashboards for status, stalls and completion
- Documented configuration and design decisions
- Admin handover with a competence check, not a demo
- A 30- and 90-day review against the baseline
What a PandaDoc implementation connects to
Both platforms named, the business purpose, and what moves in which direction.
Salesforce ↔ PandaDoc
CRM records populate document variables at creation; document status, the signed PDF and completion timestamps write back to the Opportunity. Covered in depth on our PandaDoc Salesforce consulting page.
HubSpot ↔ PandaDoc
Deal, company and contact properties populate quotes; document events land on the activity timeline where workflows can act on them. Covered in depth on our PandaDoc HubSpot page.
Payment collection
Payment captured at signature rather than chased afterwards, with payment status returning to the deal record so finance and sales see the same state.
Document storage & records
Completed agreements filed to the record and, where retention policy requires it, mirrored to your document management system with the audit certificate attached.
iPaaS — Zapier, Workato, Celigo
Event-triggered connections for narrow jobs: a signature creating a task, a status change notifying a channel. One trigger, one action, and no document analytics.
Slack & Microsoft Teams
Approval requests and signature notifications routed to the person who must act on them, not broadcast to a channel.
Billing & ERP systems
Signed line items driving invoice or subscription creation downstream, so what was signed and what is billed are the same thing.
REST API & webhooks
The escape hatch for anything the standard connectors do not reach. Scoped separately — see our PandaDoc API development page.
Five phases from empty workspace to real adoption
The shape below is the delivery model behind the eight-week engagement in the outcomes section. Timelines move with the number of document families and the number of people who hold an opinion on approvals.
Discovery & Baseline
We collect your real documents, map every field that has to populate, and record how long the current process takes. On one documented engagement this produced 14 distinct data points to auto-populate and three conditional content scenarios.
Architecture & Design
We design the workspace, roles, template families and approval paths, and specify the CRM field mapping. You approve the design before anything is built, which is where changes are cheap.
Build & Configure
We build the templates, Content Library, conditional logic and approval routing in a sandbox workspace, and validate against real records rather than sample data.
Test, Train & Parallel Run
UAT with the people who will use it, role-specific training, and a parallel run so the first live deal is not the first real test. Defects get found here, not at quarter-end.
Launch, Support & Review
Go-live with floor support through the first cycle, then a documented handover to a named owner and a review against the Phase 01 baseline at 30 and 90 days.
What a finished implementation actually changes
Real engagements, with the scope each number was measured against.
Quote-to-Cash Document Automation
40–150 sales users · 500+ documents per month · delivered in 8 weeks across 5 phases
100%
Transaction data auto-populated
<60s
To a branded, data-accurate proposal
0
Manual exports or copy-paste steps
1
System of record for every document
Proposal creation used to take a rep 45 minutes of copying data, fixing formatting, and hoping nothing was wrong by the time it reached the customer. Now they click one button inside Salesforce and a fully accurate, branded document is ready to send in under a minute. The eSignature alone has cut our average close cycle by days.
Contracts, Offer Letters & KYC Onboarding
Documents generated from CRM data the moment a record reaches the document stage
3
Document families automated
0
Re-keyed record data
Native
Salesforce generation
1
Branded template standard
Engagement scope: contracts, offer letters and KYC onboarding forms generated automatically from Salesforce Opportunities at the point a deal reaches the document stage, replacing manual assembly in Word. Outcome metrics for this engagement are being confirmed with the client before publication.
Teams at the point where this becomes worth doing properly
Implementation is an investment. These are the situations where it returns.
Teams that have just bought PandaDoc
Licences are live and nobody has decided what a document is in your business yet. This is the cheapest possible moment to get the architecture right.
Teams whose self-build stalled
You started internally, built a dozen templates, and hit the point where every new case means another copy. That is an architecture problem and it has a known fix.
Companies standardising after growth
Two offices, three product lines and four ways of producing the same contract. You need one model that every team can live inside.
Legal and finance functions taking control
Documents go out without approval and clause language drifts. You need the gates inside the tool rather than in a policy document.
Teams replacing a legacy e-signature tool
You are moving off DocuSign, Adobe Sign or Conga. Implementation and migration are two engagements — our PandaDoc Migration page covers the second.
Organisations with a compliance requirement
Audit trail, retention and identity verification are not optional for you, and the configuration has to be defensible rather than convenient.
We have done the unglamorous half before
Template design is the visible part. Field mapping, permission models and adoption are where implementations succeed or quietly fail.
We design before we build
You sign off an architecture — workspace, roles, template families, approval paths, field map — before a single template is created. Changing a design is cheap; rebuilding a library is not.
We map fields against real records
Not sample data. Picklists, formula fields and empty-value behaviour get tested on your actual records, which is where template population usually breaks.
We fund adoption properly
Role-specific training, a parallel run and floor support through the first cycle. A system nobody uses is a more expensive failure than no system at all.
We hand over to a named owner
With documentation, a change-control process and a competence check rather than a demo. If nobody internal can run it, we have not finished.
We are CRM specialists, Salesforce Partner and HubSpot Partner
So the CRM half of the implementation — the half most document specialists are weakest on — is the half we are strongest on.
500+ clients over 12+ years
With a 40+ person team across the US, Canada, UK, UAE, Australia and New Zealand, and 250+ deployments behind the delivery model above.
What teams ask before starting an implementation
The questions that determine scope, timeline and whether this is the right project now.
The documented engagement in our outcomes section ran eight weeks across five phases, covering four document types for a team of 40 to 150 users generating more than 500 documents a month. A single document family on a clean CRM can be considerably shorter. A multi-entity build with CPQ, several approval matrices and a billing integration is longer. The two variables that move the timeline most are the number of distinct document families and how much of your current approval practice is undocumented.
Implementation is the initial build: workspace, roles, template architecture, field mapping, approval design, CRM connection, training and handover. Customisation is the ongoing work of making the platform express changing commercial rules — new conditional content, revised approval thresholds, new pricing logic. Both are configuration and neither produces code you have to maintain. Development is a third category, covered on our PandaDoc API page.
Usually only a subset. Completed agreements that are still commercially live — active contracts, current MSAs, anything you would need to produce in a dispute — are worth migrating. Historical documents with no ongoing obligation are usually better left in the old system or in an archive, because migrating them costs real money and returns very little. We cover the decision and the mechanics on our PandaDoc Migration page.
Many teams can, and some should. If you have one document family, a straightforward approval path and an admin with time, the platform is genuinely approachable. Bringing in help pays when the field mapping is complex, when several teams need different templates from the same source data, when approvals cross functions, or when a previous self-build has already produced a template library nobody can govern.
Your real documents — not idealised versions — a CRM administrator with the access to install and connect an app, somebody who owns the commercial and approval rules, and a small group of end users for testing. The heaviest ask is Phase 01, where we need an honest description of how the process actually runs today, including the workarounds.
Three things. Conditional content, so one template serves several cases instead of being copied. A naming, versioning and retirement convention agreed before the first template is built. And a single named owner with a documented change process. Sprawl is a governance failure rather than a platform limitation, so the fix is governance.
We stay through the first full cycle with floor support, then hand over to a named owner with documentation and run a review against the Phase 01 baseline at 30 and 90 days. Teams that want us to keep running it move onto managed services; teams that want to run it themselves have the documentation and the training to do so.
Next Step
If PandaDoc is bought but not yet landed, start here
Bring us your real documents and an honest description of how approvals work today. We will come back with the architecture, the scope, the timeline and the things we think you should not do yet.
12+ years · 500+ clients · 40+ consultants · Salesforce Partner · HubSpot Partner
