Agenda
GLOSSARY
Agenda
GLOSSARY
Venture Clienting has its own shared vocabulary. These 19 terms recur throughout this guide and in any conversation with a practitioner — bookmark this page as a standing reference.
The transition of a solution from pilot testing into full rollout or production use, involving budget allocation, user training, process integration, and performance monitoring.
An internal champion, typically one or two people per business unit, who actively spots operational pain points and brings them to the VCU. Ambassadors extend the VCU's reach and create a steady inflow of warm, pre-qualified leads. Programs generally start recruiting ambassadors once they have a few successful PoCs to point to.
See also: Part 5, Startup relationships and ambassador networks.
A sourcing output that compares a small number of startup candidates (typically three to eight) directly against defined, measurable criteria. Used once requirements are clear and you're ready to decide.
See also: Part 4, Startup sourcing.
A stakeholder who has seen Venture Clienting deliver results firsthand and now actively advocates for it: bringing unsolicited leads, defending the program in internal conversations, and helping it survive leadership changes. A deeper relationship than an "ally," who simply cooperates when asked.
The bar a startup needs to clear to be a credible PoC candidate. Not a function of company size, but of three things demonstrated in practice: maturity to deliver (completed PoCs with other corporate customers), credibility with clients (real, checkable references), and the resources to show up (a dedicated team, not one juggling twenty other pilots).
See also: Part 4.
A framework describing the sequence a program moves through as it builds up, related to but separate from the maturity levels below, using its own thresholds that don't line up exactly (Scale starts at €500k budget, roughly where Pro also starts).
See also: Part 3, including the 100-day roadmap for the Start phase.
The share of completed PoCs that move on to full implementation. The benchmark across mature programs is 50–60%; below 40% usually signals poor scoping, above 70% often means PoCs are being scoped too conservatively. One of the eight core KPIs.
See also: Part 5.
The five tests a PoC lead has to pass to stay alive: a real and urgent problem, meaningful business impact, decision-making authority behind it, a reasonable (not overly rigid) set of requirements, and genuine willingness to invest budget or time. Failing any one is grounds to kill the lead rather than let it drift.
See also: Part 4.
A sourcing output that maps the solution space broadly across multiple categories or vendor types, typically fifteen to fifty startups across three to five categories. Used when requirements are still loosely defined and you want to explore what's available before narrowing down.
A classification used to benchmark where a program currently stands: Starter (fewer than five PoCs a year, budget under €100k, one to three FTE, ~€75k avg. cost per PoC), Growing (six to fifteen PoCs, €150k–€0.5M, two to eight FTE, ~€50k avg. cost per PoC), and Pro (fifteen or more PoCs, €0.5M+, eight to twenty-plus FTE, ~€30k avg. cost per PoC). This is the framework used for cost, KPI, and ROI benchmarks throughout the guide.
See also: Part 2.
A structured conversation between a VCU member and a Pain Point Owner to understand a business problem in depth before committing sourcing resources. Covers problem definition, urgency, decision authority, budget, and expected impact.
See also: Part 4.
The internal person, usually a department head or senior manager, responsible for the business problem being solved. The PPO defines success criteria, sponsors the PoC within their business unit, allocates resources, and makes the adoption decision if the PoC succeeds.
The general definition: a proof of concept is a small-scale exercise used to test whether an idea or solution actually works in practice before committing to it fully. In Venture Clienting specifically, a PoC is a short, structured test of a startup solution against a defined internal business problem. PoCs typically run four to eight weeks and cost roughly €5,000–€30,000 for the startup's side of the work, plus internal resource time. Every PoC has defined success criteria, a clear scope, and a binary decision point at the end.
See also: Part 4, PoC execution.
The three categories used to diversify a PoC portfolio (roughly a 60/30/10 split). Quick wins are low-complexity, high-likelihood, and build early credibility. Strategic bets are higher-risk, higher-timeline, and create outsized impact. Innovation enablers are foundational investments, like data pipelines or reusable models, that unblock future PoCs rather than solving one problem directly.
See also: Part 5.
The short brief sent to a chosen startup once a PoC is scoped: problem statement, proposed scope, success metrics, timeline, and a request for both PoC and indicative subscription pricing. The startup's response becomes the basis for procurement and kickoff.
See also: Part 4.
A documented commitment on response times and support levels, most often discussed in the context of IT's requirements for implementation or a startup's support model post-PoC. Pro-level programs formalize SLAs with procurement, IT, and legal rather than relying on informal goodwill.
The practice of buying and testing startup products to solve specific, measurable internal business problems. Unlike Corporate Venture Capital (which invests) or Corporate Venture Building (which builds new ventures), Venture Clienting positions the company as a customer and pilot user of startup innovation, gaining access to novel solutions faster and at lower risk than building internally, while giving the startup revenue and validation in return.
See also: Part 1.
The internal team that runs the Venture Clienting program. Size and structure scale with maturity, from one person at the smallest programs up to twenty or more at the largest. The VCU owns the process: identifying problems, sourcing startups, scoping PoCs, managing delivery, and reporting results. Business units own the problem itself and the decision to implement.
See also: Part 3.
A statutory employee representation body, common in Germany and other European jurisdictions, whose approval is required for any PoC or implementation involving employee data, tracking, or monitoring. Best engaged early and designed around wherever possible.
