A CTO's judgement, without the full-time seat.

I join early-stage teams as a fractional CTO. Architecture, delivery and hiring judgement from 17 years of shipping, at a pace AI-augmented engineering makes possible and most teams have not seen yet.

Lighthouse standing above the sea
Plate 001 / Guidance, not occupancy.

AI tools have made it cheap to produce code and expensive to live with it.

Velocity without wreckage. The teams that win pair the new speed with old discipline: tests first, boring architecture, small releases. That pairing is a leadership job, not a tooling choice.

Seniority without the salary. A good CTO costs more than most seed-stage companies should spend. A fractional one gives you the decisions, the delivery cadence and the hiring bar without the £150k+ seat.

Two ways in. Both start with a conversation, not a proposal document.

The offer

The 90-day pilot

A defined fractional engagement: audit in the first fortnight, then a weekly operating cadence covering architecture, delivery and team. At day 90 you have a technical roadmap, a working delivery process, and a clear decision about continuing.

Book a call →

Technical due diligence

For investors and acquirers: a focused review of a target's codebase, architecture, team and delivery record. Findings in plain English, graded by risk, delivered in days.

Built and operated, not just advised.

Plotbeacon

National planning-application alerts across England, Scotland and Wales, in beta.

Plotbeacon, 19 August 2026: 247 councils, 9,625 live applications.

Lettergraph

A European newsletter platform, in development.

“I run my own product portfolio on the same methods I bring to clients. Everything I recommend, I already do in production.”

— Ed Woodcock, founder, Bannermedia Ltd

Ed Woodcock.

Founder, Bannermedia Ltd. Fractional CTO. London.

I have shipped production software for 17 years. I have led teams, rescued codebases and run my own products with real users and real consequences. I work AI-leveraged and say so: the interesting question in 2026 is not whether to use these tools but how to get senior-grade output from them. That process is my trade.

More about how I work →

Principles.

  • Tests before code, releases in small steps.
  • Boring architecture until the interesting part earns it.
  • European infrastructure by default.
  • Plain speech: you will always know what I think and why.