HOW IT WORKS
How Novarch catches back-office mistakes.
Novarch ties one job’s records together across your systems and checks them against how your business runs, whether a person did the work or an agent did.
-
CUSTOMER PORTAL
Autodesk
PO 4471 Rough-in, second-floor restrooms
-
EMAIL
Outlook Gmail
CHANGE ORDER 2 After-hours labor, approved
-
BILLING SYSTEM
QuickBooks Acumatica
INV 10233 Rough-in, second-floor restrooms
Novarch
TIES ONE JOB’S RECORDS
PO 4471 · CO 2 · INV 10233
CHECKS THEM AGAINST YOUR RULE
Approved change orders are billed at the T&M rate.Confirmed by Lena Ortiz, Billing Lead
FLAGGED
$1,136.00
Change order 2 is approved and not on INV 10233.
To your billing lead, with all three records.
STEP BY STEP
From how your business runs to a flag someone can act on.
- Billing policy
- Ops meeting transcript
- Email from the GM
DRAFTED AS A RULE
Approved change orders are billed at the T&M rate.
Checks that every approved change order on a job is on that job’s invoice, at the T&M rate.
CONFIRMED·Lena Ortiz, Billing Lead
STEP 01 · YOUR RULES
Your rules come from how your business already runs.
Novarch turns whatever you feed it about how your business runs into rules, and nothing applies until the person who owns it confirms.
More
It reads documents, meeting transcripts and email. Each rule is shown back to you in plain words, saying exactly what it will check. Your team can also write a rule directly, in the words it already uses.
EXAMPLES OF WHERE RECORDS LIVE
- CUSTOMER PORTAL Autodesk
- EMAIL Outlook Gmail
- BILLING SYSTEM QuickBooks Acumatica
- FIELD TICKETS A shared folder
READ-ONLY ACCESS SCHEDULED EXPORTS Nothing installed.
STEP 02 · YOUR SYSTEMS
It reads from the systems the work already passes through.
Read-only access or scheduled exports. Nothing in your systems changes.
More
Wherever the records live: a customer’s portal, your billing system, the folder the field tickets land in. You can revoke access at any time.
JOB 4471
PO 4471
Rough-in
Backflow test
CO 2
After-hours labor
INV 10233
Rough-in
Backflow test
not billed
STEP 03 · ONE JOB
Records for the same job are tied together.
The PO, change orders, field tickets and invoice sit side by side, so a rule can see what no single system shows: work approved in one place and never billed in another.
- Approved change orders are billed CODE FLAGGED
- Invoice stays within the PO CODE CLEAR
- Field tickets are signed CODE CLEAR
- Extra work matches the change order’s wording MODEL UNSURE·TO A PERSON
STEP 04 · THE CHECK
Code checks what it can. A model reviews the rest.
Most checks are settled in code. A model reviews only what code flags or cannot settle, and when it is unsure, the item goes to a person.
More
Every rule is checked against the whole trail, and a check settled in code gives the same answer every time.
YOUR QUEUE·1 FLAG
FLAGGED $1,136.00
Change order 2 is approved and not on INV 10233.
Rule: Approved change orders are billed at the T&M rate.
PO 4471 · CO 2 · INV 10233 attached
Bill it Not an issue Lena Ortiz
STEP 05 · A PERSON DECIDES
A person decides every flag.
Each flag lands in one queue with the rule behind it, the records it came from and the dollar amount.
More
Your team decides what happens next. Nothing stops a person’s work while a flag waits.
- RULE
- Approved change orders are billed at the T&M rate.v3
- FOUND
- CO 2 not on INV 10233·$1,136.00
- SETTLED BY
- Code·no model
- DECIDED
- Lena Ortiz·Bill it·Oct 9, 10:42
Export Replay a reworded rule
STEP 06 · THE RECORD
Every check is written down as it happens.
Which rule applied, what was found and who decided.
More
With the rule version and, where a model reviewed it, which model. You can export it, and you can reword a rule and replay it over records already checked to see what would change before the new wording applies.
What that history buys you today, and what we want it to do next: the loop →
START WITH THE LAST 90 DAYS
The free billing audit is the same check, run once over past work.
You send 90 days of closed POs, change orders and invoices. We tie them together, check them against your billing rules, and give you a line-by-line report of what went unbilled, in dollars, so you can bill it. No cost, and no commitment to go further.
WHEN AN AGENT DOES THE WORK
The same check runs before the agent acts.
Novarch attaches where your agent calls a tool and reads everything the agent looked at before it acted. Then one of three things happens: the action runs, it waits for a person, or it never runs. Approve a paused action and the agent picks up where it left off. Deny it and that action never runs. A new rule can start in observe mode, where every action is checked and recorded and nothing is blocked until you turn it on.
The gate does one of these three things.
The agent side, defined, and how it relates to guardrails: what an enforcement layer is →
FOR YOUR IT TEAM
What it asks of IT.
Data handling, deployment and what is certified so far are on the security page.
- Access
- Read-only. Scheduled exports or read-only credentials you can revoke. Nothing is installed in your systems and nothing in them changes.
- Where it runs
- A single-tenant instance we run for you, with its own database, or inside your own environment from a private Python package.
- Sign-in
- Microsoft Entra ID single sign-on, or a named account for each person, with admin and operator roles.
- Model
- Anthropic's Claude. It drafts rules from what you feed it, and reviews only the checks code cannot settle.
- Agents
- One integration where the agent calls its tools, in Python or TypeScript. An engineer is involved once.
WHY IT HOLDS UP
Three things make this work.
IT READS THE WHOLE TRAIL
A single record can look clean and still be wrong next to the others. Novarch checks the PO, the change order and the invoice together, and for an agent, everything it looked at before it acted. That is the difference between catching a pattern and catching a keyword.
THE RULES BELONG TO WHOEVER RUNS THE WORK
The person accountable for the outcome confirms every rule, in plain words. The rule a reader sees on a screen is the rule that was applied.
A PERSON DECIDES
Every flag on a person's work goes to a person. For an agent, the gate blocks on its own only for a clear violation or, by default, when the check itself cannot run. Close calls wait for someone.
See it on your own work.
Bring a month of records or an agent you're putting into production, and we'll show you what Novarch would catch.