The copy challenge
Customer feedback arrives in sales conversations, support tickets, renewal calls and spreadsheets. Months later the team cannot say how many customers asked for a feature. Sales says everyone and support says nobody, so the roadmap is decided between two anecdotes. The copy has to explain how SignalNest groups repeated requests, separates customers from mentions and keeps the evidence behind each topic.
My role and key writing decisions
I wrote all the landing-page copy for this concept project. No client was involved.
- I built the headline on a count the reader cannot produce today. "Know how many customers actually asked for it" sets up the page's main distinction, customers against mentions. The first question under "What you can answer" gives it a case: "One frustrated admin filing eight tickets is not eight customers". The Problem section's "Sales says everyone. Support says nobody." is what the headline's "actually" answers.
- I carried one request, Data export, through the page to show grouping rather than describe it. It appears as a missing export during a renewal call in the Problem section, then as three phrasings landing under one topic in step 2, then as the topic the reader opens to see the list of companies. The grouping is shown as correctable in both the steps and the objections: rename, merge, split or move, with nothing deleted.
- I connected the count to accounts and account value so it works as a roadmap argument. Step 3 keeps every quote with its source, account and date. The questions then build in order: which accounts, whether the demand is worth the build, where it comes from, and what customers said. The account-value line sets eleven requests from the smallest plan beside four from three of the largest accounts, so the smaller number can matter more.