Sign. Automate. Move on.
The full journey to digitise a client document, get it signed and keep it. It is built to earn trust through the clarity of its steps, without copying an existing tool or showing a fake certification badge.
FlowSignContext
Getting a client to sign a document takes two people, several tools and an unreasonable amount of manual chasing.
Who it is for : Employees who get a document signed, and the clients who sign it
The problem
The signature itself takes a few seconds. The cost is everything around it: re-entering the information, checking it is right, chasing the client, then finding the document again once it is signed. On a legal subject, the smallest approximation eats into trust.
My insight
On a legal subject, trust does not come from a reassuring badge or from an interface that looks like a well-known provider. It comes from the clarity of the journey and from saying honestly what you do and do not do.
My solution
The employee imports a PDF, the tool pulls the information out of it, they check and correct it, confirm the phone number, then send the link by SMS. The client reads the document, accepts the wording, signs with a finger on their screen, and gets back a signed copy generated on their own device. Extraction and dispatch are simulated in this version.
Product hypothesis
If every step is explicit, verifiable and correctable by the user, the journey should earn trust without needing to claim a certification.
My role
- Product framing: brief, MVP PRD, decisions, roadmap and backlog
- Full-stack monorepo architecture (web, API, shared types)
- UX/UI design of the step-by-step journey
- Front-end and back-end development (React, Express, Prisma, Zod)
- File handling: PDF parsing, upload, canvas signature
- Documentation of the sensitive product semantics
- Unit and API testing
Evidence & quality
- Full-stack architecturenpm workspaces monorepo: React front-end, Express API, shared types.
- 10Test filesUnit and API tests (Vitest, Supertest).
- Product documentationBrief, MVP PRD, decision log, roadmap/backlog and sprint handoff.
Key decisions
Do not imitate an existing e-signature tool
Borrowing the visual codes of a certified provider would suggest a legal value this version does not have. The journey states in plain text: fictional data, not certified.
Trade-offAt first glance it is less reassuring than an interface people already know.
Document the sensitive semantics before writing code
Evidentiary value, retention, identity, personal data. Each of those words commits you to something precise. I defined the meaning and scope of every term in writing before letting it appear on screen.
Generate the signed copy locally
The signature is drawn in the browser and the final document is built on the client’s own device. Nothing sensitive leaves for a third-party service.
Trade-offNo qualified timestamping or sealing, which is consistent with the scope announced.
Stack
- React
- TypeScript
- Express
- Prisma
- Zod
- pdf-lib
- Vitest