Skip to content

Product opportunities

Know what to build next, from what customers already tell you

Your customers tell you what is missing every day: they search your site for an integration you don't have, land on a 404 at /integrations/e-conomic, give up on your API page and ask support whether you support SAML. ROOKON collects those signals, groups them and ranks what to build next. Requests also arrive from ROOKON's feedback widget on your site and from a CSV import of support tickets; Gmail, Outlook, Intercom, Zendesk, Help Scout and Freshdesk integrations are planned.

The problem

The evidence is there, scattered across four places

Feature requests live in support tickets, site search logs nobody reads, 404 reports and analytics. Product decisions end up following the loudest customer or the last sales call instead of the pattern.

  • Requests are buried in support conversations
  • Nobody sees which searches return nothing
  • 404s on /integrations/... pages look like noise
  • One loud customer outweighs twenty quiet ones

Live demo 1 of 3

Watch requests turn into a ranked list

Simulated support requests, searches and 404s stream in and grow clusters such as an e-conomic integration. Swipe right to build it and see a spec draft, left for never, up for not now.

  • Swipe the top card to the right
  • Watch the e-conomic counts grow
  • Press Z to undo

rookon · acme-books · opportunities

LiveSimulated data

Incoming, scrubbed

  • /integrations/e-conomic404
  • “export csv”search
  • Do you support SAML with Okta? Best regards, [name]support
  • “e-conomic”search · 0 results

Ranked

  1. 1e-conomic integration19 requests from 14 customers, 33 zero-result searches, 9 404s718
  2. 2CSV export11 requests from 9 customers, 4 zero-result searches259
  3. 3SSO / SAML8 requests from 7 customers, 12 zero-result searches216
  4. 4Help content for “refund policy”17 zero-result searches, 3 404s45

integrationscore 718

e-conomic integration

Requests
19
Customers
14
Empty searches
33

“Hej [name], kan I lave en integration til e-conomic? Vi bruger det til alle vores fakturaer.”

9 visits hit a 404 on a page about it.

How ROOKON helps

What you get

  • Site search, opt-in

    Turn on site search per project and ROOKON reads the term from ?q= or ?search=, or from rookon("search", { term, results }). Searches that return nothing count the most.

  • Missing pages that mean missing features

    404s on paths like /integrations/hubspot or /features/dark-mode are matched to the integration or feature people expected to find.

  • Behavior signals

    Sessions that look around and then leave from your integrations, API, export or enterprise pages show interest you are not serving yet.

  • Support requests in English and Danish

    Import a CSV of support tickets. ROOKON finds requests such as "do you support", "can you add", "kan I lave" and "understøtter I", and names the tools involved.

  • A ranking you can explain

    Every opportunity shows its evidence, a trend and a score: weighted signals, newer counts more, and many customers beat one loud customer.

  • Decide in seconds

    Build it, not now or never, on a board or by swiping. Never stays quiet until the evidence triples.

Live demo 2 of 3

Searches land in the same cookieless analytics

Simulated analytics for a fictional product. Custom events such as docs searches arrive alongside pageviews and sources, without cookies.

  • Open the Events tab
  • Switch the time range

rookon · acme-cloud · web analytics

Simulated data

38 visitors nowLive

Bounce rate38.0%▼ 7.5% vs prev.
Avg. visit3m 23s▲ 12.2% vs prev.

Visitors · 7 days

visitors Previous period
visitors over the last 7 days, compared with the previous period
TimevisitorsPrevious period
6 Nov1,3111,260
7 Nov1,025826
8 Nov975921
9 Nov1,4941,442
10 Nov1,3791,474
11 Nov1,6091,391
12 Nov1,4421,432
  • Invoice created471
  • Signup296
  • Docs search267
  • Upgrade clicked137

Custom events sent with rookon('event', name).

Right now

38

visitors in the last 5 minutes

Visitors per minute, last 30 minutes
Timevisitors / min
16:3011
16:3111
16:3213
16:3315
16:3416
16:3513
16:3613
16:3719
16:3812
16:3913
16:4015
16:4111
16:4212
16:4312
16:4412
16:4510
16:469
16:4710
16:489
16:4910
16:5011
16:514
16:526
16:538
16:5410
16:557
16:568
16:5710
16:5810
16:5916
  • /12
  • /pricing7
  • /features4
  • /blog/launch-week3
cookieless

No cookies or device storage. Visitors are counted with a salted hash that rotates daily, so they can’t be followed across days. Raw IP addresses are never stored.

From scattered signals to a decision

  1. 01

    Collect

    The tracker sends searches and 404s, the feedback widget sends ideas and questions, and you can import support tickets as a CSV.

  2. 02

    Scrub

    Names, emails, phone numbers, card-like numbers and signatures are stripped before anything is stored.

  3. 03

    Group and rank

    Requests about the same tool or feature are grouped and ranked by evidence, recency and unique customers.

  4. 04

    Decide

    Build it, not now or never. Building one gives you the evidence to start a spec.

Live demo 3 of 3

See where people give up

A simulated live feed filtered to behavior: rage clicks, dead ends and sessions that end on the same page, the raw material for behavior signals.

rookon · acme-cloud · live events

Simulated data

Try: Switch the filter to All · Pause the feed by hovering it

FAQ

Common questions

Which support tools can I connect?

Ideas and questions from ROOKON's own feedback widget flow in automatically, and you can import a CSV export from any help desk or mail client. Gmail, Outlook, Intercom, Zendesk, Help Scout and Freshdesk integrations are planned and marked as such in the product.

What happens to personal data in support tickets?

We strip names, emails and numbers before anything is stored or sent to AI. ROOKON keeps a scrubbed subject, a scrubbed excerpt of up to 500 characters, the date and a salted hash of the customer, never the raw message. Imported tickets are deleted after 180 days.

Is site search tracking on by default?

No. It is off until you turn it on for a project. Search terms are lowercased and stripped of emails, phone numbers, long numbers and links before they are stored.

Does ROOKON write the spec for me?

Not yet. Drafting a spec with AI from the evidence is coming soon. Today you can copy the scrubbed evidence for any opportunity into your issue tracker or your own AI tool.

Does it understand Danish?

Yes. Request detection works in English and Danish, for example "kan I lave en integration til e-conomic" and "understøtter I SAML".

Build what your customers are already asking for

Sign up, add the tracking script, turn on site search and import your support tickets.