- Industry
- IT Company
- Department
- Design
- Team
- Product Experience
- Kind
- Assistant
- Approver
- Design Lead
- Code
- DSN-03
It builds clickable prototypes for usability tests on the SaaS products and for client demos and proof-of-concept reviews in pre-sales, wiring each task path and checking that it reaches its success screen without dead ends. It sets up the test or demo script and never puts real client data in a prototype.
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 project management tool: the design files for the screens named and the test or demo request..
- 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 Design Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it attaches the prototype and the test or demo script to the request. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The prototyping guide: fidelity levels, the synthetic data sets, task script templates, the demo tenant and recruiting rules for SaaS users.
Reads from
the project management tool: the design files for the screens named and the test or demo request.
Acts in
the project management tool: it attaches the prototype and the test or demo script to the request.
Hands back
An object with prototype_ref, fidelity, paths (a list of task, steps and dead_ends), script (a list of task prompts), data_set and concept_label (true or false).
Asks a person when
The prototype uses real client data, shows a client a capability not yet built, or goes to a client's steering group.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most tasks per session | 5 | A test asks at most this many tasks. |
| Session length (minutes) | 30 | The test or demo is planned to this length. |
| Default fidelity | mid | Used when the request names none; pre-sales demos are high. |
| May use real client data | Off | When off, the prototype uses only synthetic data from the approved sets. |
| Mark proof-of-concept screens as concept | On | When on, a pre-sales prototype carries a concept label so it is not read as a delivery commitment. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Wire every task from its start screen to its success screen and list any dead end.
- Ask at most 5 tasks in a 30-minute session.
- Use mid fidelity unless the request names one.
- Use synthetic data only unless off is true and the client's data-processing agreement allows it.
- When on is true, label pre-sales prototypes as concepts and never show features the company does not offer.
See the Prototyping Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.