Why I Built WebAfro

WebAfro didn't start because I woke up one morning and decided I wanted to start an agency. It came from years of building things, working with different businesses, learning different technologies, making mistakes, shipping products and slowly becoming more certain about the kind of work I actually wanted to do.

I'm a software engineer from Cape Town. My route into technology wasn't particularly traditional. I didn't spend years at university studying computer science before entering the industry. I learned by building, going through bootcamps, working with different languages, taking on real projects and spending a lot of time figuring things out for myself.

That experience shaped how I think about software. I don't see engineering as an exercise in using the newest framework or making something look complicated. I see it as taking a real problem and building something reliable enough that someone can actually use it to move their business forward.

The long way around

My path through software wasn't straight. I worked with Ruby on Rails, Python, C#, JavaScript and eventually TypeScript. I worked across frontend and backend systems, mobile applications, APIs, databases and eCommerce.

At different points I thought I was simply jumping around. Looking back, those years were useful because every environment forced me to think differently. Rails taught me the value of good conventions. Python reinforced the importance of readable code. C# showed me how useful strong typing and structure can be. JavaScript eventually opened the door to building across the entire product.

Eventually TypeScript, React, Node and the wider JavaScript ecosystem became the environment where everything started making sense together. I could work on the interface, the API, the data layer and eventually mobile without constantly changing the way I thought about the product.

Then came real production work

Working on eCommerce projects changed my standards considerably. When you're working on a storefront that real customers depend on, software stops being a portfolio piece. Performance matters. Checkout matters. Reliability matters. A small mistake can affect someone's ability to buy something.

I've had the opportunity to work on storefronts and digital products connected to serious brands. That experience showed me what happens when engineering quality, design and business requirements have to work together instead of existing as separate conversations.

It also made me notice something closer to home.

The gap I kept seeing

There are a lot of businesses in South Africa doing genuinely good work. Founders are building brands. Small companies are growing. Agencies are winning clients. People are selling products, services and ideas every day.

But when those businesses need technology, the options can feel strangely limited. Build something cheap and accept that it may be difficult to maintain. Buy an off-the-shelf solution that doesn't quite fit. Or spend a lot of money with a large team that may not really understand the business.

I don't think those should be the only choices.

Good software shouldn't depend on your postcode.

What WebAfro is actually trying to do

WebAfro is my attempt to build a different kind of engineering partner. Not an agency that throws around technology terms and disappears after launch. Not a freelancer who simply waits for a ticket. And not a company that believes every business needs a giant custom platform.

The goal is much simpler: understand the business, understand the problem, then build the right thing.

• Build to a professional standard without making the project unnecessarily complicated.
• Use technology because it solves a problem, not because it looks impressive in a proposal.
• Be honest when something doesn't need to be built.
• Make software that the business can actually maintain and grow.
• Bring the same engineering discipline expected on serious global projects to businesses closer to home.

Why the name WebAfro

The name is deliberate. Africa isn't a limitation on the kind of software we can build. It's the environment I understand, the market I'm close to and the place where I want to create more value.

That doesn't mean every project has to be African or that WebAfro only works with African businesses. It means the starting point is here. The ambition doesn't have to stop here.

This is still being built

WebAfro is not some finished company with a ten-year master plan sitting in a drawer. I'm building it while continuing to learn, work and ship.

That's actually part of the point. I want the company to stay close to the work. Close to the code, the products, the businesses and the people using what we build.

If you're building a business and need someone who can think about the product as well as the engineering, that's where I think WebAfro can be useful.