Listening Cycles = customer evidence while you build
You're already talking to customers, make those conversations count
Sales calls, support, demos, customer requests, upselling: your team hears from customers all the time. But it doesn't always add up to a shared answer about what should change.
A Listening Cycle gives that contact a structure, starting with a hypothesis about the customer you think matters most right now: who they are, what you believe about them, and what you're currently building or positioning around. Then, while the work continues, we recruit people who fit your Bullseye Customer hypothesis and talk to 1-2 of them weekly for six weeks.
And you keep building without letting your customer assumptions get weeks or months ahead of the evidence.
- Keep it current: hear from customers while decisions are still being made
- Get outside the usual circles: talk to net-new people, not just existing users and friendlies
- Catch a wrong turn sooner: spot when the customer, problem, or positioning starts to drift
Book a 25-min call to see if a Listening Cycle could fit into what you're already doing.
How it works
We're talking six weeks (~12 interviews), usually 1-2 interviews a week, to keep a customer hypothesis or positioning direction under pressure while your team keeps working.
We start with a customer hypothesis or positioning direction worth testing. You probably already have one, most likely several.
We recruit people who fit it. Your whole team watches the interviews live, especially the people making the decisions, then we debrief immediately afterward. That matters. Otherwise, customer evidence has a habit of turning into a research report, a Slack summary, or some game of telephone where everyone ends up hearing something slightly different.
The first interviews are directional. Are we hearing the problem we expected? Does this person actually care? Are we even talking to the person who owns it? After a handful, there's usually enough signal to decide what deserves deeper investigation. Then we can chase contradictions, tighten the hypothesis, and understand what's underneath the pattern.
- We recruit — we find net-new customers who fit your Bullseye hypothesis. No talking to "friendlies" who will tell you what you want to hear.
- You watch — your whole team watches live. You see the facial expressions and hear the excitement/hesitation in their voices firsthand.
- We debrief — we huddle immediately after each call. No reports. No synthesis "later." You hear the patterns as they emerge.
Why every week? Because your team isn't waiting a month to make decisions. Feature scope changes, priorities move, somebody has a new idea, sales hears something, the co-founder talks to one customer and comes back convinced the roadmap needs to change.
If customer interviews only happen every so often, all of that keeps moving while the evidence gets stale. Weekly makes it a smaller bite. It can be as ordinary as: every Thu at 1pm, we talk to one customer. Interview, debrief, back to work.
Customer interviews shouldn't be a special occasion event. It works best as a team sport, not a research side quest.
Some teams need 5-10 interviews for a quick signal. Others keep going for 12+ weeks. We can also mix discovery and user testing when there's something concrete worth putting in front of people.
If you don't have a clear customer hypothesis to test, start with the Bullseye Customer Sprint. That gives you something specific to test against instead of just collecting more stories and context.
Break down one live product or go-to-market (GTM) decision
Take one product or GTM decision your team is making right now. In about 10 min, trace the customer evidence behind it: what you’ve heard, how recent it is, who heard it firsthand, and where you’re still filling in the blanks.
The goal isn’t to score your research practice. It’s to see whether this decision is resting on current customer evidence, old assumptions, or something in between.
Get the exercise and sign up for How Might We... — a weekly-ish newsletter for founders who prefer evidence over guesswork
Case study
The CFO had the pain, the controller had the problem
A bank-integrated fintech's pipeline had stalled. Sales were down 23% over 18 mos. So we ran a Bullseye Customer Sprint and landed on the one-liner: "For CFOs at $50M+ SaaS firms, we provide real-time visibility into processing fees with modern dashboards." And by the third interview, a CFO said this:
"I don't care about saving 50 basis points if it means my team has to spend 20 hours/mo manually fixing broken data in NetSuite. Level 3 automation that populates the line-item data that stops flagging transactions — that's not about savings, that's an audit problem. I kick it to my controller."
Then, two more CFOs said versions of the same thing. Three total. We dug back into the Bullseye and positioning interviews and found one more who said something similar. Four signals total, enough to schedule more interviews — a Listening Cycle — to confirm.
We'd found the right pain from the wrong person, which pointed us to the right one. CFOs liked the idea but controllers lived it. And the sweet spot was the "Goldilocks Zone" ($30-$100M) — big enough to have a problem but not enough to build a custom in-house solution. They didn't want another dashboard, they wanted their existing ERP to work better. The new one-liner: "For Controllers at $30M–$100M SaaS firms, we provide automated Level 3 compliance integrated into your existing ERP. Unlike Stripe or Shopify, we bridge your ERP directly to wholesale bank rates without manual data entry."
We moved from "cheaper processor" to "operational sanity," putting dashboards in the parking lot. Then we ran 13 more interviews to confirm, testing three versions of a reconciliation audit flow.
After 18 interviews total — five in the Bullseye round, a reframe, then 13 as a Listening Cycle — the customer, problem, positioning, and product direction looked materially different from where we'd started. The team wasn't making that reset from a hunch. They'd heard the pattern directly from multiple people and kept pressure-testing it as the direction changed.
=
Ready to find out if you're talking to the right customer?
Schedule a 25-min consultation. No pitch, just a look at where you are and whether this is the right moment.
When this makes sense
You have a direction worth testing — a read on who matters most right now. It doesn't have to be airtight. It's not forever. But it works best if it's specific enough to find that person.
The stakes for your next build are high, and you want evidence while decisions are still being made, not months after they're locked. A Listening Cycle can also sit alongside the customer conversations you're already having.
Skip this if you're committed to your current course and don't think talking to customers would change it. But if you're completely unsure about who to talk to first, the Bullseye Customer Sprint might be the easier way to get started.
What it costs
$11K for six weeks, plus recruitment fees. Included:
- Up to two interviews per week, ~12 live interviews over the total time
- Live facilitation and immediate team debriefs
- Archive of evidence (recordings, transcripts, and updated Bullseye)
Recruitment and screening fees vary and could be ~$2K. Need more than two a week or want to expand the timeline? Additional interviews or less time are available at additional cost.
The alternative
The problem isn't silence. Your team hears from customers constantly. The roadmap gets some of that evidence but it's mostly decided in other ways.
Frequently asked questions (FAQ)
Not the right fit? Other ways we can work together:
This is a no pitch zone
Tell us what decision your team is trying to make
We’ll talk through where you are, what evidence you already have, and whether the Bullseye Customer Sprint, a Listening Cycle, or another approach makes sense.
If we aren't the right fit, we'll say so.
Phone: +1 917-720-6388
Email: heythere@howthisworks.co
Book a call: howthisworks.co/start
Based in San Francisco, CA, working globally
How This Works show our podcast
Subscribe to our newsletter, How Might We...
Weekly-ish dispatches on customer discovery and product strategy — sensemaking from inside the work and from home, with AI in the mix
© 2026 How This Works, Inc. All rights reserved.
