Should we build Salesforce document generation ourselves or buy it?

Building it yourself gives exactly the behaviour you specify and no licence cost, but takes weeks to months before the first document and leaves you owning webhooks, retries, signed-copy write-back and every future Salesforce change. Buying is usually faster and cheaper unless the document logic is genuinely unique to your business.

What is the difference between a general document generation tool and a purpose-built Circularo connector?

A general tool is built to work with many signature providers, so templates are often rebuilt in its own editor and signing is designed around a different provider. A purpose-built connector uses your existing Word or PDF file unchanged, connects to Circularo with a single API token, and handles signer identity checks and signed-copy write-back as part of the same path.

How long does it take to connect Salesforce to an e-signature provider manually?

Building the integration yourself typically takes weeks to months, because the document merge is only the first part. You also need signature positioning, signer identity, webhook handling, retries, and writing the signed copy back to the correct record and store - then maintaining all of it as Salesforce and the signature API change.

Do we need to install a managed package for Salesforce document generation?

Not with every option. General document tools are usually distributed as a managed package that your security team must review and install. Savvy DocGen connects through a standard authorised connection instead, so there is no package to review and nothing installed into production.

Comparison

Build it, buy a general tool, or use something made for this.

No competitor names, no rigged scorecard. Three genuine approaches to getting documents out of Salesforce and signed, compared on the things that actually decide it - including the cases where we are the wrong choice.

3Approaches compared

16Decision points

WeeksTypical build-it-yourself time

1 tokenTo connect Circularo

The three options

Buy general, build bespoke, or use something purpose-built.

Almost every team lands on one of three answers. None of them is wrong in every case - they are wrong in different cases.

Option A

A general document tool

A product built to generate documents for any signature provider and any process. Broad by design, which is its strength and its limitation.

Mature and broadly capable Large ecosystem and community Templates usually rebuilt in their editor Built around a different signature provider Managed package to review and install Cost grows with every document you send

Typical shape: licence per user or per document, plus a managed package your security team reviews before anything starts.

Option B

Building it yourself

Apex, a templating library and direct calls to the signature API. Completely yours, and completely your responsibility.

Exactly the behaviour you specify No third-party licence at all Weeks to months before the first document Webhooks, retries and write-back all yours to build Breaks when Salesforce or the API changes Maintained forever by whoever is still there

Typical shape: weeks of build, then a permanent maintenance line item nobody budgets for.

Option C

Savvy DocGen

Built for one job: Salesforce records to finished documents, signed through your own Circularo account, filed back on the record.

Your existing Word or PDF file, unchanged Purpose-built for Circularo, one API token Five levels of related records, conditions, bundles Signed copy filed back automatically No managed package to review Only sensible if you sign through Circularo

Typical shape: a service level, no managed package, and the whole path maintained by the people who built it.

Side by side

Sixteen things that decide it.

The dimensions that actually change the decision, rather than a feature list weighted to make one column win.

	A general document tool	Building it yourself	Savvy DocGen
Time to first document	Days - templates rebuilt in their editor	Weeks to months of development	The same afternoon, using your existing file
Template format	Usually rebuilt inside a proprietary editor	Whatever you write code for	Your existing Word or PDF, unchanged
Related Salesforce records	Parent lookups, often one or two levels	Whatever you query for	Five levels of lookups, plus child and grandchild records
Conditional content and tables	Varies; often an add-on tier	You build it	Conditions, repeating rows, currency and images built in
Merging several documents	Sometimes, sometimes not	You write the merge yourself	Bundles, with templates included or skipped by record
Where the file is filed	Often Files only	Your choice, you code it	Files or Notes & Attachments, per template
The 25 MB Notes limit	Usually discovered when a document fails	Discovered in production, once	Warned at the moment you choose the store
Signing with your Circularo account	Built around a different signature provider	Possible, and entirely yours to build	One API token, purpose-built
Signer identity checks	Depends on their signature provider	You implement OTP and passwords yourself	Email OTP and per-signer passwords from a record field
Signed copy written back	Usually, to their chosen store	You build the webhook and the write-back	Filed on the same record, same store, matching name
Automation triggers	Flow or button, commonly	Whatever you build	Button, stage change, field change, file arrival
Sandboxes and multiple orgs	Often licensed per org	Another environment to maintain	Any number, no per-org licence
Installed into Salesforce	Managed package to review and install	Your own Apex to review and maintain	No managed package - an authorised connection
When Salesforce changes	Vendor keeps up	Your team keeps up, forever	We keep up
Who fixes it at 2am	Vendor support	Whoever wrote it, if they still work there	Us, and we built the whole path
Ongoing cost shape	Per user or per document, growing with use	Salary time, indefinitely	A service level, not a per-document meter

Handled Partly, or depends Not really

Honesty

Four times we would tell you to go elsewhere.

Every vendor claims to be a good fit. These are the situations where we are not, written plainly enough that you can check yourself against them before booking anything.

“We already sign everything through a different provider, and we are not changing.”

Then do not change. This is built around Circularo specifically - one API token, signer identity, reminders and write-back all tuned to it. Bolting it onto another provider would give you a worse version of what a general tool already does well.

Go with A general document tool

“The document does not pull anything from Salesforce.”

Then you do not have a document generation problem. If nothing is being merged from a record, a shared template folder and your existing signature tool will do the job without anyone paying for a connector.

Go with Neither - a template folder

“Our document logic is genuinely unique to how we work.”

Conditions, repeating tables and bundles cover a great deal, but not everything. If your document does something no configuration could express, building it yourself is the honest answer - and you will end up there anyway after paying someone to try.

Go with Build it yourself

“We send maybe twenty documents a year.”

Then the manual process is not costing you enough to fix. Automation earns its keep on repetition; at that volume the person doing it by hand is cheaper than any tool, including this one.

Go with Keep doing it by hand

Everywhere else - documents built from Salesforce records, signed through Circularo, filed back onto the record that started it - is exactly what this was made for, and we will back that with a demo on your own data rather than ours.

Bring the comparison to the call.

If you are weighing this against a build or another tool, come with the questions. We will answer the ones where we lose as directly as the ones where we win.

Book a Demo See every feature