For contract teams

Your CLM is fine. Its signature bill is not.

The platform is not the problem. The signing layer bolted onto the end of it is. Here is what to ask for, and the request to send.

Get the requestTalk to us instead
Enterprise ready
AICPA SOC for Service Organizations badgeSOC 2 Type II
AES-256 at rest, TLS 1.2+ in transit
Built to satisfy ESIGN / UETA
HIPAA Ready
Learn more

The gap

Three things you are paying for that have nothing to do with your contracts.

You pay twice for one contract

Your contract platform subscription covers drafting, approval, and storage. The signature at the end is metered separately, by a different vendor, on a different invoice. Nothing about the contract got harder at that step.

You pay for people who barely sign

Seat licenses bill for access, not use. Half the people who need to send a document once a quarter are carried at the same rate as the person who sends forty a week.

You did not choose the signing vendor

It came bundled, or it was the only option the ecosystem offered. Either way the pricing model arrived with it, and switching it is not a setting you control.

What to ask for

Five things a signing layer owes you.

  • Charged on documents that actually complete, not on envelopes sent, opened, or resent.
  • Everyone who needs to send a document can, without a seat license for each of them.
  • An audit trail you can export, on a record you own.
  • Your templates portable, so the signing layer is never the reason you cannot move.
  • A documented REST API and webhooks, so the platform you already use can drive it.

The request

Send this to your provider.

It names no vendor and asks for a capability, so it is a reasonable thing to have in your inbox. Change anything you like.

Subject: Request: more eSignature options for our contracts

Hi,

We're happy with the platform, but the signing layer is the part that costs us. Today we're paying per envelope and per seat on top of our subscription, and the signing vendor wasn't something we got to choose.

We'd like to be able to use Propper as our signing provider. Propper offers a REST API with document lifecycle webhooks, embedded signing, and pricing based on completed documents rather than seats or envelopes, and its team says they work with platforms on exactly this kind of integration.

Could you tell us what it would take to support it, or put us in touch with whoever owns signing on your side?

You can reach them at partners@propper.ai.

Thanks
Open it in email

Questions?

Before you send it

We are not going to claim it does. Propper® offers a documented REST API and document lifecycle webhooks, which is what an integration would be built on, but there is no pre-built connector sitting there waiting for your platform. That is exactly why this page exists: the request has to come from you, because your provider decides what its ecosystem supports.

Tell us where your contracts live.

We will tell you honestly what is possible today, and we will take the request to your provider alongside you.

By submitting this form, you agree to our Privacy Policy.

Docusign®, Adobe Sign® and Acrobat Sign®, PandaDoc®, and Dropbox Sign® are registered trademarks of Docusign, Inc., Adobe Inc., PandaDoc, Inc., and Dropbox, Inc., respectively. Propper® is a registered trademark of PropperDocs, Inc.

PropperDocs, Inc. is not affiliated with, endorsed by, or sponsored by these companies.