A co-founder of an early-stage AI hardware startup — building a product that takes the notion of a professional “colleague” to the next level — came to a one-off advisory session focused on pricing. The company was pre-seed, hiring its first specialists, and preparing for its next round of investor conversations.
The Challenge
The core tension was pricing: the structure set seemed to no longer match the economics of the business, and neither the numbers nor the story around them had caught up.
- A one-time hardware fee that no longer covered rising component costs
- Uncertainty over whether shifting to a subscription would feel like a bait-and-switch to less technical customers
- No clear view of what a new pricing structure would actually need to cover to protect margin
- Secondarily, a pitch that led with technical explanation before establishing the problem being solved
- A hardware-and-AI product that didn’t sit neatly in either the “software” or “hardware” investor camp
The Approach
1. Weighing customer perception. The session worked through how a shift from a one-time fee to a subscription would land with less technical customers and whether it would read as an unwelcome bait-and-switch, or as an expected sign of ongoing service, depending on how it was framed.
2. Mapping what the price actually needs to cover. Rather than debating a number in isolation, the conversation worked backwards from real costs — rising hardware prices, ongoing support, and the cash flow timing of ordering inventory in advance — to define what any pricing structure has to sustain.
3. Borrowing structure from an adjacent market. A consumer hardware example, where a subscription is bundled into the device purchase rather than sold separately, offered a workable reference point for the upfront-plus-ongoing structure without it reading as an upsell.
4. Naming the go-to-market path already in motion. The roadmap toward launching with a narrower, specialist version was already set before the session. Rather than revisit that sequencing, the conversation sharpened how to talk about it — starting narrow builds credibility even when the underlying model is built to generalise.
5. Reordering the story to lead with the problem. The story was explaining the technology before the problem it solves, understandably coming from a technical founder. Reordering the narrative to open with the problem and its “aha” moment, before the technical story and investor fit, was identified as the fix.
Outcomes
After our session, the founder left with more than pitch notes. She left with a clearer map of what the pitch was resting on, and what still needed to be built underneath it.
✔️ A clear-eyed view of the gaps before an investor could surface them first
✔️ A concrete plan to map and structure a data strategy and frame it as an asset
✔️ A near-term metric that demonstrates platform value
✔️ Recognition of the double-sided marketplace
All in all, a stronger, more defensible story to bring into upcoming fundraising conversations
Key Learnings
- Rising input costs are a signal to rethink pricing architecture, not just to raise the price
- How a pricing change is framed matters as much as the numbers.
- Specificity in go-to-market builds more credibility than showing full ambition upfront
- A pitch should open with the problem; the technical story follows to strengthen it.
What shifted in this session wasn’t the product or the roadmap — both were already largely set. It was the clarity to price for what the business actually needs to cover, rather than for what feels defensible in the moment, and to tell that story in the order that lets other people follow it. Neither the pricing model nor the pitch was finished, but the founder left with a framework for finishing them, rather than a set of open questions.
Sometimes, the clearest pricing model starts with knowing exactly what it needs to cover.
Leave a Reply