Loading
Because signing usually happens in a separate tool. The executed PDF ends up in the inbox of whoever sent it, and finding it in two years depends on that person still working there.
E-signature sends the proposal or contract for signature from the deal, tracks its state, collects the countersignature and stores the executed document against the record.
The request, every view, each signature and the completion certificate are recorded on the deal. Reaching signed state can move the stage, notify delivery and open billing without anybody re-keying anything.
A dispute over scope at Kanaka Foods was settled from the deal page: the executed contract, the version history showing the clause added at the customer's request, and the date they signed it.
Treepie records the signing process and keeps the evidence. Whether a given signature is legally binding in your jurisdiction is a question for your own advisers, not a claim this page makes.
Reaching signed can trigger stage automation, open Loop delivery phases from the sold lines, and let Books schedule billing against the agreed terms.
Yes, in the order you set, with each signature and its timestamp recorded.
On the deal, with the completion certificate. It is not only in email.
Yes, through the API. The record and the state tracking stay in Treepie either way.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.