Get the free diagnosis

How it works

Checked before. Read back after.

The same path at every company, from a free diagnosis to a back office that keeps learning. It starts read-only, and each function writes only after it is set up with you.

The gap

Why the work gets stuck.

Finished work waits to be invoiced.

Each day of billing lag leaves about one day’s sales in unbilled work.

Annual sales ÷ 365 = receivables added by one day of lag

POs break matching.

Leading zeros get stripped. One PO covers two orders. POs get reissued. For builder customers, an order without the PO or EPO cannot bill.

Deductions hide in notes.

The customer’s reason sits in portal notes, not in exports, and a duplicate installer deduction can reach payroll unchecked.

Exceptions leave with people.

When the person who knows them leaves, the notes and the know-how leave too. The exception list was in a head before it was in a file.

The path

A to E, step by step.

  1. A

    Diagnosis.

    Send exports, not access. We aim to return one page within 48 hours: what is earned but not billed, billed but not booked, cash not applied and supplier invoices not keyed. It is free and yours to keep, with no obligation. Nothing is installed.

  2. B

    Setup.

    It gets its own Windows computer at your company and its own login and key in your system. It never shares a login with a person or takes over anyone’s desktop. During setup it learns your system, your screens, your rules and your exceptions. Your people enter its keys, and each key is checked live before it is saved.

  3. C

    Read-only.

    On RFMS, where you have a test copy of your database, it starts there. Then it works read-only beside your team for 30 days, and we compare what it would bill, post and key with what your team did. Nothing writes in this month.

  4. D

    Turn it on.

    One function at a time, when you say so. Each write type is set up to take this path before you turn it on: before a write, the record is re-read live and must pass a written rule; after it, the result is read back. A write that fails is held and listed with the reason.

    1. Rule check
    2. Write
    3. Read back
    4. Logged

    Fails a rule → held, with the reason

  5. E

    It keeps learning.

    In the demo, each run keeps a run note listing every write and its read-back result; on your system, the run note is set up with the first function. Undo is proven in the demo: undoing a 30-order bill run took 4.2 seconds on a simulated RFMS and read back 30 of 30 cleared. On a live system, the run note lets a person reverse writes. Each exception your team settles, we write into a rule it follows from then on.

Replay a run.

Figures and times from the 11/6/26 demo proof run, shown as a replay, on a simulated RFMS with fictional data (Demo Floors). Live billing goes through your system’s screens, so it is slower; it is timed in your pilot.

01 Give me the morning board
  1. Bill-ready30 orders · $147,875.43
  2. By storeRiverbend 17 · $88,452.46 | Corliss Falls 6 · $41,095.32 | Bellweather Junction 7 · $18,327.65
  3. A/R open$336,328.12 on 74 invoices
  4. A/P open$160,362.02 on 144 invoices
  5. Back charges14 · $2,795.00 · installer deductions $742.84
  6. Schedule this week27 jobs

Answered by code, no model call

02 What can we bill today?
  1. 30 orders ready to bill, $147,875.43.
  2. By storeRiverbend $88,452.46, Corliss Falls $41,095.32, Bellweather Junction $18,327.65.

Answered by code, no model call

03 Bill the orders
  1. Billed 30 on completed dates, booked 0.
  2. API read-backok 30 · redo 030 / 30
  3. Sweep outside the run0
  4. Audit30 bill rows, 0 book rows
  5. Read-back30 of 30 billed, $147,875.4330 of 30
  6. Boardbill-ready 0 orders, $0.00

Done in 6.7 s on a simulated RFMS (demo proof run, installed copy). Live billing is slower; it is timed in your pilot.

04 Undo the bill run
  1. Undid 30 writes on 30 orders.
  2. Read-backbilled and delivery dates cleared on 30 of 3030 of 30
  3. Audit30 undo rows
  4. Boardbill-ready 30 orders, $147,875.43

Done in 4.2 s on a simulated RFMS (demo proof run, installed copy). On a live system, the run note lists every write for a person to reverse.

05 Who owes us the most?
  1. A/R open$336,328.12 on 74 invoices.
  2. By agecurrent $186,020.33 · 31-60 days $111,833.44 · 61-90 days $7,693.10 · over 90 days $30,781.25
  3. Largest balancesOstrander $67,461.93 · Velloran $66,873.62 · Corvane $54,206.88

Answered by code, no model call

↑ ↓ or j / k to choose · Enter to replay · 01 / 05

What it does not do: send email, commit anything in a builder portal, close a period or send money. It is never given your people’s passwords or MFA codes.

Demo Demo proof run 11/6/26: simulated RFMS, fictional data (Demo Floors).

  • 30 / 30writes read back after a 30-order bill runConsole run 03
  • 0writes found outside the run by the sweep that follows itConsole run 03
  • 30 of 30orders read back cleared after the undoConsole run 04

Every function

What it does, and what it checks.

It works on its own login and key in your system; there is no ERP to replace.

  • Set up for youConfigured on your system by Bearwall during setup.
  • Learns as it worksGrows from your exceptions: each one your team settles, we write into a rule it follows from then on.

Every function runs read-only beside your team before it writes.

Every function, what it checks before it writes, and how it comes to your company
FunctionWhat it doesWhat it checksAt your company
Order to cash
BillingBilling completed orders on their completed dates. Its order list and login are set up on your system during setup; in the demo, a run can be undone and read back cleared.The order is re-read live and must pass the bill rule; each bill is read back by API after.Set up for you
BookingBooking billed orders so revenue, job cost and the delivery date that drives installer pay post.Orders missing from the book list are held, not guessed.Set up for you
Cash postingApplying builder, property-manager and homeowner receipts with the remit reference.Set up in your read-only month: each posting is read back before it counts as done.Set up for you
A/R agingAnswering who owes what, by age and by customer.Read-only; totals tie to the cent.Set up for you
Builder and PMC portal readsReading the builder and property-manager portals you name, once a read recipe is set up for each one.Read-only. Each portal’s terms are checked with you first, and your people enter its logins.Set up for you
Back-charge trackingTracking back charges by status and the installer deductions behind them. It reports; it does not key them.Read-only; statuses foot to the total.Set up for you
Payables
Supplier invoicesSet up to plan every supplier invoice off-screen, so only those that tie to a PO are keyed.Set up in your read-only month: an invoice must tie to a PO before it is keyed; the rest are held with the reason.Set up for you
Three-way matchSet up to class each invoice against the PO and receiving: ties, price variance, not received, duplicate.Read-only until you turn keying on.Set up for you
Supplier payment recordsRecording supplier payments in your system at the bank date your controller approves.Recorded only at the date your controller approves; it never sends money.Set up for you
Operations
Scheduling and dispatchMoving schedule dates and keeping the crew on crewed jobs (Schedule Pro on RFMS).Set up in your read-only month: each move is read back before it counts as done.Set up for you
Morning boardShowing what is bill-ready, what is stuck, A/R, A/P and this week’s schedule on one screen.Read-only; ties to the cent.Set up for you
How it runs
Screen control where the API stopsDriving your system’s screens on Windows for the steps the API does not cover (bill, book, schedule moves, mark paid), on its own login, set up for that login.Set to stop and tell a person when a screen does not match what it expects.Set up for you
Tally, voice and chatAsk in plain words, typed or spoken. Bill-ready, A/R, A/P and the morning board, which shows back charges and this week’s schedule, are answered by code from your data. Speech runs on the machine, offline.No model call for figures.Set up for you
Company rulesYour exceptions, written down as rules it follows: which customer’s POs lose their leading zeros, which PO covers two orders, which supplier bills twice.Each rule comes from an exception your team settled.Learns as it works
Setup and approval cardsA six-step setup that checks each key live before it is saved. Bill and undo runs wait on an approval card that checks the role, as a guard against mistakes.An approval card before the run.Set up for you

Scoped in the diagnosis Asked about, and scoped company by company: purchasing runs (release runs and PO cost checks) · receiving · inventory control (rolls, locations, counts) · EDI with suppliers (850, 855, 856 and 810 documents) · installer pay audit · retainage and pay applications · back-charge capture from builder portals · collections mail drafts for a person to send · bank and remittance portals, with your sign-in.

Ask your back office a question.

Tally is the voice and chat front door to Bearwall. Bill-ready, A/R, A/P and the morning board, which shows back charges and this week’s schedule, are answered by code from your data, not by a model’s guess. Actions run through approval cards that check the role, as a guard against mistakes.

Voice and chat

Set up for you

Hears and speaks on the machine itself, and works offline. Type or talk; the answer is the same figure the board shows.

Hear it answer

Company rules

Learns as it works

A written list of the exceptions your team settles: which customer’s POs lose their leading zeros, which PO covers two orders, which supplier bills twice. We write each one into a rule it follows.

Examples of the kind of rule a company writes down

Builder POs lose their leading zeros in exports.Match POs as text, never as numbers.
One builder PO can cover two orders.Match on PO plus job address.
A zero sell price can still carry labor.Hold any order with labor and a zero sell price.

Open conversation beyond your figures is not available on production machines yet; when it is, it uses a model under your own Anthropic account.

Start at A: a free diagnosis.

Get the free diagnosis