You Shouldn't Need a PDF to Send a Contract

Open almost any e-signature tool and the first screen asks for a file. Drag a PDF here. Everything after that — placing fields, assigning signers, setting the order — is layered on top of a document that was finished somewhere else, in some other program.

For a form you never touch, that's fine. For a contract whose wording changes with every deal, the upload-first model quietly charges you rent, and the bill arrives on version two.

Vendor pricing and capabilities in this post were checked against each company's own public pricing and documentation pages on 8 August 2026. US list prices, annual billing where offered, before tax. Availability varies by region and plan.

The tax you pay on version two

Say you keep your consulting agreement in Word. Version one goes fine: export to PDF, upload, place eleven fields, send.

Then a client asks to change the payment terms. You open the Word file, edit one paragraph, re-export, and re-upload. Every field you placed is now in the wrong spot, because you didn't move the fields — you moved the text underneath them. The coordinates you drew are absolute, and the words are not.

So you place eleven fields again. And again next quarter.

This is not a rough edge on any particular product. It follows directly from the model: if the document is an opaque page and fields are rectangles drawn on top of it, then editing the words and keeping the fields are mutually exclusive.

The clipping problem nobody advertises

There's a subtler version of the same issue, and it shows up at signing time rather than authoring time.

When you draw a text field on a page, you decide its width before you know what's going into it. That guess is safe for a date and unsafe for a name. Al Ray and Alexandra Fitzgerald-Whitmore are both plausible answers to "Full legal name," and one of them is four times wider than the other.

Every product built on fixed boxes has to pick a failure mode. Documenso's field-overflow work is a good look at the decision, precisely because it's an open-source project reasoning in public: the pull request that added overflow handling introduced a four-way choice between cropping, scaling horizontally, scaling vertically, and automatic behaviour. That taxonomy exists because a fixed box on a fixed page cannot grow, so the only remaining question is which compromise the signer gets.

A field that sits inside a sentence has no box to run out of. It's part of the paragraph, so a long value pushes the rest of the sentence along and the page re-lays itself out — the same thing that happens when you type a long word in any word processor. The certified PDF is generated afterwards, from the text plus the values that were actually submitted, which is the first moment the correct layout is genuinely knowable.

The market splits into two camps, and the gap is in the middle

Once you start looking for "write the document here" rather than "upload the document here," the category divides cleanly.

Upload-first e-signature. DocuSign eSignature, Dropbox Sign, SignWell, BoldSign, Zoho Sign, Documenso, Adobe Acrobat Sign, Xodo Sign. A file is the entry requirement. Some accept DOCX, but converting it is not the same as keeping it: Documenso's own upload documentation is refreshingly direct that the original .docx is discarded and warns that "spacing, line breaks, fonts, and complex elements can shift."

It's worth being precise about the word "editor" here, because several products in this camp use it. Xodo Sign and Adobe Acrobat mean a PDF editor — annotate, redact, reorder pages, fill in a field. That's a genuinely useful thing, and it is not authoring. DocuSign's Web Forms come closest to native creation, and they're a Business Pro feature at $40/user/month; its own documentation notes that standalone forms "are not associated with a template and do not support signatures".

Contract-lifecycle and proposal software. PandaDoc, Oneflow, Juro, Proposify, Qwilr, Contractbook. These author natively and do it well. The catch is historically the price of entry: Juro publishes no pricing at all, only a "build custom pricing" calculator, and Oneflow has moved to quote-only, annual billing, starting at five users for its Business plan.

The interesting part is who sits in both camps. Oneflow's own feature comparison lists PDF contracts and "digital contracts" side by side, so it genuinely does both. PandaDoc does both too, has a real free tier with the editor included, and its Starter plan is $19 per seat per month.

So "we let you write the document" is not a differentiator, and it would be dishonest to sell it as one.

What the honest comparison looks like

Dropbox Sign and Juro are left out on purpose: we couldn't confirm their current pricing or authoring model from a public page on the day of writing, and a guess in a comparison table is worse than an omission.

What the table actually shows is narrower than "we're the only ones." Three products support both document models. The difference is the way in — whether you can get there on a free plan, without a seat minimum, an annual commitment, or a call.

What changes when both models share one engine

The thing that matters isn't that written documents exist in a product. It's whether they're a second-class mode.

That's the failure worth checking for when you evaluate any of these tools. A native editor bolted alongside a PDF pipeline tends to mean two sets of field types, conditional logic that only works on one side, and a separate audit trail. You find out which features didn't make it across after you've committed.

On Signvoy the two document types are a discriminator on one content model, not two products:

• The same field types. Signature, initials, text, date, checkbox, dropdown, radio group — assigned to whichever recipient should fill them, on either kind of document.
• The same conditional logic. Show, hide, or compute a field from an earlier answer. The rules engine never asks where the field is anchored.
• The same routing and reminders. Sequential or parallel order, per-recipient roles, CC recipients, reminder cadence, expiry dates.
• The same audit trail. An append-only event log plus a SHA-256 hash of the final PDF. A written document is exactly as provable as an uploaded one.
• The same output. A certified PDF, rendered server-side, that anyone can open without knowing how it was made.

The document format becomes a per-document decision instead of a purchasing decision. Some agreements should be PDFs because legal signed off on that exact layout. Some shouldn't be, because the wording changes every time. You don't need to predict the ratio before you pick a plan.

Where this approach is genuinely worse

Three things, stated plainly.

No redlining. There is no clause-by-clause markup, no suggested edits from a counterparty, no negotiation history. If a contract goes back and forth between two legal teams before anyone signs, that's what Oneflow and Juro are built for, and this isn't a close call.

A deliberately small editor. Headings, lists, quotes, bold, italic, underline, strikethrough. No tables, no images, no links, no manual page breaks — the constraint is that the server-side PDF renderer must reproduce every construct exactly, and anything it can't render is disabled rather than silently dropped. If your document needs a pricing table, upload it as a PDF.

No conversion path. You can't turn an existing PDF template into an editable document. A PDF is a layout, not structured text, so any automatic conversion is guesswork about where paragraphs start. Paste the wording into a new document instead, or keep the PDF as a PDF — both live in the same template library either way.

Try it on the document you're avoiding

The test that actually tells you something isn't a blank page. It's the agreement you've re-uploaded three times because a clause keeps moving.

Write that one out, drop the fields into the sentences where they belong, and then change a paragraph. If the fields are still where they should be, the upload-first model was costing you something you'd stopped noticing.

Start on the free plan — writing documents is included on every tier, including Free. Or read more about how the document editor works.