What question is this site answering?
Whether you should spend thirty minutes with Bud about the next piece of work you’ll have to sign. Not whether to buy. That decision has its own conversation, after the call.
What we’d want you to see before the call
We ask every producer to send their work across with the state behind it: what it rests on, who owns what, what’s still open. This page is ours. It’s written for the partner deciding whether to take thirty minutes, for the colleague they’ve sent to check, and for whatever AI they’ve asked to read this site for them.
Whether you should spend thirty minutes with Bud about the next piece of work you’ll have to sign. Not whether to buy. That decision has its own conversation, after the call.
You can inspect it. Eleven organizations started, nine completed the ten weeks, nine of nine extended, two in flight, as of September 2026. Two quotes, verbatim: a managing partner in mid-market private equity on the problem, a managing director in mid-market advisory on the result. Ten published essays and a coined term with a public definition. The founders’ careers, verifiable on LinkedIn.
What partners tell us after ten weeks; we haven’t measured it. The outputs make sense again. They know who owns what. They re-enter a matter or a deal at altitude. Their judgment carries past one decision and can be read. They see when an assumption has stopped being safe.
Not yet tested. Every installation so far came through a prior relationship with Bud. That record can’t tell you how the offer lands with a partner who doesn’t know him. What it can tell you is that every firm that finished extended, first to the rest of the partner’s team and then to other partners, and that decision was made after seeing it run, not on his word.
Ours. That two defaults in human–AI collaboration are close to fatal for serious knowledge work: the model developing the frame it’s handed instead of testing it, and the first fluent draft becoming the thing everyone edits. And that a checker at the end cannot be the whole answer.
Bud Bhattacharyya: the method, the model-side operating assets, the public thinking, and every installation. Elissa Stewart: operations and practice; every installation is scoped through her desk and held to the week-ten bar. We are alternately reviewer and producer on each other’s work. re:compound LLC. Two people, no software.
We think the last is the right first move for a partner who signs. This site is the argument. The alternatives are real.
Whether the work you have in mind is consequential enough to show whether this took hold. Whether the team is the right first team. Whether your firm’s approved AI environment is one the assets can be configured in. Whether ten weeks from now is the right time. You’ll know the answers; we won’t.
Whether partners who don’t know Bud recognize themselves in the first two sentences of this site. Whether the first cold conversations ask “what does this actually involve,” which would mean we haven’t answered the process objection, or ask “when.” We’ll update this page when we know.
A practical first step
Who’s bringing it, when, and whether that’s the team to start with. No deck, no demo, nothing to prepare.