About Obosu
Obosu is about moving forward.
Obosu is a technology and solutions company focused on improving how organisations work. We look at real problems, understand the processes behind them, and build practical digital solutions that make work simpler, clearer and more efficient.
The name Obosu means “ahead.” It reflects the idea at the heart of what we do: progress through practical improvement. Technology is not the objective. It is one of the tools we use to help organisations move forward.
We understand, design and build, turning everyday operational challenges into solutions that work in the real world.
What we do
The technology is not the objective. The improvement is.
We look at existing problems and processes, understand what makes them difficult, slow or inefficient, and explore how they can be improved.
At Obosu, we use digital solutions to make work simpler, clearer and more efficient.
The projects across this portfolio show how that thinking is applied to different problems and environments.
See the projectsAbout me
I’m Sandro Abomo, the owner of Obosu.
A background in finance
My background is in finance, where working closely with processes, data and day-to-day operations gave me an interest in how things could be done better.
From ideas to working software
That interest gradually developed into building solutions myself. Today, I can take an idea or a problem, work through how it should function, design the experience, and build it into a working software product. There is still plenty for me to learn, and that is part of what keeps me interested in this field.
Where it comes together
Obosu is where I bring that experience, curiosity and passion for creating solutions together.
How the work runs
Five stages, in this order, every time.
01
Understand the problem
What is going wrong now, who it happens to, and what it costs them. Written down plainly enough that you can correct it if it is wrong.
02
Improve the process
Before anything is built, the process itself gets looked at. Software that automates a bad process makes it faster and harder to see.
03
Agree what success means
Measurable outcomes with a threshold attached, so there is a way to tell later whether the thing worked rather than whether it shipped.
04
Build one complete slice
One real thing, end to end, deployed and tested, before anything is built widely. It is the fastest way to find out that an assumption was wrong while it is still cheap.
05
Prove it, then extend
Automated tests, accessibility checks and performance budgets run on every change, each completed item points at the evidence for it.
Technology
Modern tools for real problems.
Chosen per project against the problem. Nothing appears here because it is new or in fashion.
