Money in, nothing out
56% of CEOs saw zero return on AI last year. No revenue gain, no cost saving. Only 12% got both (PwC Global CEO Survey, 2026). The spend is real. The payoff is the question.
It’s quietly sabotaging it instead: ungoverned AI code that stalls delivery, security holes nobody owns, and revenue leaks that never appear cleanly in the P&L. I step in as your no-BS Fractional CTO to expose them and stop them.
They grow slowly enough that nobody raises a hand. Then delivery stalls and margins quietly thin out.
56% of CEOs saw zero return on AI last year. No revenue gain, no cost saving. Only 12% got both (PwC Global CEO Survey, 2026). The spend is real. The payoff is the question.
Nearly half of AI-written code contains a known vulnerability (Veracode, 2025). Your team ships faster than anyone reviews. That gap is your exposure.
The EU AI Act becomes enforceable in August 2026, with fines up to €35M or 7% of turnover. Only 3% of Nordic organisations feel prepared (Tieto, 2026).
I audit what you actually use AI for, kill what returns nothing, and rebuild around the few things that show up in the P&L.
Review, testing, and security checks that catch AI-generated problems before your customers do. Without slowing your team back down.
A clear answer to whether the EU AI Act applies to you, who owns the risk, and what the minimum compliant setup looks like. Practical, not a 200-page policy.
You pay for outcomes, not timesheets. Every engagement starts with the health check.
Two weeks. I audit your AI spend, your codebase exposure, and your AI Act position. You get a plain-language list of what is leaking, what it costs you, and what to do about it. Fixed price, written findings, no obligation to continue.
A definitive answer to whether the Act applies to you, a named owner for each risk, and the minimum compliant setup implemented. Fixed price. Compare it to the fine: €35M or 7% of turnover.
Two days a week, embedded. I own the technology risk by name, keep the guardrails running, and answer to your board. Three-month minimum, then rolling monthly.
Two or more? We should talk.
A decade at McKinsey & Company leading technology across the Nordics. I talk margins and risk with the board, then go fix the cause myself.
Over 20 years of hands-on engineering. The advice comes with working software attached.
Software matters when customers love it and it earns money. Everything else is hobby work on your payroll.
Client names stay under NDA. The shape of the problems, and what fixing them was worth, does not.
AI tooling spend spread across [N] unconnected vendors, none measured. Consolidated to [N], cut the spend [X]%, and delivery throughput went up, not down.
AI-generated code shipping with no review gate. Introduced guardrails that caught [N] exploitable vulnerabilities in the first month, without adding a day to the release cycle.
Roadmap slipping despite heavy AI tool adoption. Found the bottleneck in [area], fixed it, and the team shipped [outcome] within one quarter.
One health check. Two weeks. €9,500. A plain-language list of what is slowing you down, what it costs, and what to do about it.