Every model is the sum of a hundred decisions

The decisions that shape a planning model

• Attrition as a rolling twelve-month average or a fixed rate.
• Headcount planned by position or by department.
• FX from treasury's month-end rate or the market average.
• Allocations by headcount, revenue share or a driver per cost pool.
• What goes in release one, and what waits.

Each one is usually settled in a call with the customer's finance team, written in a recap, and forgotten until a new FP&A lead asks why the model works the way it does, or the customer's CFO disagrees at go-live.

What Sealbook gives a partner

• A design-decision register built from the call transcripts, each decision with the quote that made it.
• The customer's model owner confirms each one, so the register is theirs as much as yours.
• Change requests when a later conversation contradicts an agreed design, so rework becomes billable change.
• A handover document at go-live that explains the model in the customer's own words, with a fingerprint that shows it wasn't edited afterwards.

The sample project in the demo is a planning implementation, so you'll recognise the decisions.