The Field Guide
·2 min read

What I've been building

Why I'm building Corha, and what I think customer understanding has to look like now.

Luke Hawkins
By Luke Hawkins
June 11, 2026
Product strategyCustomer researchUser personasFounder writing

Welcome to Corha!


The simple version: you point it at whatever customer signal you already have, calls, tickets, surveys, support transcripts, research papers, spreadsheets full of notes someone made in 2022, anything, and it synthesises living personas from it. Personas you can ask questions of, validate work against, query as new evidence arrives.


The thing I'm probably proudest of is that Corha doesn't just look at what teams have collected deliberately. It listens in across the calls that are actually happening, product calls, sales calls, customer success conversations, the lot. That's where most of the real signal lives, and most of it never makes it into a research deck because it wasn't recorded as "research" in the first place.


This matters more than it sounds. A product team will sit with a customer and hear one thing. A sales team three desks over will hear customers push back on the exact opposite thing, again and again, in a hundred discovery calls. Both signals are real. Both are about the same product. Neither team usually knows what the other is hearing, and almost nobody is reconciling the two. Corha is built to notice exactly that kind of dissonance and surface it as something the team can actually look at, rather than something that quietly costs you a year of strategy.


And you don't need a stockpile of data to begin with. If you're a brand new startup with nothing but a company description and a rough idea of who you're for, you can put that in and Corha will generate a first set of personas to start working from. They won't be perfect. That's the point, they're starting positions, and as real data arrives, calls, tickets, conversations, surveys, the personas refine and sharpen against what's actually true rather than what you initially guessed. You don't need to wait until you've "done enough research" to have personas worth using. You start where you are, and the system catches up.


This is the bit that wasn't really buildable a few years ago and is now buildable well, and I think the teams that adopt this way of working over the next two years will look back on the old way the way we now look back on building software without proper analytics.

Get new field notes delivered

One or two emails a month. Essays like this one, plus the occasional teardown of what we're seeing across customer calls.

Field notes on customer research, product, and AI. Once or twice a month. No spam.