Feature
Vendor memory that goes beyond a contact list.
Steward's vendor book turns confirmed service events into practical memory: who worked on which building, which asset they touched, what it cost, and when they last showed up.
Vendor history rolls up from source-backed service events.
Spend and engagement context stay tied to buildings and assets.
The vendor book feeds the packet instead of becoming another spreadsheet.
Proof boundary
Vendor performance conclusions require real customer usage and should not be inferred from invoices alone.