Skip to content
Web Project StudiosFractional CTO

About

Web Project Studios was founded by Arek Adeoye.

Arek has spent 25 years building software, mostly on Microsoft .NET and Azure, and ten of those years leading the teams that build it, a lot of it in businesses where getting it wrong has a regulator attached. Through Web Project Studios he works as a fractional CTO for businesses and founders that run on their own software but have nobody senior on the technical side, remotely, for the UK, Europe and further afield.

At a glance

Experience
25 years in .NET and Azure
Leading teams
Around 10 of those years
Aon
Built the client-facing interface for an insurance reserving product and grew the team from 3 to 23
Team · 3 → 23
Wilmington plc
Head of Web Development for 12 years, including the group's GDPR compliance work
12 years
PT Workspace
Co-founder, and CTO since 2016: website, systems, booking integration, door entry
2016 → now
Domains
Mostly regulated, where the audit trail matters
Where
Remote, for the UK, Europe and further afield
Working hours
UK and European hours
Company
Web Project Studios Limited
Company no.
06690567, registered in England and Wales

Where the audit came from

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.

We found this the way most people find it, which is late. Running automations of our own, we 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 us

What that means in practice.

  1. 01

    Senior from start to finish.

    The person on the first call is the person who does the work, whether that's owning your technical decisions or writing an audit's findings, and nothing is handed to a junior.

  2. 02

    We explain, you decide.

    Every recommendation comes with what it costs, what it risks and what happens if you don't do it, written down in plain words, so the business decision stays yours.

  3. 03

    We say when the answer is no.

    If you don't need a CTO yet, or an audit isn't worth it for you, we'll tell you, and if a recommendation would lead to work we could be paid for, we'll say so up front.

Start with a call

Not sure whether you need a CTO yet?

Book thirty minutes, tell us what the business runs on and what has changed, and we'll give you an honest answer, including when the answer is no.

Book a 30-minute callHow fractional CTO works

Thirty minutes. Nothing to prepare.