- contact@verticalserve.com
Someone asks for a tool in one sentence. Agents do the intake, find the tool you already pay for, read the SOC 2 report and the contract with the page for every finding, score the risk, run security, privacy, legal and finance reviews in parallel, watch the vendor afterwards and come back before the renewal with a recommendation. Your reviewers get a prepared decision — and stay the ones who make it.
Breaches that start at a supplier, outages at a shared provider and AI tools that learn from your data now land on your desk, your regulator’s and your customers’. Meanwhile the review is still a form, a ninety-page PDF, a redline from scratch and an email chase — and the business waits.
Reviews run one after another, nobody owns the queue, and every lane starts from zero. So people buy on a credit card and the vendor never reaches review at all.
A vendor ticks “yes” to two hundred questions their SOC 2 already answers — or contradicts. Reviewers read the answers, not the report, and the exception on page 41 goes unseen.
The SOC report expires, the vendor is breached, a new subprocessor appears, the contract auto-renews. None of it reaches the person who could act until the renewal invoice does.
Third-party risk is usually sold as a control and resented as a bottleneck. InsightVendors is built so the thorough path is also the quick one: agents do the reading, the chasing and the arithmetic, reviews run side by side, and every decision carries its evidence.
What comes out — who asked, what the vendor touches, what the documents prove, who approved and on what conditions, what changed since — is exactly what an auditor or a regulator asks to see.
The business case for agentic third-party riskOne lifecycle for every third party, from the first request to the exit. Agents prepare each step; people make each decision; everything lands in one record.
One sentence. The Intake agent names the vendor, the category, the data and systems it will touch and the spend — and warns when you already have something that does the job.
The Risk agent sets the tier and an inherent score from what the vendor touches. Routing rules add the review lanes and the documents each needs, and record why.
Agents read the SOC 2, ISO certificate, pen test, insurance, DPA and contract, pre-fill the questionnaire and send the vendor only what is left, through a portal.
Each lane approves, approves with conditions, rejects or sends back — in the console or from a signed email link. Conditions become tracked findings.
Breaches, financial news, expiring documents and silent vendors arrive as signals. The Monitoring agent sizes the reaction to the vendor’s tier.
Before the notice date, the Renewal agent recommends renew, renegotiate or offboard — with spend, risk trend and open findings to back it.
A requester writes what they need the way they would say it. The Intake agent turns it into a request, flags what it could not tell, and checks your vendor list and contracts first.
One sentence in the console.
Plus the vendor, title and category, and the five questions it could not answer: CRM integration, sensitive data in calls, internal owner, SSO, the DPA and data residency.

The Document agent reads what the vendor has already produced and the Contract agent checks every clause against your playbook. Reviewers check the findings against the quoted text instead of reading from page one.
Type, period, auditor, opinion, exceptions, complementary user entity controls you must operate, subservice organisations and the bridge-letter gap.
ISO 27001, 27701 and 42001 scope and expiry; cyber, E&O and general liability limits checked against the minimum for the vendor’s tier.
Date, tester, open critical and high findings, and whether a retest shows them fixed.
Subprocessors, breach-notification window, data location, transfer mechanisms and deletion. Subprocessors become your fourth-party map.
Liability cap, indemnity, termination, auto-renewal, notice period and governing law — each deviation from your playbook with a proposed redline.
Going-concern language and liquidity in statements, alongside financial signals such as layoffs and acquisitions.


Deterministic arithmetic with weights you own, every point listed. The agent explains the score; it never invents it. Tier and residual risk decide how deep the review goes and how often it is repeated.

From the demo organisation. A residual score that stays high after strong evidence is the signal to work the findings list: here, mostly insurance and pen-test details awaiting confirmation.
The Assessment agent picks the questionnaire the tier calls for — Core (SIG-Lite aligned), Privacy & DPA, AI vendor, business continuity, financial health — pre-fills every answer your documents already prove, marks where each came from, and prepares the invitation.

Breaches, financial news, expiring reports and vendors that stop answering arrive as signals; the Monitoring agent decides between a note, a finding, a re-assessment or an escalation. Renewals arrive before the notice date with a recommendation.


Intake, Research, Risk, Assessment, Document, Contract, Monitoring, Renewal, Remediation and Copilot. Each runs at the level you choose, every action is recorded with what it cited, and every message waits in the outbox until a person releases it.

Tier × residual risk heat map, critical findings, and the Copilot answering in plain words with links.
Average days per review lane and what is open in each, so the bottleneck has a name.
Spend under management by tier, duplicate tools caught at intake, and renewals with notice dates.
Tiering, due diligence, contract terms, monitoring and exit — recorded per vendor, exported to InsightAssure.


The same product either way. Vendor contracts and SOC reports stay where your regulator wants them.
We run it; you invite your reviewers and import your vendors. Shared monitoring and, as it arrives, the vendor network.
Docker Compose with your PostgreSQL and identity provider, and the AI model of your choice — or none.
PostgreSQL row-level security on every tenant table, so a missed filter in code still returns nothing from another organisation.
Not by reviewer seat, so the whole business can request and approve. Ask us.