Product updates

VendOrca product updates are where I write about VendOrca, the AI-native vendor management system (VMS), itself: what it does, how a workflow runs in it end to end, and why we built it the way we did. This is not a changelog. Release notes tell you that something shipped. These posts tell you what problem it answers and what we gave up to answer it that way.

VendOrca is built for contingent and outsourced workforce programs. It takes a worker from onboarding through an assignment, approved time and an invoice to your accounts payable team, and you run it by asking in plain language. A few decisions shape everything else, and these posts keep coming back to them.

Program rules change by proposal. A Program Admin describes a change in plain language, VendOrca drafts it and shows what would change and how it would play out on sample work, and nothing takes effect until a person applies it. Software that configures itself should still answer to someone.

Records are added, not overwritten. A rate change adds a new version of the assignment and the old one stays. Invoices are built only from approved work, and a tie-out reports whether the invoiced and approved totals balance to the cent and lists every difference. Money questions get asked months later, and the system should be able to say what was true on the day.

VendOrca never touches your money. It runs the workflow, and your own payment run pays the invoices.

Agents read; they never write. People can connect an AI assistant over the Model Context Protocol (MCP) or VendOrca's application programming interface (API) with a read-only key in their own name, and that key sees only what they can already see.

Each post in this topic links to the docs page that shows the feature, so you can check what I say against how the product behaves. If a post and the docs ever disagree, the docs win, and I want to hear about it.