Question 1

We already talk to our customers — why do we need this?

Accepted Answer

That's usually true — and it's actually part of what makes this hard to see. Most teams do talk to customers. The problem is what happens after. One or two people take the call, form a read, and summarize it for everyone else — and somewhere in that translation, the team splits. Not because anyone's being difficult. Because they each heard a different version of the same conversation. Six months of that compounds. The debate about who you're building for doesn't come from a lack of customer conversations. It comes from each person on your team having a slightly different picture of what those conversations said. The sprint is structured so that happens a lot less. Your whole team watches the same five interviews live, then debriefs together immediately after each one. No summaries, no one's interpretation standing in for the source. When you hear a customer say the same thing in their own words — and your co-founder heard it too, and your product lead heard it too — the debate stops. Not because someone made a good argument — because everyone has the same evidence.

Question 2

What if our team can't agree on a single critical question?

Accepted Answer

That disagreement is exactly why you're here — and it's more useful than you'd think. Activity 1 of the sprint is designed specifically to surface where a team diverges. Everyone works alone first, then shares. The places where your answers cluster are what you agree on and the places where they scatter are your critical question waiting to be written. Teams that walk in with clean consensus often find they've been papering over real uncertainty. Teams that walk in arguing tend to leave with the clearest question of all — because the tension points directly at what actually needs testing. You don't need to agree before you start. You need to be willing to look at the disagreement together.

Question 3

What does this actually require from us?

Accepted Answer

Less than you'd expect, and it's concentrated in one week. Outside of interview week, the commitment is a couple of hours per week from whoever owns product and customer decisions — mostly Phase 1 alignment work and recruitment coordination. Interview week is heavier: five live 60-minute interviews with an immediate debrief after each one, which runs 8-10 hours across the week. In total, most teams invest about 25 hours over the two months. Many find it folds into existing planning cycles without adding a separate workstream. On recruitment: we need five customers for the full sprint. Good starting points are current customers, churned users, or prospects who didn't buy. We can also help recruit through platforms like userinterviews.com. If access is genuinely limited, we'll work through alternatives on the discovery call.

Question 4

Can we do this if our team is distributed?

Accepted Answer

Yes. We coordinate interviews so your whole team can observe live via Zoom or video call. Distributed works — it just requires discipline around scheduling. The immediate debrief after each interview is critical; waiting too long means losing the live context that makes the debrief worth doing.

Question 5

What's the difference between the Bullseye Customer Sprint and the Listening Cycle?

Accepted Answer

The Bullseye Customer Sprint is a one-time diagnostic. Two months, $20K, five customer interviews to move you from assumption to evidence. You walk away with a staked customer hypothesis and recorded proof. Best used when you need to settle internal debates and establish clarity. A Listening Cycle is ongoing calibration — 2-3 months at $7.9K/month, running parallel to your build. Weekly interviews keep your roadmap tethered to customer reality so you catch drift before it becomes a problem. Most teams do the sprint first, then move into a Listening Cycle once direction is clear.

Question 6

Will we find our Bullseye Customer?

Accepted Answer

Maybe — and that's not a hedge, it's the honest answer. Every sprint ends with a traffic light routing decision. Green means the pattern is clear, three or more customers matched your hypothesis, and you're ready to move. Yellow means partial signal — refine and run a few more conversations. Red means the hypothesis missed, and you learned that in two months instead of six. All three are useful outcomes. Finding out 'no' early is exactly what the sprint is designed to do. In our work so far, fewer than half of teams stake their Bullseye Customer after a single sprint — and that's the methodology working, not failing. For teams that need to keep going, the Listening Cycle picks up where the sprint leaves off.

Question 7

Who is not a fit for this sprint?

Accepted Answer

Teams where leadership has already decided who the customer is and isn't genuinely open to evidence suggesting otherwise
Teams with zero customer access and no warm network and no budget for recruiting
Teams that can't commit 2-3 hours per week for two months — not counting interview week

If any of these apply, let's talk during our initial call — sometimes there's a modified path; sometimes this just isn't the right moment, and that's worth knowing early.

Stop guessing who your customer is, get the evidence and agreement

How it works

Benefits

What you will get

Case study

How Replay found their customers — five hypotheses, six mos, a clear Builder

When this makes sense

What it costs

Frequently asked questions (FAQ)

Tell us where you're at