P1 — The Evaluating CTO
“I need to move fast on AI, but I can’t afford to pick the wrong partner. I need someone who’s done this before.”
Profile
| Field | Detail |
|---|---|
| Role | CTO, VP Engineering, or Head of Engineering |
| Company size | 50–500 employees |
| Industry | Tech, fintech, scale-up, or enterprise undergoing digital transformation |
| Location | US, UK, or Western Europe |
| Seniority | Senior decision-maker with budget authority |
Context & Motivation
This persona is actively evaluating AI engineering vendors. They have a concrete initiative — building an AI feature, modernizing a data pipeline, augmenting their existing team — and a board or executive mandate to move on it. They are time-pressured and have likely already spoken to 2–3 competitors.
They arrive at the company.com through referral, conference, or targeted search. They know what they want; what they need is confidence that the company can deliver it.
Goals
- Quickly assess whether the company has the right technical depth for their specific problem.
- Understand engagement models (dedicated team, staff augmentation, project-based).
- Get a rough sense of cost and timeline without committing to a formal RFP process.
- Validate the company’s AI and engineering credentials with concrete evidence (case studies, team profiles).
Frustrations
- Wasting time with vendors who overpromise and underdeliver technically.
- Generic sales pitches that don’t speak to their specific stack or problem.
- Long response times — if they don’t hear back within hours, they move on.
- Being passed around between sales reps who don’t understand engineering.
Behaviour on the website
- Navigates directly to Services and Case Studies.
- Spends time reading technical detail — not just outcomes but how the work was done.
- May open multiple tabs comparing the company against competitors.
- High intent to contact if the content validates their expectations.
Qualification signals
- Mentions a specific AI initiative or technical problem.
- References company size or team structure.
- Asks about timeline or availability.
- Asks about specific technologies (LLMs, RAG, MLOps, etc.).
Chat strategy
Engage technically. Ask about their initiative early. Surface the most relevant case study. Move quickly toward scheduling a call. This persona has low tolerance for vague answers — the chat must feel like talking to a technical peer, not a sales assistant.
Job-to-be-done
When I’m under pressure to ship an AI initiative and my internal team lacks the expertise, I need to quickly identify a partner I can trust technically, so that I can recommend them to my leadership without risking my credibility.