The back office that checks its own work.

Bearwall is an AI operator built to do the billing, cash posting and supplier-invoice entry inside your RFMS, so your controller reviews the exceptions instead of keying every line.

Every write is checked before and read back after, and anything that fails a rule goes to a person with the reason. Billing, undo and the morning board run today on practice data; replay them below.

Get the free diagnosis See it run on practice data

Works with RFMS · Runs on its own Windows machine at your company · A second set of hands for your controller

Bill run

Practice data

Orders ready to bill: 30
Value: $147,875.43
Billed on completed dates: 30
Read back by API: 30 / 30
Writes outside the run: 0
Left in the pool: $0.00

Demo Floors, a fictional three-store contractor. Demo proof run 11/6/26 on a simulated RFMS.

Practice data Simulated RFMS, fictional data (Demo Floors), demo proof run 11/6/26.

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

01 · The problem

The status lives in one system. The work lives in another.

A job is complete in the scheduler and unbilled in RFMS. A supplier bill sits in email, not in AP. A back charge sits in a builder portal, not on the installer’s pay. Someone carries each one across by hand, one screen at a time.

Three questions that are hard to answer on any morning

What is ready to bill and not billed?

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
What is stuck, and why?

Builder POs break matching.

Leading zeros get stripped. One PO covers two orders. POs get reissued. Without the builder’s PO or EPO, the order cannot bill.
What is unpaid, or deducted without agreement?

Back charges hide in notes.

The builder’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 logins, the notes and the portal MFA leave too. The exception list was in a head before it was in a file.

Bearwall carries the work across the gap with fewer handoffs between desks and fewer errors: every write is checked before and read back after, and logged.

02 · How it works

Checked before. Read back after.

The same four steps at every company, in this order.

01
It runs on a machine of its own.

It runs on its own Windows machine at your company, under its own RFMS seat and key. It never shares a login with a person or takes over anyone’s desktop. Your data stays on that machine, except what goes to a model once you turn on open conversation, or to an optional service you consent to (see Security and data).
02
Practice data first.

We aim to run it on your RFMS Practice database before it touches live books, then read-only beside your team for 30 days: the list of what it would bill, post and key, next to what your team did. Nothing writes until you turn a function on, one at a time.
03
Every write is checked before and read back after.

Before a write, the order is re-read live and must pass a written rule. After it, the result is read back from RFMS by API. Anything that fails goes to a person, with the reason.
1. Rule check
2. Write
3. Read back
4. Logged
Fails a rule → to a person, with the reason
04
Every write is logged.

Each run writes one audit row per write and a read-back line. On practice data, 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, a reversal is a separate step you approve.

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 runs at screen speed on your calibrated seat.

01 Give me the morning board

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

Answered by code, no model call

02 What can we bill today?

30 orders ready to bill, $147,875.43.
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

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

Done in 6.7 s on a simulated RFMS (demo proof run, installed copy). Live billing runs at screen speed on your calibrated seat.

04 Undo the bill run

Undid 30 writes on 30 orders.
Read-backbilled and delivery dates cleared on 30 of 3030 of 30
Audit30 undo rows
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, a reversal is a separate step you approve.

05 Who owes us the most?

A/R open$336,328.12 on 74 invoices.
By agecurrent $186,020.33 · 31-60 days $111,833.44 · 61-90 days $7,693.10 · over 90 days $30,781.25
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 or close a period. It makes no payments and is never given bank logins.

03 · What it runs

The keyed work, from billing to the schedule.

Bearwall works on its own RFMS seat and key at your company. There is no ERP to replace. Each function shows its status, and nothing in build or on the roadmap is sold as working.

Practice dataRuns today in the Bearwall demo, on a simulated RFMS with fictional data (Demo Floors).
In buildBeing built into the Bearwall engine now. Not sold as working until it runs on practice data.
RoadmapLater. Listed under the table.

At your company, each function is calibrated to your RFMS seat and runs on practice data first, before anything writes.

What it runs, and what it checks before it writes
Function	What it does	What it checks	Status
Order to cash
Billing	Bills completed orders on their completed dates. On practice data, 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.	Practice data
Booking	Booking 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.	In build
Cash posting	Applying builder and homeowner receipts with the remit reference.	Each payment is read back by API after it posts.	In build
A/R aging and collections	Answers who owes what, by age and by builder.	Read-only; totals tie to the cent.	Practice data
Builder portal reads	Reading the builder portals you name, with a login you give it, once a read recipe is built for each portal.	Read-only. Each portal’s terms are checked with you before it is turned on.	In build
Back-charge tracking	Tracks back charges by status and the installer deductions behind them. It reports; it does not key them.	Read-only; statuses foot to the total.	Practice data
Payables
AP keying	Planning every supplier invoice off-screen first, then keying only those that tie to a PO.	An invoice must tie to a PO before it is keyed; the rest go to a person with the reason.	In build
Payables reconciliation	Classing each invoice against PO and receiving: ties, price variance, not received, duplicate.	Read-only until you turn keying on.	In build
Supplier payment records	Recording supplier payments in RFMS at the bank date your controller approves.	It never moves money and is never given bank logins.	In build
Operations
Scheduling and dispatch	Moving schedule dates in Schedule Pro and keeping the crew on crewed jobs.	Each move is read back by API.	In build
Morning board	Shows 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.	Practice data
Operator
Screen control where the API stops	Driving RFMS screens on Windows for the steps the API does not cover (bill, book, schedule moves, mark paid), on its own seat, calibrated to that seat.	Built to stop and tell a person when a screen does not match what it expects.	In build
Tally, voice and chat	Ask in plain words, typed or spoken. The board’s questions (bill-ready, A/R, A/P, 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.	Practice data
Company memory	In the demo, a page that lists exceptions written down. Linking them to orders and turning them into rules is being built.	Nothing writes.	In build
Setup and approval cards	A 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.	Practice data

Roadmap Not sold as working: 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 · back-charge capture from builder portals · collections mail drafts for a person to send · other flooring ERPs, starting from exports · the Tally camera.

04 · Security and data

What it can touch, and where your files go.

The answers to settle before you send a file or give it a seat. A line that is not in place yet says so.

Before you send a file (the free diagnosis)

Agreement: We sign a mutual NDA with you before you send anything.
How files arrive: Through a private upload link to Bearwall’s Cloudflare R2 storage, sent to you after the first call. Not by email, and there is no upload form on this site. Never passwords or keys.
Where they sit: In Bearwall’s Cloudflare R2 storage, encrypted at rest.
Who sees them: Fateen Majumder, and no one else. No AI model vendor processes the files you upload.
How long: Deleted 30 days after the diagnosis closes. We email you when they are.
If something goes wrong: We tell you within 72 hours of finding a breach that touches your files.

When it runs at your company

Where it runs: On its own Windows machine at your company, under its own RFMS seat and key. Screen control runs only on that seat; it never takes over a person’s desktop.
What it needs: Its own Windows login, its own RFMS login and API key (the exact RFMS permissions for its seat are confirmed during the diagnosis), and a read-only login for each builder portal you turn on. You can revoke any of them at any time, and it stops.
What it can write: Only the write types you turn on, one at a time: bills, bookings, cash receipts, supplier invoices, supplier payment records and schedule dates.
Never given: Bank logins, card numbers or the right to change supplier bank details. It cannot move money. We set up its RFMS seat with you so it cannot delete records or close a period, where RFMS permissions allow.
Approvals: Bill and undo runs wait on an approval card that checks the role, as a guard against mistakes. It does not send email, commit in builder portals or close a period. Approval cards on every write type are being built.Practice dataIn build
Audit log: Each run writes one audit row per write and a read-back line; the console above shows them. A daily log file for your controller (time, order, field, before, after, read-back, approver) comes later.Practice dataRoadmap
Stop: One Stop command shuts it down on its machine. Revoking its RFMS key stops it for good.Practice data
When RFMS changes: Built to stop and tell a person when a screen or a field does not match what it expects. It does not guess. We aim to adapt within 5 business days.In build
Open conversation: The board’s questions (bill-ready, A/R, A/P, back charges and this week’s schedule) are answered by code with no model call. Open conversation uses a model under your own Anthropic account and stays off until you turn it on. It is not offered on production machines until its permissions are tightened.In build

Who else touches data

Vendor	What for	When
Cloudflare	Serves this website	Always, for this site only
Cloudflare R2	Stores diagnosis exports, encrypted at rest	Only if you send exports; deleted 30 days after the diagnosis closes
Esri	Map tiles for the on-screen Stage map	Only when the Stage map is open; requests map tiles for the area shown
OpenStreetMap (Nominatim, OSRM)	Address lookup and drive-time estimates	Only when a map or scheduling lookup runs; sends the address being looked up
Hugging Face	Downloads the local speech and voice models	Once, at install; no company data is sent
Anthropic	Open conversation, under your own Anthropic account	Only if you turn it on
TypeSafe, ElevenLabs	Optional judgment and voice services the engine can use	Off by default; only with your consent

Hearing and speaking run on the machine itself, offline, with no vendor. Privacy for this website: /privacy/.

05 · Tally

Ask your back office a question.

Tally is the voice and chat front door to Bearwall. The board’s questions (bill-ready, A/R, A/P, 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.

You · typed

“What can we bill today?”

Tally

30 orders ready to bill, $147,875.43. By store: Riverbend $88,452.46, Corliss Falls $41,095.32, Bellweather Junction $18,327.65.

Typed question answered by code in 0.4 s, no model call. Practice data. Voice adds speaking time.

This page does not use your microphone.

Voice and chat

Practice data

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

Company memory

In build

In the demo, a page of exceptions written down: which builder’s POs lose their leading zeros, which PO covers two orders, which supplier bills twice. Turning them into rules is being built.

Camera

Roadmap

Show Tally a delivery ticket, a damaged roll or a screen instead of describing it. Not built yet.

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 uses a model under your own Anthropic account. It stays off until you turn it on.

06 · Pricing and terms

Start with a free diagnosis. Pay per desk after.

One offer: the Bearwall operator on its own machine and RFMS seat at your company. You start read-only, and you see the full quote before anything is installed.

The operator

The back office, carried.

Free diagnosis. Send exports, not access. We aim to return one page within 48 hours: what is ready to bill, billed but not booked, cash not applied and supplier invoices not keyed. It is yours to keep, with no obligation. Nothing is installed.
Quote. The full quote comes within 48 hours of the diagnosis, before any install.
Pilot. Two functions, on your RFMS Practice database first, then read-only beside your team for 30 days. Nothing writes until you turn a function on.
Month to month. After the pilot, with 30 days’ notice to cancel.

How it is priced

A monthly fee per desk, plus a one-time setup. A desk is one back-office function (AR, AP, controller or dispatch), not a person or a login. Prices are quoted after the diagnosis.

Get the free diagnosis Talk to the founder

Terms in plain English

Length: Month to month after the pilot.
To cancel: 30 days’ notice.
What you own: Your data, your configuration, the written rules and the run history. You keep a copy when you leave.
Machine and seat: You buy the agent’s Windows machine and its RFMS seat, under your own RFMS subscription.
Support: During business hours, Eastern Time.
If RFMS changes: It stops and tells you. We aim to adapt within 5 business days.
If Bearwall is not there: The machine, the configuration, the rules, the run history and the documentation stay with you.
The agreement: We send the draft agreement with the diagnosis.

Also from Bearwall

Front-office builds.

Your builders and buyers judge you by your website, your portal and your reports. Bearwall builds them to the standard of this page, on the data your back office already holds. Scoped and quoted per project.

Websites with real SEO.
Fast, structured pages written for builders, buyers and search, including AI answers.
Example: You are on one.
Executive dashboards.
Bill-ready, A/R, A/P and the schedule on one screen, tied to the cent.
See the specimen
Job-footprint maps.
Where you work, by state, market and community.
See the Southeast map
Apps for phone, tablet and desk.
One build that reflows to each screen.
No app example shown yet. The console shows the same reflow.
Switch the console to Phone
Customer and builder portals.
Order status, documents and payment status in one place, behind your customers’ own logins.
No example shown yet.
An in-house assistant.
Tally, set up on your rules and your data.
See Tally

Demo Floors · Morning

Practice data

Bill-ready

$147,875.43

30 orders

Riverbend Largest$88,452.46 (17)

Corliss Falls$41,095.32 (6)

Bellweather Junction$18,327.65 (7)

A/R open

$336,328.12

74 invoices

Current$186,020.33

31-60$111,833.44

61-90$7,693.10

Over 90 Oldest$30,781.25

A/P open

$160,362.02

144 invoices

Schedule this week

27

jobs

Back charges

$2,795.00

14 back charges

Issued$509.00

Open, claimed Largest$994.00

Conceded$694.00

Recovered from installer$598.00

Executive dashboard specimen, drawn from practice data. Demo Floors is fictional. With a mouse, hover to magnify; on any device, open it full size.

View full size

Advisory Division launches into production-builder work, and ERP migration readiness: data clean-up, cut-over reconciliation and opening balances. Scoped per engagement. Talk to the founder

07 · Founder

Who stands behind it.

Fateen Majumder

Founder, Bearwall LLCRan AR, AP and back charges for a multi-location builder-flooring contractor on RFMSWrites Bearwall’s rules and engine

Bearwall LLC · Atlanta, Georgia

Bearwall’s rules are written around the RFMS data traps he knows by name from that work: stripped leading zeros, compound POs, open-order duplicates and discount accounts.

Bearwall has no reference customer yet, and says so. A pilot starts read-only, and you can talk to Fateen before you send a single file.

A bearing wall carries the load of the structure. Bearwall is built to carry the weight of the back office as the company grows.

The first call is with Fateen.

Fateen on LinkedIn

08 · The Southeast

Built for flooring contractors in the Southeast.

Bearwall starts with contractors in Georgia, the Carolinas, Tennessee, Alabama and Florida. Setup and support are remote.

Use + and − to zoom, 0 to reset · Select a state

States
State	Establishments (2024)	Single-family permits (2024)
Georgia	not yet published	not yet published
South Carolina	not yet published	not yet published
North Carolina	not yet published	not yet published
Tennessee	not yet published	not yet published
Alabama	not yet published	not yet published
Florida	not yet published	not yet published

09 · FAQ

Questions a controller asks first.

What is Bearwall?

Bearwall is an AI back-office operator for flooring contractors on RFMS. It is built to bill completed orders, post cash, key supplier invoices and move schedule dates. Billing, undo and the morning board run today on practice data. Every write is checked before and read back after, and anything that fails a rule goes to a person with the reason.

Does it work with RFMS?

RFMS is the first system Bearwall is built for. It is built to run on its own seat, under your RFMS subscription and API key, and to drive the screens where the API stops. The demo runs on a simulated RFMS; a pilot is its first run on a real one. Bearwall is not affiliated with or endorsed by Cyncly.

What does it cost?

A monthly fee per desk plus a one-time setup. A desk is one back-office function: AR, AP, controller or dispatch, not a person or a login. The diagnosis is free. You see the full quote after the diagnosis and before anything is installed. After the pilot it is month to month, with 30 days’ notice to cancel.

What if it posts something wrong?

Before each write, the order is re-read live and must pass a written rule; after it, the result is read back by API. A write that fails either check goes to a person you name, with the reason. On practice data, a 30-order bill run was undone and read back cleared. Live, a reversal is a step you approve.

Where does our data go?

The agent runs on its own Windows machine at your company, where the board’s figures are answered by code with no model call. Open conversation stays off until you turn it on, then uses a model under your Anthropic account. Diagnosis exports are deleted 30 days after the diagnosis closes. Security and data names every vendor.

What do I need to run it?

A Windows machine used only by the agent, an RFMS seat and API key for it under your own RFMS subscription, and a read-only login for each builder portal you turn on. You buy the machine and seat; Bearwall sets them up. It needs Windows 10 or 11. The full spec and supported RFMS versions are confirmed in the diagnosis.

Will we need to hire as we grow?

Bearwall is built for no new hire as you grow on the same desk work. Your controller gets a second set of hands, and the people who know your builders approve the exceptions. Bearwall gives no staffing advice and makes no promise about headcount.

What happens if RFMS changes, or we move off it?

If an RFMS update changes a screen or a field, Bearwall is built to stop and tell you instead of guessing, and we aim to adapt within 5 business days. If you move to another system, migration readiness is a service we offer: data clean-up, cut-over reconciliation and opening balances.

What are back charges and retainage in flooring?

A back charge is an amount a builder deducts from a flooring contractor’s payment, usually for damage, rework or cleanup, often with the reason only in the builder’s portal notes. Retainage is a share of each invoice the customer holds until the job or project closes. Bearwall tracks back charges by status on practice data; capture is on the roadmap.

10 · Contact

Start with a read-only diagnosis.

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

Email: hello@getbearwall.comWrite to us
Phone: (943) 215-4122
LinkedIn: Fateen Majumder
Address: Bearwall LLC, Atlanta, Georgia

Write to us and we send a mutual NDA and a private upload link for the exports. We never ask for passwords or keys. Please do not send them. How we handle the files: Security and data.

Talk to the founder

The back office that checks its own work.

The status lives in one system. The work lives in another.

Finished work waits to be invoiced.

Builder POs break matching.

Back charges hide in notes.

Checked before. Read back after.

It runs on a machine of its own.

Practice data first.

Every write is checked before and read back after.

Every write is logged.

Replay a run.

The keyed work, from billing to the schedule.

What it can touch, and where your files go.

Before you send a file (the free diagnosis)

When it runs at your company

Who else touches data

Ask your back office a question.

Voice and chat

Company memory

Camera

Start with a free diagnosis. Pay per desk after.

The back office, carried.

Front-office builds.

Websites with real SEO.

Executive dashboards.

Job-footprint maps.

Apps for phone, tablet and desk.

Customer and builder portals.

An in-house assistant.

Who stands behind it.

Built for flooring contractors in the Southeast.

Questions a controller asks first.

What is Bearwall?

Does it work with RFMS?

What does it cost?

What if it posts something wrong?

Where does our data go?

What do I need to run it?

Will we need to hire as we grow?

What happens if RFMS changes, or we move off it?

What are back charges and retainage in flooring?

Start with a read-only diagnosis.