Built for the forms nobody else will touch.
Two-page contracts are solved. What is not solved is a nine-page application about six people, where the same ID number is asked for three times and only one of them is labelled. That is the document this product was built around.
- undefined_3member.id_number
- Text Field 47spouse.date_of_birth
- Check Box 12member.smoker
- undefined_58dependant_2.relationship
- Signature1member.signature
Ready to send. No fields to drag.
The form never knows who Dependant 1 is. We do.
A medical scheme application asks for a member, a spouse and four dependants — six sets of the same twelve questions, in six places, answered by one person. A field-and-signature tool sees 284 unrelated boxes. Vumasign sees six subjects, asks each question once, and puts the answers everywhere the form repeats them.
Nobody builds that for a two-page NDA. It is the reason the hard forms work here.
The PDF you already use, read in a minute.
Upload the form and every field on it is found, named and placed — including the ones drawn as a grid of single-character boxes, which most tools treat as a picture. You correct what is wrong rather than building 284 fields by hand.
The correcting is the product. The finding is what makes correcting worth doing.
Asked once, even when the form asks four times.
A question is asked of a subject, not of a rectangle. An ID number that appears on pages 2, 7 and 9 is one question and one answer, typed once — and it validates as an ID number while it is typed rather than after the signer presses Sign.
Sealed on completion, verifiable without us.
When the last person signs, the answers are flattened into the document, a Certificate of Completion is appended, and the whole thing is sealed with a trusted timestamp. Change a byte and the seal breaks — in the reader’s own software, with no account and no request to Vumasign.
The forms these numbers came from.
Real South African benefit and insurance forms, counted as published. Scheme and fund names are withheld; the counts are not.
| Document | Pages | Fields | Subjects |
|---|---|---|---|
| Medical scheme application, employer group | 9 | 284 | member · spouse · dependant 1–4 · employer |
| Retirement fund nomination of beneficiary | 6 | 127 | member · beneficiary 1–6 · witness |
| Funeral cover application | 4 | — | member · spouse · children · extended family |
| Group life insurance application | 4 | — | member · beneficiaries · employer |
| Group life beneficiary nomination | 2 | — | member · beneficiary 1–4 |
Field counts are as published in the source PDFs. Scheme and fund names withheld on this page.
The things every product in this category has.
Listed because you would otherwise have to ask, and stated plainly because calling any of them innovative would be the first dishonest sentence on this site.
Build once, send many. Text tags for the people who prefer to mark up the PDF.
Sequential, parallel, or a mix. Approvers who sign nothing and still have to say yes.
One template, a list of recipients, one batch.
Your logo and colours on the signing screen and the emails. Your own sending domain.
Chased automatically, closed automatically, both recorded.
A signature drawn on a phone, typed in a typeface, or photographed off paper.
Every event, with who and how they were identified. Exportable, and append-only.
Embedded signing on your own domain, and six events worth acting on.
Priced by the document, on every plan.
R7 on Team, R5 on Business, published. Building signing into your own product? The API plan is R500 a month with 50 included, then R10 each.
Open one of your own forms.
Upload the worst one you have. The fields it finds, and the ones it misses, will tell you more than any feature list.