E3

Start here

How to evaluate E3
without a procurement process.

A working session on our files, or on de-identified files of your own. No NDA required to start the conversation, no sales sequence, and nothing installed.

Two ways in

Start with our files, or with yours

Most people start with the first. It costs you nothing and shows you the same thing.

OPTION A
A synthetic file, no data from you
We run a synthetic loan file end to end and walk you through it: what was read from each document, which rules ran, which were skipped, what was flagged, and what a reviewer sees. You send us nothing. Use this to judge whether the evidence is the shape your auditors would accept.
OPTION B
Your files, de-identified, outcomes you know
Three to five closed files whose outcomes you already know, ideally including one that was cleared and should not have been. That is the most informative test there is, because you can check our findings against what actually happened. De-identified, redacted or otherwise controlled historical files only, under a mutual NDA. See the constraint below before planning this.
WHAT YOU GET
The findings, and the working behind them
A walkthrough of each finding: the document and page each value came from, the rule version applied, the rules that did not run, and the exception as a reviewer would receive it. Plus an honest list of what E3 did not catch.
WHAT WE ASK
Your form mix and one rule set
Which loan programmes you run and which investor or agency requirements matter most. That is enough to configure a meaningful test.
SCOPE
Whole platform, or parts of it
E3 is API-first, so extraction, the versioned rule engine, and the evidence and lineage layer are separable services. If you want the rule engine behind your own reviewer workflow, or to deliver quality control to your own clients, modules can be contracted or licensed rather than taken whole. Scoped as an engagement, not bought off a shelf: see architecture.
HOW FILES REACH US
Delivered files. Nothing to build.
An evaluation needs no integration work: files are delivered into tracked processing sessions. Origination connectors, batch ingestion and mortgage data interfaces including ULDD are on the roadmap rather than available now: see intake.

Scope of an evaluation

What we work with, and what comes later

Worth knowing before you plan the session rather than after.

Evaluations run on sample, synthetic, redacted or appropriately controlled historical loan files. Use involving live borrower personal information follows completion of the security, privacy and customer controls programme now underway.

This is a real test of the product rather than a demonstration, and we will describe it accurately: it is an evaluation, not a production pilot on live originations. E3 runs today in a riTara-managed cloud environment, with customer-controlled private cloud and on-premises deployment on the roadmap.

If your timeline requires live borrower data inside your own environment, tell us early and we will be straight with you about where that work stands and whether the timing fits. Security and compliance certification is a current company priority.

Questions we expect

Ask these before you spend time on a session

If the answers are not satisfactory, the session is not worth your afternoon. We would rather you asked now.

What runs in production today, and what is still being built? We will answer this specifically rather than in general terms, and we will not describe a roadmap item in the present tense.

What have you measured? We do not publish an accuracy percentage, because we have not measured one against a stated document set that we could defend. We will tell you what we have tested, on what, and what we have not. A number without a method behind it is worth less than that answer.

What happens to our borrower documents? Answered on the home page and in the privacy policy before you ask. Short version: they are not training data, a third-party model does the reading, retention is contractual.

Who does the work on our side? One person who knows your QC standard, for about two hours across the session and the follow-up. We do the configuration.

How we would measure it

Agreed before the session, not argued afterwards

A demonstration proves a system can do a thing. Only a measurement tells you whether it does it well enough for you.

GROUND TRUTH
Your existing QC outcome is the answer key
Files whose outcomes you already know. Your recorded findings are what ours are compared against. Where we disagree, your reviewer adjudicates, not us. That is the only honest arrangement, because we have an interest in the result.
WHAT WE COUNT
Misses, false alerts, and time
Findings you recorded that we did not raise. Findings we raised that your reviewer rejects. And how long resolving our findings took against your normal review time. Three numbers, agreed in advance, computed together.
WHAT IT CANNOT TELL YOU
Three to five files is a signal, not a rate
A handful of files establishes whether a larger evaluation is worth authorising. It does not establish accuracy across a portfolio, and we will not present it as though it does. Anyone quoting a percentage off five loans is selling.
COST
The session and the first evaluation are unpaid
We are not charging for a proof of concept. Beyond that, pricing is not a per-page fee: it reflects cloud and model consumption plus the engineering to configure your programmes and rule sets. We will put a number and its basis in writing before you commit to anything.
WHERE IT LEADS
A decision, not another meeting
A good session should end in a scoped evaluation with written acceptance criteria. A good evaluation should end in an explicit decision: proceed to a production pilot, wait for named readiness work, or stop. We would rather hear a clear no than schedule a fourth call.

What happens next

Four steps, no sales sequence

1
You write to us
Tell us which option you want and roughly what you review. Two lines is enough.
2
We reply with times, and what to expect
A named person, not a scheduling sequence.
3
The session
About an hour. You see the product, not slides.
4
You decide whether there is anything here
If there is not, tell us and we will stop. We will not run a nurture campaign at you.

Ask for a session

Tell us what you review

Two lines is enough. A person reads this and replies; it does not enter a sales sequence.

We use this to reply to you and nothing else. It is not added to a marketing list. See the privacy policy. Or write to support@ritara.ai if you would rather not use a form.