Salesforce document generation pricing

Salesforce Document Generation Pricing: Conga Composer, Nintex DocGen, S-Docs and PDF Butler Costs Compared

Four of the six best known Salesforce document generation apps publish no price at all. Conga shows a lead form, S-Docs says outright that it does not offer one-size-fits-all pricing, Nintex routes you to a sales contact form, and PDF Butler has no pricing page anywhere on its website. Meanwhile the figures circulating on review sites contradict each other by more than a factor of eight for the same product. Below is what each vendor actually publishes, checked on 16 September 2026, what each one meters, and the two questions that decide your bill before a salesperson gets to name a number.

PDF and archive in one call
Plans from $29 a month
Your HTML stays yours

Live demo

Runs in your browser. Nothing is uploaded. One PDF free to try, then a plan.

Sample Page size Orientation Margins

Your HTML

Live preview

Your PDF is downloading. That was the free one. The Starter plan converts as many as you need, for $29 a month or $174 a year.

See the plan

Short answer

Salesforce document generation is sold two ways, and only one of them publishes prices. The Salesforce-native apps, Conga Composer, Nintex DocGen, S-Docs and PDF Butler, are all quoted per user through a sales conversation and publish no rate card. Third-party estimates for Conga Composer alone run from $6 to $50 per user per month, a spread of more than eight times, which tells you those numbers are guesses. The platform-agnostic tools do publish: Documint from $39 a month for 200 documents, Docupilot from $29 a month for 100, and Formstack Suite at $299 a month for 250 document deliveries.

The rule that decides which camp is cheaper for you: per-user pricing punishes breadth and per-document pricing punishes depth. If 200 people each need to click a button twice a month, seats will cost you five to twenty times more than a document meter. If two integration users generate 30,000 statements overnight, seats are almost free and the document meter is the whole bill.

Written and fact checked by the Sitepdf team.

Every Salesforce document generation tool: what it publishes and what it meters

Read from each vendor own website on 16 September 2026. The fourth column is the one that decides your invoice, because a tool that meters people and a tool that meters documents produce completely different bills for exactly the same job. Where a number came from a third party rather than the vendor, it says so, because we could not verify it at the source and neither can you.

Tool	How it runs	Published rate card	What it meters	Best fit
Conga Composer Managed package	Native, inside your Salesforce org	None. conga.com/pricing is a page headed "Get Conga pricing" with customer logos and six bullet points about pricing philosophy. No figure appears on it.	Per user, with a document allowance on top. The overage rate is not published.	Large orgs with deep conditional logic and an existing Conga relationship
Nintex DocGen for Salesforce Formerly Drawloop	Native, inside your Salesforce org	None. The pricing route is a sales contact form. Third-party sources quote both $5,000 a year for up to 100 users and $20 per user per month, which at 100 users differ by 4.8 times.	Reported as org level, but the two circulating models disagree.	Teams already standardized on the wider Nintex process platform
S-Docs	Native, 100 percent on-platform	None, and it says so plainly: "Because every organization has unique document volumes and workflow requirements, we do not offer one-size-fits-all pricing."	Per user, quoted per org.	Orgs that want generation and e-signature in one native package with no data leaving Salesforce
PDF Butler	Native, plus Flow and API triggers	None. There is no link containing the word pricing anywhere on pdfbutler.com. Third parties say $14 per user per month and disagree with each other about whether a 5 user minimum applies.	Per user, with batch generation sold separately as BULK Butler.	Design-heavy documents and high volume batch runs
Formstack Documents Formerly WebMerge	Standalone, with a Salesforce connector	Partly. The Suite plan is $299 a month, or $250 a month billed annually, and includes 250 document deliveries a month and 3 builder users. The separate "Salesforce Solutions" line is Custom Pricing.	Documents delivered, plus builder seats.	Teams that also need forms and e-signature on one subscription
Documint	Standalone API and integrations	Yes, in full. $39 a month for 2,400 documents a year, $124 for 12,000, $249 for 60,000. Overage is published too: 100 docs for $24.50, $14.90 or 1,000 docs for $59.80 depending on tier.	Documents only. Templates are unlimited and seats are not counted.	Predictable monthly volume where nobody wants to count seats
Docupilot	Standalone API and integrations	Yes, in full. $29 a month for 100 documents, $99 for 500, $149 for 1,000, $199 for 2,000, $399 for 5,000, $699 for 10,000. Extra seats are $4 each.	Documents and seats together. There is no overage: at 100 percent you upgrade.	Mid volume with a small team that also wants e-signature envelopes
Sitepdf This site	HTML to PDF render API, called from Apex or middleware	Yes. $29 a month for 10,000 renders, $99 for 50,000, $299 for 250,000. Yearly billing costs the same as six months.	Renders. No seats, no template count, no per-user licence.	Automated, high volume generation where developers own the document in HTML

For Conga, Nintex, S-Docs and PDF Butler the finding is the absence of a figure, confirmed on each vendor own site on 16 September 2026. That is not an oversight on their part and it is not a scandal. It is enterprise sales working as designed. It does mean you cannot budget this category from public information, which is the practical problem this page exists to solve.

Per user or per document: the arithmetic that decides everything

Every argument about which of these tools is cheapest collapses once you fix a shape and run the numbers. The two meters do not just differ in size, they respond to different things. Seats respond to how many people can touch the feature. Document meters respond to how many documents come out. A Salesforce org almost always has far more of one than the other.

Below, four common shapes, priced against a per-user tool at $25 per user per month and against Documint published ladder. To be explicit: $25 is the middle of the range third parties quote for Conga Composer, and we use it as an illustration, not as Conga price, because Conga does not publish one.

Shape	Documents a month	People who need access	Seats at $25 a user	Documint, per document	Gap
A. Small sales team generating quotes on demand	500	12	$3,600 a year	$1,488 a year Gold, 1,000 a month	Documents win 2.4x
B. Whole org can print a record to PDF	2,000	200	$60,000 a year	$2,988 a year Platinum, 5,000 a month	Documents win 20x
C. Nightly Flow, nobody clicks anything	30,000	2 integration users	$600 a year in seats, plus an unpublished document meter	$2,988 plus overage on 25,000 documents at $59.80 per 1,000, about $20,900 a year	Seats look cheap until you see the meter
D. Field service, every technician generates reports	8,000	150	$45,000 a year	$5,140 a year Platinum plus 3,000 overage	Documents win 8.8x

Three of the four shapes favour a document meter, and not narrowly. That is the single most useful thing on this page, and it is also why the native vendors sell the way they do: a per-user list price would lose most of these deals on arithmetic alone, so the number arrives after a discovery call that has already established how many seats you will accept.

Shape C is the one worth staring at, because it is the shape automation produces and it inverts the rule. When nothing is user-initiated you need almost no seats, so a per-user tool suddenly looks like the bargain. It is not, necessarily. It is the shape where the invisible document allowance and its unpublished overage rate become the entire negotiation, and where you are least able to check the answer. If your generation is automated, the seat price is a distraction and the overage rate per document is the only number that matters.

Why four of these vendors will not show you a price

This is not evasiveness for its own sake. Salesforce-native document generation is sold into orgs where seat counts, document volumes and edge cases vary enormously, and where the buyer is usually already in an annual Salesforce negotiation. A published list price would anchor every one of those conversations. So the vendors keep the anchor for themselves.

Read the wording though, because it varies in a way that tells you how each one sells. Conga pricing page is the softest: it promises "clear details about product options and associated costs" and then shows you T-Mobile and LinkedIn logos. Nintex does not pretend to have a pricing page at all and sends you to a form. PDF Butler simply has no pricing page in its navigation. S-Docs is the most honest of the four and states the reason: "Because every organization has unique document volumes and workflow requirements, we do not offer one-size-fits-all pricing."

The practical cost to you is time, not money. Getting four comparable quotes from this category takes four discovery calls, usually spread over two to three weeks, and the quotes will not be structured the same way, so comparing them is its own small project. Budget for that before you promise anyone a decision date.

Note also what the published vendors reveal by publishing. Documint and Docupilot both print their overage and seat rates, and Formstack prints its Suite price while marking its "Salesforce Solutions" line as Custom Pricing. The same company publishes a price for the standalone product and withholds it for the Salesforce edition. That is the clearest single piece of evidence that the opacity tracks the sales motion rather than the product.

What you are really buying: who is allowed to change the template

Price follows architecture in this category, so it helps to name the architecture out loud. There are two, and they answer one question differently.

Template merge, inside Salesforce. Conga, Nintex, S-Docs and PDF Butler all work the same way at heart: a business user uploads a Word, Excel or PowerPoint file with merge fields, maps them to Salesforce objects, and the app fills them in. The person who changes the wording of a contract is the person who owns the contract, and no release is involved. That is worth real money in a legal or sales operations team, and it is why these tools are priced per user: the users are the product.

Rendering, from HTML. The other approach treats the document as code. A developer writes HTML and CSS, the data comes from Salesforce, and a rendering service turns the result into a PDF. Changing the wording is a deployment. In exchange you get exact typographic control, real web fonts, charts, page break control, and a meter that counts documents rather than people.

Neither is better. They are answers to different org charts. If your marketing team redesigns the quote template twice a quarter without asking anyone, buy the merge app and pay for seats. If your documents are generated by a scheduled job and last changed when the finance team changed a disclosure, the seat model is charging you for an editing workflow nobody uses. We go through the same fork for the wider market on our document generation API comparison and our document automation software page, both of which price the non-Salesforce vendors in more detail.

The questions to ask when there is no rate card

Since four of these vendors will quote rather than publish, the leverage is in the questions. These six get you a comparable number out of every vendor in this category, and asking them in writing usually saves a round of calls.

Does every user who can trigger a document need a licence, or only the people who build templates? This single answer can move a quote by a factor of ten. Ask for it in writing.
Is there a document allowance on top of the seats, and what is the overage rate per document? Get the number, not the phrase "we work with you on volume".
Does an automated generation consume a seat or a document? A Flow, a scheduled Apex job and a Platform Event all run as some user. Ask which licence that user needs.
What is the uplift cap at renewal? Without a cap in the contract, year two is a second negotiation from a much weaker position.
What is the minimum term and the minimum seat count? Minimums are where a cheap per-seat rate becomes an expensive annual commitment.
Is batch or bulk generation a separate SKU? At least one vendor in this table sells batch as a distinct product, so the quote you were given may not cover the job you described.

If you want a sanity check on the answers, price the same job against a published ladder first. Documint and Docupilot rates above give you a defensible per-document figure, and our own PDF API pricing comparison gives you a second one from the rendering side. Walking into a quote with a number already in hand changes the conversation completely.

Where a rendering API fits, and where it does not

We sell the rendering side, so treat this as the list of reasons not to buy from us.

We are not a managed package. There is nothing to install in your org, and nothing to review in a security assessment of AppExchange packages, because we are an HTTPS endpoint your Apex calls. Some Salesforce security teams prefer the on-platform option for exactly that reason, and that is a legitimate preference.
Your data leaves the platform. Native tools like S-Docs make a point of generating entirely on-platform. If your compliance posture forbids sending record data to an external service, that decides it and no price will change your mind.
We do not merge Word templates. If your contract lives in .docx and your legal team edits it there, a merge app is the correct purchase and we are the wrong one.
Business users cannot edit the template. Your document is HTML in your repository. That is a feature if developers own it and a serious cost if they do not.

Where the rendering approach wins is narrow and clear: generation that is automatic and high volume, documents that need real typography, and a bill that should track documents rather than headcount. Shapes B, C and D in the table above are all in that zone. Our ladder is $29 a month for 10,000 renders, $99 for 50,000 and $299 for 250,000, with no seat count anywhere in it, and the arithmetic for calling it from Apex is on our Salesforce PDF generation cost breakdown, which also covers the platform limits that push teams off Visualforce rendering in the first place.

Generating a PDF from Apex and saving it to the record, with no managed package installed

public with sharing class QuotePdf {

    @future(callout=true)
    public static void generate(Id quoteId) {
        Quote q = [SELECT Id, Name, TotalPrice, Account.Name FROM Quote WHERE Id = :quoteId];

        String html = '<html><head><style>'
            + 'body{font-family:Inter,system-ui,sans-serif;font-size:11pt}'
            + 'h1{font-size:20pt;margin:0 0 24px}'
            + '</style></head><body>'
            + '<h1>Quote ' + q.Name + '</h1>'
            + '<p>Prepared for ' + q.Account.Name + '</p>'
            + '<p>Total: $' + q.TotalPrice + '</p>'
            + '</body></html>';

        HttpRequest req = new HttpRequest();
        req.setEndpoint('callout:Sitepdf/v1/render');
        req.setMethod('POST');
        req.setHeader('Content-Type', 'application/json');
        req.setTimeout(60000);
        req.setBody(JSON.serialize(new Map<String, Object>{
            'html'   => html,
            'format' => 'Letter',
            'margin' => '18mm'
        }));

        HttpResponse res = new Http().send(req);
        if (res.getStatusCode() != 200) {
            throw new CalloutException('Render failed: ' + res.getStatus());
        }

        insert new ContentVersion(
            Title         = 'Quote ' + q.Name,
            PathOnClient  = q.Name + '.pdf',
            VersionData   = res.getBodyAsBlob(),
            FirstPublishLocationId = quoteId
        );
    }
}

This is the documented API call shape. Full request and response walkthrough.

Questions about this job

How much does Conga Composer cost?

Conga does not publish a price. Its pricing page is a lead form headed "Get Conga pricing" with no figures on it, checked 16 September 2026. Third-party review sites quote anywhere from $6 to $50 per user per month, a spread of more than eight times, which means none of those figures is reliable. Expect a per-user quote with a document allowance on top, and ask for the overage rate per document in writing.

Does Nintex DocGen for Salesforce publish pricing?

No. Nintex routes pricing questions to a sales contact form and publishes no rate card for DocGen for Salesforce, formerly Drawloop. Two incompatible third-party models circulate: about $5,000 a year at org level for up to 100 users, and about $20 per user per month. At 100 users those differ by 4.8 times, so confirm which model applies to you before comparing Nintex to anything else.

What is the cheapest Salesforce document generation tool?

It depends entirely on whether you count people or documents. For a small team generating a few hundred documents a month, a published per-document tool like Documint at $39 a month is usually cheapest. For an org where hundreds of users each generate a handful, per-document pricing wins by ten to twenty times. For automated overnight generation, a per-render API at $29 to $299 a month is normally the floor.

Is Salesforce document generation priced per user or per document?

Both models are in the market. The Salesforce-native apps, Conga, Nintex, S-Docs and PDF Butler, are quoted per user, usually with a document allowance layered on top. The platform-agnostic tools, Documint, Docupilot and rendering APIs, meter documents or renders and ignore headcount. Work out which of those two numbers is larger in your org before you shortlist anything.

Do I need a Salesforce licence for automated document generation?

Automated generation still runs as a user. A Flow, a scheduled Apex job or a Platform Event handler executes in some user context, and vendors differ on whether that context needs a paid document generation licence. Ask the question explicitly, because the answer changes an automated workload from two seats to every seat in the org.

Can Salesforce generate PDFs without buying an app?

Yes, Visualforce can render a page as PDF with no licence at all, and for simple internal documents it is enough. It carries hard platform limits though: the response must be under 15 MB before rendering, web fonts are not supported, and JavaScript-rendered content does not appear. Those limits are what push most teams to buy either a merge app or a rendering API.

Index

More PDF and archiving tools

Get started

Render and archive with one API call

A pixel perfect PDF and a dated copy of the page from the same request. Plans from $29 a month.