The Three-Hours-a-Day User Call Habit: A Deep Dive
startupplaybooks
Why Origami's CEO spends three hours every day on user calls, what actually happens in those calls, and how to structure them so the roadmap writes itself.
Three hours a day, every day, the CEO on user calls. Not a launch stunt — the permanent operating system. Here's what that habit actually looks like when you take it apart.
Why three hours, not thirty minutes
A half-hour scheduled slot gets cancelled the first busy week. Three hours is load-bearing: it forces you to build user calls into the shape of the day, which means they survive fundraising, hiring sprints, and outages.
What happens in the calls
- First 5 minutes: watch them use the product, silent.
- Next 15: ask what they were trying to do this week and where they got stuck.
- Last 10: show one thing you're considering building and read the reaction.
No pitch. No demo script. The call is diagnostic, not promotional.
How the roadmap writes itself
After ~50 calls, the same three pain points show up in different words. That repetition is the roadmap. Features nobody mentions get cut, no matter how clever they seemed on the whiteboard.
What breaks the habit
- Scaling the CEO out of calls too early ('the CS team can do it').
- Talking to prospects instead of paying users.
- Treating calls as sales opportunities.
How to instrument it
Capture call notes into a single searchable place. Tag by feature area and by user segment. Review weekly.
For teams that want to scale this listening discipline beyond one founder's calendar, an AI Agents Store agent can pre-process transcripts and surface recurring themes.