Service Demand Analysis Agent
Tests demand for new shopping and fulfilment services by shopper segment.
- Industry
- Retail
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Assistant
- Approver
- E-commerce Director
- Code
- PRD-03
It tests demand for a new omnichannel service or app feature (same-day delivery, ship-from-store, rental or resale, a paid delivery pass, in-store mode in the app) in each shopper segment against the evidence: survey and panel results, search and site behaviour, order and fulfilment data, and catchment size. It writes a segment-by-segment demand verdict with the evidence and the next test, and records it on the opportunity in the product management tool.
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 order management system: orders by fulfilment option, delivery zone and segment, with basket value and fulfilment cost..
- 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 E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it records the demand verdict on the opportunity. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The demand testing standard: the shopper segments, survey thresholds, how site behaviour and order data count as evidence, catchment and delivery-zone data, and past service launches and their uptake.
Reads from
the order management system: orders by fulfilment option, delivery zone and segment, with basket value and fulfilment cost.
Acts in
the product management tool: it records the demand verdict on the opportunity.
Hands back
A list with one entry per segment, each with segment, verdict (strong, emerging, weak or none), evidence (a list, each with type and finding), cost_to_serve_vs_margin (text) and next_test.
Asks a person when
The verdict recommends launching a paid service or one with a cost to serve above the expected margin, or the evidence uses shopper-level personal data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Survey interest that signals demand (%) | 40 | Share of a segment saying they would use it often that signals demand. |
| Least survey responses per segment | 100 | Survey results from fewer shoppers than this are not relied on. |
| Independent sources per verdict | 2 | A verdict needs at least this many kinds of evidence agreeing. |
| Oldest evidence (months) | 12 | Evidence older than this is left out. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A segment shows demand only when 40 percent or more express frequent use from at least 100 responses, and behaviour or order data agree.
- Every verdict rests on at least 2 independent kinds of evidence no older than 12 months.
- Weigh demand against the cost to serve: a service whose cost per order exceeds the expected basket margin is not viable without a fee.
- Use loyalty and order data only in aggregate, never at the level of a named shopper.
- Name the next test for each segment, the cheapest one that would change the verdict.
See the Service Demand 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.