Procurement OS

An agent operating system for hotel FF&E procurement, from budget to close-out
Proposal for Hotel Properties Limited

Every 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.

Process
14 stages
Plan · Source · Deliver · Close
Agents
—
status against this demo
Decisions kept human
—
budget, bid list, RFQ, award, PO, approvals, payment
Rule
Cite or it did not happen
every finding names the document and page

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

The reply loop
Email arrives→Matched to its point→Point updated→Digest to the buyer↺

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.

Escalation
Reminder→Second reminder→Relationship owner→SVP

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.

What never sends itself
RFQ·Award·Claims·Anything with money

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.

What it saves
Asking·Chasing·Reading·Retyping

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 register
Loading register…
Price memory. The "Last paid" column in the vendor comparison is the seed: every PO line becomes a reference for the next tender of the same item type, with vendor, date, quantity and incoterm. With HPL's last three years of POs loaded, every negotiation starts from what HPL actually paid, not from the vendor's opening number.

Value 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.
Step 1 · Discovery · 2–4 weeks

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
Gate: findings verified by HPL on real documents, baseline signed, scope of the build agreed
Step 2 · Build · 2–4 weeks

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
Gate: one live tender levelled, negotiated and awarded through the system, side by side with the old way, with no unexplained difference
Step 3 · Launch & validate · 2–4 weeks

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
Gate: measures against the baseline, savings ledger signed by finance; HPL decides on the portfolio rollout
What HPL provides. PO and cost-report formats (received), three years of POs and change orders, the approved vendor list, designer spec packs per project, opening dates and budgets, a mailbox for outbound clarifications, and one named owner for the rollout. What Maxify delivers. The agents above, running on HPL's documents, with every output citing its source, and the weekly measured ledger.

Governance

The system is designed so that trust is earned by evidence, not asked for.
People signBudget, bid list, RFQ, award, PO, change order, payment. An agent drafts; it never commits HPL to anything.
Deterministic checksEvery compliance and money check is a rule, not a model. The same inputs give the same issues, and each one cites document and page.
Two kinds of emailRoutine messages (reminders, acknowledgements, document and status requests) are sent by rule from HPL's mailbox and logged. Anything that negotiates, awards, claims or commits is drafted by the system and sent by a person. HPL chooses the mode per touchpoint.
Audit trailEvery extraction, check, decision and email is logged with who, what and when, and can be exported.
Data stays HPL'sDocuments and the register live in HPL's tenant; vendor data is used for HPL's negotiations only.
Measured, weeklyIssues open by severity, bids levelled within 48 h, items at risk, forecast vs budget, savings ledger, vendor response time, invoice match rate.