
Platform · marketplace
AfroFind
Hard part: Listings, providers, events, and trust cannot each be a separate product.
Outcome: A live UK discovery platform with one shared object model for businesses, bookings, and reputation.
View project
WezDev
Software engineer · Manchester
I help founders and teams design and ship multi-sided products, payment-heavy systems, and cloud-native backends — then keep them observable when real users show up.
Proof
Start with the platforms. AfroFind and MOMO Lens are the clearest signal. Gravity Fall shows the same delivery bar on a full product build.

Platform · marketplace
Hard part: Listings, providers, events, and trust cannot each be a separate product.
Outcome: A live UK discovery platform with one shared object model for businesses, bookings, and reputation.
View project
SaaS · payments
Hard part: Mobile-money flows differ by country, and merchants need a ledger that survives bad networks.
Outcome: Production React Native and NestJS stack with reconciliation, sales, and reporting in select markets.
View project
Game · 3D parkour
Hard part: Browser parkour needs honest physics, portal SDKs, and size budgets that still feel distinct.
Outcome: A 3D Babylon.js + Havok climb across four worlds, live in QA and under CrazyGames review.
View projectWhat you hire
The same themes as the rest of the site — platforms, cloud delivery, web and mobile, production. That is the engagement shape.

01
Different actors, different permissions, one product. AfroFind lists UK African and Caribbean businesses for the people trying to find them. MOMO Lens handles sales, mobile money, and reconciliation for merchants.

02
Serverless backends on AWS: Lambda, API Gateway, DynamoDB, SQS. Defined in Terraform and CDK, with the IAM, networking, and ops work that has to be right before anything goes live.

03
React, Next.js, and React Native when the product spans web and mobile. Inventory, POS, and reconciliation on a phone that does not assume fast data or a flagship device.

04
Cypress and CI before code reaches production. Dynatrace, CloudWatch, and CloudTrail when something pages. Dashboards and internal tools so one incident does not mean five tabs and a guessing game.
Fit
Process
01
Send a short brief on Get started — what you are building, constraints, and timing.
02
We talk about the real risks: data model, permissions, payments, infrastructure, and delivery.
03
Agree scope, stack, and what “done” means for the first useful slice.
04
Ship in production-minded increments with the same bar as AfroFind and MOMO Lens.
FAQ
More context on WezDev is on the about page.
Next
Tell me what has to work in production. I will tell you whether I am the right engineer for it.
Your privacy
We use essential cookies for theme and consent. With your permission, analytics shows which pages and projects people explore so the site can improve. You can change this anytime.