# How to win a first enterprise software customer without faking maturity. - working worksheet

Reviewed alongside the Eli guide: https://hireeli.io/resources/win-first-enterprise-software-customer

## Decision to make

Navigate the first enterprise sale with honest proof and a narrow implementation

Owner: ____________________
Review date: ____________________
Canonical page or destination: ____________________

## Buyer questions

- [ ] How to win a first enterprise software customer without faking maturity?
- [ ] What should a B2B startup do first to navigate the first enterprise sale with honest proof and a narrow implementation?
- [ ] Which evidence shows that navigate the first enterprise sale with honest proof and a narrow implementation is working?
- [ ] What is the most common mistake when teams try to navigate the first enterprise sale with honest proof and a narrow implementation?

## Evidence-led work plan

### 1. Why this decision appears: enterprise buyers need risk reduction

Enterprise buyers need risk reduction, but an early company rarely has the logo wall, security history or implementation team of an incumbent.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 2. Sell a bounded business outcome with explicit limits, named ownership and verifiable security and product facts. 

Sell a bounded business outcome with explicit limits, named ownership and verifiable security and product facts.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 3. Map the buying committee and the economic problem, then create a truthful security and implementation pack

Map the buying committee and the economic problem.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 4. Measure track stakeholder coverage

Track stakeholder coverage, security review progress, pilot activation, outcome evidence and commercial next step.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 5. Do not cross this boundary: never invent certifications

Never invent certifications, customer references, uptime history or product capabilities to compensate for being early.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

## Source ledger

- [ ] HubSpot: ways to find and keep a first customer: https://blog.hubspot.com/sales/first-customer
- [ ] Google Search Central: people-first content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- [ ] Google Search Central: optimizing for generative AI features: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- [ ] Eli AI Visibility Index methodology: https://hireeli.io/ai-visibility-index/methodology

## Measurement boundary

Baseline date and exact context: ____________________
7-day observation: ____________________
14-day observation: ____________________
30-day observation: ____________________
Known limitations: ____________________

Keep technical eligibility, citations, recommendations, visits, leads and revenue as separate evidence. This worksheet does not guarantee an external ranking or commercial result.