Hertz runs four rental brands, Hertz, Dollar, Thrifty and Firefly, sharing fleet, systems and operational scale. A contract for any of them has facts that live in more than one place: what the sourcing record says, what the ERP says, what the supplier master says. Most tools quietly pick one. This board does not. It reads all of them and shows a conflict as a conflict, not as a guess.
The four-brand structure is public, from Hertz's own newsroom and investor materials. Every contract below is sample data generated for this page. No counterparty, spend figure, or Hertz system appears here.
Filter by brand, category, or status. Select any row to open it and see exactly where each fact came from, and where two systems do not agree.
| Reference | Brand | Category | Counterparty | Status | Reconciliation | Renewal |
|---|
This page runs on sample data. The production board reads from the systems a procurement and contracting team already runs, the sourcing platform, the ERP, the supplier master, the compliance file, through access you issue and can take back. It does not decide which system is right. It shows you both and lets a person decide.
The board reads. It never writes back to the sourcing platform, the ERP, or the supplier master, so nothing in a system of record changes because the board exists.
Access is limited to the contracts in scope. For a pilot, that means one brand or one category and nothing outside it.
Revoke the access key and the board goes dark. Nothing to uninstall, and no data left behind that you did not already hold.
Small enough to approve inside a new function. Large enough to know whether it earns a place next to the systems already in use.
Connect one category's contracts through read-only access. The board fills from what already exists, and every field names its source.
A weekly read with the contracting lead. What renewed, what is still a conflict between two systems, and what spend has no signed document behind it.
Keep it and add a category, or switch it off. Either answer is a clean one.
Great Breads Studio is a design and technology studio in Harlem, New York. The studio designs and engineers systems for founders, brands, and public-sector clients, and builds its own software products alongside brand, web, and editorial work.
The studio built this board. It is shown here with sample data so it can be read without a login. The studio is not a legal or contracts adviser and the board makes no determination about which system is correct: it surfaces the disagreement and names both sources, so a person decides.