Product Dev & Engineering · Find

Signal miner.

Mines the conversations you are already having for the unmet needs in them, and produces a defensible opportunity list on a schedule.

Experiential lens1 evidence-backed list a month modeled targets · not client results
.crft/Signal miner

evidence-backed list a month

to the Scan's evidence — before any scope

4–10 wks

to a system in production, not a pilot

modeled targets · not client results · timings are CRFT's standard engagement

The work, today.

Product priorities come from whoever argued best in the last meeting, or from the customer who complained loudest. Meanwhile every call recording and support ticket contains the actual answer, unread, because reading them is nobody's job.

Where the Scan startsWith call recordings, tickets and the market sources your team already trusts.

What the system is.

Four lines, the same four on every system we build. Where they fall is what makes this one different from the last one.

Sales and success call recordings and transcripts
Support tickets and their resolutions
Lost-deal reasons, as recorded and as actually stated
The market sources your team already reads
01

What it reads

The signals it works from. Typically connects to Call recording, Support desk, CRM and Research sources.

01Which needs recur, across how many accounts, and worth how much
02Which are already solvable and which need building
03What is a genuine pattern versus one loud customer
04What evidence supports each, quotable and traceable
02

What it decides

The calls it makes on its own, unattended, every time it runs.

A ranked opportunity list on a monthly cadence
The supporting quotes, with the account and the date on each
A running record, so recurrence over quarters is visible
03

What it writes back

Into the tools the work already lives in.

04

Where the human stays

The product decision stays entirely with the people who own the roadmap. The system removes the excuse that the evidence was not available; it has no opinion about strategy.

How we set it up.

The same four legs as every CRFT engagement — written for this system rather than in general.

  1. 01
    Scan48 hrs · evidence before scope

    We mine one quarter of existing calls by hand. If the exercise produces nothing your team did not already know, the system will not either, and we say so.

  2. 02
    Scope1 week · the report is the scope

    Scope is set by source access and language coverage. Recordings behind a vendor with no export are the usual blocker and are worth resolving first.

  3. 03
    Build4–10 wks · production, not a pilot

    The evidence chain is the deliverable. A claim without a traceable quote is worse than no claim, so nothing surfaces without one.

  4. 04
    Compoundongoing · it reports, then improves

    Which opportunities you pursued and how they performed teaches it what a real opportunity looks like here, rather than what a frequent complaint looks like.

What we hold it to

Whether the list changes a roadmap decision, and whether the opportunities pursued from it outperformed those chosen the old way.

Get CRFT

Build the intelligence your company compounds on.

Five inputs, a published price, a report in 48 hours. Decide with numbers — then own what gets built.

Or just send us a note
What kind of system? Pick any that apply