Identifreed client work
Projects where Identifreed is the provider. These will be published as permissions and evidence are ready.
Some projects are Identifreed engagements. Others are work Anele led or contributed to while working inside another organisation. This page keeps that distinction visible instead of folding everything into one agency portfolio.
Book a discovery callEach project is labelled by relationship first, then by the problem, thinking, system and result.
Projects where Identifreed is the provider. These will be published as permissions and evidence are ready.
Work led or contributed to by Anele through employment, partnership or another organisation.
Useful systems work shown without exposing a client name, sensitive data or unsupported results.
Products, experiments and ideas can live here once they are ready to be shown as real work in progress.
The examples below are not presented as Identifreed client contracts unless that relationship is true.
Building the operating structure behind the work.
The organisation was growing beyond speaking, keynotes and motivational work into programmes that needed stronger client management and operational support.
The useful question was not only how to add more services, but how to make delivery repeatable enough that new work could be supported without everything staying founder-dependent.
Work included client-management structure, Connector support, repeatable processes and the systems around delivery.
A stronger operating base for managing client work and supporting additional programmes. Exact growth and retention claims remain unpublished until they can be documented precisely.
Working inside a live product system.
A software product needs changes to stay traceable, testable and safe as features move between web and mobile environments.
The work is treated as a product system: version control, QA, role behaviour and platform parity all affect whether a feature is actually ready.
GitHub version control, application testing, Android development and system-design work across the product.
A body of product-development experience that shows how systems thinking changes when the output is software rather than an internal business process.
Turning trainer knowledge into repeatable SOPs.
When coaching standards live mainly in people’s heads, consistency becomes harder to teach and maintain.
The aim was to capture how the trainers work without making the documentation heavier than the work itself.
SOP structures for trainers, organised so the process can be taught, referred to and improved.
A small but clear example of systems architecture without software: knowledge turned into a repeatable operating process.
A private multi-location dental organisation will eventually be shown through anonymised system maps, dashboards, custom SVGs and process work rather than through confidential client details.
The rule is simple: show the thinking and the system without inventing metrics or exposing work that is not ours to publish.
If the business is stuck, we can start by understanding what the current system is asking people to carry.