Procurement OS
An agent operating system for hotel FF&E procurement, from budget to close-outEvery document read, every check run, every deadline computed. People decide; agents do the rest.
Procurement today is a chain of hand-offs held together by PDFs, spreadsheets and email. The operating system below reads every document into one register, runs the checks deterministically, keeps money and time in two live loops, and turns every purchase HPL has ever made into negotiating power for the next one. The demo you have seen is the first six agents on real Mahé documents.

The process, end to end
Fourteen stages in four phases. Open a stage for what is manual today, which agent takes it, which decision stays with a person, and how it is measured.Four control loops
A stage list is not a system. These four loops run continuously across the stages and are what make the work compound.Ten agents, one register
Each agent has a narrow job, reads and writes the same item register, and has one thing it never does. Status is against the demo as it stands today.Vendor communication, automated at the right moments
Most coordination cost is email: asking, reminding, chasing, and reading what came back. Every agent above writes and reads through one outbound mailbox and one inbound reader, at the moments below. Two modes: routine messages are sent by rule; anything that negotiates, awards, claims or commits is drafted and a person sends it.Fourteen touchpoints, one thread per vendor
Every outbound email carries a reference per point. When the reply comes in, the reader matches each answer to its point, marks it answered, accepted or still open, and re-asks what was skipped. The buyer gets one morning digest: who replied, what is settled, what needs a decision.
Silence is a signal. A vendor that does not answer a check-in in three days is chased once more, then the relationship owner is told, then the SVP. Response time feeds the vendor scorecard.
Rule-based messages ask, remind and acknowledge. They never change a price, a quantity, a date HPL has committed to, or a specification. Those are drafts, and a person sends them from HPL's mailbox.
In the value model, the manual-hours lever is mostly this: the hours a buyer spends writing the same email to the same vendor, and reading the reply to update a spreadsheet. The system writes it once, in one thread per vendor, with the evidence attached.
Portfolio leverage
Two sources of negotiating power HPL already owns and does not yet use: the same item types across concurrent projects, and the price on every PO ever issued.Same item type, several projects
from the live registerValue model
Illustrative and editable. The percentages are ranges typical of levelled tenders and three-way matching; the point of the pilot is to replace them with HPL's own numbers.Rollout: discovery, build, launch
Maxify's process, not the project's calendar. Three steps of two to four weeks each, six to twelve weeks in total, each ending at a gate HPL can fail. Live projects keep running on whatever is already proven.Read HPL's process and documents
- Walk the 14 stages with the procurement and installation team: who does what, in which file, with which hand-off
- Load HPL's real documents: spec packs, quotations, POs, GRNs, invoices, three years of PO history, the approved vendor list
- Run Document Intelligence and Compliance Guardian on them; HPL verifies every finding against the page
- Agree the measures and the baseline: hours per tender today, change-order rate, bid-to-award days, invoice match rate
Configure the agents to HPL's way of working
- PO, cost report and comparison in HPL's own formats; vendor profiles and price history from HPL's POs
- Tender Desk, Expeditor and Negotiator wired to HPL's mailbox, calendar and approval chain
- Human gates placed exactly where HPL signs today; audit log and exports
- HPL's team trained on one live tender in parallel with the old spreadsheet
Run it live and measure
- All live projects on the system; weekly steering pack to the SVP
- Payment Guardian on every invoice; Logistics & Receiving on every shipment
- Savings ledger kept weekly: awarded vs first bid, awarded vs last paid, change orders avoided, hours removed
- Vendor scorecards and the first close-out