Independent technical advice

Clear technical
direction.

Independent technical advice for CTOs and founders.

I assess complex platforms, establish technical direction and help engineering teams improve how they deliver. I combine technology leadership with practical engineering, grounding recommendations in the systems, constraints and people involved.

Where a critical assumption needs evidence, I investigate and test it.

Portrait of Joe Keene

Joe KeeneCTO and Director of Engineering experience. Principal Engineer engagements at GSK and the Financial Times.

Independent judgement, practical help

Where I can help

I take responsibility for the agreed technical assessment, recommendation and validation. I work alongside your team so they understand the decisions and can take the work forward.

Platform and architecture decisions

The situation

You need to connect systems, modernise a platform or decide what to retain and replace.

How I help

I assess the existing architecture, dependencies and constraints, compare the credible options and recommend a practical way forward.

Engineering effectiveness

The situation

Delivery is slow or inconsistent, or the team needs a more effective way to use AI.

How I help

I investigate what is holding delivery back, strengthen development and release practices, and coach engineers through improvements tested on real work.

Applied AI

The situation

You have a promising AI idea, but need to establish whether and how it will work in practice.

How I help

I assess the workflow and data, define what success should look like and test important technical assumptions through a focused prototype where agreed.

Experience

Selected leadership and consulting experience

Experience from previous leadership roles and consulting engagements.

Helio Intelligence

Director of Engineering

Reworked AWS architecture with a DevOps engineer, strengthened development and release practices and introduced AI into engineering workflows. Led a team of six engineers and QA specialists and delivered the agreed September 2026 roadmap.

Bot-Hive

Chief Technology Officer

Led technology strategy, architecture and product delivery for a robotics startup. Designed and built a component compatibility engine using graph modelling, with supporting cloud services and a visual interface.

GSK

Principal Engineer

Built data ingestion workflows using AI agents to structure scientific datasets for an internal research platform. Designed reusable skills that enabled the research assistant to work with newly ingested datasets.

Financial Times

Principal Engineer

Designed and delivered AWS middleware connecting Salesforce and Oracle across sales, invoicing and reconciliation. Validated sales data before passing it to Oracle for invoicing, then synchronised invoice details back to Salesforce.

Further selected engineering work: Jisc, defining architecture and technical direction for a Higher Education Statistics Agency platform; and Complete Cyber, designing AWS data pipelines and Neo4j models for cybersecurity telemetry.

Technical
Direction Sprint.

For one important technical question, I review the relevant systems and credible options, then give your team a recommendation, rationale, risks and practical next steps.

What you leave with

A Technical Direction Pack covering the recommendation, key decisions, tradeoffs, risks and implementation sequence. A 60 to 90 minute walkthrough gives your team space to question the approach.

Keene DevelopmentIllustrative example, not client work
Example decision from a Technical Direction Pack

How should a sales platform pass confirmed sales to the invoicing system?

Working recommendation
Put the handoff behind a queue rather than waiting for a synchronous response from the finance system.
Proposed flow
  1. Sales system
  2. Durable invoice request
  3. Background handoff
  4. Finance system

Failed or uncertain result: retry safely or review for reconciliation.

Reason
Sales can continue while the finance system is unavailable.
Tradeoff
Invoices are not immediate, so the handoff needs monitoring and reconciliation.
What to validate
Timing requirements, repeated-request behaviour and how failed records are reconciled.
One clearly defined technical decision

One product, platform or system area, with a framing session and up to three technical discussions.

Typically 1 to 2 weeks

Subject to agreed access and availability.

5 business days for clarification

After the walkthrough. Not ongoing support.

The process

How the Sprint works

  1. Understand the question
  2. Compare the options
  3. Recommend and hand over

Standard Technical Direction Sprint: £4,500 plus VAT

For one clearly defined technical decision. We confirm the scope together before you commit.

Payment is made before the engagement starts.

About Joe

About Joe.

I’m Joe, based in Bath. I have more than 14 years of software engineering and technology leadership experience. I established Keene Development in 2016.

I bring strategic judgement and practical engineering to architecture, delivery and applied AI decisions. I stay close enough to the technical work to recommend an approach your team can use.

More about my experience on LinkedIn

Practical details

Questions before we start.

Is this a fractional CTO service?

Advisory can provide defined technical input alongside your team. Ongoing engineering management and programme ownership are not included unless separately agreed.

What happens on the first call?

We’ll discuss the outcome you need, the technical situation and what you’ve already tried. If there’s a fit, I’ll recommend an appropriate scope and explain how we could work together.

What sits outside a standard Sprint?

The £4,500 plus VAT fee covers one clearly defined technical decision. Broader engineering coaching, practical validation, prototype work, production implementation and ongoing support are separately agreed. A Spike or Proof of Concept and Advisory are individually scoped formats.

How are access and timing handled?

We agree the relevant systems, material and people before starting. Access is kept to what is needed, preferably read only. Start dates are agreed around existing commitments; a typical Sprint spans one to two weeks elapsed, not full time availability.

Contact Joe

Tell me what you’re working on.

Tell me about the technical challenge, the outcome you need and what you’ve already tried. A few sentences are enough to start a conversation.

joe@keene.dev

Prefer a simple email? That works too.
Please don’t include credentials or confidential client data.

Keene Development · Service overview

Technical Direction Sprint.

One important technical question. A recommended approach your engineers can take forward.

What it includes

A framing session, review of agreed technical material, up to three relevant technical discussions, a Technical Direction Pack and a 60 to 90 minute walkthrough. Five business days afterwards are included for clarification of the recommendation.

What you receive

The recommendation and rationale, software architecture where relevant, credible alternatives, tradeoffs, risks, assumptions and a practical implementation sequence.

Standard Technical Direction Sprint: £4,500 plus VAT

For one clearly defined technical decision. We confirm the scope together before you commit.

What it doesn’t include

Broader engineering coaching, production implementation, programme or line management, ongoing support and an exhaustive security or code audit are outside the standard scope. Practical validation and prototype work are separately agreed.

Other engagement formats

A Technical Spike or Proof of Concept can test a specific uncertainty. Advisory provides defined independent input alongside your technical team. Each is scoped and quoted individually.

How we start

We’ll discuss the outcome you need, the technical situation and what you’ve already tried. If there’s a fit, I’ll recommend an appropriate scope and explain how we could work together. A start date is confirmed after acceptance of the engagement terms and cleared upfront payment.

Typically one to two weeks elapsed, subject to access and availability. No follow-on purchase is required.

Discuss your technical challenge

Keene Development

Privacy notice

How Keene Development handles website visits and enquiries.

Your enquiry

The form sends your email address, optional name, selected topic and message through a protected Cloudflare Worker to Joe’s Google Workspace business inbox. It is used to respond to your enquiry and is not a mailing-list signup. Please do not send credentials or confidential client material.

Security and providers

Cloudflare provides site delivery, Turnstile, rate limiting and email sending. The Worker stores no enquiry database and does not deliberately log form content. Cloudflare, Google Workspace and the external font providers process the operational information needed to provide their services.

Retention

Unsuccessful enquiries are kept for up to 12 months after the last meaningful contact and deleted earlier when no longer needed. Necessary engagement records may be kept for up to seven years after an engagement ends, with the reason documented. That period is not automatically applied to client datasets, repository copies, credentials or system access.

You have data-protection rights and can complain to the Information Commissioner’s Office. Contact joe@keene.dev with a request or question.

Read the complete privacy notice