Can I vibe code DocuSign?
Send documents for legally binding e-signatures.
The mechanics are very buildable: upload a PDF, place signature fields, email a signing link, draw-or-type a signature, flatten it into the file, log every step. That's a weekend. What you can't vibe-code is the legal weight: court-tested audit trails, compliance certifications, and the counterparty trust that comes from a name their lawyers recognize. Fine for low-stakes agreements; use the real thing when it matters.
Build a lightweight e-signature app for low-stakes documents (make the low-stakes framing explicit in the UI). Flow: I upload a PDF, drag signature and date fields onto pages (render with pdf.js), enter the signer's email, and send a unique tokenized link. The signer sees the document, signs by drawing or typing, and the server flattens the signature into the PDF (pdf-lib), stores it, and emails both parties the signed copy. Keep an append-only audit log (opened, viewed, signed, IP, timestamp) shown on a /audit/[id] page. Next.js, database + object storage, deployable to Vercel.
A signing flow: upload PDF, drop signature/date fields, send a tokenized signing link, capture the signature, emit a flattened signed PDF plus an audit-log page.
- Court-tested evidence packages and compliance certifications (ESIGN/eIDAS posture)
- Counterparty trust — clients hesitate at unfamiliar signing domains
- Identity verification options beyond email possession
- Templates, bulk send, and CRM integrations
When a contract might end up in front of a judge, nobody wants to explain their homemade audit trail. The brand is the compliance story.
A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.
Start Course 01 →