Market Fit Analysis Agent
Tests product demand against target segments.
- Industry
- Oil & Gas
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Assistant
- Approver
- Head of Digital Products
- Code
- PRD-03
It tests demand for a digital product against its target users before the company builds or extends it, for example a distributor self-service nomination portal, a fleet emissions dashboard on the fuel card, or a mobile operator rounds app for a new asset. It weighs survey, pilot and usage evidence and writes a fit assessment.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the product analytics tool: usage, retention and pilot adoption for the product and segment named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Digital Products with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it files the fit assessment on the product record. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The product discovery guide: target user groups, fit criteria and thresholds, pilot sites and accounts, evidence standards and past fit assessments.
Reads from
the product analytics tool: usage, retention and pilot adoption for the product and segment named.
Acts in
the product management tool: it files the fit assessment on the product record.
Hands back
An object with verdict (strong, emerging, weak or none), evidence (a list, each with type, sample_size, result, weight and dated (true or false)), differences_between_segments (a list), next_tests (a list) and recommendation.
Asks a person when
The assessment recommends entering or exiting a segment or rolling a field product to all sites, or the record would carry named customers' answers or account values.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Users who would be very disappointed without it (%) | 40 | Fit is strong at or above this survey share. |
| Smallest sample | 30 | Evidence from fewer users is labelled weak; field operator populations are small. |
| Pilot adoption that shows fit (%) | 60 | A pilot where fewer of the eligible users use it weekly does not show fit. |
| Independent sources | 2 | A fit verdict rests on at least this many kinds of evidence. |
| Oldest evidence (months) | 12 | Older evidence is labelled dated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Fit is strong at 40 percent very disappointed, or pilot adoption of 60 percent weekly, with at least 2 kinds of evidence.
- Evidence from fewer than 30 users is weak, and evidence older than 12 months is dated.
- A pilot at one site or one distributor is not proof for the rest; say what differs.
- Never put named customers' answers or account values in the record.
See the Market Fit Analysis Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.