Skip to content
Est. 2025 · United Kingdom

Engineeringformotorsport.

A UK consultancy delivering vehicle, manufacturing, and software programmes from first principles. The engineer scoping the work is the engineer doing it. No account managers, no handoffs, no theatre.

0+
Years engineering
0h
Average response time
0
Disciplines in-house
0
Flagship product
01 · Introduction
Precision engineering, directly delivered.

Godfrey Engineering is a UK-based multi-discipline consultancy. We work across automotive, motorsport, manufacturing, and software. The same team, the same standards, the full stack.

No layers between you and the engineer. No handoffs. Founded in 2025 by Ben Godfrey, after a decade of motorsport, automotive, and production-engineering work for OEMs and racing teams. From 72-hour rig turnarounds to fourteen-month vehicle programmes.

More about us

03 · How we engineer

Four ways the work changes shape.

Watch the gearbox rotate. Each facet is a different dimension of how a Godfrey programme runs.

04 · Why work with us

Four rules.
Applied to everything.

Principles that show up in how we scope a brief, write a report, and close a programme.

01
First principles
Re-derive every constraint. Catalogues are a last resort, never a first move.
02
Directly delivered
No account managers, no layers. The engineer designing your system is the one on the call.
03
Software-augmented
We build the tool if it doesn't exist. Our own solvers, pipelines, and dashboards ship with the work.
04
Proven in the field
On track, on the shop floor, in the test cell. Designs live or die in measurement, not in the CAD viewer.
03 · Product · Coming Summer 2026

ChainSolve.
Block-graph
calculator.

Rust core, WebAssembly runtime, 182KB gzipped. Tolerance stacks, thermal networks, NVH predictions, composed visually and solved at native speed. Sub-40ms solves on 100k-node graphs. Your CPU, not ours.

<40 ms
100K-node solve
182 KB
WASM bundle
Jul '26
Launch
suspension-tolerance.chain
● SOLVING32ms
INPUT · Ra 0.8μ=0.8 σ=0.12INPUT · ±0.05mmtol ±0.05INPUT · 2024-T3α=23.1e-6OP · RSS + WCmode: RSSOP · K&C XFORM6-DOFΣ STACKΣ=0.082mm
6 NODES · 6 EDGESΣ = 0.082mm · σ = 0.017WASM · 182KB
The difference

The usual way. Our way.

Six things that separate a Godfrey engagement from a typical consultancy. None of this is revolutionary. It's just how engineering should be done.

Topic
Typical consultancy
Godfrey
Who talks to you
Account manager, pre-sales, then a junior engineer does the work
The engineer running the programme is on every call
Scope definition
Broad statement of work, flexible success criteria
Written acceptance criteria before work starts
Contract
Six-figure minimum, 12-month commitment
Day rate, fixed price, or retainer. No minimums
Delivery format
Slide decks with recommendations
Working drawings, code, analysis reports, test plans
Scope changes
Change request, 3-week lag, new SOW
Discussed the same day, re-quoted the next
Where we work
Remote only, slides and calls
On-site at the test cell, on the shop floor, track-side
05 · How we work

Four stages.
No theatre.

A deliberate process. Small enough to run fast, structured enough that nothing is lost between meetings.

01
Discover
Scope the problem, audit the constraints, agree success metrics in writing.
02
Design
Concept studies, first-principles calculations, analysis, peer review, sign-off.
03
Deliver
CAD, drawings, code, reports, test plans. Production-grade documentation.
04
Support
On-call through validation. Revisions, field issues, closing the loop.
Selected feedback

What the engineers on the other side say.

Attribution is by role because most of these programmes are under NDA. Full case briefs available on request.

They rewrote the rear end in fourteen weeks. We found 0.82 seconds a lap on identical driver and tyre on day one. I'd have paid twice as much.
Head of Vehicle Performance
LMP-class motorsport team
-0.82s
lap-time delta
The rig passed UN 38.3 on the first submission. Throughput went up four times. That's not a consultancy result, that's an in-house-team result delivered faster.
Chief Engineer, Battery Systems
Tier-1 automotive supplier
UN 38.3
first submission
We knew the intake was the problem. Nobody had a solution that fit the packaging. Ben's team delivered the ducting in nine weeks and the car shipped with it.
Programme Director
UK supercar manufacturer
+4.1%
wheel power
Stack

The software we actually use.

We match your pipeline, not the other way around. If your team standardises on a tool that isn't listed, tell us and we'll pick it up.

CAD
  • NX
  • Catia
  • SolidWorks
  • Onshape
  • Creo
  • Inventor
Analysis
  • Abaqus
  • Ansys
  • HyperMesh
  • Fluent
  • OpenFOAM
  • LS-Dyna
Code
  • TypeScript
  • Rust
  • Python
  • MATLAB
  • WebAssembly
  • C++
Standards
  • ISO 9001
  • FIA GT3
  • UN 38.3
  • ECE R100
  • IATF 16949
  • ASME Y14.5

No vendor partnerships, no affiliate arrangements, no kickbacks. We pick the tool that fits the problem and document the choice in the SOW.

Questions

Before you send a brief.

Six things we get asked most. If your question isn't here, send a note and we'll answer in the first reply.

Still have a question
How small can a Godfrey engagement be?
A single afternoon for a design review, a week for a targeted analysis, or twelve weeks for a vehicle programme. We don't run minimum-commitment contracts. The shortest engagement we've done was two days. The longest so far is fourteen months.
How do you price work?
Day rate for scoped work, fixed-price for scoped deliverables, or a monthly retainer for ongoing support. No hidden rate cards. Every SOW includes a written scope and an acceptance criterion. If the scope changes, we renegotiate before the change starts.
Can you work under NDA?
Yes. Most of our work is. We sign mutual NDAs up-front and keep programme artefacts out of any external demo or portfolio unless you explicitly approve sharing. The case studies on this site are either NDA-waived or written with identifying details removed.
What tools do you use?
CAD in NX, Catia, SolidWorks, or Onshape depending on your pipeline. FEA in Abaqus, Ansys, or Altair HyperMesh. CFD in Fluent or OpenFOAM. Software in TypeScript, Rust, Python, or whatever the problem calls for. We match your stack, not the other way round.
How fast can you start?
Usually the week after a signed SOW. Urgent programmes with a pre-scoped statement of work have started inside 48 hours. Anything bigger than a four-week programme typically has a two-week lead time for resource planning.
Who does the work?
The engineer on the call. That's the whole point. We don't do account-management layers, pre-sales engineers, or handoffs between the person who wrote the proposal and the person doing the analysis. If you brief an engineer, that engineer delivers.
09 · Start

We reply within
one working day.

Short engagements. Long programmes. Second opinions. Send a brief and the engineer you'd be working with writes back the same day.