S0 · About Cloud23
Every ambitious organisation carries the same distance — between the strategy on the wall and the system in production. Cloud23 exists to close it.
Origin
Ambition
Destination
Reality
Scroll to run the lap ↓
S1 · Why we exist
01Strategy should become a working system.
02Technology should create measurable value.
03Transformation should not take forever.
04Accountability should not end at go-live.
05Complex organisations should still move quickly.
That is why Cloud23 exists.
S2 · Our story
From one conviction to a connected delivery engine — Cloud23, 2021 to 2026.
2021 → 20261 → 3 delivery hubs0 → 10 Salesforce awards330+ programmes today
2021
Origin
ProvisionalNo inherited network. No established route. Just a clear destination and the determination to build the track.
By 2021: 1 of 3 delivery hubs, 0 of 10 Salesforce awards, 1 milestones laid.
The conviction
Cloud23 is founded on a single conviction: world-class engineering and enterprise delivery can be built from Africa and trusted by organisations anywhere.
2022
Departure
ProvisionalThe first route goes live. Cloud23 takes on enterprise programmes and earns the trust that lets a young firm work on systems that matter.
By 2022: 1 of 3 delivery hubs, 0 of 10 Salesforce awards, 2 milestones laid.
Into the enterprise market
Cloud23 enters the South African market and takes on its first enterprise programmes — including digital onboarding work in banking.
2023
Momentum
ProvisionalDelivery centres open and teams grow multidisciplinary. The first formal recognition arrives on the line.
By 2023: 2 of 3 delivery hubs, 1 of 10 Salesforce awards, 4 milestones laid.
Delivery centres in Johannesburg and Hyderabad
Delivery capability scales with engineering centres in Johannesburg and Hyderabad, backing programmes with distributed teams.
Multidisciplinary delivery
Teams grow across strategy, experience, engineering, integration and managed operations — the beginnings of one accountable delivery model.
2024
Reach
ProvisionalProgrammes extend across African markets and managed services deepen. Recognition follows the depth of the work.
By 2024: 2 of 3 delivery hubs, 2 of 10 Salesforce awards, 6 milestones laid.
Programmes across the continent
Programmes extend across African markets — South Africa, Uganda, Ethiopia, Botswana and Mauritius among them — mostly in banking and financial services.
Managed services deepen
Cloud23 runs live platforms as a managed operation for regulated institutions, staying accountable well past go-live.
2025
Intelligence
ProvisionalTraditional engineering gains a data and AI control layer. Signals travel alongside the train; the operating model gets smarter.
By 2025: 2 of 3 delivery hubs, 6 of 10 Salesforce awards, 7 milestones laid.
Intelligence enters the engine
Data engineering and governed AI — including Agentforce — become part of how Cloud23 builds and runs platforms.
2026
Today
A Johannesburg headquarters with delivery centres in Hyderabad and Bucharest, programmes across Africa and beyond, and one team accountable from strategy to run. The track continues past the horizon.
By 2026: 3 of 3 delivery hubs, 10 of 10 Salesforce awards, 10 milestones laid.
Three delivery hubs
Cloud23 delivers from a Johannesburg headquarters with engineering delivery centres in Hyderabad and Bucharest.
One accountable engine
Strategy, experience, engineering, intelligence and operations run as one system — accountable from the first workshop to the managed run.
The track continues
The line keeps being laid — governed enterprise AI, composable platforms and African engineering at a global standard.
S3 · The system
Most firms sell you one of these and leave the seams to you. We run all five as a single drivetrain — strategy turning into design, into working software, into intelligence, into operations.
We decide what to build and why — target architecture, roadmaps, the business case.
We design the journeys and services customers actually complete.
We build and integrate the platforms — the core discipline everything else serves.
The core discipline
We turn data into decisions and governed AI that works in production.
We run, secure and continuously improve the platform once it is live.
S4 · The difference
The difference is not a methodology slide. It is who owns the outcome when the demo ends.
Traditional consulting
Cloud23
S5 · Delivery network
Johannesburg is home base; Hyderabad and Bucharest keep the engines running. The working day opens in the east and follows the sun west — so there is almost always a Cloud23 team on the clock.
Hyderabad
India · Delivery centre
--:--
—
JohannesburgHQ
South Africa · Headquarters
--:--
—
Bucharest
Romania · Delivery centre
--:--
—
Delivering into
Cape TownSouth Africa
Capitec, Betterhome
KampalaUganda
Stanbic Bank Uganda
Addis AbabaEthiopia
Awash Bank, Bank of Abyssinia
GaboroneBotswana
Standard Bank Botswana
Port LouisMauritius
Standard Bank Mauritius
DurbanSouth Africa
Cosco Shipping
LuandaAngola
Banco BCS
All delivered from the Johannesburg hub, backed by the delivery centres.
Country presence
Africa
Asia
Europe
Americas
One headquarters, two delivery centres, and operational presence in the markets where our clients run.
S6 · Continental reach
14
African countries delivered in.
We launch from Johannesburg and deliver across the continent — banks, insurers and enterprises, in the markets where the work actually lives.
18 countries and markets in total. One headquarters, two delivery centres, and operational presence in the markets where our clients run.
Headquarters1
Delivery centre2
Operational presence15
S7 · Success stories
Not slideware. Systems live in banks across the continent, doing measurable work. Outcomes as reported by the client.
Capitec Bank · Business Banking
< 5 min
to open a business account
Sub-five-minute business onboarding — complex structures handled within a day, on a fast path that stays fast because complexity is routed to its own track.
Read the storyStanbic Bank Uganda · Personal Banking
Days → minutes
account opening time
Account opening cut from days to minutes, and an account that can transact immediately — digital onboarding as financial-inclusion infrastructure, not just convenience.
Read the storyStandard Bank Botswana · Business Banking
Branch visit, removed
for business onboarding
The branch visit engineered out of business-account onboarding — every participant's trip removed, not just the primary applicant's, from the very first touchpoint.
Read the storyS8 · The people
We don’t assemble a fresh crowd of contractors for every job. The same disciplines work together, programme after programme, accountable to the same outcome. Here is what each one holds itself to.
Owns · The decisions that outlive the programme
“I write the decision down — with the trade-off and the date. If someone inherits this in three years, they should find the reasoning, not just the result.”
The standard
Architecture decision records on every programme
Owns · The system that has to run on Monday
“The demo isn't the deliverable. I'm not finished when it works on my machine — I'm finished when it survives production, monitoring, and the next person who touches it.”
The standard
Reviewed, tested, and handed over readable
Owns · Intelligence acting on data you can defend
“Anyone can make a model say something impressive. My job is making it say something true — on data with lineage, inside guardrails a regulator can read.”
The standard
Grounded, evaluated and governed before a customer meets it
Owns · The journey the customer actually completes
“I design for the person on a bad connection, mid-queue, on their third attempt. If it only works in the happy path, it doesn't work.”
The standard
Tested with real users, not just stakeholders
Owns · The honest status
“Green means green. If a date is at risk I say so the week I know, not the week it slips — the only thing worse than bad news is late bad news.”
The standard
Risks raised early, in writing
Owns · The evidence that it works
“I'm not here to find bugs at the end. I'm here so the team can change a core banking platform on a Tuesday — and sleep on Tuesday night.”
The standard
Automated coverage where the risk actually sits
Owns · The platform after go-live
“Go-live is the start of my job, not the end of someone else's. If your customers tell you the platform is down before we do, we built the wrong thing.”
The standard
Service levels defined, monitored and answered for
Owns · Whether anyone actually uses it
“A platform nobody adopts is an expensive screenshot. I work with the people whose day changes — before the change lands on them.”
The standard
Trained, supported, and measured on real usage
Role archetypes, not stock photography — leadership profiles publishing soon.
S9 · Culture
Not values on a wall. Behaviours you would see on any programme.
If we take it on, we own the result — end to end, not to the edge of our statement of work.
We say the hard thing early, internally and to you. A risk raised late is a risk we already own.
Process, governance and repeatability outperform individual brilliance — decisions recorded, gates held.
Every engineer is expected to leave the people around them better than they found them.
We earn it by doing what we said we would do, on the date we said we would do it.
Continuous improvement past go-live: if your team and your client can count on you, that becomes opportunity.
S10 · Roots & ambition
We started from a conviction that world-class engineering can be built on this continent, for the world — and proved it on the hardest programmes in African banking. The address on the door is Johannesburg. The standard is global.
S11 · What’s next
The gap keeps moving. So do we. Three places we’re putting our engineering weight next.
Agents that act on real data with real guardrails — intelligence that survives production.
Systems assembled from reusable, well-architected parts, so change stays cheap.
Scaling a delivery model that competes with anyone, from the continent outward.
Finish line
Tell us the gap you need closed. We’ll bring the strategy, the engineering and the accountability to close it.