Platform

Build the software your company actually needs. Run it on operations that already work.

VendorSpoke is a complete application, and most customers never want anything else. But if your team is going to build its own interfaces and assistants — and increasingly it can — we would rather that sit on top of us than beside us.

The expensive part was never the screen.

Put a competent developer and a good model together and you will have a working dashboard by Friday. What you will not have is the rest of it: a vendor who is qualified for this trade at this address today but not next month when the certificate lapses; an award that has to be blocked because of it; a commitment that routes to the person allowed to approve that number, lands against the right property and contract, and can still be explained when the owner asks about it two quarters later.

None of that is interesting to build, and all of it is unforgiving. It touches money, permissions, compliance and history at once, and the moment you write it yourself you are maintaining it forever — including the parts you only discover after the first disputed invoice.

So split the work along the line that actually matters. What is specific to your company is worth building and rebuilding as often as you like. What every operator in this industry needs — the vendor network, the bidding, the commitments, the approvals, the billing and the record of all of it — is worth renting from something that already does it.

What VendorSpoke keeps track of for you
Vendors & crews
Trades, coverage, classification, compliance documents, performance history
Customers & properties
Portfolios, buildings, units, contracts, markup rules, spending limits
Work
Projects, service orders, work orders, RFQs, bids, awards, assignments, daily logs
Money
Estimates, purchase orders, commitments, bills, invoices, deposits, cost codes
Control
Roles and module permissions, approval chains by amount, cost-blind and margin-blind roles
History
Financial event ledger with reversals rather than edits, plus an audit trail of actions
Every company gets an isolated workspace with tenant separation enforced at the database layer, not in application code. Anything built on top inherits that boundary rather than re-implementing it.
Worth building yourself
Maintenance intake that reads like your inbox
An agent that turns an emailed complaint into a drafted work order with the right unit, trade and photos attached, for a coordinator to release.
The report your owners keep asking for
Committed versus billed by property group, in the format that goes into their board pack.
A technician screen with three buttons
Built around how your crews actually work, in the order they work in.
An assistant that answers operational questions
"Which buildings are over budget on plumbing this quarter, and who approved the overage?"
Not worth rebuilding
Qualification and compliance
Expiry dates that change who is eligible, retroactively and mid-auction.
Bidding and dispatch states
Deadlines, escalation, tiered invitations, fallover, relisting, and the states in between.
Financial logic
Commitments, change orders, markup hierarchies, progress billing, deposits, pay-when-paid gates.
Identity, permissions and history
Staff, customers and vendors in one model, approvals by amount, and a ledger that survives an argument.

Building on it

The whole product runs on a typed interface over the data described above, and the assistant inside the app uses it under the same permissions a person has — a cost-blind role stays cost-blind when it asks a question rather than clicks a screen.

Customer-built tools use that same interface. Access is scoped to your workspace and to the permissions of the user it acts for, so a reporting tool cannot see more than the person who set it up. Tell us what you intend to build and we will point you at the right entry points and the integration patterns other customers use.

Available today
ShippingThe full application, the client and subcontractor portals, and the in-app assistant working under your permission model
ShippingProgrammatic read and write access for customer-built tools, scoped to your workspace and to the permissions of the user it acts for
ShippingData exports of your jobs, financial history and documents
Talk to usAccounting and payment integrations, and outbound notifications as work changes state