Build · recover · govern · operate

Start with what you need the system to do.

The portfolio is now organised around solutions and working demonstrations first. Professional history and industry exposure still exist, but they support the capability story rather than becoming the opening story.

Choose a path

What are you trying to understand?

Each path answers a different buyer, recruiter or collaborator question without forcing you through an industry-by-industry biography first.

01 · Solutions

What can Mandiso build or fix?

Productised offers across legacy recovery, workflow automation, WhatsApp operations, governed AI, release assurance, digital estates and more.

Browse solutions →
02 · Interactive labs

Can I see the thinking in motion?

Exercise seven synthetic system demos covering workflow state, lead capture, AI approvals, system truth, release proof, estate operations and opportunity scoring.

Open the labs →
03 · Delivery evidence

What kinds of hard problems has he handled?

Anonymised evidence organised by problem pattern rather than client logo or company name.

Review evidence →
04 · Capability map

What disciplines sit underneath the solutions?

Architecture, integration, platforms, security, operations, modernisation, evidence and AI-enabled engineering.

Explore capabilities →
05 · Architecture

How are boundaries and trade-offs shaped?

Context, services, data ownership, identity, NFRs, decisions, migration, delivery and governance.

Open architecture →
06 · Integration

How are systems made to cooperate?

APIs, webhooks, messaging, identity, retries, idempotency, provider boundaries and audit trails.

Open integration →
07 · Modernisation

What if the system already exists?

Current-state recovery, stabilisation, controlled refactoring, API extraction and migration without a big-bang rewrite.

Open modernisation →
08 · Governed AI

How is AI used without losing control?

Human approval, bounded tools, evidence, policy, safe knowledge boundaries and release discipline.

Open AI engineering →
09 · Working method

How does Mandiso solve unclear problems?

A repeatable route from discovery and current-state truth through implementation and production proof.

See the method →
10 · Professional history

How did the capability develop?

The evidence-backed chronology from software development foundations into integration, operations and solution architecture.

Open history →
11 · Digital CV

What is the formal career record?

Roles, education, technology depth, alignment and a downloadable professional document.

Open CV →
12 · Conversation

Is there a practical fit?

Bring the workflow, inherited platform, production problem, integration or AI idea that needs to move.

Contact Mandiso →
Living evidence surface

More than a CV site.

12productised solution families
7interactive synthetic labs
18approved awareness records
1conversational evidence layer
Have a specific problem?

Ask the portfolio in the language of the problem.

Try “we have a legacy PHP application nobody understands”, “our WhatsApp orders are manual”, “we need human approval around AI”, or “we cannot prove what version is live”.