Common questions

The work Ruby runs for you on a schedule, a trigger, or when you ask: documentation checks, denial-risk flags, dispatch readiness, settlement invoicing, and apps like a job board. Ruby builds each one with you, from an idea or your own description, and you refine it until it fits how your shop runs.

Yes. Describe what you want in plain language and Ruby drafts it: the steps, the checks, the output. You refine it, you run it, it's yours.

Every RubyPlaybooks plan includes a monthly pool of credits that every chat and playbook run draws from. One flat price covers your whole company, however many locations and people you have. The pool refreshes each billing month and doesn't roll over.

If the pool runs dry, auto top-up adds credits at your plan's rate in the amount you choose, and those credits roll over. It's on by default for new plans, and you can turn it off any time in Billing. You can also move up a plan any time; the bigger pool lands right away, prorated for the rest of the month.

RubyConnect is the connection layer. It gives any AI access to your tools, and it's useful on its own. RubyPlaybooks adds Ruby herself: her chat, one picture of your jobs across every tool, answers grounded in restoration standards with sources cited, and the playbooks and apps she builds with you. With RubyConnect alone, a general-purpose AI reads your data; with RubyPlaybooks, Ruby reads it knowing the trade.

The team behind Ruby, building with you. We build a playbook or app around your SOPs, your systems and your standards, at a fixed price per job function from XS ($500) to XL ($10,000), sized before we start. Every build ends as a playbook running on your plan.

Tell us what you'd want built and we'll reach out.

Yes. Every system you connect widens what she can see and tightens what she can resolve. With one tool connected she answers questions; with your whole stack connected she answers the questions that span it, which are the expensive ones.

Ruby's playbooks are informed by a decade inside restoration billing: what carriers dispute, what they cut, what they settle, and what they deny, learned across 100,000+ claims. That experience is built into how she reads a file. It's the difference between grading your documentation against the standard of care and grading it against the carrier's standard of payment.

Most of it falls into two buckets. A vendor's built-in assistant is smart inside its own system and blind to the other five your jobs run through. A general AI with connectors can reach your data but knows nothing about the trade, remembers nothing between sessions, and has no stake in whether you get paid. Ruby reads across your whole stack, grounds answers in the standards of the trade, and grades your file against the carrier's standard of payment, what they dispute, cut, and pay, because she is built on both ends of the chain: the field record and the check that cleared, across 100,000+ claims. See Why Ruby for the side by side.

Every connection is scoped, permissioned, and audited, and your data is isolated to your tenant. Ruby's access runs through the same permission layer a human user would have, and a human reviews anything external before it sends.

A team with a decade inside restoration billing and 100,000+ claims behind them. We've spent that decade getting restoration contractors paid, and Ruby puts that experience into software.

Claude, ChatGPT, Gemini, Grok, and any other AI client that can use connectors, including whatever ships next. It also works in Ruby's own app.