What we do
Behind the system
Behind ECM.dev is Russell Lack, who has spent over thirteen years running enterprise cloud and data architecture programmes across the Nordics before turning the same discipline on content. That background is why the work reads like an audit, not a workshop deck.
Why this exists
Most organisations still treat content as a finished product: a page, a document, a translated file, filed and forgotten. That assumption breaks down once content also has to feed search, feed AI answer engines, and feed decisions inside the business itself. Content that only looks right to a human reader is no longer enough on its own. This isn't a new idea. Content strategists have understood content as a system rather than a pile of assets for well over a decade. ECM.dev applies that discipline to the work itself: a defined project that leaves your team with a system it can run, not a report you're left to implement yourself.
How we work
The same person scopes the work, delivers it, and leads any support that follows, so judgement doesn't reset each time something changes. Most "AI content audits" on the market are shallow: a search-visibility check dressed up as a system review. We built ecm-agent, our own AI-readiness scoring engine, because that wasn't good enough. It scores governance, workflow, technology and AI-readiness together, against a versioned rubric, with every finding traceable back to its evidence. We call that provenance, not certification, because we won't claim more confidence than the evidence supports.
What makes this different
There are really only two ways most businesses solve this today: hire for it, or hand tasks to whoever's available and hope the pieces add up to something coherent. Both have a real cost. A hire means recruiting, management time, and months of ramp-up before you see the judgement you're paying for. Handing out tasks means no one owns the outcome, and whatever gets built has to be rebuilt the next time someone new picks it up. ECM.dev is neither. You get a system your own team can run, senior judgement available again when you need it rather than re-hired each time, and an AI-readiness score you could defend to your own board.
Start here
There are two ways in. The Content Operations Maturity Assessment takes about five minutes and shows its result without asking for your email. It is a self-check based on your own answers, not a review of your content. Or start with a conversation about one problem. If a first project makes sense, you receive a written scope, fee, timing and the time it needs from your team before any work starts. When it is complete, you decide whether anything more is useful. Stopping there is a good outcome. If you want continued support, it is scoped separately, with a rhythm that fits your team.