Contracts
Where external systems become canonical records.
Every contract starts somewhere else — a CRM, a shared drive, a forwarded PDF. Contracts is where HarborOS ingests, extracts, reconciles, and promotes those records into the canonical system. One gate in. One record out. Every field traceable to the clause it came from.
Belknap & Hart
Your contracts live in four systems. None of them agree.
A renewal closes in Salesforce. An amendment arrives in email. A PO uploads to a shared drive. The signed PDF lives in someone's inbox. Four sources, four versions of the same contract — and a VP of Finance reconciling them in a spreadsheet before the numbers mean anything.
The problem isn't volume or data entry. The problem is that no system owns the contract as a structured, extractable, lifecycle-aware record. CRMs track deals. ERPs track invoices. Neither one models the contract itself — the terms, the clauses, the renewal chain, the escalators, the commitments that every downstream number depends on.
Connect once. Ingest continuously.
Contracts connects to Salesforce, HubSpot, Attio, Pipedrive, Google Drive, and OneDrive. It reads opportunities, deals, and documents on a configurable cadence — no CSV uploads, no manual imports, no copy-paste.
When a deal closes or a document lands, the system sees it. Every connector reports its own health; when something stops syncing you find out here, not three weeks later when the numbers stop matching.
One record. Every field traced to a clause.
The contract record in HarborOS isn't a row in a spreadsheet or a field on a CRM opportunity. It's a structured, lifecycle-aware object — ARR, term dates, renewal chain, escalators, auto-renew terms, billing schedule, and every field citing the clause it was extracted from.
This is the atom. Everything downstream — renewals, pipeline, forecasts, snapshots, board reporting — derives from this record.
Parse, match, flag, resolve.
Incoming records are parsed and matched against existing contracts. When a renewal in HubSpot matches an active contract, the system links them automatically. When fields conflict — different close dates, mismatched amounts, overlapping terms — the system flags the conflict and stages it for operator review.
Nothing enters the record silently. Promotion is an explicit act — reviewed, confirmed, traceable.
If you can't trust the record, you can't trust anything downstream. The contract is the atom — every number in the system traces back to it.
Contracts is the foundation. Every surface in HarborOS reads from the contract record.