The four options a restoration shop has, side by side.
The status quo, your vendor's AI, a chatbot with plugins, or Ruby: what each one gets you.
The status quo: disconnected systems
Any question that spans two systems means someone pulling reports by hand. Each one costs a little time, and across every job that time comes out of margin.
You get: what you have today.
Your vendor's AI: smart inside one box
Useful inside that one system and blind outside it. A restoration job lives across six systems, and an assistant that sees one of them misses most of the job.
You get: one tool's view.
A generic LLM with a pile of plugins
It can reach your data but knows nothing about the trade. It starts from zero every morning and does nothing unless asked.
You get: access without resolution.
Ruby
One picture of each job. The Albi project, the Encircle file and the CompanyCam photos are one job.
Knows the trade. Grounded in the trade's published standards, sources cited.
Works without being asked. Playbooks on a schedule or trigger catch the gap on day 1.
Has seen what gets paid. 100,000+ insurance claims of payment intelligence.
Auditable. Every action permissioned and logged; people approve anything external.
What each option covers.
Five things a restoration company needs from an assistant, and where each option stands on them.
| Capability | Status quo | Vendor AI | LLM + plugins | Ruby |
|---|---|---|---|---|
| Sees the whole value chain | No | No | Partialaccess without resolution | Yes |
| Knows the restoration trade | N/A | Partialone domain | No | Yes |
| Works without being asked | No | Partialinside its own tool | No | Yes |
| Payment intelligence | No | No | No | Yes |
| Audit trail and permissions | Partialper system | Partialper system | No | Yes |
Sees the whole value chain
Knows the restoration trade
Works without being asked
Payment intelligence
Audit trail and permissions
The standard of care vs. the standard of payment.
Any good tool can grade your documentation against the standard of care. Only Ruby grades your file against what carriers dispute, cut, settle and deny. The standard of care tells you what’s defensible. Ruby tells you what gets paid.