Onboarding brief

Tell us about your use case.

Write it the way you'd explain it to a colleague — no technical terms needed. We'll come back with a first read shortly after you submit.

Part 1

The Basics

Your contact details and a short label for this use case.

Which part of your company is affected?

e.g., Operations Lead, IT Manager, Procurement Specialist.

Part 2

The Problem

What is taking too long, costing too much, or breaking too often?

This is the most important part. Write it the way you would explain it to a colleague. No technical terms needed.

Describe in plain language what is slow, expensive, or error-prone right now.

Daily / weekly / per shipment / per month.

e.g., 4 hours per day, 45 min per shipment.

Role or team name.

Errors, delays, costs, complaints.

Part 3

The Data and Tools

What comes in, what goes out, and which systems touch it today.

Format of input data: PDF, Excel, email, WhatsApp, scan, web form.

What should the system do once it has processed the input?

SAP, Salesforce, email, WhatsApp, Excel, DMS, ERP.

Which system receives the final output?

GDPR, confidential data, approval gates.

Part 4

The Target Outcome

What does a good result actually look like for your team?

Time saved, errors gone, steps removed. The more specific, the better.

e.g., under 2 minutes, under 3 minutes per shipment.

Which team or person gets their time back?

Processing time, error rate, headcount freed up.

Pick the level that best fits.

Any previous attempts, budget context, or things we should keep in mind.