Questions a controller asks first.

Bearwall is an AI back office for builder, multifamily, commercial and retail flooring contractors. It works inside the system you already run, starting with RFMS, and is set up one function at a time: billing, A/R and back charges first, then booking, cash posting, payables and scheduling. Every write is checked before and read back after.

Likely, yes. If your team does the work with a keyboard and mouse, Bearwall can learn it: by API where there is one, by export, or on screen. It starts on RFMS; on another flooring system, or an accounting package like QuickBooks or Sage, the diagnosis maps yours first and the quote says what it will run.

RFMS is where Bearwall starts. It runs on its own seat under your RFMS subscription and API key, and where the API stops, it drives the screens on that seat, set up during setup. The demo replays on a simulated RFMS; your read-only month is where it proves itself on yours. Bearwall is not affiliated with or endorsed by Cyncly.

No. Bearwall is made for builder, multifamily, commercial and retail flooring contractors. The work differs: builder POs and back charges, property-manager turn orders, retainage and pay applications, deposits and homeowner balances. Billing, A/R, cash posting and the payables check apply to all four. The diagnosis sets what it takes on first and what is scoped, such as retainage.

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.

Before each write, the record is re-read live and must pass a written rule. Billing is read back by API; other write types are read back as set up in your read-only month. A failed write is held. In the demo, a bill run was undone and read back cleared. Live, the run note lists writes to reverse.

Bearwall runs on its own Windows machine at your company, where the board’s figures are answered by code with no model call. Open conversation is not offered on production machines yet. Diagnosis exports are analyzed with Claude (Anthropic), seen only by Fateen Majumder, and deleted from storage 30 days after upload. Security and data names every vendor.

It can be scoped, portal by portal, in the diagnosis. With your sign-in and approval, it can be set up to download remittances and statements, then post receipts and cash and three-way match payables in your own system, each write checked. A person at your company signs in and keeps the passwords and MFA. It never sends money.

Its own Windows computer, and its own login in your system: on RFMS, a seat and API key under your own subscription. You buy the computer and seat; your people enter its keys, and Bearwall sets them up. It runs on Windows 11 (Windows 10 is confirmed in the diagnosis). The full spec and supported versions are confirmed there too.

Bearwall is made so the same desk work needs no new hire as you grow: your controller gets a second set of hands, and the people who know your customers approve the exceptions. That is what it is made for, not a promise about headcount, and Bearwall gives no staffing advice.

If an RFMS update changes a screen or a field, Bearwall is set to stop and tell you instead of guessing, and we aim to adapt within 5 business days. If you move to another system, it can learn the new one, and we help with the move: data clean-up, cut-over reconciliation and opening balances.

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; portal capture is scoped in the diagnosis.