Built by people who lost $2M on a claim.
Clerxi was born from a real loss — a $2M claim that was winnable but couldn't be recovered because the documentation didn't exist. That experience became the foundation for everything we build: a system where every deadline is tracked, every claim is preserved, and every dollar is protected.
We didn't set out to build software. We set out to never lose another claim.
Clerxi's founders spent years running construction crews on public-works projects — bridges, schools, municipal water, pavement, the kind of work where every change order has a seven-step paper trail and every missed notice window can wipe out a quarter of margin. We learned the trade on the job, not in a conference room. We bid the work, ran the crews, signed the certified payroll, and chased the retention.
The $2M loss wasn't a freak event. It was a slow accumulation of small things: a delay notice that went out two days late, a differing site condition logged in a foreman's notebook instead of an RFI, a daily report that lived in someone's truck. By the time the dispute went to mediation, the proof we needed was in seventeen places — none of them admissible. The claim was winnable on the facts. It was unrecoverable on the documentation.
We looked for software that would have prevented it. What we found were point tools — one for RFIs, one for daily logs, one for submittals — each living in its own silo, none of them tied to the contract terms or the notice windows that actually decide whether a claim survives. So we started building the thing that should have existed.
Four beliefs.
One mission.
Built for Trust
SOC 2 in progress. Role-based access. Every query scoped to your organization.
Built from Pain
Founded by contractors who lost $2M on a single claim. Every feature exists because something went wrong.
Built for Teams
Owners, brokers, carriers, and agencies — all connected through one shared data layer.
Built to Scale
650+ database tables. 12+ modules. From one crew to enterprise operations.
Why public-works contractors first.
Public-works contractors operate under the strictest paper regime in construction. Certified payroll. Prevailing wage compliance. DBE reporting. Buy America provisions. Notice windows measured in calendar days, not business days. A general contractor on a federally-funded job is responsible for documenting things a private commercial GC never has to think about — and the penalty for getting it wrong is not a difficult conversation with the owner, it is a withheld progress payment or a debarment letter.
That is also the segment where the documentation gap is most expensive. Margins on public-works work are tight by design. When a delay claim or a differing site condition gets disallowed because the notice was late or the daily report was incomplete, the loss does not come out of a contingency line — it comes directly out of overhead. We have lived that math. So we built Clerxi to enforce the timeline the contract already required: notices that fire on schedule, daily reports that link to the RFI they justify, change orders that carry their full provenance into the dispute file.
We start with construction because construction is where the founders earned the right to have an opinion. Owners, brokers, carriers, and agencies sit on the same data layer, but the system was designed contract-first, field-first, and dispute-first — because that is how the work actually gets paid.
We are not a construction-management add-on.
Most construction software treats the project as the unit of truth. You open a project, you log a daily report, you upload a photo, you close the project. The data lives inside the project record and dies with it. Clerxi treats the contract as the unit of truth. Every notice window, every escalation clause, every retention term, every flow-down to a sub — all of it is parsed once when the contract is loaded, and then the system drives the schedule of paperwork from those terms automatically.
The practical difference: a general construction-management tool tells you what happened. Clerxi tells you what is required to happen in the next 72 hours, who owns it, what the contractual consequence is if it slips, and what the downstream evidence chain looks like if a dispute opens later. RFIs are linked to the daily reports that justify them. Change orders carry the original RFI, the schedule impact, the cost backup, and the owner correspondence in a single immutable record. When a claim opens, the dispute file is already assembled.
We are also opinionated about integrations. The platform ships with 12+ modules built natively on a shared 650+ table data model rather than stitched together from acquisitions. That matters because the moment a notice fires in one module, the consequences ripple correctly through billing, scheduling, and compliance without an export, an import, or a reconciliation report.
"We built Clerxi after losing over $2 million on public works projects — not because we did bad work, but because we missed a 5-day notice deadline buried in page 847 of the Special Provisions."
Where we are on compliance and security.
We will be specific because construction data is sensitive and our customers ask us this on every diligence call. Clerxi is currently SOC 2 Type II in progress. We are mid-audit, not certified, and we will say so on this page until the report is issued. We would rather be slow and accurate than fast and misleading.
On the underlying controls: all customer data at rest is encrypted with AES-256. All traffic in transit is protected with TLS 1.2 or higher. Every read and write against the platform is captured in a tamper-evident audit log tied to the authenticated user, the organization, the resource, and the contract record involved — the same audit log that becomes evidence in a dispute. Access is role-based, every query is scoped to your organization, and we operate a least-privilege model internally.
If your procurement team needs the current security packet, the SOC 2 bridge letter, or a customer reference, write to support@clerxi.com. We answer diligence questionnaires in plain English with the underlying control descriptions attached — not marketing language.
The proof is in the architecture.
This isn't another SaaS tool duct-taped to a database. Clerxi was architected from the ground up.
Want to see the
platform?
Book a 15-minute demo and we'll show you how Clerxi works.