One orchestrated build behind every package

When reporting, the forecast and deal prep run as separate projects, each one keeps its own copy of the books. Every handoff between them is a chance for a number to change without anyone deciding it should.

Here they share one build. The variance, the forecast and, where one is built, the board deck come off the same workbook, so they agree. When a deal comes up, the deal work runs on the same system, and its figures trace back to the books the same way.

Each package goes through an automated check, and where a deck is built, it confirms the headline figures read the same in the workbook and the deck. A separate review goes to a reviewer that did not build the package and cannot edit it, and today a person sends it for that review.

The numbers come from code. Today, no language model computes, alters, or writes a number in what you receive.

Click the number you trust least. The formula bar shows the cells it came from, and the trail ends at the trial balance line as you exported it. Reject an add-back or move an assumption, and the schedules move with it.

Ahead of a sale or an acquisition, the questions a buyer's team is likely to ask come up while there's still time to deal with them.

Judgment calls stay with a person. An adjustment that needs a market input, owner compensation being the standing case, is identified and evidenced and handed over unsized. A check whose data didn't arrive shows as pending and names the missing input.