02 · Cases / 02
CrossmotionOS
Client
Crossmotion · international logistics · where I lead IT and projects · being built in phases
Agents gather the context. People sign off.
The challenge
People in sales, pricing, and operations spent a good part of the day hunting for emails, copying data between systems, and chasing replies. The existing systems had to stay; nobody wanted one more system to feed.
The approach
A single working interface per role, sitting on top of the tools the company already uses. It doesn't replace them: it reads, joins, and presents. We started with one process (managing quote requests) and grow in phases. Before writing code I drafted a one-page vision with the line we don't cross.
The system
01What already exists
- Files
- CRM
- Rates system
02Agents
- Gather context
- Classify emails
- Spot duplicates
- Prepare drafts
03File
- One file per request or shipment
04Screen per role
- Sales
- Pricing
- Operations
05A person signs off
- Send to customer or supplier
- Accept or counter
- Write to the CRM
The boundary
Agents decide
- Gathering a shipment's context.
- Classifying and linking emails.
- Suggesting which contacts to send a request to.
- Spotting duplicates and measuring response times.
- Preparing drafts.
People decide
- Sending any email to a customer, partner, or supplier.
- Choosing who gets a request.
- Accepting, rejecting, or countering a rate.
- Uploading a rate or writing to the CRM.
- Granting or removing access. Reserved by design, never automatic.
Every action is logged: who (person or agent), when, and how to undo it. Pauses waiting for a person are visible and have an owner.
Result
Each role opens one screen with what it needs that day, context already assembled. What took hours of searching takes seconds and leaves a trail.
What I learned
The written vision is worth more than the plan: the plan changes weekly, the vision is what stops an agent (or me) from crossing the line. And integrating beats replacing: nobody adopts something that adds work.