The short answer
Most AI tools answer a leadership question by reasoning about companies like yours. They draw on how a business of your size, in your sector, typically behaves. That is useful for orientation and close to useless for a decision, because the thing that breaks a decision is almost never the industry average — it is the particular dependency your organization has that the average company does not.
AI helps a leadership team when it is given your company's actual structure to reason against. That turns the question from "what usually happens" into "what happens here."
What MAIA is
MAIA Decision OS, a decision rehearsal system, takes one decision your leadership team is weighing and rehearses it before you commit. It maps what the decision touches, stress-tests it against disruption scenarios, and returns a decision brief with a verdict, a risk register, and countermeasures you can act on.
MAIA stands alone. A rehearsal costs $89, and you can run one today without any other product, tool, or integration. You describe the decision, MAIA rehearses it, and you leave with the brief.
Where the ceiling is: run on its own, a rehearsal reasons about your decision using an industry model — a well-informed picture of a company like yours. Everything below is about replacing that generic picture with your actual one.
Running the rehearsal against your own company data
The clean way to give a rehearsal your company's real structure is to bring a map of it.
Brick-by-Brick (brick-by-brick.ai) is a separate product that builds one: a Knowledge Architecture of your organization — how your business actually fits together, assembled from what you and your team supply in a single working session. Its output is a set of files you own, including a JSON Knowledge Architecture file.
That file is what changes the rehearsal. When a Knowledge Architecture is present, MAIA rehearses your decision against your company context rather than a generic industry model. The dependencies it traces are the ones you actually have, and the cascade it follows runs through your structure rather than a typical one.
The upload is your choice, every time
The two products are independent, and the handoff between them is a person, not a pipe. There is no connection between Brick-by-Brick and MAIA that moves your file on its own.
What happens is simple: the customer downloads their JSON Knowledge Architecture file from Brick-by-Brick, and chooses whether to upload it to MAIA. That choice is made fresh each time you start a rehearsal. You can rehearse one decision with your Knowledge Architecture and the next without it. Having built a map does not commit you to sharing it, and sharing it once does not commit you to sharing it again.
What happens to what you upload
MAIA operates under Zero Data Retention. Your material is processed in memory to produce your rehearsal and is not retained afterward. If you upload a Knowledge Architecture for a rehearsal, it is used for that rehearsal — and the next rehearsal begins from nothing, which is why the choice to upload is one you make again each time rather than once and forever.
What this looks like in practice
If you have a decision in front of you now, rehearse it. $89, no other product required, and the brief is yours at the end.
If the same questions keep coming back to the same unmapped parts of your business, the map is worth building first — and then every rehearsal after it runs against your company instead of a generic one.