Trust-management softwareSource-backed brief

How did Vanta find customers? Service work before software

[Inference] Vanta’s early story is a useful study of when manual work can be more informative than software. A founder who helps a company understand a compliance gap can observe the actual documents, uncertainty and coordination involved. That makes demand more tangible. It does not yet establish a scalable delivery model, a paying customer or the economics of a mature compliance platform. Those distinctions are central to interpreting the supplied founder account.

Evidence and interpretation

This story condenses a source-backed brief. Some historical details and internal metrics are not established. [Inference] marks analysis. Source numbers keep the numbering of the full case, and the evidence is from the 10 Nov 2026 research edition. Read the research method.

The first evidence came from concrete service experiments

Christina Cacioppo describes preparing a SOC 2 gap-assessment spreadsheet for Segment and a reusable version for Front. A referral suggested demand beyond the initial work. Early software gathered inputs while people still produced reports manually. The interview does not establish that the first spreadsheet experiments were paid contracts. [1]

[Inference] The important commitment was participation in a real assessment, not enthusiasm for a hypothetical product. Working through actual material could reveal which questions repeated and which depended on customer context. That is more useful discovery evidence than simply collecting approval for the idea of easier compliance.

The beachhead connects preparation with a business constraint

[Inference] Startups preparing for enterprise sales can have a practical reason to organize evidence and understand gaps. The buyer is not necessarily seeking another dashboard; they may need clarity about the work required before a commercial conversation can progress. That creates a useful discovery question: which uncertainty is blocking action today? The answer might concern missing evidence, unclear responsibility or unfamiliar requirements. These are hypotheses to test with the customer, not established descriptions of every early Vanta account or a claim that software alone supplies certification.

A simple deliverable can reveal a complex buying group

[Inference] A spreadsheet is accessible, but its contents can involve several owners. Engineering may understand systems, leadership may own priorities and another person may coordinate evidence. The founder needs to discover who can provide information and who can authorize changes. A successful assessment is therefore not equivalent to a completed organizational sale. The practical evaluation should separate comprehension, agreement on actions and willingness to pay for ongoing assistance. This avoids mistaking a helpful one-time interaction for a repeatable subscription opportunity.

Founder learning extended into the sales process

The account describes using the Y Combinator network to identify prospects, including early customer Lattice. Cacioppo later asked outside salespeople to review her scripts and conversion process. These details establish routes to learning and prospect access, rather than a fully documented first-contract sequence. [1]

[Inference] External review can help a technical or product-oriented founder notice where an explanation becomes confusing or a conversation lacks a clear next step. The useful capability is willingness to expose the sales process to scrutiny. The source does not identify a complete early sales team, formal training curriculum or individual seller performance.

Manual delivery should expose what deserves automation

[Inference] The strongest product question is which recurring work can be standardized without hiding necessary judgment. Gathering inputs, maintaining context and making missing material visible may require different approaches from interpreting an unusual situation. If every customer needs extensive bespoke work, apparent demand can conceal a costly service business. If repeated tasks become easier while customers still understand the result, software has a clearer economic role. The reviewed evidence does not establish onboarding cost, current pricing, account expansion results or retention, so neither SaaS margins nor a mature success organization should be assumed.

What the founder experiment does and does not prove

[Inference] Vanta’s transferable lesson is to make the customer’s problem concrete before choosing the automation boundary. A better next experiment would compare repeated assessments, identify where labor remains necessary and test whether customers value ongoing visibility after the initial deliverable. Referrals can indicate relevance without proving a scalable acquisition cost. The first paying identity and detailed conversion sequence remain unresolved here. The case supports service-led discovery and deliberate sales learning; a complete growth verdict would require evidence of paid continuity, delivery efficiency and customer outcomes beyond the initial assessment.

GO DEEPER

Vanta: the full GTM case

The complete case holds the named people, the economics, the available historical evidence, the critique and the open research questions.

Read Vanta’s full GTM case

Terms in this story

Enterprise salesWillingness to payCustomer onboardingCustomer retention

Questions behind the story

How do I choose between product-led and sales-led growth?Why does the site leave CAC and retention blank for some companies?All 104 GTM questions answered

Sources

Numbers match the source list of the full Vanta case. A source’s publication date and the date of the event it reports can differ.

  1. Vanta's Path to Product-Market Fit — Solve the Customer’s Problem, Then Write Code review.firstround.com