Storylab.

For HR and L&D leaders

You are buying a development programme you can defend in a budget review.

Two things get soft-skills tools cancelled: nobody used it, and nobody could prove it did anything. Cohort pricing fixes the first by changing the denominator. The measurement layer fixes the second by reporting completion of behaviour, not minutes of attention.

Book a security walkthrough

Read this part before you pitch it internally.

You will not be able to read what your people write, and there is no tier, role or export that changes that. It is worth understanding why before you present this: roughly half the workforce assumes a tool like this reports back to HR, and the product only produces anything honest if that assumption is provably false. The guarantee is the asset. Selling it as visibility would destroy the thing you are buying.

Security

What your security team will ask on the first call.

Answers, not a trust-centre landing page. A full architecture document and pen-test summary are available under NDA before you sign anything.

Identity
SAML 2.0 and OIDC single sign-on via Okta, Entra ID or Google Workspace. SCIM 2.0 for provisioning and — more importantly — deprovisioning on the same day someone leaves.
Encryption
TLS 1.3 in transit. AES-256 at rest, with session content held under a separate key from account and billing data so an admin-side compromise does not reach it.
Access
Four roles: learner, cohort lead, admin, owner. None of them can read session content. Every admin action is written to an append-only audit log you can export.
Residency
EU (Frankfurt), UK (London) or South Africa (Cape Town). Chosen at contract, not migrated later.
Retention
Session content is retained while the account is active and deleted 30 days after closure. Aggregates recompute without the deleted person rather than keeping a shadow copy.
Subprocessors
A short published list with 30 days' notice of any change. Model inference runs under a zero-retention agreement — nothing your people say is used to train anything.

POPIA

Aligned

SA operator agreement available

GDPR

Aligned

DPA with SCCs, DPIA template

SOC 2 Type II

In progress

Observation window closes Q1 2027

ISO 27001

Planned

Following SOC 2

The business case

Three defensible claims, and one we will not make.

Behaviour completed, not content consumed

Rung-three completion means somebody had a conversation they would not otherwise have had. That is an observable change in how a person works, and it is the strongest thing any development tool can report.

Movement on a standard instrument

A pre/post self-report across awareness, storytelling and reframing — the format L&D teams already benchmark against, so it sits inside the reporting you have rather than beside it.

Retention of the programme itself

Return after a fourteen-day gap, which is the only engagement figure worth quoting. It measures whether people came back after they stopped, not whether they opened it yesterday.

The claim we will not make

We will not attribute a change in your attrition, engagement score or productivity to twelve weeks of reflection. Anyone selling you that attribution is selling you a correlation with your own headcount trend, and it will not survive the second year.

Rollout

Twelve weeks, one cohort, one meeting in the middle.

  1. Week 0

    Scope one cohort

    Pick a real team of 24–40 with a manager who wants it, not a volunteer sample scattered across five departments. Set the data agreement and residency.

  2. Week 1

    Cohort lead onboarding

    Ninety minutes with the person whose name is on it. They need to be able to answer “can my manager read this” without hedging, because they will be asked in week one.

  3. Weeks 1–12

    The programme runs

    People talk to the coach when it suits them. You watch completion by rung climb in the admin view. Nobody is chased, and no reminder is ever framed as a debt.

  4. Week 6

    Halfway read

    The one meeting that matters. If rung-three completion is under forty percent we diagnose it now — usually pace, sometimes the cohort composition.

  5. Week 12

    Completion report

    Pre/post skill movement, completion by rung, and return-after-gap. Written so you can put it in front of a CFO without translating it first.

Bring your security lead to the first call.

  • Architecture and data-flow walkthrough
  • Draft DPA and subprocessor list
  • A live look at exactly what an admin can and cannot see
Book a walkthrough