New: AI Visibility Audit for B2B software
← Demo LabINDEPENDENT CONCEPT · DESIGN REVIEW
PARTNER WORKSPACE DESIGN PROPOSAL / 01

Give every partner request a clear next move.

A compact workspace to review a travel-partner brief, prepare a draft and keep human approval visible.

Try the live prototype
WORKING DESIGN PROTOTYPE↗
Visual concept for the proposed workflow
Fictional requests. Local session only; no shared board, supplier data or CRM connection.
01 / UNDERSTAND THE FRICTION

A message thread can hide the current state of a request.

Working hypotheses to validate with your team.

01

Responsibility and status may be scattered.

02

A draft can be confused with the approved version.

03

A partner needs the next action, not another status chase.

THE DESIGN RESPONSE

Make the handover part of the workflow.

01

Keep requests in visible stages.

02

Prepare a reviewable draft from the brief.

03

Check suppliers and prices before approval.

02 / TRY IT YOURSELF

A short test. A clearer decision.

Open the prototype ↗
01

Open a sample partner request.

02

Prepare the draft and move its stage.

03

Inspect the approval checklist.

03 / DEFINE THE VALUE

What would make this worth building?

Design earns its place when it improves a real process. Capture a baseline, test a limited release and compare the same measures.

  • Requests without an assigned next action.
  • Turnaround from brief to reviewed draft.
  • Rework caused by missing information.
04 / A CONTROLLED FIRST RELEASE

Test one partner-request workflow.

A bounded request board with ownership, stages and an approval checklist. CRM replacement is outside this pilot.

01

Define

Map the current workflow, constraints and baseline. Agree on a written scope and acceptance criteria.

02

Design

Review the important journeys with representative content before implementation.

03

Build & verify

Implement the agreed scope, test integrations and review real content with the owner.

04

Launch & learn

Hand over source and operating notes, agree support boundaries and compare results with the baseline.

WHAT EXISTS TODAY

A clear prototype. A separate production scope.

Fictional requests. Local session only; no shared board, supplier data or CRM connection.

No real order, payment or external message is created by these demos. Input stays in the current browser session; downloads are optional. Reloading clears demo state. Do not enter real customer data.

THE NEXT DECISION

Choose a direction.
Define the first release.

Bring the current workflow, constraints and a small set of representative examples. We can define a written scope, acceptance criteria, price and milestones before implementation.

Discuss this concept ↗

Prepared by Reza Farsi · Product design & software engineering · Design direction, architecture, review and delivery led by Reza.

REZA FARSI / CONCEPT PRESENTATION

Prefer a direct message?

Send a short description of what you need. We can clarify the next step together.