P2 — The Exploring Founder
“I know AI is important for my product but I don’t fully know what I need yet. I’m trying to figure out what’s realistic.”
Profile
| Field | Detail |
|---|---|
| Role | Founder, Co-founder, or Product lead at an early-to-mid stage startup |
| Company size | 10–80 employees |
| Industry | SaaS, marketplace, B2B product |
| Location | US, UK, or Western Europe |
| Seniority | Budget authority, often also product decision-maker |
Context & Motivation
This persona is exploring rather than buying. They have a product vision that involves AI — a smarter feature, an automated workflow, a recommendation system — but they are still figuring out scope, feasibility, and cost. They may not have a technical co-founder, which makes them dependent on external input to shape the brief.
They arrive at the company website through content marketing, LinkedIn, or a peer recommendation. They are not yet ready to commit but are open to being educated.
Goals
- Understand what AI engineering actually costs and how long it takes.
- Get honest input on whether their idea is technically feasible.
- Find a partner who can help them scope the work, not just execute a spec.
- Avoid being oversold into a contract they don’t fully understand.
Frustrations
- Vendors who jump to proposals before understanding the problem.
- Jargon-heavy conversations that make them feel out of their depth.
- Uncertainty about whether they need a full team or just a few engineers.
- Feeling pressure to commit before they’re ready.
Behaviour on the website
- Browses broadly — homepage, About, Services, Blog.
- Spends time on case studies that are closest to their industry.
- May read multiple blog posts before engaging.
- Lower intent to contact immediately; needs a lower-friction entry point.
Qualification signals
- Describes a product idea or early-stage feature.
- Asks about process (“how do you work?”) before asking about price.
- References their stage (“we’re pre-Series A”, “our team is small”).
- Asks about minimum engagement size.
Chat strategy
Lead with education, not qualification. Answer their questions generously. Build trust by demonstrating understanding of their stage and constraints. Collect email in exchange for a resource (guide, checklist, case study) rather than pushing for a call. The goal is to move them from exploring to considering — not to force a premature close.
Job-to-be-done
When I have an AI product vision but no technical roadmap, I need someone to help me understand what’s possible and what it costs, so that I can make a confident decision about whether and how to move forward.