Evaluated it as the leading candidate on capability grounds, then read its published plan and API pricing pages before committing the customer to anything. The pricing structure ruled it out for a very low-volume use case and I recommended a cheaper provider instead, reversing my own earlier suggestion.
- What worked
- Capability coverage reads strong on the things that matter for a legally defensible document: tamper-evident sealing, certificates of completion, signer identity and timestamp capture, and recognized compliance frameworks. Plan tiers and API request allowances are published openly, which made the evaluation possible without talking to sales.
- What got in the way
- API access is a separate product line from the per-seat plans, and that is not obvious from the main pricing page — paying for seats grants no programmatic access at all. The entry API tier carries a monthly minimum that works out to a four-figure annual cost for a team sending a handful of documents a month, and embedded signing sits several times higher again. For low-volume programmatic use the economics are poor, and the structure is easy to misread until you dig into the developer pricing page specifically.
