Your team is doing work that shouldn’t exist.
I join your team and fix the small daily problems nobody has time for.
It’s not the big stuff.
It’s the little things.
- The things that take 30 minutes instead of 30 seconds.
- The things that require five tabs, two spreadsheets and lots of copy-and-paste.
- The things someone does every Friday because nobody has ever had time to fix them.
Most of these problems are too small for a consulting project.
So they survive.
And they multiply.
Marginal Wins exists to get rid of them.
What the little things cost
What happens
- I join your team
- I find the small problems
- And build fixes, fast
There is no discovery phase that ends with a 60-page recommendation.
No six-month roadmap before anyone touches the problem.
Not one revolutionary breakthrough.
Hundreds of small improvements.
That is the idea behind Marginal Wins.
When Dave Brailsford took over British Cycling, the team started looking for tiny improvements everywhere.
- Better nutrition.
- Better sleep.
- Better training.
- Better equipment.
- Better recovery.
The idea became known as the aggregation of marginal gains: improve enough small things, and the combined effect becomes significant.
Hi, I’m Ronnie.
I’m a software developer with a first-class degree in computer science. For the past two years I’ve built software for clients across a range of industries, and I co-founded an AI company.
Marginal Wins is just me.
- I’m the person who you speak to.
- I’m the person who meets your team.
- I’m the person who saves you time.
Before you get in touch
What kind of problems do you fix?
The small, repetitive stuff that slows people down. Copying data between systems, reports that take an hour to put together, emails that get written the same way every week, spreadsheets held together with manual work. Things everyone knows are annoying but nobody has time to sort out.
How is this different from hiring a developer or an agency?
Agencies usually start with one big project and spend weeks scoping it. I start by sitting with your team, finding what gets in their way, and fixing it the same day where I can. Lots of small fixes, delivered quickly, rather than one big one delivered slowly.
How long does it take?
Roughly one working day per person on your team, plus a short setup period at the start. We agree the exact number of days before I begin.
How much does it cost?
A fixed day rate for an agreed number of days. You know the full cost before I start, with no surprises.
Do you need access to our systems?
Only what’s needed for each fix, and only with your approval.
Is it safe to use AI with our data?
I tell you exactly which tools I’m using and what data goes into them before I build anything. If something shouldn’t leave your systems, I find a way to build it that keeps it there.
Who owns what gets built?
You do. Everything I build belongs to your company.
What happens when you finish?
You keep everything, and it keeps working without me. I build on the tools you already use wherever I can, so there’s nothing new for your team to learn. Every fix comes with a plain guide for the people who use it, and notes for whoever looks after it, written so someone other than me can maintain it.
Let’s cross the first one off.
Book a 20-minute call and tell me the bit your team hates doing.
Calendar not loading? Open it on Cal.com.