Unlocking the customer signal

Don’t build for 6+ mos on a "maybe"

Okay, you've just finished a Bullseye Customer Sprint. Or some similar customer clarity or positioning work. That means right now you're aligned as a team and clear on who you’re building for.

The biggest risk you face right now isn't the competition — it's the 'silence gap' that happens while building. Don't let your customer clarity go cold while you're head-down in development. The Listening Cycle keeps your roadmap tethered to what's happening in the world.

  • Bridge the gap: keep the pulse of the market while you build, not after you ship
  • Neutralize "friendlies": we find net-new customers who don't know you and won't pull punches
  • Catch the pivot early: discover if your "Bullseye" was 5 degrees off before you spend three mos coding


Book a 25-min call to explore whether the Listening Cycle fits your situation.

Or see more about how it works.

Next section

How it works

You have a single hypothesis or positioning. We're talking about three mos (~25 interviews) to test it. The Listening Cycle runs parallel to your build cycle. You're designing and developing while we're all listening. No waiting. No pausing.

The cycle runs in two phases. The first five interviews get directional signal — same recruitment rigor and debrief process as the Bullseye Customer Sprint. By the 5th interview, the patterns worth acting on have typically surfaced. The remaining interviews shift toward qualitative depth: confirming those patterns, pressure-testing the hypothesis, and building the confidence to commit.

Why weekly? Your team makes dozens of decisions weekly — feature scope, design details, prioritization. If you're only checking in with customers monthly, that's a big chunk of information that needs to be folded into decisions all at once. Weekly interviews connects it all and keeps it current, making it a smaller bite.

  • 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.


This rhythm keeps you honest. By watching up to two interviews per week with your whole team, you can see and hear what's happening in the market. You get the evidence you need to pivot your roadmap before you burn the budget.

Flexible as needed. Some need 5-10 interviews for quick signal. Others go 12+ weeks for deeper validation. And depending on what you need, we can combine discovery interviews with user testing (in a 60-min session) or stick with discovery-only (about half that).

Customer interviews shouldn't be a special occasion event. They work best when done on the regular and involve the whole team. An example — every Thu at 1p, we talk to one customer. It takes about 90 minutes, 15-min internal kickoff, 60-min interview, and 15-min debrief. It's normalized and it's a thing you all do.

If you haven't run a structured customer clarity effort yet, start with the Bullseye Customer Sprint. Without a clear hypothesis, there's little to test against — you're collecting general stories and context.

Listening Cycle Confidence/Evidence Gap cover page showing a 30-minute stress-test for evaluating roadmap bets against customer evidence, with three key principles about proof, non-friendly customers, and recent evidence mattering more than perfect evidence.

Get the 30-min Confidence/Evidence Gap exercise

Stop building on conviction alone and start mapping where your roadmap bets have drifted from market reality — identifying which efforts are tethered to evidence and which are burning payroll on stale assumptions.

Get the 30-min Confidence/Evidence Gap 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 two versions of a reconciliation audit flow.

After 18 interviews total — five in the Bullseye round, reframe, then 13 as a Listening Cycle — the results were clear: higher retention, shorter sales cycles, wider swathe of accounts. The reset happened because the evidence was concrete enough to act on. Not a hunch, customer signal.

=
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 just finished a Bullseye Customer Sprint and the stakes for your next build are high. You have a strong hypothesis about your best customer and want evidence before (or during) a major dev cycle. You want to catch market shifts while you build, not months after.

Skip this if: you're still in pure exploration mode (no hypothesis yet). We’d recommend the Bullseye Customer Sprint to first stake your target. Or you already have a structured, weekly-ish process for interviewing net-new customers. Maybe you have a rotating customer advisory councils/cohorts.

What it costs

$7.9K/mo, typically three mos Included:

  • Recruitment and screening of net-new customers
  • Up to two interviews per week, ~25 total live interviews (spread over the cycle)
  • Live facilitation and immediate team debriefs
  • Archive of evidence (recordings, transcripts, and updated Bullseye)


Need more than two a week or want to compress the timeline? Additional interviews or less time are available at added cost.

The alternative

The silence gap can compound. Six months of building on expired assumptions doesn't announce itself — it shows up in your pipeline and in your customer churn.

Frequently asked questions (FAQ)

Do we need to have done the Bullseye Customer Sprint (BCS) first?
Not necessarily — but it helps to have a starting point.
 
The Listening Cycle is intended to test a direction, not necessarily find one. You can run interviews without a clear hypothesis — and they'll inform the picture — but without a specific direction to recruit against, signal takes longer to emerge and costs more to find. If you're still figuring out who you're building for, the BCS is the faster, more focused first move.
What if we find out our hypothesis is totally wrong?
Then you've saved months of cash burn — and that's not a consolation prize, that's the process working.

If we hear a consistent "no" or a clear pivot signal in the first 5-7 interviews, we don't keep grinding. We pause, huddle, and redirect recruitment for the remaining sessions to test a reset direction. The Listening Cycle is designed to catch drift early, not confirm what you already believe. Better to find out in the fifth interview than the sixth month.
How many people from our team should attend?
As many as are available, but at minimum the people who represent product, design, and engineering — or whoever holds those roles on your team. Those lines often blur early on, and that's fine. What matters is that the people making build decisions are in the room.
 
When someone writing the code hears a customer's frustration firsthand, you don't need a 40-page research report to convince them to change course. Alignment happens in the room, in real time.
What does a Listening Cycle actually produce?
At the end of each cycle you have a signal archive — all recordings, transcripts, and debrief notes from every interview, plus an updated Bullseye Customer hypothesis reflecting what you heard. That's the tangible output.
 
The more important output is more ephemeral: a team that has been in the room with real customers consistently, making decisions against live signal rather than assumptions that have been quietly expiring. The archive is your record of truth. The team's calibration is the result.
How long does this run and how do we know when to stop?
We recommend three months as the baseline for consistent signal — up to two interviews per week, ~25 total depending on pace and complexity. Additional interviews or less time are available at added cost.
 
The cycle runs in two phases. The first interviews are focused on directional signal — does this customer match the hypothesis or not? In the first five interviews, the pattern is usually clear enough to act on. The remaining interviews shift to qualitative depth: confirming what you heard, pressure-testing specifics, building the confidence to commit to a direction
 
The stopping point follows the same traffic light logic as the BCS. Green means a clear pattern has emerged across three or more interviews — your hypothesis is holding and your team has what it needs to move. Yellow means partial signal — tighten the hypothesis and run a few more. Red means the hypothesis missed, and you redirect rather than stop. In practice, most teams feel the signal consolidate around weeks 6-8. When your whole team is hearing the same things and the surprises have stopped — that's the sign you've earned the clarity you came for.

Not the right fit? Other ways we can work together:

Design SprintSprint method
Getting UnstuckWorkshop method
1-hour power hourWorkshop method
Goals That StickWorkshop method
Clear Path ForwardWorkshop method

This is a no pitch zone

Tell us where you're at

We'll talk through your situation and be straight about whether our approach makes sense for you and your team

Book a 25-min call
How This Works co — Evidence-based strategy for B2B teams

Based in San Francisco, CA, working globally

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.

A hidden cassette tape angled easter egg linking to the How This Works co contact page