The signature
closes the loop.
A signature should stay connected to the job. Sigil sends the proposal already in the record for signature and tracks it from sent to viewed to signed, and shows which downstream steps, such as the invoice and the handoff, are still pending.
The pains the founder built it against.
- 01.A signed proposal that lives in a separate e-signature tool's inbox — not the job record — so the next person on the account has to go looking for it, or never finds it at all.
- 02.The manual step after a document is signed: someone has to remember to raise the invoice, log the activity, and email the customer their copy. Miss the step and the job sits half-started.
- 03.A per-envelope or per-seat fee on top of everything else in the stack, for a tool that does one thing: get a signature on a document you'd already written.
- 04.No record of whether the customer actually opened it — a signature request that went out three weeks ago and nobody knows if it was ever seen.
The tools that ship together.
Send proposals, contracts, and change orders for signature from the job record, and track their progress inside Forge. Nothing is retyped into a separate tool, and the signing experience is a real e-signature flow, not a PDF and an email.
Draft, sent, viewed, signed, completed, declined, expired, voided — the envelope's real state, visible against the job it belongs to. No more wondering whether a signature request three weeks old was ever opened.
The moment a document completes, Sigil fires what comes next: the invoice, an activity record on the job, and a signed-copy email to the customer. Each step reports its own status back, so a failed send is visible, not silent.
A signed agreement doesn't dead-end in an inbox. It attaches to the job record it belongs to, so the next person on the account — scheduling, the field, billing — is working from the same signed document, not a copy someone forwarded.
On the menu.
The honest answers,
without the sales gloss.
Sigil uses an electronic-signature flow built to the same US standards (ESIGN Act / UETA) that other major e-signature providers follow. Whether a specific agreement type requires a wet signature or additional formality is a question for your own counsel, not something this page decides for you.
The envelope's status stays visible as sent, viewed, or expired — it does not silently disappear. Nothing else fires until it completes: no invoice, no activity record, no handoff.
For documents already in the Forge job record — proposals, contracts, change orders — yes: sending them through Sigil means the signature and the job stay attached to each other. Sigil is not a general-purpose document tool for paperwork that has nothing to do with a job in Forge.
The invoice, an activity record on the job, and a signed-copy email to the customer are triggered automatically. Each is its own step with its own status — if one fails (a delivery issue, for instance), that shows up rather than failing silently.
Hire Sabina — she works inside Forge, at hiresabina.ai.
Or run Sigil on its own — custom quoted.
Start with a short operational assessment of your business.