Selected work
Systems we built, and still run
Work we have delivered for clients, and the systems we built for ourselves and still run. The second is a large part of why the first is any good.
Clients
Who we have built for
MTN Cameroon
Client and partner30%
improvement in sales
The problem
Demand existed for MTN’s digital products, domain names, cloud services and the rest, and too little of it was converting into sales.
What we built
A system to accelerate sales and conversion across that product range. We built it and we run it.
The result
Sales improved by 30 percent. We are also MTN’s partner on the first corporate venture studio in Cameroon.
UNDP
United Nations Development ProgrammeOSSP
A national entrepreneurship platform · ossp.cm
The problem
A national entrepreneurship programme run across three institutions, with training, coaching and mentoring that had no single place to happen.
What we built
OSSP, the platform the whole programme runs on. Entrepreneurs, mentors and coaches all work inside it, and training and coaching are delivered through it.
Who it serves
UNDP, in partnership with Cameroon’s Ministry of Economy and Planning and BADEA, the Arab Bank for Economic Development in Africa.
Both names are published with permission. A third slot sits empty here on purpose, for the next client who agrees to be named.
Booking, messaging and payments
One system instead of four tools
Rvamply
The three systems in one place. A customer finds the business, books, pays, and gets asked back, and the owner never opens a second application.
It is not an operations tool, it is a revenue tool, and we sell it on revenue. The pitch to an owner is not a feature list. It is that one recovered no-show a week pays for the month.
North America
Beauty businesses. The system replaces a booking tool, a marketing stack and, increasingly, the person who answers the phone.
The maths is simple for an owner. One recovered no-show a week pays for the month.
Cameroon
Startups inside an incubation and acceleration programme, with the programme paying for the cohort rather than each company buying alone.
One agreement equips everybody at once, which is the only model that works at this price in this market.
Two markets with almost nothing in common, running on the same system. That is how we know it is not a local accident.
Mobile money collection
The payment rail
RvPay
We built a payment rail because we could not get paid.
The platform was built on card payments. Cards are not how Cameroon pays, and the standard processors do not operate here. Our own customers could not pay us.
So we built the thing that was missing rather than asking customers to work around it. It collects by mobile money and is live today.
- 2operators live today: MTN MoMo and Orange Money
- 18+markets reachable through the infrastructure it runs on
- 1integration, rather than one per operator per country
If you are building in this region and payments are the part nobody has solved, this is the conversation we are best at having.
Engineering capacity
A pod inside a German team
We run a standing arrangement with SoftXCloud GmbH in Germany, supplying engineers and teams as a pod rather than as individual contractors.
A named team, a defined period, our standards, and a timezone that overlaps the whole European working day. This is the shape the capacity work takes when it goes well.
Why we run our own
A supplier who ships late loses a client. We lose revenue.
Running these systems changes what we recommend. We have supported software at two in the morning, argued with an operator about a failed collection, and refunded a customer for our own mistake.
It is also why we will tell you not to build something. A supplier paid by the hour has no reason to say that sentence.
Want the same team on yours?
The engineers behind these are the ones who would be on your project. If one of these systems already solves your problem, we will say so on the call rather than quote you to rebuild it.