Title
deals modeled
decks rendered
recurring infrastructure
The platform
Not a chat box bolted to a template. A deck engine with a versioned content library, a tenancy model with a single credential surface, and a ledger that can answer what a deal cost.
Twelve slides composed from a versioned option library and rendered against the real master — native tables, no SmartArt, a print-ready PDF every time.
Every row carries its firm. Row-level security is the mechanism, not a convention, and one process holds the database credential.
Every model call is metered, attributed to a deal and checked against a cap before it runs. A refused request costs nothing and says so.
How it works
A warm deal skips the deck and enters at engagement. Everything else walks the whole rail, and every crossing is recorded.
Five fields close the transaction gate: type, size band, industry, metro and origination.
Slots resolve against the approved option library for that transaction shape.
python-pptx builds the deck on the firm master; LibreOffice produces the PDF.
A reviewer signs off, the watermark drops, and the delivery copy is exported.
Budget caps refuse spend before the call. Approvals gate the watermark. Row-level security decides what a query can even see. Nothing here is a policy document.