Product
Building what customers do, not only what they ask for
The request list is long, contradictory, and mostly from the loudest customers.
Signals to look for
- roadmap
- feature request
- customers want
- backlog
- priorities
- workaround
Questions to answer
- What do customers do repeatedly outside the product to get their outcome?
- Which requests come from customers who pay and stay?
- Which request, if built, would change a business decision for the customer?
- What are people exporting, copying or doing by hand?
Evidence required before committing
- repeated manual behaviour observed or reported
- requests weighted by customer value and retention
- usage data where it exists
Likely constraint
- Building for the loudest rather than the most representative
- No visibility of behaviour outside the product
How the decision branches
- IfMany customers do the same manual workaroundThenThat is the strongest roadmap signal available — stronger than any request list.
- IfA request comes from one large customer onlyThenPrice it as bespoke work, do not treat it as roadmap.
- IfRequests conflictThenSegment them; the conflict usually means two customer profiles.
What to test
Interview five customers about what they do immediately before and after using the product, and count repeated behaviours.
Read after 21 days.
What success looks like
- At least three of five describe the same behaviour
- The behaviour maps to something buildable in weeks
What means stop
- No repeated behaviour appears — do not build on a single account's request
Typical next move
- A behaviour repeats across profiles → Build the smallest version and measure adoption.
- It repeats in one profile only → Build it only if that profile is the target.
Who does the work
Aury can carry out: read company, prepare research brief, file memory, create task. Specialists involved: product, research.
Your approval: The founder approves customer interviews before they are requested.
Where this stops being true
Requires access to real customers willing to talk.
Five interviews find strong patterns, not weak ones, and customers describe their behaviour imperfectly.
Provenance
- Sourced operator experience: Founder/operator case study analysed inside Aurygine — bootstrapped B2B software company, 2026
- Sourced operator experience: Customer-behaviour discovery practice
- Aurygine synthesis: Aurygine synthesis across founder journeys
Confidence: medium. Last reviewed 2026-08-25. Your company's own recorded results override this playbook whenever the two disagree.