| Supplier | POs | Spend |
|---|
A dated term sitting directly on the purchase filing. Confirmed only — no guesses, no inferred dates. Tick Only terms still running above to see just what has not lapsed.
| Status | Ends | Supplier | Description | Amount |
|---|
| PO # | Dept | Supplier | Description | Category | Start | Amount |
|---|
A purchase order tells you what a department bought. It doesn't tell you what survived, what's actually in production, or who owns it. Their own CalCareers job postings do — a department hiring someone to administer a platform is telling you that platform is running, staffed, and load-bearing. This is a second, independent source: nothing below comes from the purchase record, and every line links to the posting it came from.
Corroboration. DMV staffs for Salesforce and has filed 94 purchase orders naming it — that install base is real, and you can reference it in a meeting without hedging.
The interesting one. DMV hires for LoadRunner and Jama with no purchase order behind either — so it arrived inside a reseller bundle, on another agency's vehicle, or on a contract that lapsed. Each is a different conversation, and a question their own posting earns you.
Some gaps mean nothing: CDT staffs for Python and DMV for JMeter, and both are free. Absence of a purchase order is only a lead where the product costs money.
explicit the posting names the product outright. implied the posting describes the function unmistakably without naming a vendor. Follows the department filter above.
This is two departments out of 176.
The licensed edition covers every one of them: an Account Runbook per department with named buyers and technical owners, a grounded advisor that drafts your notes, and a 30-day refresh.