Four situations, one product
Sightelle does not know what you sell — it knows your people are already talking somewhere. What changes per situation is where the voice comes from and which axes mean something. The product ships with three ready taxonomies, so you have themes from day one, before a single signal arrives.
Two customers worth €150,000 in ARR showed signs of risk. The larger one, at €96,000, had 486 signals since January, scattered across tickets and an NPS survey.
A software company with subscribers
The voice is already written down — scattered across tickets, Jira, and an NPS nobody has time to read in full.
- Where it comes from
- Zendesk or Jira on automatic sync, the NPS as a Sightelle survey, and a CSV of old tickets for the history.
- The axes
- Customer (with ARR), product and sub-product from your Jira structure, plus a dimension of your own: subscription plan.
- What gets measured
- The theme becomes a task, closing it is measured 14 days before and after — and if complaints return, it reopens by itself.
The “bad product” can turn out to be one courier in two regions. With the courier as your own dimension, it shows in one click, not as a hunch.
An online shop or retail chain
Customers speak after delivery, not inside a ticket — and when they do, the complaint sounds like the product is at fault.
- Where it comes from
- A post-delivery survey with personal links, a QR on the receipt for everyone without an email, and the helpdesk export as CSV.
- The axes
- Product category from a CSV column, plus dimensions of your own: courier, store, pickup method.
- What gets measured
- The loop is compared per dimension: switching courier shows up as a drop in one region only, not as a feeling.
The loudest client is not always the unhappiest — and the quietest may carry the largest share of revenue. Revenue weighting puts them in the right order.
A services firm — accounting, legal, technical, consulting
Few customers, each one large. Here it does not matter how many said it — it matters who.
- Where it comes from
- ClickUp per client or project, a survey at every project close, and emails that end up as CSV.
- The axes
- Customer with ARR (weighting becomes Revenue, not Volume), service line, and a dimension of your own: project lead.
- What gets measured
- The “at risk” list with names and amounts, and next to it the happy list — for reviews and referrals.
In a real run, 157 issues became 256 signals and 26 themes. The 29 signals that landed nowhere were the most useful list of the day.
IT, shared services, internal support
Your “customers” are departments, there is no revenue, and the question is which department is struggling and with what.
- Where it comes from
- Jira or ClickUp with the internal requests — the structure your team already built is the axis, with nothing to write.
- The axes
- Department from the project, system from components, plus dimensions of your own: priority, channel, reporter.
- What gets measured
- Weighting becomes Volume — with no ARR, intensity is how many people asked, not how much money.
The first audit is free
Upload a CSV and see your themes — no integration, no card.