How the software works

Two sources go in. Nothing comes out without a source attached.

HEWEN reads what your company has written down, and listens to what the people in it actually say. Then it lays one over the other. Below is every step in between — in the order it happens.

We take it in

We read it

We listen

We lay one over the other

We weigh it

We show it

Step by step

From your systems to a sentence you can act on.

Each step has one thing it does, what it takes in, what it hands on, and the line it does not cross.

We take it in

Your files and systems are copied into one place that only your project can read.

Read-only connections to the systems you already run — ERP, CRM, ticketing, HR, planning, plus the documents nobody has a system for: board packs, strategy decks, audit reports, meeting notes. Every file keeps its origin: which system, which folder, which date, who last touched it.

Goes in

Systems, folders, exports

Comes out

Every source with a fixed ID

Never

Read-only. HEWEN never writes back into your systems.

We read it

The software pulls out sentences and numbers, and keeps the page they came from.

Each document is broken into single statements: a rule, a target, a number, a date, a responsibility. Every statement stays attached to its page or section so it can be shown back to you word for word. Numbers get a unit, a period and a definition — so a 'margin' from one report and a 'margin' from another can actually be compared.

Goes in

Documents and tables

Comes out

Statements with page and date

Never

Nothing is paraphrased at this stage. The original line is kept.

We listen

We talk to the people doing the work, and treat what they say as evidence.

Short, structured conversations, anonymous by design. Not satisfaction scores — questions like 'What does your team know that another part of the company could use?' Each answer is stored with role, area and date, never with a name. If several people say the same thing without being prompted, the software counts it.

Goes in

20–200 conversations

Comes out

Quotes with role, area, count

Never

No names, ever. Nothing is reported back per person or per team below five answers.

We lay one over the other

The documents say one thing. People say another. The gap between them is the finding.

Every statement from a document is matched against every statement from a conversation about the same topic, unit, process or number. Four things can come out of that comparison — see below. Only comparisons that hold in more than one place become a finding.

Goes in

Statements from both sources

Comes out

Matches, gaps, contradictions

Never

A single quote is never a finding. One voice is a lead, not a fact.

We weigh it

Each finding gets a confidence level and a number you can recalculate yourself.

Confidence is not a feeling. It comes from how many independent sources agree, how recent they are, and whether the number can be derived from your own data. Every euro figure carries its arithmetic: which quantity, which price, which period. If we had to assume something, the assumption is written down next to the number.

Goes in

Sources, dates, arithmetic

Comes out

Confidence + value, both traceable

Never

Where the data is thin, the software says so instead of rounding up.

We show it

Two levels: the short version in seconds, the whole evidence one click deeper.

Level one is a sentence a CEO can read while standing. Level two is the ledger: the document line, the page, the date, the anonymous quotes, the arithmetic, and what we did to avoid fooling ourselves. From there a finding becomes an action with an owner and a date, and the monthly check-in tracks whether the number moved.

Goes in

Weighed findings

Comes out

Findings, actions, monthly progress

Never

HEWEN never decides. It shows what it saw and asks the question.

The overlay

Four things can happen when both sides meet.

This comparison is the whole product. Everything else exists to make it trustworthy.

They agree

The paper and the people describe the same reality. Good news — and a solid base for anything you build on it.

The plan says two deliveries a week. Everyone in the stores describes two deliveries a week.

The paper knows, the people don't

A decision exists, but it never reached the floor. Usually the cheapest thing on the list to fix.

A framework contract with better prices exists. Three regions still order outside it.

The people know, the paper doesn't

Knowledge exists in the building and never makes it into a system. This is where most unused potential sits.

Service staff see the same six problems in fourteen countries. No product team receives them.

They contradict each other

Two true things that cannot both be acted on. Not a mistake — a decision that was never made.

The strategy asks for faster launches. The approval rule adds nine weeks to every launch.

How sure is sure

Confidence is a rule, not a feeling.

High

Two or more independent documents plus several unprompted voices, and the number can be recalculated from your own data.

Medium

The pattern is clear in the sources, but one part of the number rests on an assumption we wrote down.

Worth a look

Something showed up in one place only. We show it as a question, not as a finding.

What it never does

The limits matter as much as the abilities.

01
It does not grade people. No scores per employee, per manager or per team.
02
It does not decide. It never says 'you should'. It says 'we noticed' and asks the question.
03
It does not write into your systems. Every connection is read-only.
04
It does not train public models on your material. Your content stays inside your project.
05
It does not hide its reasoning. If a claim has no source, it does not appear.

Asked in every room

The five questions that always come.

How often does it refresh?

Connected systems pull nightly. Documents whenever you add them. Conversations in waves — a full round at the start, then a shorter round every quarter.

Where does the data sit?

In the EU, in a project that belongs to you alone. Encrypted on the way in and at rest. Deleted on request, including derived findings.

Who can see what?

Access follows your own roles. Leadership sees findings and evidence. Nobody, including us, sees who said which sentence.

What if it is wrong?

Open the evidence, read the line it used, and reject the finding. A rejected finding stays visible with the reason, so the same wrong turn is not taken twice.

How long until the first result?

Four weeks to the first picture, ninety days to a measured change. One department, three systems, twenty conversations to start.

See it in practice

Every finding in the demo carries the full ledger: the document line, the page, the anonymous quotes and the arithmetic.

What we found→Both sides, side by side→How the first four weeks run→