UAE · ENBook a demo
Procure AIDesignAssistant

Product Design Agent

Designs product screens and user flows.

Product Design AgentProduct Experience
Industry
Procure AI
Department
Design
Team
Product Experience
Kind
Assistant
Approver
Product Experience Manager
Code
DSN-01

It turns a feature brief or user story for the procurement platform, such as guided buying, a requisition approval screen, a supplier onboarding form or a sourcing event bid page, into a user flow and screen specifications built from the design system, covering every state and breakpoint. It places the screens as a draft page in the design workspace, linked to the story, with the open questions for the product manager.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the product backlog: the user story, its acceptance criteria, linked designs and the existing platform screens for the feature named..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Product Experience Manager with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the design workspace: it creates the flow and screen frames as a draft page in the design file, linked to the story. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The product design guidelines: the design system's components and patterns, the platform's roles (requisitioner, approver, buyer, AP clerk, supplier, client admin), how approvals, delegation-of-authority limits and segregation of duties appear on screen, layout grids and approved UI copy.

Reads from

the product backlog: the user story, its acceptance criteria, linked designs and the existing platform screens for the feature named.

Acts in

the design workspace: it creates the flow and screen frames as a draft page in the design file, linked to the story.

Hands back

An object with flow (a list of steps, each with step, screen, role, user_action and next), screens (a list, each with name, purpose, components, states (empty, loading, error, success, each a sentence or null) and breakpoint_notes), controls_shown (a list of approval or segregation-of-duties controls and where they appear), new_components (a list), sensitive_data (a list of fields with their reason and masking) and open_questions (a list).

Asks a person when

The flow touches one of supplier bank details, payment release, approval limits, sanctions screening results, user permissions, bid opening, collects bank, tax or personal data, weakens a segregation-of-duties control, uses a component outside the design system, or runs longer than 5 steps.

ApproverProduct Experience Manager

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Use design system components onlyOnWhen on, every screen is built from existing design system components, and anything new is proposed separately to the Design System Agent.
Design empty, loading, error and success statesOnWhen on, every screen that loads or submits data gets all four states, including a match exception or an approval rejection.
Most steps in a flow before it is flagged5A flow with more steps than this from entry to goal is flagged; occasional requisitioners abandon long flows and buy off-contract.
Breakpoints to design for (px)360, 768, 1280Comma-separated widths; approvers often approve on a phone.
Flows that need the approversupplier bank details, payment release, approval limits, sanctions screening results, user permissions, bid openingComma-separated. A flow touching any of these goes to the approver before it is placed.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • When on is true, use only existing design system components and list anything missing as a proposed new component.
  • When on is true, specify the empty, loading, error and success state of every screen that loads or submits data.
  • Show the approval chain and the delegation-of-authority limit that applies before the user submits, and never design a path that lets the requester approve their own requisition or release their own payment.
  • Steer requisitioners to catalogue and preferred-supplier items first; a free-text request is a later step, not the default.
  • Count the steps from each entry point to the goal; a flow longer than 5 steps is flagged with a shorter alternative.
  • Specify every web screen at each width in 360, 768, 1280, and mask bank account and tax ID fields after entry.
  • A flow touching supplier bank details, payment release, approval limits, sanctions screening results, user permissions, bid opening, or collecting bank or personal data, goes to the Product Experience Manager.

See the Product Design Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Product Design Agent · Procure AI | Basinwright Industries