Upload the whole file.
Get the whole answer.
Contract, addenda, disclosures, inspection, HOA — read together, not one at a time. You get one plain-English report you can forward, a chatbot your agents can ask instead of texting you, and a portal where their clients can see where things stand.
Your first home is free, listing or contract. Start to finish.
- One forwardable report
- A chatbot for your agents
- A portal for their clients
- No per-seat fees
- 50-state coverage
- AI document analysis, not legal advice
You are not behind.
You are outnumbered.
Nothing about coordinating is hard in isolation. It is hard because it arrives twenty-five times at once, and every file assumes it is the only one you have.
- Thirty to eighty pages. Per file.
The contract is the short part. Then come the addenda, the seller disclosures, the inspection report, the HOA packet, the title commitment. You read all of it, because you are the only person on the deal who will.
- The same six dates, typed four times.
Effective date, inspection, financing, appraisal, closing. Out of the contract, into the TMS, into a calendar, into an email to the agent. Every re-key is a chance to be off by a day on something that matters.
- You are a human status API.
Agents ask you things that are already in the file. Clients ask the agent, who asks you. The answer is almost always on a page somebody already has — but you are the one who has to go find it and say it out loud.
- Deadlines collide across files.
Twenty-five concurrent files means twenty-five sets of deadlines running at once. Nothing in your stack tells you that three inspection windows all land on the same Friday until the Friday.
Three deliverables.
One file.
You drop the packet in once. What comes back is not a summary of one document — it is the read on the whole file, plus two surfaces that answer questions so you do not have to.
Forwardable, plain-English, and built to be sent as-is.
The report is the read on the whole file, in one place.
- Every deadline pulled out with the date it derives from.
- Every red flag with the page it came from.
- Conflicts between the contract and an addendum surfaced side by side, because they were read together instead of one at a time.
- Send it to the agent without rewriting a word.
They ask the file. Not you. At eleven at night.
Every file comes with a chat surface grounded in the actual documents in that file.
- Your agent asks when the financing contingency expires or whether the HOA allows a short-term rental, and it answers from the page — with the citation attached.
- The questions that used to arrive as a text at 11pm stop arriving.
When does the financing contingency expire?
The buyer or seller gets a page, not a phone call.
A branded status page showing where the transaction actually stands, plus a chat scoped to what that client is allowed to see.
- The agent looks organized.
- The client stops asking for updates.
- Neither of those messages routes through you first.
Chat shows only what this client may see.
Other tools read the contract.
Contre reads the file.
Contract-level tools do a real job well: they pull the fields out of the purchase agreement. A file is bigger than its contract. The addenda amend it, the disclosures qualify it, the inspection triggers it, and the HOA packet can quietly contradict all four. Reading those together is a different job.
| What you compare | Contract-level toolse.g. ListedKit | ContreWhole-file intelligence |
|---|---|---|
| What gets read | The purchase agreement | Contract, addenda, disclosures, inspection, HOA |
| Cross-document analysis | Each document on its own | Documents read against each other, conflicts surfaced |
| Agent-facing chat | Not included | A chatbot per file, answering with citations |
| Client-facing surface | Not included | A branded status portal with scoped chat |
Competitor capabilities are as publicly listed at the time of writing. Both tools are worth the money for what they do — they are simply scoped to different units of work.
You are the judgment.
We are the read.
A tool that invents a deadline is worse than no tool, because you would have to check all of them anyway. So the system is built to be checkable: every claim points back at the page it came from.
- Every alert cites its source
Nothing is surfaced without the document and location it was drawn from. If the report says the inspection period ends on the 14th, you can see the clause that says so. Findings that cannot be traced to a document do not make it into the report.
- Fields are verified, not assumed
Extracted values are re-checked against the source text before they reach you, and low-confidence reads are flagged for review rather than quietly presented as fact. When the file is genuinely ambiguous, you get told it is ambiguous.
- Nothing gets decided for you
Contre never sends, files, waives, or signs anything. It reads and it reports. The coordinator stays the coordinator — this is leverage on the reading, not a replacement for the person doing the work.
AI document analysis, not legal advice. Contre surfaces what the documents say and flags what looks inconsistent. It does not interpret the law, and it is not a substitute for review by a licensed attorney or your managing broker.
Questions from
coordinators
Your first home is free, listing or contract. Start to finish. For a coordinator, a home is one file, and a file means the whole packet — contract, addenda, disclosures, inspection report, HOA documents — not each document on its own. There are no per-seat fees, no monthly minimum, and no contract.
Purchase and sale agreements, addenda and amendments, seller property disclosures, inspection reports, HOA documents and CC&Rs, title reports and commitments, loan and financing documents, counter offers, contingency removals, termination notices, and general transaction correspondence. PDFs, scanned images, and multi-page documents are all supported. The point is that they are read together — an addendum that changes a date in the contract is caught because both were read as one file.
All 50. Contre reads the documents you actually upload rather than relying on a fixed library of one state's forms, so state and local association forms, brokerage-specific addenda, and custom paperwork are all handled. There is no waiting list for your market.
You invite them to the file. Each transaction gets a chat surface grounded in that file's documents, and you send your agent an invite to it. They ask questions and get answers with citations back to the source page. They do not need to buy anything, and there is no per-seat charge for adding them.
A branded status page for their transaction — where things stand, what has happened, what is coming — plus a chat scoped to what that client is permitted to see. Clients never see the full document set or anything belonging to another party unless it is shared with them. Your agent looks organized, and the update requests stop routing through you.
Documents are encrypted in transit and at rest, with strict isolation between accounts so nothing you upload is visible to another coordinator or brokerage. Your data is never used to train models and never shared. Access to a file is limited to the people you invite to it.
No, and it is not trying to. Open To Close, Trackxi, and similar platforms own task automation, checklists, and workflow — they do that job well and Contre does not attempt it. Contre is the intelligence layer that sits alongside them: it reads the file and tells you what is in it. Keep your TMS and keep your process.
Yes. AI file review is a service your agents want. You can add it to what you charge for a file, or sell it as an upgrade. You set what you charge them.
Run one file.
Judge it on that.
Take the next packet that lands in your inbox — contract, addenda, disclosures, inspection, HOA, all of it — and upload it. Read the report against the file you already know. If it does not tell you something you would have had to find yourself, you have lost nothing.
Your first home is free, listing or contract. Start to finish. No per-seat fees. No contract.