AI at work/ Interactive workflow example
Agents retrieve customer terms, coordinate internal and supplier requests, process replies and assemble a quote within your pricing and approval rules. Company Brain supplies shared company knowledge throughout; the Laava Platform orchestrates work and system actions.
Fictional company, customer, suppliers and amounts. Emails, requests and sending the quote are simulated.
An email with a three-line attachment
Stock, engineering and two suppliers, in parallel
An approved quote on the original email thread
01 / The example
Play it, step through the chapters or choose another path. Click any item to open its document, including how the customer or supplier sees it.
Interactive workflow exampleFictional
RFQ-NKP-2291Received
Case timeTue 13 Oct · 08:12+0 m · Time compressed
01 / 08RequestStep 1 of 13
Noordkade emails a request with an attachment: three lines, delivery by 13 November and ATEX zone 2 for the butterfly valves.
Click any item to open its document.
Document · Step 1
Good morning Eva, Please send us a quote for the lines in the attachment, delivered to Delfzijl by 13 November. The butterfly valves must be suitable for ATEX zone 2. Kind regards, Sanne Visser Purchasing, Noordkade Proces
Case time is compressed: more than a working day in about a minute.
02 / Step by step
The standard path of the example, from the first email to the updated case record.
01Request
Noordkade emails a request with an attachment: three lines, delivery by 13 November and ATEX zone 2 for the butterfly valves.
The intake agent matches the customer on sender and customer number, and maps their part numbers to your own. Case RFQ-2026-0418 is open.
02Context
Company Brain supplies the framework agreement, the previous quote, the ATEX procedure and the margin policy, each with source and version. Every later step uses the same facts.
03Parallel work
Stock is checked, engineering gets the ATEX check and two suppliers get a price request. Suppliers only see specification, quantity and date.
24 ball valves and 120 gasket sets are reserved and can ship on 4 November. Nobody has to wait for that.
04Wait and resume
Cheaper, but delivery only on 3 December, price valid until 23 October and no ATEX marking on the datasheet. This offer cannot meet the request.
Wednesday morning Kostrel replies: more expensive, but delivery on 6 November and an ATEX certificate. The reply lands in the same case. Only engineering is still pending.
Joris checks the certificate and approves the Kostrel valve for zone 2. Every condition for the quote is now met.
05Build the quote
Fixed calculation rules, not a language model: 8% customer discount on valves, fixed price for gaskets, purchase cost plus freight. Net €30,344.16, margin 26.94%.
06Review
Above €25,000 the policy requires the account manager's approval. Eva sees exactly what she approves: revision R1, discount, margin and delivery dates.
The approval belongs to this one revision. If a price, quantity or term changes later, it lapses.
07Send
Revision R1 goes out as a reply to Sanne's original email, with prices, delivery and terms. No purchase prices or margin. Sending is simulated here.
08Record
Chosen supplier, technical approval, sent revision and a follow-up on 21 Oct are in the case. The framework agreement itself does not change.
03 / Who does what
Customer agreements, part mappings, procedures and policy, with source, version and owner. Every step uses the same facts, with only the knowledge that step needs.
Case, tasks, waiting, reminders and system actions. Replies land on the right case and line; a duplicate message is processed once.
Prices and margins come from fixed calculation rules, not a language model. Engineering and sales decide where policy asks for it. An approval covers one revision.
The next step
Together we look at one process: where it starts, where it waits and which rules apply. Then it is clear what a first application can do.
Discuss this workflow for your organisationMore about Company Brain