Skip to content

Give your agents a clear job.

Turn the promise of your agent into an agreed customer workflow. Define the job, information, actions and human decisions before engineering configures, evaluates and deploys it.

Explore the example. See the decisions behind the delivery.

Context Boundaries Review Recover
01

Focus on useful work

Tie the agent’s proposed role to a specific job in the customer’s operation.

02

Make human decisions explicit

Agree approval rights, exception routes and escalation ownership before live operation begins.

03

Give engineering testable boundaries

Carry reviewed rules and acceptance cases into implementation, evaluation and production checks.

For agent teams

Design the job before you deploy the agent.

Map the work, choose where an agent helps and keep people in the decisions that matter, in the product your team already reviews.

  1. ProcessScout / TransformReal product · fictional data
    Map the job around the agent: Transform with fictional example data
    Try this step in the demo
  2. ProcessScout / TransformReal product · fictional data
    Choose where the agent helps: Transform with fictional example data
    Try this step in the demo
  3. ProcessScout / TransformReal product · fictional data
    Design the work and the boundaries: Transform with fictional example data
    Try this step in the demo
  4. ProcessScout / Build FactoryReal product · fictional data
    Review the change before it ships: Build Factory with fictional example data
    Try this step in the demo

Interactive demo · Fictional customer data · No sign-up

01

Agree the customer job and human decision.

In the Northstar example, a proposed assistant checks purchase-request fields and recommends an approval route. People approve or reject. Agree that division of work before implementation.

  • Input: order ID, amount in USD and urgent status.
  • Assistant: check fields and prepare a route for review.
  • Person: approve or reject through the agreed route.

A purchase request supplies fields. The proposed assistant checks the request and prepares a route. A designated person makes the approval decision.

Define the job and the decision rights.Proposed workflow
Inspect the exampleNorthstar Supply
Northstar Supply · Purchase approvalProposed design

Purchase-request workflow

REQUESTOrder ID · amount · urgent status

Ordinary route

  1. Check the amount
  2. Below USD 10,000 → purchasing manager
  3. At or above USD 10,000 → finance
  4. A person records the approval decision

Urgent branch

  1. Mark urgent
  2. Notify purchasing manager
  3. Keep the amount-based approval route
Urgency does not bypass approval.

Proposed target after D-01 and D-02. The original walkthrough remains uncertain about finance approval.

Open question

Q-05 · Who receives an escalation, and through which route?

Owner: Customer process owner

Illustrative example - fictional customer data. Inspect the source material.
02

Make the exception paths part of the design.

Missing amounts require clarification; urgent orders require notification and approval. Conflicting sources need a customer decision. The assistant must neither guess values nor bypass approval.

Urgency does not bypass the required approval. If the amount is missing, the assistant asks for clarification and does not prepare a route. Conflicting sources need customer review, not a guessed rule.

Uncertainty needs a human route.Proposed agent behavior
Inspect the exampleNorthstar Supply
Northstar Supply · Purchase approvalProposed design

Give uncertainty a human route.

R-02 · D-02

Urgent order

Notify the purchasing manager. The amount-based approval still applies; urgency cannot authorize bypass or release.

Inspect urgent-request behavior
R-03 · D-03

Missing amount

Ask the requester for clarification. Do not prepare an approval recommendation until a valid amount is supplied.

Inspect incomplete-request behavior
Q-01

Unclear or conflicting policy

Keep the disagreement visible and ask the customer process owner to decide. A proposed assistant must not invent a resolution.

Inspect the question register
Illustrative example - fictional customer data. Inspect the source material.
03

Review behavior at the important boundaries.

Check amounts below, at and above $10,000, plus urgent and incomplete requests. Turn each into an acceptance case your evaluations can run.

Under the fictional reviewed target rule, USD 9,999 routes to the purchasing manager. USD 10,000 and USD 10,001 route to finance. These acceptance examples have not been executed.

Make the boundary testable before building.Acceptance cases
Inspect the exampleNorthstar Supply
Northstar Supply · Purchase approval

Boundary acceptance cases

A-01USD 9,999 · ordinary

Purchasing manager review

R-01 · Expected behavior
A-02USD 10,000 · ordinary

Finance review

R-01 · Expected behavior
A-03USD 10,001 · ordinary

Finance review

R-01 · Expected behavior
A-04USD 10,000 · urgent

Notify purchasing manager; finance approval still required. No bypass or release.

R-02 · Expected behavior
A-05Amount missing · ordinary or urgent

Request clarification; do not prepare an approval recommendation.

R-03 · Expected behavior

These are expected behaviors for the fictional target. No model or implementation tests have been executed.

Illustrative example - fictional customer data. Inspect the source material.
04

Put reviewed boundaries into the engineering brief.

Document permitted reads and actions, required tools and human decisions. Include urgent and missing-information paths. Engineering must confirm architecture, permissions and runtime behavior during implementation.

The proposed assistant reads agreed context and prepares a recommendation. Purchase approval or rejection remains with a person. The diagram does not run an agent or enforce permissions.

The assistant prepares. A person authorizes.Implementation must enforce the boundary
Inspect the exampleNorthstar Supply
Northstar Supply · Purchase approvalProposed design

Agent actions and human approvals

Required inputs

Order ID · valid amount in USD · urgent status · reviewed routing rule

Assistant may prepare
  • Check supplied fields for completeness
  • Request clarification for a missing amount
  • Prepare a routing recommendation using R-01
  • Flag urgency and notify the purchasing manager
A person must decide
  • Confirm the business rule and permissions
  • Make and record the approval decision
  • Resolve unclear policy and escalation
  • Authorize any release in the implemented workflow

Proposed design for the customer implementation. Urgency never authorizes bypass. Identity and access (Q-04) and escalation (Q-05) remain open.

Illustrative example - fictional customer data. Inspect the source material.
05

Use observed behavior for the delivery decision.

Run the agreed requirements through implementation evaluations and operational checks. Record what ran, the observed results and remaining decisions before reviewing readiness with the customer.

  • Exercise threshold, urgent and incomplete-request paths.
  • Check permissions, human approval and escalation.
  • Review observed results before deciding on live delivery.

Take the expected cases into implementation checks, record actual results after execution, and have a person review the evidence before deciding on live delivery.

Compare expected behavior with actual execution.Evidence before go-live
06

Bring operating lessons into reviewed product changes.

An exception may suggest a rule, integration or product change. Keep its customer evidence attached, then review scope and engineering work before changing agent behavior.

A customer request enters Product review. Agreed scope can inform development; later operating feedback returns with its customer context. The fictional CR-01 request is still pending.

Keep the customer reason with the change.Fictional example
Inspect the exampleNorthstar Supply
Northstar Supply · Purchase approvalProposed design

From a customer request to a product decision

Customer request · CR-01

Add production integration for the approval route.

The request extends the agreed brief. Production integration remains excluded until scope, architecture, access and effort are reviewed.

Product decision
Review standard configuration, customer-specific extension or a reusable product change. No option is approved in this example.
Development input
A cited specification, affected requirements, boundary cases and dependencies. A build starts only after the appropriate review.
Return to Product
Capture the request and later deployment feedback with the customer context intact. Decide what belongs on the product roadmap.
Illustrative example - fictional customer data. Inspect the source material.

Questions buyers ask.

How a pilot works

  1. Choose one workflowA real customer process your product or agent must support.
  2. Share what you haveWalkthroughs, policies and spreadsheets, under agreed permissions.
  3. Review the briefYour team and the customer confirm the rules and decisions.
  4. Measure the effortCompare preparation, review and rework with your baseline.
Who is this for?

SaaS vendors, agent providers and partners implementing agents inside customer businesses, whether agents extend the platform or are the product.

Does ProcessScout run or evaluate the agent?

It prepares customer context, rules and acceptance cases. Your engineering team owns model evaluation, runtime behavior and production checks.

Who decides what the agent may do?

The vendor and customer review proposed permissions, risks and business decisions. The brief records boundaries; implementation must enforce them.

What if customer sources disagree?

Keep the conflict visible and assign a reviewer. An unreviewed interpretation must not become the operating rule.

Bring the job your agent must do.

We’ll scope the workflow, rules and human responsibilities your engineering team needs to review.

Discuss a pilot

Scope, timing, access and terms are agreed before a pilot begins.

Product view

ProcessScout interactive demo · Fictional Northstar data