← ALL WORK

CASE STUDY · 2024 · SAAS

HARBOR

Contract-lifecycle workspace, signature-first.

ROLE
Full-stack
YEAR
2024
STACK
Next.js · tRPC · Zustand

PROBLEM

Most contract tools treat the signature as the destination. The teams I built Harbor with treat the signature as a checkpoint — a single sealed moment in a year-long relationship that includes amendments, side-letters, renewals, and a quiet drawer of correspondence the lawyers all know about and the spreadsheet doesn't.

The status quo was a pile of PDFs in a shared drive, a DocuSign dashboard nobody could search, and a Notion page where someone tried to keep an index. Every quarter, a deal broke because two people were citing different drafts of the same clause.

APPROACH

Modelled the workspace around the contract, not the document. A contract is a long-lived object with versions, parties, milestones, and an audit chain — Harbor renders the same object three ways: as a lawyer's redline view, as a stakeholder summary, and as a signature surface.

Signature flow is one screen with no hops to a third-party iframe. Signers see the clause in context, not a flattened render of it. The signature event writes to an append-only log keyed by document hash; tampering with the original invalidates the chain.

Built a clause library where every paragraph that has ever been signed is searchable across the org, with provenance. Drafting a new MSA pulls the closest precedent and the negotiation notes that shaped it.

OUTCOME

Two design partners closed their first ten contracts on Harbor without bouncing to email; cycle time on standard MSAs dropped from a fortnight to roughly four days.

Internal counsel at one partner replaced a Notion + Google Drive + DocuSign stack with the workspace alone.

In private beta with seven design partners; pricing model and self-serve onboarding still being shaped.

CREDITS

Engineering & product
João M. Mota
Legal advisory
Two practising counsels (anonymised)

ELSEWHERE IN THE ARCHIVE

More stations