Home / About / Client Outcomes

Client outcomes

Operating results, not product deliveries

A platform installed is not an outcome. What follows is what actually changes in the running of the business — what a training record looks like at the end of a cycle, what an auditor receives, and which indicators become trendable data. Client names and client-specific percentages are not published here; the substance is.

Request a reference conversation → How we engage

0E-learning courses delivered for corporations and government departments

0Off-the-shelf courses available in the Cyberwisdom Academy catalogue

0Enterprise learning heritage, operating since 1999

0Countries and regions where programmes are delivered

On numbers and on client names. We do not publish named client testimonials or client-specific outcome percentages on this page. Baselines, measurement windows and market conditions differ so much between engagements that side-by-side percentages would imply a comparability that does not exist, and a figure we cannot trace is worse than no figure. In a reference conversation we will walk you through the actual deliverables for a comparable programme, the methodology behind them, and the caveats — including engagements where the result was less than we hoped.

Where to start, and what to start with

The top-right quadrant is where engagements convert fastest and where we usually start. The bottom-left is where we tell clients to slow down and fix the policy first.

How much does the evidence already exist?↑

Start with content

The obligation is documented but the record does not exist. This is a content and configuration problem — a library course or a short build may be enough.

The usual first engagement

The obligation is documented and the record is partial. Configuration, assessment design and reporting get the programme to a defensible state — the strongest candidate for a first platform deployment.

Fix the operation first

The record exists but nobody runs it. This is an operations problem: administration, assignment rules and renewal cycles before any new content.

Not a platform question

The obligation itself is unclear or contested. This is a policy and process design exercise before it is a technology one.

How much is the obligation written down?→

What we deliver

The artefacts a client ends up holding

We usually deliver the following to a client, in the client's own repository and in the client's own formats. This is the shape of the engagement, not a showcase of individual projects.

The training record

A per-person record showing what was assigned, when it was due, what version of the content was delivered, the assessment result, the re-sit if there was one, and the credit or certification derived from it. It is the artefact that survives an audit, and it is produced as a by-product of running the programme rather than assembled for the audit.

→

What it contains

Assignment, delivery, content version, assessment score, pass threshold, re-sit, expiry and renewal — per person, per obligation, per date.

→

How it is produced

From the system of record during normal operation. No re-keying, no reconciliation, no spreadsheet rebuild the week before the review.

→

What makes it defensible

The obligation behind each assignment is documented, and the reporting names the policy version it was run under.

wizBankAudit evidencePer-person record

The audit pack

What an internal audit, a regulator or a client's own assurance function receives when it asks how the mandatory programme is performing. It is assembled from the same record, so it can be produced in the time the examiner allows.

→

Population

Who is in scope for each obligation, by role, region, scheme and licence, including populations outside the HR system.

→

Coverage and gaps

Completion, assessment performance, and the named list of people approaching expiry or already lapsed.

→

Underlying activity

The qualifying activity and the evidence attached to it, for CPD and continuing professional development schemes.

ComplianceCPDExportable reporting

The indicators that become trendable

The measures a client can run a trend on rather than a one-off snapshot. They come from the same record, so the trend does not depend on anyone maintaining a separate report.

→

Coverage and compliance rate

By population, obligation, region and cycle — so a fall is visible before the review, not after it.

→

Assessment performance

First-time pass rate, re-sit rate and assessment scores, which is where curriculum quality shows up first.

→

Expiry and renewal

Licence and certification validity tracked forward, with the renewal window opening before the lapse rather than after it.

→

Operational load

Administration hours, support queries and manual reconciliation — the cost side of the programme.

ReportingLearning analyticsTrend data

The capability left behind

The part of the engagement that outlives the contract: your team running the programme, in your systems, against your rules, with a named owner who knows what the reporting means and what an examiner will ask.

→

Written into your repository

Obligation maps, course specifications, assessment designs, reporting schedules and runbooks, in your formats.

→

Trained operators

Administrators and supervisors trained before go-live, with the training itself recorded in the system as evidence.

→

A named owner

One person in your organisation who owns the obligation, the record and the review.

TransferManaged learning servicesHandover

What we do not claim. We do not publish cost-reduction percentages, completion-rate improvements or time-saved figures attributed to named clients, because we cannot stand behind a percentage that describes a different organisation, a different baseline and a different measurement window. What we will show you in a reference conversation is the artefact itself: the record, the audit pack, the reporting schedule and the handover pack — because those are the things that have to work in your business, not ours.

What we commit to, and how you can check

Every one of these is falsifiable. If we cannot evidence it, we have not done it.

Baselines are captured before go-live. Comparisons against a baseline chosen after the result are not comparisons.
What we commit to	How it is measured	When you see it
An obligation map	Every obligation, the population it binds, the evidence an examiner expects, and the gap in each	Week 2
A configured system of record	Enrolment, assessment, certification and reporting describing the same person, with no manual reconciliation	Week 8
An assessment that proves competence	Assessment sets written against your own historical cases, reviewed by your subject experts, re-run on change	Week 8
Operators trained	Administrators and supervisors trained before go-live, with the training recorded in the system as evidence	Week 8
Evidence accepted by your risk function	The record and the reporting pack reviewed and signed off by the people who will be asked for them	Week 9
A measured baseline	Your metric, captured before go-live rather than after the result	Day 90

The evidence pack your risk and audit functions will receive

Designed in during the build, not assembled afterwards. This pack is the difference between a training programme and a folder of attendance sheets.

The obligation map — who must take what, by when, because of which rule
The population definition, including partners and contractors outside the HR system
Assignment and reminder rules as configured, with the version they were run under
Completion and assessment records, per person, per content version, per date
Credit and certification validity, with renewal windows and escalation
The reporting schedule, and the export that produces each pack
The incident and exception log for the period, with the path actually used
The handover documentation, in your repository and your formats

Reading the results

The pattern behind every engagement

Different sectors, different starting points, and the same underlying sequence. This is the sequence we run, and it is why the result holds past the first cycle.

The obligation was written before anything was bought

Who it binds, what evidence an examiner expects, and which populations sit outside the HR system. Most failed implementations skip this and buy content first.

The record was the design

Enrolment, assessment, certification and reporting were specified as one system of record, so the answer exists without a second tool.

Assessment was treated as evidence, not decoration

Where the obligation requires demonstrated competence rather than attendance, the course was built and the assessment written to test it.

Operations were stood up in parallel, not afterwards

Administration, enrolment rules, reminders and reporting schedules were live before the organisation-wide rollout, not once the launch was over.

We left, and the client kept it

Internal teams own the record, the rules and the review. Dependency was the failure mode we designed against.

The difference our clients actually buy

Delivered by everyone

A platform installed and licensed
Usage and satisfaction measured
Training as a separate line item
Value argued from a vendor benchmark
Evidence assembled when someone asks

Delivered by us

A record that describes the same person everywhere
Your metric, against a baseline captured before go-live
Assessment design and operator training inside the build
Value argued from your own historical cases
An evidence pack your risk function accepts in week nine

How an engagement actually runs

Every client gets the same shape. The content changes by industry; the discipline does not.

Diagnose

We find the workflows that are already written down as policy — because those are the only ones that can be delegated safely.

Weeks 1–2

Design

We design the operating model: who decides, who supervises, what the agent may not do, and what gets logged.

Weeks 3–4

Build

One workflow goes into production. Not a pilot that never ships — a real one, with a trace and a named human approver.

Weeks 5–7

Train

The people who will operate it are trained before go-live, and the training is recorded in the LMS as evidence.

Weeks 6–8

Measure

Ninety days later we measure against a baseline you did not choose, and scope the next workflow from what we learned.

Day 90

Start with the proposition, not the platform

Every claim on this page is a number we can evidence: 50+ delivered programmes, 300+ consultants and engineers across Asia, US$20M from Morningside and a US$30M Series B from a family office and private equity. If a number here is not useful to your decision, tell us which one and we will show you the underlying detail.

Next step

Ask to see the artefacts, not the case studies

We will show you a training record, an audit pack and a reporting schedule from a programme comparable to yours, and talk through what we would do differently in yours.

WhatsApp us Request a reference conversation → Compliance & CPD