Solutions / Post-launch founders

Test features and learn why people leave, with the same discipline you used to find the problem.

You have customers now. Every support email, churn call and feature request is evidence, if you keep it and score it. Narrera makes the discipline survive the launch.

Imports
Fwd: Monday bookingsemail thread · 6 messages3 findings
r/physiotherapy: no-showsweb page2 findings
G2 reviews · competitorweb page · 24 reviewsreading
Support inbox exportcsv · 210 rows11 findings

What changes.

Support is research

Forward threads, import the inbox. Complaints are 5s. Feature requests are usually 2s.

Churn interviews

A project per churn reason. Ten questions about what happened in the last week before they left.

Feature tests

Before building, run a round on the belief behind the feature. Results open at your target.

The team

Everyone hears the customer.

Engineers and designers read the quotes, not a summary of them. A read-only link to a project puts the evidence in front of the people building.

  • Shared workspace, no extra seats to argue about
  • Read-only project links for the wider team
  • Findings typed, so "every workaround" is one filter
Workspace · Launch Pad cohort
Jordan M.owneractive
Priya S.member · 2 projectsactive
Diego R.member · 1 projectin a call
Mentor viewread-only link3 opened
An example finding

The feature request hides the real problem.

Finding
GraceOwner · Lindqvist Hair

I stopped using it in March because the rota I export never matched what the girls actually worked.

5 · BehaviouralPain · VolunteeredSource 3, 00:08:12

Start with one belief.

Sign up, write the sentence, and Narrera writes your first ten questions. The notetaker joins your next call.