E-Sign Contract Sender

What it does

Builds or adapts a complete e-signature application: a sign page for the recipient, signed PDF generation with an audit certificate, automatic reminders, and an admin panel for the contract owner. Integrates into an existing Next.js + database app or deploys as a fresh project.

When to use it

• Needing to send a contract for signature without relying on a paid external service
• Wanting to integrate e-signature directly into your own app or client portal
• Automating follow-up on pending contract signatures within a GoHighLevel sales flow

Steps

1. Decide whether to integrate into an existing app or deploy a new project
2. Configure the sign page with the contract's fields and clauses
3. Implement signed PDF generation with a validity certificate (timestamp, IP, hash)
4. Set up automatic reminders for pending signers
5. Build the admin panel so the owner can see each contract's status
6. Test the end-to-end flow before sending any real contract to a client

The skill

---
name: e-sign-contract-sender
description: Ship a self-hosted e-signature app (sign page, signed PDF with audit certificate, reminders, admin panel) for your own stack or Vercel.
---

# E-Sign Contract Sender

## When to use it
When you need to send contracts for signature without paying for an external provider subscription, or want to integrate e-signature directly into your product.

## App components
Public sign page, signed PDF generator with certificate (timestamp, IP, integrity hash), reminder system, admin panel for the owner.

## Deployment options
Integrate into an existing Next.js + database app, or deploy as a standalone Vercel project.

## Signer flow
Receives the link, reviews the document, signs, gets a copy of the certified PDF by email.

## GoHighLevel connection
Signature status (pending, signed) can sync with the client's pipeline stage in GoHighLevel to trigger the next sales step.

## Safety rules
Every contract is previewed before sending; nothing is ever sent automatically without explicit user approval. Never invent clauses or signer data. No API keys or email provider credentials exposed in chat.

For Claude Code, save it as ~/.claude/skills/e-sign-contract-sender/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.