A walkthrough of one Wirey loop on demo data: a question in Slack, eight interviews, one cause and a small pull request waiting for review.
The question
Anna, a product lead at Acme, asks in #product-research: “@Wirey how did the signup interviews go?” She already sees in PostHog that people drop off at signup, but not why.
The evidence
Wirey had invited recent signups to short interviews, by voice or chat, with consent recorded. After eight interviews it posts a summary: 5 of 8 people stopped at signup because they could not find the price before entering a card. Three found step 2 too long, and two were unsure what the free plan includes. Every pattern links to the quotes behind it, like “I stopped at signup. I had no idea what it would cost me.” The summary also lands in Notion, so the team does not have to dig through transcripts.
The fix
Anna replies: “That matches the funnel. Can you take a pass at the fix?” Wirey moves pricing onto step 1 and cuts step 2 from five fields to two, using Acme’s existing components. It opens pull request #142, “Show pricing on signup”: three files, twelve lines added and three removed. The description links the interview quotes and the funnel step, with before and after screenshots. Checks run as usual.
The review
Nothing merges on its own. The pull request waits for a person, under the same branch protection and required reviews as any contributor. Anna can approve, ask for changes or press “Keep mine”, which also teaches Wirey her team’s taste for next time.
What changes for the team
The team did not schedule research, write a brief or open a ticket. They answered one question in Slack and reviewed one small pull request. That is the loop Wirey runs every week: listen, find the cause, ship the fix, check it worked.
#product-research · @Wirey“How did the signup interviews go?”Demo workspace · Acme