Agreements and signature

Contracts on infrastructure you own

One line of natural language produces a branded, legally reviewed agreement with signature fields placed and an audit trail, running on a self-hosted signature platform under your own domain. It stays a draft until a human sends it. Always.

Who it is for
Operators sending recurring agreements, statements of work, and renewals who do not want their contract archive living in someone else pricing model.
Deployed for
Prospectr internal client agreements, plus client deployments running signature under their own subdomain.
Status
Live deployment
01

The goal

Remove the two hour gap between agreeing a deal on a call and getting a signable document in front of the person.

Keep the legal language consistent. Every clause comes from one master template rather than being reworded by whoever drafted this one.

Own the archive. Executed agreements are a permanent business record and they should not sit inside a subscription you can be repriced out of.

02

Cost, against the human alternative

What the build costs

The signature platform is open source and self-hosted, so there is no per-envelope or per-seat charge. The cost is deployment and the infrastructure it runs on.

The human alternative

Anchor title: Administrative Coordinator assembling and chasing agreements by hand, alongside a commercial e-signature subscription priced per envelope or per seat. An administrative coordinator runs a typical fully-loaded cost of $60,000 to $70,000 a year including payroll tax, benefits, paid time off, ramp time, and turnover. That is a market range for the title, not a quote of anyone actual salary. We have not benchmarked a specific competitor e-signature price and will not quote one we did not verify. The goal is not to replace that person. It is to put them in their most productive role. Rebuilding the same contract in Word for the ninth time is not why that seat exists. Onboarding the new client properly is.

The structural point is that cost stops scaling with volume. Sending your thousandth agreement costs what sending your first one did.

Redeployment, not headcount reduction

The goal is not to replace humans. It is to put them in their most productive role. Nobody gets cut here. Your billing manager stops doing data entry and starts working collections. Your GM stops chasing paperwork and starts selling. The agent absorbs the repetitive half of a job so the person keeps the half that actually needs a person.

This is a typical fully-loaded annual range for that title, meaning base pay plus payroll tax, benefits, paid time off, ramp time before the person is productive, and the cost of refilling the seat when they leave. It is a market range for the role, not a quote of anyone actual salary.

03

Security

  • Every agreement is created as a draft. The send endpoint is never called autonomously. The signing link is delivered to the owner, who sends it.
  • Terms are confirmed in writing with the owner before any document is generated. Getting terms subtly wrong is the expensive failure here, so it is gated rather than assumed.
  • All legal clauses come from one master template. The agent does not invent or reword legal language.
  • Self-hosted under your own domain, on your own database. The executed archive is yours.
  • Signing links are verified before delivery, so an agreement is never sent with a link that does not resolve.
04

Output

  • A branded agreement document with signature and date fields placed correctly.
  • A tracked signing workflow with an audit trail: who signed, when, and from where.
  • A delivery draft addressed to the owner, carrying the live signing link, ready to review and forward.
  • A void and recreate path for the case every operator eventually hits, which is a signed agreement that needs correcting.
05

Ongoing cost to maintain

  • Hosting and database, both of which are yours and both of which are flat.
  • No per-envelope pricing, no per-seat pricing, no annual renewal negotiation.
  • The genuine ongoing costs are certificate and credential rotation, which are scheduled maintenance rather than a vendor bill.
06

The framework that keeps it safe and keeps it cheap

  • Human in the loop is absolute. The agent never sends an agreement to a counterparty. The gate is in the design, not in a setting.
  • One canonical legal template, one canonical pricing source. The agent reads terms from the published source rather than reconstructing them from memory.
  • Self-hosted on infrastructure the customer owns, which is what makes the words no ongoing extortion in cost literally true rather than a marketing line.
  • Documented recovery paths for the failure cases, including credential rotation and voiding a sent document, so an incident is a runbook rather than a panic.

The procedures behind this

Each of these is a written document with a plain-English section for a person, a machine-readable section for the agent, and a dated changelog.

  • documenso
  • agreement-engine
  • documenso-signing-link-verification-gate
  • documenso-void-recreate
  • documenso-aurora-rotation-recovery

Where every claim on this page comes from

  • The never-send-autonomously rule, the draft-only default, and the confirm-terms-first gate are hard rules in skills/documenso/SKILL.md, with the terms gate carrying an owner directive dated 2026-07-14.
  • The single master legal template rule is a standing owner directive dated 2026-07-14 recorded in the same skill.
  • The platform is self-hosted under a Prospectr-owned subdomain, per TOOLS.md, which is what makes the no-per-envelope claim structural rather than aspirational.
  • Signing link verification, void and recreate, and credential rotation recovery each exist as separate documented procedures in the library.
  • Setup and term pricing quoted here are Prospectr published pricing dated 2026-07-14.

Questions people ask about this

Can the AI send a contract to my customer without me?

No. Every agreement is created as a draft and the send function is never invoked autonomously. The signing link is delivered to you, and you send it. This is a design decision, not a configurable preference.

Who owns the signed agreements?

You do. The platform is self-hosted under your own domain on your own database. There is no vendor holding your executed contract archive.

Does it cost more as we send more agreements?

No. There is no per-envelope or per-seat charge because there is no vendor in the middle. Your thousandth agreement costs what your first one did.

What happens if we need to correct a signed agreement?

There is a documented void and recreate procedure. It is a runbook, because this is a situation every operator eventually hits and improvising it is how audit trails get broken.

Is there a version of this in your business?

The discovery call is a working conversation, not a demo. Bring the process that annoys you most.