7,000 files.
Every field.
Before we wrote a line of code.

Before OpsFlows verified a single document automatically, we verified thousands by hand. This is what we found — and how it became the product.

The problem

Most AI tools don’t know what an OACIQ mandatory document is.

They don’t know the difference between a brokerage contract and a declaration by the seller. They haven’t counted the 197 questions across 13 pages. They don’t know which fields are mandatory under the Real Estate Brokerage Act, which clauses require initials versus full signatures, or what a blank GST/QST status means for a transaction.

Generic document AI reads text. Compliance verification requires knowing what the text is supposed to say — field by field, regulation by regulation, form by form. That knowledge doesn’t exist in a language model. It has to be built.

The process

We read everything before we built anything.

7,000 real transaction files from Quebec brokerages. Every mandatory document. Every filled field. Every error, omission, and edge case — reviewed manually before a single line of code was written.

Collect real files

We sourced 7,000 transaction files from active Quebec brokerages — brokerage contracts, declarations by the seller, counter-proposals, and mandatory disclosures.

Map every required field

For each mandatory form, we identified every required field, its clause reference, its validation rules, and what a missing or incorrect entry means under OACIQ regulations.

Document every edge case

Conflicting addresses, unsigned amendments, co-seller ID mismatches, partial GST exemptions — every real-world deviation was catalogued and built into the verification logic.

Key findings

What 7,000 files taught us.

197

questions across 13 pages

Declaration by the Seller

Every question is mandatory. Every blank is a liability. Each declaration implies a detailed explanation the system understands and detects. We mapped each one — what it asks, which clause it ties to, what a missing answer means for the brokerage during an inspection. Each mandatory form required by regulatory bodies is fully mapped out before integration into our AI.

sections across 11 pages

Brokerage Contract

Remuneration, GST/QST status, seller ID type, contract number, broker signatures — 15 sections, each with required fields that must be present, correctly formatted, and internally consistent.

34s

average automated verification time

vs. 45 minutes manually

Once the field-by-field logic was built from the file review, the same verification that took a compliance admin 45 minutes could run in under a minute — with greater accuracy and a full audit trail.

What it became

The knowledge is in the product.

Every rule inside OpsFlows came from a real file. The verification logic wasn’t built from OACIQ documentation alone — it was built from watching what goes wrong in practice. Missing initials on page 7. A broker signature present on the cover but absent on the amendment. A property address that doesn’t match the cadastral entry.

When OpsFlows flags an issue, it cites a clause. When it passes a document, it has checked every required field against the same rules we derived from 7,000 real transactions. That’s not an approximation — it’s the standard.

See it on your files.

No commitment. Your data stays in Canada.

7,000 files. Every field. Before we wrote a line of code.