Two people at a table discussing a sketch, with open laptops beside them.

LOKI in sales

AI for sales. Costings and commitments stay in the building.

“What did we promise customer Meier in the 2021 warranty case?”

An order passes through many hands. What it produces lives in documents, emails, minutes and databases. LOKI reads it all and answers. With sources.

In sales

The customer asks. You have the proof.

LOKI runs fully locally on your hardware. It searches quotes, costings, contracts and mailboxes with a single question. Every answer names its source.

Monday, 8:10 a.m.

Customer Meier calls and refers to a commitment from 2021. It was made by a colleague who now works in another department.

What did we promise customer Meier in the 2021 warranty case?

In the warranty case, customer Meier was promised a goodwill replacement for up to 24 months after delivery, in writing on 14 March 2021 by sales 1. The contract addendum from April 2021 confirms the arrangement and extends it to spare parts 2. The ERP history documents a 2022 replacement already handled under this rule 3.

  • 1Email thread
  • 2Contract (PDF)
  • 3ERP history

The callback happens the same morning. With the commitment word for word and the contract that goes with it.

Inside sales

Which quotes to Meier are still open, and when do they expire?

Two quotes are open 1. The one for the switchgear is valid until 30 November, the one for the spare parts until 15 December 1. On Monday, the customer’s purchasing team asked about the delivery time for the first one 2.

  • 1Quote list · ERP
  • 2Email thread

Head of sales

Which projects in the food industry can we name as references in the quote?

Three projects since 2022 qualify 1. For two of them, the customer has agreed in writing to be named as a reference 2. For one, there is a project report with photos in the sales folder 3.

  • 1Project list · ERP
  • 2Reference approvals
  • 3Project report

Along the order

From the inquiry. To the complaint.

An order passes through many hands. LOKI knows the status at every station.

Hands on a tablet in a bright office.

01Inquiry

An inquiry comes in. What your company has already been through with this customer is in the ERP, in complaint files and in mailboxes.

New inquiry from Meier. What have we delivered to this customer so far, and were there any problems?

Four orders since 2019, most recently the 2023 extension 1. One delivery led to a complaint in 2022, resolved with a goodwill replacement 2. Since January, a new head of purchasing has been in charge at the customer. The change is in the email thread 3.

  • 1ERP history
  • 2Complaint file
  • 3Email thread

Sales goes into the conversation knowing the customer’s whole history.

Two people at a table sketching a process on a large sheet of paper.

02Quote and costing

The inquiry sounds familiar: MCC switchgear, similar power class, similar industry.

Have we ever costed an MCC assembly like this before? And what went off the rails back then?

Yes, in 2023 for a project in a comparable power class 1. Three change orders grew out of it 2. The internal minutes record why the terminal compartment design caused a two-week delay back then 3.

  • 1Costing 2023
  • 2Change order file
  • 3Project minutes

The quote builds on what your company has already learned. The risks are on the table before the price is set.

Two people at a table going through a document, a pen pointing at a line.

03Change orders

Four months after acceptance, the client disputes ever having ordered a change. 18,000 euros are at stake.

The customer’s disputing the change order on the incoming feeder. Who requested the change, and when?

It was requested at the site meeting on 11 March and confirmed in writing by the site manager 1. The meeting minutes record the approval 2, and the measurement record entry of 19 March documents the execution 3.

  • 1Email thread
  • 2Meeting minutes
  • 3Measurement record

Change orders rarely fail on merit, mostly on evidence.

Two colleagues at a screen, one pointing at a spot.

04Order clarification

The order is in. The clarification meeting settles acceptance, documentation and open points. Not everyone who works on the order was there.

What did we agree with Meier on acceptance in the clarification meeting?

Acceptance takes place at your plant, with two of the customer’s representatives 1. The documentation goes out in German and English, as PDF 1. The color of the control cabinets is still open. The customer’s purchasing team promised an answer by email by Friday 2.

  • 1Clarification minutes
  • 2Email thread

Everyone works from the same status. Including those who weren’t at the meeting.

Hands on a keyboard at a bright desk.

05Customer communication

The customer wants to know where the order stands. The answer is in the order confirmation, purchasing and assembly planning.

Meier is asking about the delivery date. What did we promise, and will we make it?

Week 14 is promised, as stated in the order confirmation 1. A supplied part arrives one week later than planned, purchasing reported this on Tuesday 2. According to the assembly plan, the buffer still covers it 3.

  • 1Order confirmation
  • 2Purchasing email
  • 3Assembly plan

The customer gets the answer on the same call.

Employee with a tablet at a machine tool.

06Complaint

The customer reports a dimensional deviation. The 8D report is due by Monday.

Complaint about part 4711. What measurements do we have, which tool was in, which program version?

The measurement report from the final check shows all dimensions in tolerance 1. The machine data collection (BDE) journal records a tool change in the middle of the batch 2. And the NC program version was changed two days earlier, the change note states the reason 3.

  • 1Measurement report
  • 2BDE journal
  • 3NC change note

The report cites documents, not memories.

Examples. Customers, names, data and details are fictitious.

Cited Answers

Every answer. With proof.

LOKI numbers its sources. One click opens the original on the right page and highlights the passage. Down to the paragraph.

The customer’s disputing the change order on the incoming feeder. Who requested the change, and when?

It was requested at the site meeting on 11 March and confirmed in writing by the site manager 1. The meeting minutes record the approval 2, and the measurement record entry of 19 March documents the execution 3.

  • 1Email thread
  • 2Meeting minutes
  • 3Measurement record

2Site_meeting_minutes_11-03.pdfPage 2 of 3

Site meeting on 11 March

Item 1 Construction schedule

Installation of the low-voltage distribution is on schedule. The ground floor rooms have been handed over, the screed in the technical room is dry.

Item 2 Cable tray

The tray in the basement is laid except for the section at axis C. The rest follows once the old wall has been removed.

The client is checking whether the tray should be built 30 percent wider for a later extension.

Item 3 Incoming feeder

The client’s site manager requests the feeder for 800 A instead of 630 A. He approves the work as a change order. The change order quote follows by 15 March.

The modified feeder does not delay acceptance of the low-voltage distribution.

Item 4 Dates

Next site meeting on 25 March, 9:00 a.m. Participants receive the minutes by email.

Distribution

Client site management, project management, sales, installation.

Example. Customer, minutes and details are fictitious.

Governance

Every department. Its own rights.

Roles and groups control who can see what. If someone isn’t allowed to see it, search won’t find it for them.

Sales and engineering groups with users, managers and approved tools.
Log of access to external models: time, user, model and tokens per request.
Overview in a plant engineering company’s dashboard: 12,480 documents, 92 users, 7 groups, plus chats and requests from the last 30 days.

Example. Company, names and figures are fictitious.

Rights all the way to the index.

Access limits apply in the interface and all the way into search. SharePoint permissions carry over during sync.

What goes out gets checked.

Before data goes to a cloud model or web search, HEIMDALL checks it. You decide right in the chat. More about HEIMDALL

Sign in as usual.

With Microsoft Entra ID, with two-step sign-in if you like. New users land in the right group automatically.

The Promise

Runs in-house. Without the cloud.

Costings, quotes and customer commitments belong in-house. LOKI comes to you on its own hardware. Everything is on board, from the language model to text recognition. Without any internet connection, if you like.

The included LOKI server

No internet?No problem.

Zero

data in the cloud. Out of the box.

Unlimited

users. With one license.

Under 4 weeks

to production. Plug and play.

Want more? Then you enable cloud models, and HEIMDALL checks every request before it leaves the building. More about HEIMDALL

Platform

Four tools. One system.

This page shows LOKI. Three more tools pick up where LOKI alone does not reach: at the machine, on the way to the cloud and in the meeting room. Each runs on its own, and together they form one system.

AI knowledge assistant

Answers questions from your documents, mails and databases. With sources.

LOKI searches what your projects left behind and answers with the exact passage. On your own hardware.

BenefitWhat you learned on the last project goes into the next quote.

More about LOKI

Machine AI · Design partner program

Readings that never end up in a file.

MINERVA captures currents, temperatures and switching cycles at the equipment, with its own boards on your own network. LOKI then cites the series like a document.

BenefitMaintenance by condition, not by calendar.

More about MINERVA

AI firewall

Cloud AI for the quote. Without customer names.

When you pick a cloud model in LOKI, HEIMDALL checks every request before it goes out. Whatever it detects, the cloud only sees as a placeholder. Or you handle the request locally.

BenefitCustomers, orders and prices only go out as placeholders.

More about HEIMDALL

AI minute-taker

SAGA takes the minutes of the project meeting.

SAGA records the meeting in house and drafts the minutes. You capture decisions in one click, and the minutes carry the source in the margin.

BenefitIf the change order is disputed, the minutes show what was discussed.

More about SAGA

Examples with invented names and values.

Start with one and add the others when you need them.

LOKI in engineering

And in engineering?

Engineering works with the same LOKI. It asks about specifications, revision status and commissioning.

LOKI in sales

One station. One conversation.

An intro call shows where along the order LOKI makes the biggest difference for you, and which documents you already have for it.

LOKI can make mistakes. Please verify important information against the cited sources.