Files, agents, and skills, installed into your own Claude Code. Nothing runs on RBD.'s servers, nothing leaves your machine, and nothing you did not put there yourself.
Four fictional beats, morning to close.
A skill reads your calendar and inbox, then hands you a short brief. It drafts and sends nothing.
$ morning briefCalendar, 3 events. Inbox, 1 thread waiting on a reply: Priya Nandan asked for the updated scope, 2 days old. Nothing sent. Draft attached for your review.
You talk or paste raw updates in any order and get a one-line receipt showing where each item was filed.
$ dump: closed the Whitfield renewal at $1,400/mo. Peebles wants a proposal by Friday.Routed Whitfield renewal ........... project file, closed at $1,400/mo Peebles proposal ............ decision queue, due Friday 2 items routed. Nothing sent without you.
A pricing call goes to a small standing board that argues out loud. A new build goes to an architect first.
$ ask the board: take Peebles at $1,400/mo, or hold for $2,000?contrarian ask once for $2,000, in writing, before you answer recommendation: ask once at $2,000. if declined, $1,400 still clears.$ architect review: new client-intake routingverdict: BUILD-WITH-CHANGES, stage output to a review file, no auto-send
At session's end, one pass routes anything worth keeping into next time's files.
$ retire sessionRouted Peebles ask-once decision ....... decision queue, closed the discount pattern above ...... feedback file, new rule 2 items filed. Nothing left loose for next time.
A folder of plain text, not an app and not a login.
Agent files, skill folders, templates, and one install guide arrive in a folder next to your Claude Code project, shaped by three answers: your practice, your tools, and which decisions you want a standing team on.
You install it yourself: copy files into place, read one guide.
You fit it to your own agents and templates in a separate working session: the Build Session, $750.
It does not run unattended by default: no email sent, no post made, no change made on its own. Anything staged on a schedule writes to a draft for you to approve.
The honest way to describe it: in its first week inside RBD., one seat wrote a confident diagnosis with five claims in it, and the read-only auditor seat checked each one against the actual files and found all five were made up. The fix that came out of that is now part of the system: work gets verified against the files before it reaches you.
That is a habit built from corrections, not a guarantee about what it will do next.
Purchases are governed by the Terms of Sale and Refund Policy. Want it fitted to your practice in a live working session instead: that is the Build Session, $750.