The Mission

Why We Exist.

We solve a real, complex, multi-million pound problem faced by nearly every large company. By going back to first principles, we drastically increase the probability of software and transformation programmes delivering real, tangible value.

A brief foreword from the founder on AI

William Devos

William DevosFounder

TLDR: AI is software. Software always needs good data. Ergo, we need to fix the data.

Hi, I'm William - founder of Modern Productivity. Our philosophy boils down to one belief: over the long term, fixing the underlying issues with data is the single, most valuable investment any business can make. The AI era has made that belief urgent - not theoretical - for every senior leader signing off on the next wave of spend. We have already lived through this once, and it saddens me that many organisations are about to pay a lot of money to learn it again:

I refer to the dawn of Business Intelligence tooling, which arrived to much fanfare and corporate purse-opening. However instead of using BI to expose the major flaws in corporate data estates - e.g. the absurdity of holding 38 duplicate suppliers across four different instances of SAP - it was used predominantly as an aesthetic presentation layer. Vendors charged top dollar to create beautiful, colourful dashboards that made everything look wonderful while the underlying semantic plumbing was still leaking into the basement. These manufactured chains of hidden digital spaghetti presented their own, novel problems: now understood only by a handful of reporting professionals or worse still external vendors, further increasing friction, complexity debt, and creating significant knowledge-retention risk.

The agentic era upgrades the old adage. Garbage in, garbage out becomes garbage in - incredibly expensive and authoritative-sounding garbage out. Here is my prediction of the mistakes enterprises are about to, if not already, embark upon:

  • Software and AI vendors will charge exorbitant fees to build semantic layers on overly complex, fundamentally broken core data. (It is a much easier, more lucrative sell to offer a shiny AI wrapper than a gruelling, complicated, data governance and simplification programme.)
  • Because LLM and agentic workflows charge by the token, a messy data estate effectively acts as a heavy tax. Lookups that should cost fractions of a penny against clean data run to dollars per query against redundant, inconsistent structures - a multiplier that turns tolerable pilot spend into a board-level problem at scale.
  • Responses take too long to be useful, costs will skyrocket, accuracy will be questionable, and users will lose confidence in the results.
  • Inevitably, the expense becomes too astronomical to sustain, scope is cut, and the benefits that would have been unlocked had underlying complexity been addressed will never be realised.

At Modern Productivity, we are here to directly challenge this paradigm because it violates our key principle of addressing complexity. Specifically, our challenge is this: would it not be vastly easier - and vastly more courageous - to face the elephant in the room and tackle these structural issues head-on? I would posit that the single, true, and most effective ROI for enterprise AI is not automation or generation for its own sake - but entity resolution, duplicate / anomaly detection, and targeted reasoning to locate where the data estate is weakest - so we can fix it. We need to use AI to expose complexity and radically simplify it.

Many companies will spend millions learning that the hard way. I would rather we skip that part and get straight to delivering value. If that resonates with you - drop us a line.

A Philosophy of Lasting Simplicity.

Introduction

(Firstly, a disclaimer for those who wonder - every word of this manifesto is written by a real, thinking human - apparently an increasingly rare commodity nowadays).

After nearly fourteen years inside large projects and transformation programmes - in banking, pharma, and beyond - I learned that most expensive failures are not caused by the wrong vendor or the wrong architecture. But by complexity accumulating faster than anyone is able or willing to simplify it.

When a software or transformation programme launches to much fanfare, this is often the first time key stakeholders come face to face with the hard reality of the true operational, data, and workflow complexity that occurs daily in BAU. Rather than pause and reflect, political face-saving demands that the project continue with its original objectives maintained - so the project team becomes a clean-up crew. At that point the game is already lost (delivery schedules slip, scope gets cut to protect budgets, and the rollout is half-baked and everyone involved pretends it was successful).

The reality is the estate is left just as complex as it was before - perhaps more so. Colleagues who sounded the alarm months ago (but were shut down for 'being difficult') roll their eyes, become further disenfranchised, and go back to using Excel or worse - apply for new jobs. That outcome is usually filed under cost and delay. I see something else in it: it is disrespectful. People who gave their judgment and their years to the place were ignored when it counted, and left fighting the environment instead of doing the work. The ones who can leave, leave.

I started Modern Productivity to attempt to solve this problem.

We combat complexity through continuous simplification

Complexity is corporate cancer. I say this not because it's a statement PR professionals love, nor to be unnecessarily facetious or provocative. Complexity, like cancer, spreads from the inside out - often undetected until the damage is structural. It drains resources, erodes capability, and compromises the integrity of everything built on top of it. This has to be addressed if you want a productive, cost efficient organisation in a modern world.

This is not surprising. On the surface, we feel that simplicity should be easy. It sounds simple and it's easy to conceptualise. The sad truth is that simplicity is actually extremely challenging to achieve. Human evolution wires our default settings to be predisposed to building rather than continuously reforming. I like to imagine organisations as an army of spiders, each hell-bent on spinning their own web. Convincing them to work on the same web requires leadership, incentivisation, discipline, constant monitoring, intellectual and practical rigour, high levels of collaboration and communication, and a great deal of time explaining to each spider why it matters to stick to and enforce the central nodes. Worst of all, it involves painstakingly untangling interwoven threads - many wrapped in several others that should never have been woven in the first place, and many not visible until you tug on another.

While we untangle yesterday's threads, complexity continues accumulating in BAU. Rather than pause and confront that drift, we are told the answer is another platform, another integration layer, another AI pilot - a pattern I have watched play out often enough to recognise the ending. Good-faith responses, in other words, can accidentally compound the disorder they were meant to relieve. Trying to buy your way out of complexity before understanding what (webs) you are building on is how organisations keep spending heavily to make the problem worse.

Fixing this is in itself highly complex. It requires a smorgasbord of disciplines - gravitas, charisma, and patience to name a few. That difficulty is not an excuse to look away - but rather to lean in. Complexity left to accumulate is a signal from leadership - louder than any values statement on any wall - that people's judgment and years are not worth the untangling. If an organisation claims to value its people, simplification is how that claim is honoured.

Data culture > software projects

Data is where complexity accumulates. It's not just that expertise tends to live outside of decision makers, but vendors play a large part in proliferating the issue as it suits them to do so. When I first read the data centric manifesto it was validating - thoughts I'd held privately were not only understood by others, but documented articulately and with the vigour and rigour the topic demands. Ultimately applications are transient: they are replaced, upgraded, sunset, and superseded. Data is the permanent operational record of business - the one asset that compounds in value when treated with respect, and erodes quietly noisily if not.

As business leaders, we need to stop treating data like a commodity, or even oil - but rather the high-octane rocket fuel that it could and should be. It is popular to think that AI and agents make this problem go away, but in truth they intensify this logic. When software can read, infer, and act on information at scale (indeed even while we sleep), weak data practices become sources of massive, compounding, compute, and cost error - not to mention a significant competitive disadvantage.

In my humble opinion, it's increasingly clear that what matters more than any system is whether an organisation has started the journey of embedding a genuine data culture - where employees at all levels (not just IT) are thinking strategically about how data is structured, connected, and governed. Software can assist that culture, but it cannot create it. Culture precedes tooling. If you get the culture right, the right systems follow (or more likely people realise it's the data, not the system, that's the problem). Get it wrong, and no implementation budget will save you.

Stakeholders in success. Trusted partners, not vendors

I am acutely aware of what the large advisory firms optimise for - and it is rarely speed, intimacy, or accountability to outcomes. While I respect the intellect of many of their employees, it is undeniable how these firms often thrive commercially in ambiguous or complex environments. We are not that model, we do not pretend to be, and we do not want to be.

When we partner with you, I do not want us to behave like outsiders dispensing advice from a safe distance. I want us to treat your business as if it were our own, and do valuable, meaningful work alongside you that we can both be proud of. If an initiative does not move your bottom line, improve your operational resilience, reduce your complexity, or help your people to do excellent work, then we should not do it.

We do things properly, or not at all

This isn't a clever commercial strategy around brand quality or positioning - just genuine honesty. I have zero motivation or interest in performative theatre or tick-box exercises - they are not interesting precisely because they do not unlock real value. I would rather walk away (and indeed have) from well-paid work than be part of something I would be ashamed of in eighteen months' time.

The well-known adage "if it ain't broke, don't fix it" - has unfortunately been twisted by the more indolent among us into a quasi-plausible rationale for complacency. Serious, professional people regularly inspect and improve upon the things that already work, in the firm knowledge that doing so advances progress and that failure to do so leads to rust and decay.

As a result, we don't do duct tape or tactical solutions (or for my Indian stakeholders - no "Jugaad"). No temporary fixes dressed up as progress or solutions that work at ten headcount but collapse at a thousand. If we are working on a project with you, I want to be able to look our key stakeholders in the eyes and not just show them what we are doing but show-off what we are doing - because we genuinely believe in the value and are proud of the outcome.

We aim to make ourselves redundant

This is the principle that surprises people most, and it is the one I am most committed to.

From the first day of an engagement, we aim to build capability, processes, and clarity that work long after we have left. The more replaceable we make ourselves, the more valuable I perceive the engagement has been. If you still need us for the same problem in three years' time, then we didn't finish the job.

This is not altruism, but a belief stemming from the fact that there is always more work for people with enough integrity to democratise information and do their utmost to optimise or automate their work away.

Assurance is one expression of a deeper commitment

If you have come to us through our software assurance work, you have seen one surface of what we believe. Reviews, data modelling, and procurement discipline matter - especially when the cost of getting it wrong is measured in millions and in years of organisational drag.

But assurance is not the full story. It is part of what happens when a philosophy of radical simplification meets the moment a major technology decision is about to be made. The deeper commitment is the same whether we are reviewing a programme, reshaping your data estate, or helping your leadership team build a culture that uses information well: reduce complexity, protect what lasts, and compound efficiency over time.

That is what I built Modern Productivity to do. If this resonates with how you want to lead - not just what you want to buy - I would welcome the conversation.

Want to see how we put this into practice?

Get in touch