I’m a VP Finance at Aegis Software, and HarborOS started as the tool I needed for my own finance work. The problem I kept running into was not that ARR was hard to calculate once. It was that every board cycle, renewal meeting, forecast update, and month-end close seemed to recreate the same question from scratch: Why did the number change? The CRM had one version of the future. The ERP had one version of the past. The board deck had the polished answer. The contract usually had the truth, but getting back to it was slower than it should have been. So I started building HarborOS around a simple belief: the contract should be the source record for revenue truth. ARR, renewals, churn, expansion, forecast changes, and variance should all tie back to the contract record and the snapshot in time when the team believed the number. Not a spreadsheet that gets overwritten. Not a manual bridge rebuilt before every meeting. We now use HarborOS against live production data at Aegis, which has forced the product to stay practical. It has to answer the questions finance actually gets asked, especially when the number moved and everyone wants the story behind it.

HarborOS

The contract intelligence layer for SaaS finance teams

The contract intelligence layer for SaaS finance teams