A founders' agreement needs three signatures. You've signed already. Now you need to route the file to two co-founders, get their signatures, and end up with one clean PDF carrying all three. Done right, every signature is valid. Done wrong, the first signature is invalidated by the second.
The order matters
Most e-signature systems treat the act of signing as a sealing event. After your signature is applied, any further change to the document — including someone else's signature — can break the integrity check.
The fix is to use a signing flow that's aware of multiple signers and applies each signature in sequence without re-flattening the file. Tools that just 'edit and add a signature image' will quietly invalidate earlier signatures.
Using Flint for sequential signing
Flint's signing flow supports multiple signers in order. Add the document, place fields for each signatory, and route the file to each in sequence. Each signer applies their signature in their own browser; the document is updated incrementally without breaking the chain.
The end state is a single PDF with every signature applied and a single audit trail covering all of them.
Common patterns
Sequential: you sign, then your CFO, then your investor. Used when later signers want to see earlier signatures first.
Parallel: all three signers sign at the same time, in any order. Used when there's no review dependency.
Witnessed: one signer signs, a witness countersigns. Used for deeds and some employment documents.
FAQ
Can I just sign and forward the PDF for the next person to sign?
Some tools allow this; many don't. Each subsequent signature adds a new revision. If a downstream signer 'flattens' the PDF, earlier signatures may be reduced to images and lose their cryptographic integrity.
How many signatures can a PDF hold?
There's no fixed limit. Practically, contracts with 5–20 signatories are routinely handled by serious e-signature tools.
Does each signer need a Flint account?
They need to be able to open the link Flint sends them. No long-lived account required for the signer in most flows.
What if one signer declines?
The document remains in an unsigned state. The audit trail records the decline. You can cancel the request or revise the document.
Three or thirty signatures, the principle is the same. Use Flint's signing flow and keep every signature valid.