In short: when no budget line exists, you sell against the cost of what the buyer does today, through a category they already recognise, to the person who owns the pain. The category story is for investors.
Key points
- Position against the status quo and price against what it costs, not against a nonexistent budget.
- Use a borrowed, familiar category to get the first meeting, then expand after a proven pilot.
- Sell to the person with a hard cost on their own budget; use the visionary as a sponsor.
- Mark each claim as deployed, piloted or tested in lab; one overstated claim costs more than ten honest gaps.
- Keep the investor story and the customer story in separate documents with separate owners.
The buyer has no budget, no title and no comparison set
In an established market, the buyer knows what they are shopping for. They have a budget line, a job title that owns it, and three vendors to compare. Emerging technology has none of that.
That changes the job. You are not winning a comparison. You are creating a purchase that did not exist in the plan. Every step of the sale has to answer a different question: not "why you" but "why spend at all".
Each audience needs one belief (see One truth, three audiences). In emerging tech the customer's belief is narrow and concrete. It is "this costs me money now and that can stop". Anything wider belongs in the investor deck.
Position against the status quo, not against competitors
You do not have competitors in the usual sense. You have the current way of doing things. That is your real rival, and it is cheaper to describe than a category.
Write down what the status quo costs. Manual inspections and the people who do them. Downtime between failures. Compliance fines and the audit hours that precede them. Energy bought at the wrong time. Fraud losses and the checks that fail to catch them.
Then price your product against that number, not against a budget that does not exist. A buyer can approve a saving. They cannot approve a category.
Be specific about where the cost sits. "Inefficiency" is not a line item. "Four field engineers spending a day a week on site visits that a sensor could replace" is.
Borrow a category to get the meeting, then expand
Buyers file new things under old names. Use that. If your agent infrastructure looks like workflow automation to a procurement team, let it get in the door as workflow automation.
The borrowed category is a door, not a home. Once you are inside and the first use case is proven, you widen the frame. The sequence is: familiar name, narrow pilot, visible result, then the real story.
Founders resist this because the borrowed category undersells the product. That is fine. The first meeting does not need to understand you. It needs to happen.
| Stage | What you call it | Who hears it |
|---|---|---|
| First meeting | The nearest existing category | Procurement, the budget holder |
| Pilot | A narrow problem with a cost attached | The operational owner |
| Expansion | What it really is | The sponsor and the board |
Sell to the person who feels the pain today
The visionary in the organisation will love your product. They will take every meeting. They rarely sign.
Find the person with a hard cost on their own budget: the head of operations with a maintenance bill, the risk lead with a loss number, the compliance manager with an audit deadline. They have a reason to act this quarter. The visionary has a reason to talk.
Use the visionary as a sponsor. Ask them to open the door to the owner of the cost. Then build the case for that owner, in their numbers, on their timeline.
First customers are design partners (see Your first ten customers are design partners). Here the design partner must also be a cost owner, or the pilot never converts.
Product truth and the claims register for something new
The product truth still applies: one sentence about what the product does that is true today. For a new technology, the temptation is to write what it will do. Resist it.
The claims register is harder when references are few. Keep three columns: what we claim, what evidence supports it, who can verify it. Where the evidence is a lab result rather than a deployment, say so. Where the only reference is a pilot under NDA, record what you can share and what you cannot.
Buyers in new categories expect thin proof. They do not expect exaggeration. One overstated claim costs more than ten honest gaps.
Investor story versus customer story
The investor buys the category: why it will exist, how big it gets, why you win it. The customer buys a problem solved: this process, this quarter, this saving.
Keep them in separate documents with separate owners. When the customer story leaks into the investor deck, the raise looks small. When the investor story leaks into the sales deck, the buyer cannot find the number and the deal stalls.
This is one system, not three problems (see You don't have three problems). In emerging tech that means the two stories share a product truth and a claims register, and nothing else.
The checklist
- [ ] The cost of the status quo is written down in the buyer's own numbers
- [ ] A borrowed category gets the first meeting; the expansion story is ready for after the pilot
- [ ] The buyer is a named cost owner, not the visionary
- [ ] The product truth describes what works today, not the roadmap
- [ ] The claims register marks each claim as deployed, piloted or tested in lab
- [ ] Investor story and customer story live in separate documents
Common questions
How do you sell a new technology when the customer has no budget for it?
Write down what the current way of doing things costs in the buyer's own numbers, then price the product against that. A buyer can approve a saving, not a category.
Who should I sell emerging tech to inside a large organisation?
The person with a hard cost on their own budget, such as a head of operations or risk lead. The visionary rarely signs, so use them to open the door.
Should a startup describe itself as a new category in sales meetings?
Not at first. Use the nearest existing category to get the meeting, prove a narrow pilot, then widen the frame to what the product really is.
Should the sales pitch and investor pitch tell the same story?
No. Investors buy the category; customers buy a problem solved. Keep them separate, sharing only a product truth and a claims register.