On this page
Three differences you can check before you choose
- Real requests the same week. Turian’s own site says its implementations “typically take four to six weeks from kickoff to live processing”. ERP Agent starts from the product file you export today. Send it, and your reps forward real customer requests to your company’s agent mailbox the same week, while the connection to Business Central, SAP, NetSuite or your other ERP is set up. Past quotes help it learn how your customers write.
- A trial on this week’s requests. Turian’s site offers “a proof of concept using historical documents from the customer’s own order mix”. With ERP Agent the trial is your live inbox. Reps forward the requests that arrive this week, from any customer, and review each draft line by line in the web app. You count the lines that come back right on requests your team has to answer anyway. The pilot checklist shows how to score it.
- When two products fit, the runner-ups are already on the line. Turian’s quotations page says that when a request stays ambiguous, it “surfaces its best candidate with a confidence indicator and routes it to the inside sales team”. In ERP Agent the line carries the agent’s pick and up to three ranked alternatives from your catalogue, each with its own match score, unit price and line total. Your rep presses 1, 2 or 3 to swap, 0 to go back to the agent’s pick, or A to run a fresh search for that line. Nobody has to look the product up in the ERP.
Turian vs ERP Agent, side by side
The Turian column uses Turian’s own homepage and quotations page.
| Turian | ERP Agent | |
|---|---|---|
| First real request processed | Implementations “typically take four to six weeks from kickoff to live processing” | The same week, from the product file you export today |
| Trying it on your own requests | A proof of concept “using historical documents from the customer’s own order mix” | Live requests from any customer, forwarded to your agent mailbox in the first week |
| More than one product could fit the line | Surfaces “its best candidate with a confidence indicator” and routes it to the inside sales team | The pick plus up to three ranked alternatives on the line, each with score, price and line total; keys 1–3 swap, A searches again |
What your rep does with a 40-line request in ERP Agent
All of this happens in one review screen, and every step works from the keyboard.
The draft fills in while you watch
Lines appear in the table as the agent matches them. Requests with several hundred lines are split into batches that run in parallel.
Go straight to the marked lines
Every line carries a match score from 0 to 100. Press N to jump to the next line under 80. The customer’s original wording sits next to the proposed product, with the agent’s reason for choosing it.
Swap with one key
Press 1, 2 or 3 to take a stored alternative, and see the new price and line total at once. Press 0 to go back to the agent’s pick, or A when you want the agent to search that line again.
Change the rest by typing
In quote chat, type the change in your own words. The agent searches your catalogue and shows each change as before and after. Keep or reject each one. The chat cannot send anything.
Send, and it learns
Send to your ERP with “Final — send and learn”. The next time a customer writes the same thing, the agent picks the same product. Nobody writes a rule.
Example: a workshop’s request in its own words
A metalworking shop emails a technical wholesaler of fasteners and steel. Prices are left out here; in a real draft they come from your company’s pricing.
“Hello, please quote the following for week 48, delivery to our workshop.”
- 200 x hex bolt M12x60 8.8 zp
- 200 x nyloc M12
- 400 x washer M12 large
- 6 x flat bar 40x5 S235 6m
- 10 x our art. 77-1203
| Request line | Proposed product | Qty | Match | Note |
|---|---|---|---|---|
| hex bolt M12x60 8.8 zp | Hex bolt M12 × 60, 8.8, zinc plated | 200 | 96 | “zp” read as zinc plated; size and grade match. |
| nyloc M12 | Nylon-insert lock nut M12, class 8, zinc plated | 200 | 84 | “Nyloc” read as nylon-insert lock nut. Finish not stated in the request. |
| washer M12 large | Washer M12, large series, zinc plated | 400 | 74 | Marked: two large-series washers fit. The A2 stainless one is alternative 1, one keypress away. |
| flat bar 40x5 S235 6m | Flat bar 40 × 5 mm S235JR, 6 m | 6 | 95 | Section, grade and length match. |
| our art. 77-1203 | Threaded rod M12 × 1000 mm, 8.8, zinc plated | 10 | 98 | The customer’s own code, learned from an earlier quote and shown on the line. |
Illustrative example with sample products, codes and scores, showing what the review screen explains on each line.

Why the product decision is the part that matters
Reading the fields off a PDF is the easy half of a quote request. The slow half is deciding which of your products each line means when the customer writes shorthand, gives dimensions in their own format or uses their own article number. According to our case study, a sales rep spends on average 4–7 minutes per line when creating quotes and orders by hand (calculate your cost).
Turian’s FAQ describes AI assistants for “diverse business functions, such as Sales & Service, Procurement, or Compliance Management”. A platform built to automate many processes asks you to adopt that platform. ERP Agent does one job thoroughly, on top of the ERP you already run: it turns the request your customer sent into a priced quote or sales order. It makes the product decision for every line, shows how sure it is, and leaves your rep a one-key fix when it is wrong. See how ERP Agent automates quotes.
How to test it on your own requests
You can run ERP Agent on real requests before any integration work begins.
Send your catalogue
The product file you export today is enough to start; past quotes help it learn faster.
Forward this week’s requests
Your company gets its own agent mailbox. Reps forward customer requests there or paste them into the web app, and a typical request is ready for review in 3–8 minutes.
Count the lines that come back right
Include the difficult requests: long lists, scans, shorthand and lines where two of your products could fit. Our pilot checklist shows how to set up a fair trial.
Connect your ERP
We set up the connection to your ERP or CRM during onboarding. Reviewed quotes and orders then land in the system your team already uses.
ERP Agent in numbers
- 4–7 min
- per line when quotes and orders are created by hand, according to our case study
- Over 95%
- average automation across our customers
- Over 95%
- accuracy in quote-line automation at LVI-WaBeK
- 3–8 min
- for the agent to prepare a typical request
ERP Agent is live with steel, HVAC and fastener distributors. Read how LVI-WaBeK turns customer requests into quote lines with the right products and prices.
