Value management for organisations

See the value that moves between your departments.

Enterprise Value Center is a workspace to account for value at every level of an organisation: company, departments, teams and people. See who delivers what to whom, what recipients actually received, and where value is lost at the seams. Then change processes, meetings and timing so more of it gets through.

  • End-to-end encrypted wallets
  • No people rankings
  • Cloud (EU) or on-premise
Value flows between departmentsIllustrative diagram: six departments connected by value flows around the company goals. One seam, between Sales and Legal, shows a loss.

value flowloss at a seamIllustrative example

The problem

Work crosses departments. Value gets lost at the seams.

IT works for sales. Finance works for everyone. HR works for managers. Yet each department measures itself from the inside: tasks, KPIs, budget. Nobody sees what the recipient actually got.

Invisible seams

Handoffs between departments have no owner and no measure. Expectations drift, and nobody notices until it hurts.

Effort without value

Teams are busy and reports are full. Recipients still say they did not get what they needed.

Priorities by escalation

Without a shared view of value, priorities go to whoever is loudest. Approvals multiply. Meetings grow.

How it works

Every department and every person is a Value Transformer.

In Value Management terms, a department takes in value elements, transforms them and passes them on. So does every employee. They act in linked value systems: the company, the department, the team. EVC keeps the accounts on every level and links them through flows and goals.

  • Value elements of different types. A result, a decision, information, knowledge, help, a service, access, a risk removed.
  • Anti-value. Delay, rework, an incident, a needless meeting, a broken promise. Recorded by whoever received it and visible to the source.
  • Costs. Time, money and resources, meetings included.
PlannedWhat the giver or the recipient expects.
RealizedWhat the recipient says they received.
RetrospectiveThe real impact, assessed later.

Product

One workspace. Eight modules.

Each module is useful on its own. Together they close the loop from data to decisions.

Value Wallets

Each department keeps a wallet of value given and received. A department can also turn on work wallets for its employees. End-to-end encrypted: the server and the administrator cannot read the content.

Value Stream Schemas

Draw how value moves between departments. Nodes are Value Transformers, links are flows. Analytics sit on top: line width and colour show value and losses.

Collaborative Value Estimation

Teams estimate value and cost together. Blind mode, reveal, median and spread. The result becomes the plan for a department or a flow.

Value Stream Analytics

A map of seams between departments. Plan vs fact, net value, response time, share of rated handoffs, and where value is lost.

Goals and Alignment

Goals for the company, departments, teams and employees, linked with a share of support. The alignment map shows goals without support and work without a goal.

Improvement Loop

Turn a signal into a tested change: hypothesis, estimate, experiment, before and after, decision. A change log keeps the results.

Meetings as value events

A meeting is an event with participants and cost. One-click anonymous reactions show value per meeting hour.

Coming soon

BPMN import

Already have processes in BPMN 2.0? Get a draft of departments, flows and value systems. A person confirms every flow.

Value Stream Analytics

Find where value is lost between departments.

One screen with focus: a system, a department or a flow, plus a period. A mini map, three numbers, an event feed. Details on demand.

  • Seam map. Where value flows and where most of it is lost.
  • Flow view. Plan vs fact, net value, cost, response time, share rated.
  • Period to period. Changed a flow? See whether it got better.
  • Actions. Ask recipients for ratings, assign a Flow Owner, start an estimation.

Contribution

Real contribution. No leaderboards.

EVC shows the real contribution of each team and each person to the common result, as assessed by the people who received the work. It never ranks people.

Why so strict? When contribution becomes a ranking, people start managing numbers instead of value. They record what looks good and hide anti-value. Honest data is the condition for EVC to work at all.

What EVC does

  • Contribution is the recipient's assessment, not a self-report and not a manager's formula.
  • The employee sees their summary first, three working days before the manager, and can comment.
  • Any rating can be disputed: a comment or a request to re-rate.

What EVC never does

  • No leaderboards, no places, no top 10, no side-by-side comparison of people.
  • No numbers without enough data. Below the minimum it says: not enough data.
  • AI never scores people. It only suggests events.
  • No export of contribution to HR or pay systems by default.

Goals and alignment

Ask the questions that align work with goals.

EVC asks at the right moment: at the start of a period, after a retrospective, when analytics see a signal. Alignment works both ways: signals from below can change goals and weights above.

01Employee

  • Who receives the result of your work, and how will they know they got value?
  • What part of your work is not linked to any goal? Does anyone need it?
  • Which meetings give you value, and which do not?

02Department

  • Who are our recipients, and what do they value right now?
  • Which of our flows create anti-value, and for whom?
  • Where do we wait for other departments, and where do they wait for us?

03Company

  • Which departments are weakly linked to company goals?
  • Where is value lost between departments?
  • Do goal weights match where the money and time actually go?

Improvement loop

The main driver of process improvement.

Outcomes, meetings, timing, handoffs: everything that affects how value is delivered gets better one tested change at a time.

  1. SignalAnalytics or a goal question shows a problem: loss, anti-value, a costly meeting.
  2. HypothesisWhat we change, the expected value, the cost of the change, the check date.
  3. EstimateIf there are several options, the team estimates them together and picks one.
  4. ExperimentThe change is marked on the flow, practice or meeting.
  5. Before / afterRealized value, losses, response time and cost over equal periods.
  6. DecisionKeep, adjust or roll back. The change log keeps the result.

Roles

Roles are ownership, not job titles.

A role is assigned to an object in the model: a department, a value system, a flow, a practice or a domain. One person can hold several roles. Permissions follow role and object.

Department or team

Value Transformer Owner

Runs the department wallet, its goals and value system. Appoints representatives, starts estimations, sees incoming and outgoing flows.

Value system

Value System Owner

Sets goals and weights of the system, its departments and flows. Owns the system schema and closes the period.

Flow between departments

Flow Owner

Owns a seam. Analyses losses, requests ratings from recipients, proposes changes, reviews plan vs fact.

Shared practice

Practice Owner

Looks after a practice used by several departments, such as code review or hiring, and its effect on value.

Quality domain

Domain Owner

Owns a quality context such as security or continuity. Tracks events of the domain, including anti-value.

Tenant or value system

Value Master

Keeps the method healthy: setup, training, templates. Flags goals without contribution and costs without ratings.

Deployment

Cloud or on-premise. Same product.

One codebase, one build, two configurations.

Cloud (EU)

Run by Behind Software Group in the EU. Start in days.

  • Continuous updates
  • Tenant isolation, daily backups
  • Email with 2FA, SSO on Enterprise

On-premise

Runs in your infrastructure. We do not see or process your data.

  • Docker Compose, Helm, offline bundle
  • Your SSO: OIDC, SAML, LDAP or AD
  • Works without internet access

Compare in detail

Pricing

Pricing on request.

Every organisation is different. We size the offer to your structure, deployment and rollout.

Cloud subscription

On request

Monthly or annual. Plans grow from one value system to the whole organisation, with SSO and service levels for Enterprise.

On-premise licence

On request

A term subscription with updates and support. A signed licence file that works offline.

Implementation

On request

Workshops on your structure and goals, BPMN import when available, role training, the first period report. By us or a certified partner.

Observers and people who only rate what they received do not need a paid seat.

Request pricing

For coaches and consultants

Help organisations improve. Show the value of it.

Our partner program gives business coaches and process consultants training, certification and a tool that makes their results measurable.

Become a partner

FAQ

Questions we often hear

Is EVC a performance rating tool?

No. EVC shows contribution as assessed by the people who received the work, in the context of goals. There are no leaderboards, no places and no side-by-side comparison of people. EVC does not make HR decisions and does not send contribution data to HR or pay systems by default.

What counts as an enterprise?

Any organisation with its own departments: a company, a holding, a government department, a municipality as an organisation, an NGO. The word Enterprise marks a commercial, paid product.

Who can read the content of wallets?

Only the members of the department and the people it chooses. Wallets are end-to-end encrypted. The server and the tenant administrator cannot read them. Company analytics are built from period summaries that the department owner publishes explicitly.

Can we run EVC on our own servers?

Yes. The on-premise version is the same product. It runs on a single server with Docker Compose, on Kubernetes with Helm, or in a closed network from an offline bundle.

Do we have to model the whole organisation first?

No. A typical start is one department and two departments that receive its work, over two periods. You extend from there.

Can we export our data?

Yes, at any time, in open formats (JSON and CSV). An expired licence never locks your data.

How is pricing set?

Pricing is on request. It depends on deployment (cloud or on-premise), the size of your structure and the implementation support you need.

Request a demo

See EVC on your own structure.

Tell us about your organisation. We will show EVC on an example close to yours and suggest a pilot: one department, two recipient departments, two periods.

  • A 45-minute call with a walkthrough on a generic example.
  • Cloud (EU) or on-premise, your choice.
  • Pricing on request, sized to your structure.

We use these details only to reply to you. See the privacy notice.