- contact@verticalserve.com
Each one is a worked example on the demo organisation, Northwind Labs, and its fictional vendors, with the screens at every step: what the requester asks, what the agents prepare, what each reviewer sees and decides.
Support wants an AI tool that drafts replies from ticket history. Six lanes, the AI questionnaire, and terms that let the vendor train on your data.
one sentence → tier 2 → 6 lanes → AI questionnaire → conditions SecurityType, period, opinion, exceptions, CUECs and subservice organisations, each with its page — and the Type I with a future-dated period.
upload → extract → findings with pages → CUECs Legal & privacyTen clauses checked, eight deviations, a proposed redline for each, approved by a lawyer in the agent inbox.
MSA → playbook → 8 deviations → redlines RiskA credential-stuffing incident at a vendor holding customer data becomes a re-assessment, sized to its tier.
signal → reaction → re-assessment → renewal Vendor riskAn accounts-payable vendor’s SOC 1 expired in September. Validity, signals and bridge letters keep assurance current.
expiry → signal → finding → request Procurement & financeRenew, renegotiate or offboard — decided before the notice date, with spend, risk trend and findings.
notice date −90 → recommendation → decision ProcurementA second call-recording tool caught at intake, and the request that becomes a new use instead.
sentence → duplicate → new use RiskSubprocessors and subservice organisations turn a vendor list into a graph.
DPA + SOC → fourth parties → concentrationOne sentence, a status page, and an answer in days rather than weeks.
Findings with pages, a score with reasons and redlines drafted — check, change, decide.
Duplicates caught at intake, renewals before notice, spend under management by tier.
Tiering, due diligence, monitoring and exit recorded per vendor and exported as evidence.