Customer Stories
Stories, as they become publishable.
No customer or deployment story is published yet. This page says why, what a story will contain when one is, and how one gets approved — so that when a story does appear here, you can believe it.
People.Partnerships.Progress.
A story is published only with written permission to name, an approved description, and a named contact who confirms it. Nothing here will ever be a composite.
- None published yetAnd the page says so
- What a story will containThe challenge, the decisions, the measure, the misses
- How one gets approvedPermission, description, a named contact
- BharatSamarthThe first white-label deployment, in development
Why this page is empty
A story has to be earned before it is told.
Zynaut keeps a register of what this site may claim, and every kind of proof on it — named customers, anonymised deployments, testimonials, measured outcomes — currently stands as unavailable. That is not a gap in the marketing. It is the rule working.
A customer story is published here only when three things exist: written permission to name the organisation, a description of the work that the organisation has approved, and a named contact at that organisation who confirms it. Until then there is nothing to show, so nothing is shown.
No composite stories, no anonymised examples and no invented quotes stand in for the real thing. The illustrative journeys further down are labelled as illustrative.
What a story will contain
Four things, every time.
A story that carries only the first two is an advertisement. All four, or it is not published.
The challenge
What the organisation was trying to do, in its own words, and why the systems it already had did not do it.
The design decisions
What was deployed and what was left out; which decisions belonged to the deployment, and which to the design.
What was measured, and how
The baseline, the period, the method and who verified it. A number without those four is not published.
What did not work
What the deployment got wrong, what was changed, and what remains open.
The first deployment
BharatSamarth — in development.
The version of Pathways being built for India, under its own name: the same record and the same rules about who can and cannot see it, with only the Indian qualification frameworks, issuer registries and scheme integrations belonging to it rather than to Pathways itself. This site once listed it as an offering in its own right; it is one branded instance of the flagship.
Status: In development — Active implementation exists. General availability is not claimed. An implementation exists for this market and is being built against. General availability is not claimed for it, and its progress does not imply the platform's.
There is no BharatSamarth story yet, for the same reason there is no other: the deployment is being built, nothing has been measured, and nothing is published before it is.
Illustrative journeys
What a deployment is for.
Three journeys the design is built around — from the side of a school, a programme and an employer. Illustrative, not reported.
A school's programme coordinator
Sees where a cohort stands as an aggregate, and what the programme built against what it set out to build. Never any one student without that student's permission — and never another school's learners.
A government programme officer
Sponsors a population and sees it as an aggregate built for scrutiny: what was known, what was assumed, and why a conclusion followed. No league table, and no route to an individual.
A hiring manager at an enterprise
Receives what a person chose to send, with each claim traced to its evidence and how strongly it is supported. Comparing candidates stays her judgement — no search, no ranking, no score.
Illustrative journeys, written to show what the design is for. Zynaut Pathways is in development and no customer story, testimonial or measured outcome is published yet.
