You give Harbor your contracts.
Harbor builds your renewals model.
You get a weekly, defensible forecast.
The CRM owns deals. The ERP owns invoices. The CSM platform owns health scores. But the contract lifecycle — the single dataset a PE board uses to underwrite recurring revenue quality — lives in a spreadsheet that gets rebuilt from scratch every quarter.
The renewal pipeline is in someone’s head. The reforecast is a guess dressed up in Excel. The board pack gets assembled manually, under pressure, the night before it’s needed.
You describe how your contracts work in plain language — five sentences. Harbor reads every document, every CSV, every CRM export through your rules. The renewals table builds itself.
The CFO locks a snapshot. The system compares it to last week. Every dollar of movement is traced to a specific contract decision. The audit trail PE firms have never had.
Every number is paired with an assumption. Not just what Harbor extracted — why it made that call.
A deliberate act. The CFO reviews, commits, reports. Immutable once locked. The number is a fact.
Any two snapshots, side by side. Headline deltas, contract-level changes, rollforward movement. The diff writes itself.
AI-generated variance summary from the diff. The CFO reads it, confirms it matches judgment, and sends. The board pack paragraph writes itself.
HarborOS runs on live production data at a PE-backed software company. Real contracts. Real board prep. Real weekly operating rhythm.
It was built by the VP of Finance who needed it — not a product team that studied the problem from the outside. Every feature exists because it solved a specific, recurring pain in the weekly reforecast workflow.
Multiple tenants are live. The system handles multi-entity, multi-currency operations across US and EMEA. The architecture was designed for PE portfolio deployment from day one.