Decision Architecture vs Private Advisory
Both are the top of the pyramid. Both are easily confused. Knowing which one the founder is actually asking for is the difference between paying for a frame and paying for a seat beside the frame.
9:02 AM. The founder calls and asks "can you help me think through whether to sell." A decision architect asks what the question underneath the question is. A private advisor sits beside the founder while the founder thinks. Different roles. Same hour. Same call.
When Decision architecture is right
The frame is wrong, not the answer.The founder keeps reaching the same answer and the answer keeps failing. The work is one layer up. Naming the actual question is the deliverable.
Three departments are solving three different problems.Each department is internally consistent. The company is incoherent. The architecture is missing.
A binary feels forced.Either-or framings are usually a sign of frame compression. Decision architecture asks what the missing third option is.
A decision has been "made" six times and keeps reopening.Reopening signals the frame is not done. Naming it ends the cycle.
When Private advisory is right
The frame is clear. The judgment is loaded.The founder knows what they are deciding. Everyone close to them has an incentive in the answer. Outside judgment becomes the cheap fix.
The decision will close in two weeks.An architect needs a quarter. An advisor needs a Thursday. Time horizon matters.
The founder is thinking out loud and needs a sparring partner.Not an analyst. Not a friend. Someone with no upside in the answer.
The decision is structurally irreversible.M&A. Cap-table moves. Co-founder splits. Advisory sits there.
Structural differences
| Decision architecture | Private advisory | |
|---|---|---|
| Subject of the work | The shape of the question | The operator inside the question |
| What gets built | A frame the company can use later | Judgment in this specific call |
| Engagement shape | Diagnostic engagement over weeks | Ongoing seat through specific decisions |
| When it ends | When the frame is named and adopted | When the operator stops needing the seat |
| What fails when wrong | A clean frame nobody acts on | A confident operator working from the wrong frame |
Real situations
Decision architecture is the answer
Five years of "should we expand to Europe" that was actually "should we be a different kind of company." Decision architecture surfaces the second question. The first one becomes obvious.
Private advisory is the answer
Private advisory in the call when the term sheet comes back. Architecture is too slow now. The advisor is the seat.
Neither is the answer yet
They need to sleep on it for a week. Then most of the anxiety becomes a specific question, and the right layer becomes obvious.
Who to choose when
If both feel partially true, the architecture probably comes first. Build the frame. Then bring the seat. Decision architecture explained.
When advisory fits
If the question is one layer above the comparison on this page, private advisory sits with the operator before money goes out the door.
See ways to work