Procurement that follows your rules.
Solicitation, competition, award, purchase order, work and billing on one connected record — configured around the purchasing methods, thresholds and approvals your organization already operates under.
Your organization defines the procurement rules. VendorSpoke makes them operational — and keeps the record the work itself creates.
Your procurement policy shouldn't live only in a PDF.
Purchasing authority, dollar thresholds, required competition, approval levels, vendor eligibility, exceptions, emergency procedure, documentation. All of it exists — in a 74-page manual a buyer is expected to recall at the moment of purchase.
VendorSpoke turns those rules into a routing engine. It doesn't tell staff what the policy says; it sends the transaction down the path the policy requires, and records why it went there.
Different purchase, different process. Same record.
Five genuinely different ways a purchase can begin — each with its own controls, its own competition and its own documentation. All five end up on the same record.
A sealed bid and a 4 a.m. emergency award begin nothing alike. They converge here — same authorization model, same purchase order, same billing, same history. Which paths your buyers can reach is a matter of your rules, not five buttons everyone sees.
Two ways to run price competition, and they are not the same thing.
Every response is submitted before the deadline and stays inaccessible until the opening point you configure. Nobody sees a number early, including staff.
Qualified vendors see their standing and can improve their price inside a defined window, instead of submitting one static number each.
Easy for vendors doesn't mean loose controls for procurement.
Where the process permits it, an invited vendor can receive a text message, open a secure link and respond — without being pushed through account creation, password resets and a portal they will use twice a year.
The two-person paving outfit responds as easily as the firm with a bid department. Your side of the process — who was invited, what was submitted, when, and by whom it was reviewed — is unchanged.
The award shouldn't be the end of the procurement record.
Solicitation in one system, award in a spreadsheet, purchase order in a second system, invoice in a third, and the history reassembled by whoever is still employed. Each step below is created by the step above it, on the same record.
Built for scrutiny.
A purchase can be questioned years later, by an auditor, a council member, a losing bidder or a reporter. The question is rarely “was this a good idea” — it is “show me what happened.”
Because the record is a byproduct of doing the work in the system, it also outlives the people who did it. Who was invited last time, who responded, what they charged, how the job went, what was billed — that history sits on the vendor and the job, not in the inbox of the buyer retiring in March.
- What was requested, and when
- Who had the opportunity to respond
- What came back, and at what time
- What was selected, and on what basis
- Who approved and authorized it
- What changed afterward, and what was billed
Where the selection is not the lowest number, the reason and the approval are captured with it rather than remembered.
Move quickly without losing the record.
A main breaks at 4 a.m. A roof fails in a storm. A building is unsafe by morning. Nobody is going to run a formal solicitation first, and your rules already say so.
An emergency is a different workflow, not the absence of one. The exception invoked, the justification, the vendor accepted, the authorization and the eventual bill are captured while the crew is being dispatched — not a week later from memory.
- 04:12Exception invoked · public health and safety
- 04:14Justification entered by on-call supervisor
- 04:19Hollis Underground accepted by text · on-call vendor
- 04:31Crew on site · work order open
- 09:40Authorization confirmed · public works director
- +6dVendor bill received against the same record
Shaped to your agency. Never boxed in by ours.
VendorSpoke ships as a complete application — intake, solicitations, competition, approvals, purchase orders, bills and reporting — and most agencies run it as it comes. Nothing here needs to be built to get started.
But every agency has something the standard interface should bend to: an intake form that mirrors a department's own process, a report in the format the council already reads, solicitations flowing into the ERP. Those are not workarounds. The same objects the interface runs on are open to you, so the system extends to fit your process instead of your process adapting to the system.
Vendor records, bidding, permissions, purchase orders and billing history are the part nobody should rebuild. They are provided, and they are the same whether you use the interface as shipped or shape it to your agency.
Walk us through your procurement process.
Bring your purchasing policy, your thresholds, your approval structure and the two or three purchase types that cause the most paperwork. We will map them into VendorSpoke with you and show you the workflow your own rules produce.
Examples on this page are illustrative, not legal guidance. Agencies, projects, vendors and thresholds shown are fictional.