Product — CovenantAI
The deadlines that cost money live inside documents nobody has time to read.
Draws, lien waivers, certificates of insurance, loan covenants, lease options. Every one of them has a date attached, and every one of them arrives as a PDF in somebody’s inbox. CovenantAI reads the documents and turns those dates into a schedule that is tracked rather than remembered.
Where this stands
CovenantAI is a working product. It is not a client story.
We have not run a delivery engagement in construction or commercial real estate, and we would rather say that first than let you find it out on the third call. What we have is software that runs, which you can watch work on a document of your own choosing. For most buyers that is the stronger evidence anyway: a demo on your paperwork survives questions that a case study does not.
The dates in question
Five obligations, one filing cabinet
None of these are hard to manage once somebody has written them down. The work is the writing down, and it has to happen again every time a document arrives.
- Draws
- Submission windows, and the documents each one has to arrive with.
- Lien waivers
- Which tier owes which waiver for which period, and what is still outstanding.
- COI expiries
- Certificates that lapse quietly until somebody notices at the worst moment.
- Loan covenants
- Reporting dates and financial tests, set out in a document read once at closing.
- Lease options
- Renewals, escalations and go-dark rights that matter on one specific date.
What it does
Read the documents, produce the schedule, watch the dates
The obligation schedule is the output that matters: what is owed, to whom, by when. It is built once from the documents, confirmed by a person, and then monitored.
- Reads contract documents and returns structured terms
- Extracts covenants, deadlines and key terms into one obligation schedule
- Tracks compliance against those dates instead of leaving them in a spreadsheet
- Answers plain-language questions about a document set
- Exports and schedules reports, with calendar reminders
Checking it
We build extraction so it never has to be trusted on its own.
An extracted date you cannot check is worse than no date, because it gets believed. So a document build we scope returns every term with a pointer to the page and clause it was taken from. Verifying one takes seconds, and the review happens over a list rather than over a stack of PDFs.
That is the division of labour we build to everywhere. The system does the recall across a document set no person has time to re-read. A person makes the call on the one that matters. It finds the needle; you confirm it.
Why deadlines first
A missed date caught a week late is recoverable. A wrong number in a distribution is not.
Dates and dollars live in the same documents, so the obvious question is why we start on the calendar. Two reasons, and both are about the cost of being wrong.
The first is consequence. A deadline surfaced late is embarrassing and usually fixable — you call the lender, you file the report, you renew the certificate. A recovery, a coverage ratio or an escalation that goes out wrong is not fixable in the same way, because somebody has already acted on it.
The second is the cost of checking. A date is verifiable in seconds against the clause it came from. A calculated figure is only verifiable by rebuilding it, which is precisely the work you were trying to remove. Cheap verification is what makes the first version of anything safe to use.
So obligations and the calendar first, arithmetic later, and only once the extraction underneath it has earned some trust. That is the same sequencing we apply to every build. How the Proof Build works
Being straight about it
What we are not claiming
- We have not delivered a client engagement in construction, CRE or CRE lending. This is working software, not a case study.
- It does not replace Procore, Yardi, MRI or Sage 300 CRE. It sits above them and reads the documents, which is a different job.
- Nothing downstream should depend on an extracted term until a person has confirmed it against the clause.
Built for: construction lending, law firms, contractors, commercial real estate
Where we would start
One workflow. Four to six weeks. Fixed fee.
Document extraction with a deadline calendar, running on the mailbox and the documents you already hold. We would not propose integrating with Procore or Yardi to begin with. Vendor interface access is licensed and quoted case by case, so the question worth asking before anyone scopes a build is what your vendor quoted you. The documents and the mailbox you already own outright, and they need no approval at all.
Before we start, we agree in writing the number the build has to hit. If it does not hit it, we keep working at no additional cost until it does.
$6,000
credited in full against month one of any retainer started within 30 days
Everything is built inside your own Microsoft tenant, and you own the code.