Fractional CTO · AI Architecture · Technical Leadership Coaching

Turn chaotic engineering organisations into teams that deliver predictably.

You already know something needs to change. Whether that is an AI system that needs to work in production or an engineering organisation that has stopped delivering, the diagnosis starts the same way.

See all services →
Smartr365 - Predictable Delivery client Vodafone - Predictable Delivery client Coadjute - Predictable Delivery client Dealogic - Predictable Delivery client Impact Advantage - Predictable Delivery client Smartr365 - Predictable Delivery client Vodafone - Predictable Delivery client Coadjute - Predictable Delivery client Dealogic - Predictable Delivery client Impact Advantage - Predictable Delivery client
20+
Years in engineering leadership
£100m+
Raised across VC-backed engagements
2×
Companies built to £50m valuation
80%
Of world's IPOs processed at Dealogic
3×
VC due diligences passed with no issues

AI and Agentic Systems

88% of organisations use AI. Only 6% see it hit the bottom line.

I design and build multi-agent AI systems in production. Not proofs of concept. Not vendor integrations. Purpose-built agentic architectures where each agent has a domain, the orchestration is auditable, and the system holds under real-world conditions.

Agentic architecture

Multi-agent orchestration. Domain-specific agents. LangGraph. State management. Validator patterns. Full audit trails. Currently building a production system with scoping, outcome modelling, evidence retrieval, and predictive scenario agents.

AI integration

Safe interfaces between LLMs and organisational data. RAG pipelines. MCP server design. Prompt engineering at scale. The boundary between what AI decides and what humans decide. Build-vs-buy grounded in production reality.

AI strategy

Starts with whether you need AI at all. Architecture decisions before you commit. Vendor evaluation. What actually works in production versus what the demo showed you. Grounded in current hands-on experience.

AI due diligence

For investors evaluating AI claims. I know what a real agentic architecture looks like and what a wrapper around an API looks like. The difference is visible in the first hour.

AI specialists command 2x the rate of generalists because the gap between demo and production is where most projects die. That gap is architectural. I close it.

Discuss AI strategy →

The Work

The problem is rarely what it looks like.

Missed deadlines are a symptom. So is team friction, slow releases, and technical debt that never shrinks. I find the actual cause and fix that.

Coach

For technical leads who inherited a mess or stepped into a role they were not prepared for. I help you see what is actually broken, build the processes that create momentum, and develop the confidence to own the hard calls.

Advise

Board-level executive advisory. AI strategy, architecture decisions, build-vs-buy. The judgement of someone who has built what you are evaluating.

Transform

Fractional CTO leadership. I embed in your organisation, own the technical strategy, and hold the team to the standard that creates real delivery momentum.

Validate

Technical due diligence for investors and acquirers. I know what investors look for and where the real risks hide. Including AI capability assessment.

The Opportunity

Picture the next board meeting where the engineering update is not the problem.

01

Your releases ship when they're supposed to. Not because the team is working harder. Because the system is finally working correctly. The relief is immediate.

02

Investors get a technical story they can believe. Not because it's been polished. Because the evidence is actually there.

03

You have a technical leader you can trust to own the hard calls. So you can focus on the business, not on managing around the engineering team.

In Practice

What this looks like when it works.

Smartr365: Fintech

A monolithic codebase built by an outsourced team with no documentation, no tests, no deployment process. Transformed into a multi-tenant SaaS platform. Passed VC due diligence with Legal & General and Experian. Reached a £50m valuation.

Vodafone Africa: Telecoms

A 70-person engineering organisation with a four-hour release cycle and all critical knowledge in a single person. Rebuilt team structure and delivery process. Release time dropped to 30 minutes. CMMI Level 3 achieved.

How It Works

Most people who reach out do not need a service. They need a diagnosis.

Here is what happens when you get in touch.

01

You reach out

Tell me what's going on. A few lines is enough. No form to fill in, no qualifying questions. Just what's prompting the conversation.

02

A 15-minute intro call

A focused conversation about what you are dealing with. Direct questions. By the end, a clearer view of the actual problem and whether I am the right person to help.

03

I propose an approach

If there's a fit, I'll outline what working together would look like. Scope, format, and what I'd expect to deliver. Specific to your situation, not a packaged offer.

04

Work begins

No lengthy onboarding. I embed quickly, build context fast, and start having an effect within the first two weeks. Speed without rushing. Traction, not process. The difference matters.

What Others Say

We had an independent consultant conduct a technical Due Diligence on us for investors and came through with flying colours. A result Rees should be proud of.

Dan Salmons, Co-Founder & CEO, Coadjute

Rees was our second employee and built the tech function from scratch. His ability to create a team from nothing and then lead that team is second to none in those critical, formative stages.

Conor Murphy, CEO, Smartr365

Rees proved to be a capable, diligent CTO. Balancing priorities, solving multiple problems, and working closely with the CEO and L&G. He has integrity and loyalty.

Len Baudert, Business Consultant, Legal & General

His exceptional skill was building a well organised team of capable and empowered developers. He put well designed systems in place to reduce chaos, promote technology transfer, and ensure proper coverage across a range of technologies and domains.

John Williams, Senior Manager: Application Development, Altron Systems Integration

Common Questions

Fractional CTO: what people ask before they reach out.

My engineering team keeps missing deadlines. What is actually going wrong?

Missed deadlines are a symptom, not the cause. The actual problem is usually structural: unclear ownership, no delivery process, technical debt compounding faster than the team can pay it down, or the wrong team shape for the work. I diagnose which of these is the root cause in the first conversation.

What is a fractional CTO and when do I need one?

A fractional CTO is a senior technical leader who works part-time in your organisation. You need one when the engineering team needs strategic direction and accountability but a full-time CTO hire is premature, too expensive, or too risky. I embed in your team, own the technical strategy, and hold delivery to a standard that creates momentum.

How do I know if our AI project is actually going to work in production?

Most AI projects fail between demo and production. The gap is architectural: no state management, no validator patterns, no audit trail, no plan for when the model gets it wrong. I assess whether the architecture will hold under real-world conditions and what needs to change if it will not.

We are raising a round and investors want technical due diligence. What does that involve?

I review your architecture, codebase, team structure, deployment process, security posture, and technical debt. The output is a clear report that tells investors what is strong, what is at risk, and what needs fixing. Three VC due diligences I have led passed with no issues.

What is the difference between a fractional CTO and an interim CTO?

An interim CTO fills a vacancy full-time until a permanent hire is made. A fractional CTO works part-time, typically one to three days per week, providing strategic leadership alongside your existing team. I work fractionally so you get senior experience without the full-time cost.

How quickly can you start having an impact?

Most engagements show visible effect within the first two weeks. No lengthy onboarding. I embed quickly, build context fast, and start making changes that the team and the board can see immediately.

Rees Watkins, Fractional CTO and AI Architect, London

Fifteen minutes is usually enough to find the real problem.

You have been carrying this alone. In the first fifteen minutes, that changes. You describe what is happening. I tell you what I see. Most people leave knowing exactly what to fix first.

Book a 15-minute intro →