Building Personas from Research — How a Solo Founder Actually Works
Translating an abstract target into a concrete person, then grounding that person in web research instead of imagination. A solo founder's three repeated activities, the loop their week turns on, the biggest pain the research surfaced — and exactly where fecit sits inside it.
Building Personas from Research — How a Solo Founder Actually Works
We have an abstract definition of who fecit is for. To validate it in a pilot, we have to translate that abstraction into a concrete person — and for that person to be useful in validation, they have to be rooted in reality, not in our imagination. This week we built out our personas and scenarios, and grounded persona #1 (the solo founder) in web research.
1. Personas and Scenarios
The abstract target is two sentences:
- Someone who repeats the same kind of execution, where the quality of that execution is decided in the preparation.
- Someone who believes that improving the process improves the result — and is willing to spend time on that improvement.
We translated this into five concrete kinds of person — a solo founder, a one-day-class / workshop operator, an online instructor / coach, a content creator, a solo trainer. All of them are hypotheses to test in the pilot.
One insight shaped the frame. The loop doesn’t attach to the whole role — it attaches to the repeated sub-activities. A founder’s work is heterogeneous, but inside it are repeated sub-activities (customer interviews, weekly reviews, publishing), and the prepare → execute → reflect loop runs on those sub-activities, not on “being a founder.” So we nailed the validation signal down to one observable sentence rather than a vibe: “In the second execution, do they reopen the record from the first?”
A persona is only as useful as it is grounded. So we decided to test each persona against real behavior — starting with #1, our channel entry point.
2. Reviewing and Applying Persona #1
We used web research to understand how a solo founder actually works — reality first, the product laid on top afterward, rather than the other way around. (Sources at the end.)
Here’s the reality. A founder’s work is heterogeneous, but three repeated activities ran clearly through the research.
- Customer interviews — aiming for three 30-minute calls every two weeks; using The Mom Test rule to dig for concrete facts from the past (“last time you had that problem, what did you do?”) while leaving out assumptions and pitches; taking notes live during the call, keeping the customer’s raw words separate from your own interpretation; and right afterward, while it’s fresh, pulling out what surprised you, what got confirmed, and what’s still uncertain. The friction is clear too: notes scatter across places, and prep for the next interview often starts from a blank page again.
- Weekly review — Monday: decide the five things to ship this week; Tue–Thu: build; Friday: ship. Friction: you’re alone, so no one is watching.
- Building in public — Friday’s shipped work becomes the raw material for the public post.
The week was a loop: Monday plan → Friday ship & publish → next Monday. Weekly review and building in public aren’t separate; they meet as one thing on Friday.
And the research pointed clearly at something we would have missed if we’d only imagined it.
The founder’s biggest pain wasn’t money or skill. An analysis of 20,000+ solo-founder posts concluded that the deepest one was the absence of accountability and feedback — “silence.”
“I set goals on Monday. By Wednesday they’re gone. No one checks, no one cares.”
“I spent three weeks on a feature and couldn’t tell myself whether it was brilliant or dumb. There was no one to ask.”
The solution that actually worked was a 30-minute weekly check-in with another founder at the same stage. “Productivity doubled” — and when the call stopped, things went right back.
Lay fecit on top and a lot of it fits naturally. A customer interview becomes an execution template — the Mom Test structure becomes the fields; the first mistake the research flagged (“I led the witness toward the answer I wanted”) gets nailed down before execution as a premortem obstacle; the retrospect stays as the three strands of surprised / confirmed / uncertain; and the second interview starts from a copy of the last template, so “from a blank page again” disappears. Just having the scattered notes gather into one document is direct value for this person. Weekly review and Friday publishing lay on as repeated templates too.
And thanks to the research, we now know fecit’s place more precisely. What actually solved “silence” was a person — a peer’s weekly check-in. fecit isn’t a tool that tries to replace that rhythm; it’s a tool that provides structure alongside it. For a founder, fecit is strongest when it sits next to a coach or a peer. That isn’t a weakness of the product — it’s a precise picture of where the product should live.
A persona built from research teaches you things you’d never have learned by imagining — how a founder’s week turns, what their deepest pain is, and exactly where fecit sits inside it. Personas come alive when you build them from reality.
Sources
- Customer interviews · The Mom Test: koji.so · mtlynch.io
- Interview notes & synthesis practice (raw words vs. interpretation): Product Talk · CleverX
- Weekly rhythm (Monday plan → Friday ship & publish): The Solo-Founder Playbook
- The biggest pain, “silence” · weekly check-in: I analyzed over 20k posts from solo founders (Indie Hackers)
- Building-in-public rhythm: Building in Public Guide