Internal call recap
Where LEVR meets its user — and who that user is
A working call on product sequencing: lead with a native voice experience, or meet leaders inside the tools they already use. The buyer got clearer. The sequencing did not.
Executive summary
Chase and Chad used the call to pressure-test two things at once: where LEVR should meet its users, and who those users actually are. The second question resolved. The first did not.
On the user, they converged: LEVR is being built for CEOs, C-suite leaders and strategy owners — not for a broad base of organizational or project-management users. That narrowing carried straight into differentiation. What LEVR sells is product-market-fit context, strategy, guardrails and market intelligence. It is not another generic AI chat interface, and positioning it as one would throw away the only thing that makes it defensible.
On sequencing, the tension stayed live. One path leads with a native walk-and-talk voice experience, treating voice as the primary high-leverage interaction and keyboard and integrations as support. The other meets users where they already work — Slack, Google Meet, ChatGPT, Claude and MCP — and asks far less behavior change of them. Both readings were argued seriously and neither was closed.
The sharpest gap surfaced around collaboration: editing together, and turning a conversation into a shared artifact the team can actually act on. That gap, more than the voice-versus-integrations question, is what the call decided to go answer with real customers — and the reason the mid-November launch date was explicitly let go rather than defended.
Overall sentiment
Constructive and strategically clarifying, with genuine unresolved product-prioritization tension. The disagreement was about sequencing, not direction — and it was left open on purpose rather than settled early.
Major talking points
-
Native voice experience vs. meeting users in their existing tools
The central question of the call. Leading with a native walk-and-talk voice experience makes LEVR the place the thinking happens. Meeting users in Slack, Google Meet, ChatGPT, Claude and MCP puts LEVR where leaders already spend their day and asks almost nothing of them. Both were argued as the opening move; neither won.
-
The target user and buyer is the CEO, not the organization
Focus belongs on CEOs, C-suite leaders and strategy owners — the people who own the strategic call — rather than on broad organizational or project-management users. That choice narrows the product surface and changes what has to be excellent first.
-
Differentiation is context and judgment, not another chat box
LEVR’s edge is product-market-fit context, strategy, guardrails and market intelligence. The failure mode to avoid is being read as a generic AI chat interface — a category where LEVR has no advantage and where the work it actually does becomes invisible.
-
Voice as the primary high-leverage interaction
Voice is where a leader thinks fastest and gives the most context per minute, which is what makes it high-leverage rather than merely convenient. Keyboard and integrations support that mode — the open question is whether voice leads the product or arrives behind the integrations.
-
Collaboration and shared artifacts are the critical gap
A conversation that stays a conversation does not move a company. Collaboration, editing, and turning a conversation into a shared, actionable artifact is the clearest hole in the current product — and the piece that most needs to be validated before anything else gets locked.
Decisions & alignment
- Validate the collaboration workflow with real users. Take it to early customers and strategic contacts and find out how collaboration and editing need to work in practice.
- Do not force the mid-November launch date. The date is released as a forcing function rather than defended on principle.
- Prioritize learning and a design that works over shipping on schedule. Shipping an unvalidated collaboration model is the worse outcome.
- Aim initially for roughly 100 highly satisfied CEOs. Depth of satisfaction in a narrow group is the early target, not breadth.
Open tensions to keep discussing
- Native experience versus integrations-first — which one opens the product?
- How much behavior change is reasonable to ask of a CEO?
- How does collaboration and editing actually work in practice?
- What is the roadmap and timeline for a usable iOS walk-and-talk experience?
- Which integrations should come first?
Next steps & ownership
- Chase Prototype the collaboration workflow Build it far enough to be reacted to, then collect feedback from early customers and strategic contacts on how collaboration, editing and shared artifacts need to work.
- Team Set priorities and timeline from what comes back Use the validation learnings to settle the sequencing questions and set a timeline that reflects a design that works.