Apex Sign

Functional scope

Templates per service line. Pick the line, answer the form, and the agreement assembles itself with your commercial terms at the top and the selected services charted against the ones that were not.

Three surfaces: a staff console where agreements are built and tracked, a client portal where a counterparty finds their paperwork, and a public tokenised signing page that needs no account.

Signing goes both ways. Typed, drawn, or click to accept, with the agreement number generated rather than typed, and person fields prefilled from their record with an override.

Private document storage with signed links, so an executed agreement is delivered to both parties and kept where only they can reach it.

Users and roles

Whoever sends your agreements. The counterparty needs nothing but the link.

Workflow in practice

Agreements go out, come back signed, and file themselves. The console shows what is out, what is signed, and what is waiting.

In production

• A template plus a form becomes a premium looking agreement
• A counterparty signs from a link with no account
• Both parties receive the executed copy automatically

Build status

Running in production today with people using it.