About
Web Project Studios is one person: Arek Adeoye.
Not an agency. When you work with Web Project Studios, you work with me. I've spent 25 years building and fixing the .NET and Azure systems businesses actually run on, around 10 of them leading the teams that build them, much of it in regulated domains where the audit trail matters as much as the feature. The practice is narrow on purpose: one failure mode, and how expensive it gets when nobody is looking for it.
At a glance
- Experience
- 25 years in .NET and Azure
- Leading teams
- Around 10 of those years
- Aon
- Led delivery of a greenfield insurance reserving product and grew the team from 3 to 23
- Wilmington plc
- Head of Web Development for 11 years, including the group's GDPR compliance work
- Domains
- Mostly regulated, where the audit trail matters
- Working hours
- Remote, covering UK and EU hours
- linkedin.com/in/arekadeoye
- Company
- Web Project Studios Limited
- Company no.
- 06690567, registered in England and Wales
Why I do this
The failures that hurt are almost never the loud ones.
A loud failure gets fixed the same day. Something throws, someone gets paged, the dashboard turns red, and within an hour there are three people on a call. That system works. It has worked for decades.
The one that costs real money is the process that reports success and does nothing. It doesn't throw, so nothing pages. The dashboard stays green, because green only ever meant 'no errors were raised', which is not the same claim as 'the work happened'. Nobody is misreading the signal. The signal was never being measured.
I found this the way most people find it, which is late. Running automations of my own, I went looking for why a number seemed wrong and found a job that had been reporting success for weeks without executing once. It is a seam problem, not a carelessness problem: two systems either side of a handover, each assuming the other did the work, and no assertion anywhere that it had.
So that is what this practice does. Check whether the thing ran. Check whether it produced anything. Tell you plainly which processes are exposed and which are fine. In a business with filing obligations, that gap is the difference between an inconvenience and a breach.
Working with me
What one person means in practice.
- 01
You deal with me.
The person on the first call is the person who does the checking and writes the findings. Nothing is handed to a junior.
- 02
I read, I don't change.
I can look, not change. Access is removed at the end, and nothing in your live systems is touched.
- 03
You get it in writing.
Plain findings, ranked by risk. If nothing is wrong, the report says so, in writing.
Start with the audit
Want me to look at yours?
Tell me which process you'd least like to have quietly stopped. If you can't say how you'd find out, that's the one to check first.