Skip to main content
PKB Solutions logo

Working with us

Start with a scoped conversation

Tell us the outcome you are chasing and we will map it to a realistic first phase.

Contact the team
PKB Solutions logo
Home

Company

About PKB Solutions

We measure the technology experience of people at work, and we are unusually careful about what that measurement can and cannot claim.

Abstract network composition representing connected people and technology across an organisation.
Photography slot reserved for a team collaborating in a bright modern office
Photography slot reserved for two colleagues reviewing work at a laptop

Who we are

We build the evidence layer for the digital workplace

Enterprise IT has never had more monitoring and never had less certainty about what work actually feels like. Dashboards are green, tickets are closed, and people are still losing an hour a week to a machine nobody has measured properly.

PKB Solutions exists to close that gap. We measure devices, applications, sessions and networks from the side the employee sits on, turn that into a score somebody can defend in a steering committee, and then help teams act on it and confirm the action worked.

Experience first Measured from the endpoint, not inferred from the datacentre.
Evidence, not assertion Every score decomposes into the measurements behind it.
Never surveillance No content, keystrokes or individual productivity scoring.
Photography slot reserved for a wide editorial view of a working office environment

What we are actually claiming

A measurement company, not a productivity company

Those two things use similar language and very different data. We collect operational state — how the technology behaved — and deliberately do not collect what a person was doing with it. That boundary is the reason a workforce will tolerate being measured at all.

How we work

Four positions we will not trade away

These shape the product and occasionally cost us deals. We would rather state them here than discover the disagreement in month six.

We do not publish numbers we cannot support

No invented customers, testimonials, statistics or awards. Where a figure would normally sit and we do not have a verified one, you will see a placeholder instead of a plausible number.

We show the method, not just the result

Every score decomposes into components, weights, thresholds and the population it was calculated over. A number nobody can interrogate stops being reported within a year.

Measurement is not monitoring

The platform cannot produce an individual productivity score, because the data required to do so is never collected. This is a capability boundary, not a configuration setting.

We will tell you when we are the wrong fit

Several of our solution pages include a section on when not to run the programme. If measurement is not your binding constraint, more measurement will not help.

Working together

What the first ninety days look like

Deliberately unglamorous. Most of the value in the first quarter comes from having a baseline nobody argues with, not from a feature.

A scoped conversation, not a pitch

We ask what you are trying to change and who would own it. If the answer is unclear, that is the finding, and it is worth more than a demo.

Data scope agreed before deployment

Security, privacy and works council review happen first. Collection scope is configured to what was agreed, not to the maximum available.

Baseline through a full business cycle

Including a month-end and a patch cycle. We resist acting on week-one anomalies, and we ask you to as well.

One improvement, honestly reported

A single friction source with a named owner, fixed and re-measured. Reported either way — including when the intervention did not move the number.

Layered diagram of the collect, correlate, analyse and act model.

Why we insist on the baseline

Without a stable reference point, every subsequent claim is unfalsifiable — including ours. A baseline is the only thing that lets you hold a vendor to an outcome.

Bring us a problem, not a procurement form

The most useful first conversation is about something specific that is costing you time and that you currently cannot explain.