I Don't Want WebAfro to Become Another Agency

There are already plenty of agencies.

They build websites. They run campaigns. They redesign brands. They sell packages. Some are excellent. Some aren't. I don't see much value in creating another version of the same thing.

So I'm quite intentional about what I don't want WebAfro to become.

I don't want to sell technology for the sake of selling technology

If a business needs a simple website, let's build a simple website.

If Shopify is the right answer, use Shopify. If WordPress is enough, use WordPress. If the problem genuinely requires a custom application, then build the application.

Being able to build complicated systems doesn't mean every client should get one.

I want to stay close to the work

One reason I enjoy software engineering is that there is a direct relationship between the problem and the thing you build.

You can sit with the problem, write the code, see the result, test it, change it and eventually watch someone use it.

I don't want to move so far away from that process that WebAfro becomes mostly meetings about meetings.

The business matters as much as the code

At the same time, engineering for engineering's sake isn't useful either.

A business doesn't come to WebAfro because it wants TypeScript. It wants more customers, a better buying experience, less manual work, a stronger presence online or a product that allows it to do something it couldn't do before.

The technology is how we get there.

Clients don't need more software. They need better outcomes.

Small team, serious work

There is also something I like about staying relatively close to the work: accountability.

When there aren't layers of people between the person building the system and the person using it, feedback travels faster.

That makes it easier to understand what is actually happening, fix problems and make better decisions.

What I want WebAfro to become

I want WebAfro to become a trusted engineering partner for businesses that are serious about what they're building.

Sometimes that might mean a storefront. Sometimes a mobile app. Sometimes an internal platform. Sometimes a messy existing system that needs to be understood and improved.

The common thread is not the technology.

It's the work.