Orqen: the spreadsheet nobody admits is the real system.

A requester wants the vendor working yesterday. Procurement wants policy compliance. Finance wants clean tax and bank data. Legal wants acceptable terms. Security wants controls. The vendor just wants to know what's missing and when they'll be approved. Each team completes its own step correctly, and no single view answers the only questions that matter: what's the status, what's blocking, what's next, when will it finish.

I know this failure personally. In six years of finance operations I lived inside that invisible stack: the chase emails, the duplicate entry, the vendor discovering a missing document three weeks in. The PRD came from scar tissue, not imagination.

Companies already own procurement suites, ERPs, contract tools and payment systems. The failure lives between them, so the product should live between them too. The MVP is an orchestration layer: a vendor record vault, computed compliance freshness so documents expire visibly instead of silently, a full audit trail, and an AI assistant that answers status questions from live data instead of from someone's memory: retrieval-grounded, so it cites the vendor record rather than guessing, because a hallucinated compliance answer is worse than none.

Built and live: orqen.vercel.app, with the vendor vault, PAN, GSTIN, Udyam and penny-drop verification checks, compliance freshness, audit trail and a live-data assistant, designed to sync with the SAP, Oracle and Tally records companies already keep. Behind it: a 25-screen prototype across four surfaces on one design system.
Validated: the problem, through competitor teardowns and my own years inside the workflow.
Not yet validated: willingness to pay, and risk-based onboarding tiers. Both are marked as bets, and both are next.