Services

Three ways to bring
ten years into your project.

Start with the specification, turn it into something you can show and cost, then build it. Each stage is scoped so you know what you are buying before you buy it.

Engagements

Start small.
Find out early.

Most projects start with a fixed-price Project Discovery, because two weeks and a known number is a cheap way to find out whether the plan holds. Where it leads is a fractional CTO engagement or full delivery — and either way the rest of the bench comes with it, brought in as the work calls for it rather than contracted for separately.

Engagement 01

Project Discovery

2 weeks

USD $4,500

Fixed price, agreed before we start

The front door. Two weeks with a senior engineer on your project — enough to work out what you are actually building, and whether the plan you have survives contact with all five disciplines.

  • Two weeks of part-time fractional CTO access
  • A minimum of three hours on live calls with you
  • A written project plan your team can execute against
  • Initial platform drafts, to make the concept concrete
  • Yours to keep and act on, with or without us
Start with discovery

Engagement 02

Fractional CTO

Ongoing

Scoped per project

Where discovery usually leads, and it is not a solo appointment. We hold the technical direction with you — and bring in whichever disciplines the specification turns out to need.

  • The real specification, not the wish list
  • Architecture decisions made early, deliberately
  • Full specification and system renders as the design firms up
  • Mechanical, electrical, firmware and test engineers on tap
  • Supplier and make-or-buy calls, and the procurement to follow them
Talk about a CTO engagement

Engagement 03

Project Delivery

~6 months typical

Scoped per project

We run the project end to end on our six-month design template — concept, prototype, field deployment, production readiness — and hand you a product and the documentation to build it again without us.

  • Design across all five disciplines, in step
  • Prototype build, tuning and instrumented flight test
  • Supplier selection from an existing qualified network
  • Production planning and build documentation
  • A handover package your team can build from
Scope a project

Engagement 01

Project Discovery

2 weeks

USD $4,500

Fixed price, agreed before we start

The front door. Two weeks with a senior engineer on your project — enough to work out what you are actually building, and whether the plan you have survives contact with all five disciplines.

What it involves

  • Two weeks, fixed scope and fixed price, starting in days rather than months.
  • A minimum of three hours on live calls — working sessions with a senior engineer, not status updates.
  • We work out what you are actually building, and what that forces in every discipline downstream.
  • Risks get named and ranked while they are still cheap to act on.
Suits
Teams that need something concrete before committing real budget — to cost the project, to put in front of a board or an investor, or to find out whether the plan survives contact with the five disciplines.
You get
A written project plan and initial platform drafts. Yours to keep and act on, with or without us — most clients carry it into a fractional CTO engagement, but nothing obliges you to.
Start with discovery
A rendered view of a folded quadrotor and its battery seated in a custom foam-cut transit case.

Engagement 02

Fractional CTO

Ongoing

Scoped per project

Where discovery usually leads, and it is not a solo appointment. We hold the technical direction with you — and bring in whichever disciplines the specification turns out to need.

What it involves

  • We read what exists first — drawings, CAD, schematics, BOM, flight logs, the plan.
  • Then we work out the real specification with you: what the system actually has to do, in the environment it has to do it in.
  • We take the architecture decisions that constrain everything downstream, deliberately and early.
  • We stay accountable for the technical plan as the project runs, at whatever cadence it needs.
Suits
Teams without a senior hardware voice in the room — strong software leadership, funded, and about to commit to an architecture nobody present has built before.
You get
A specification your team can execute against, and a senior engineer who owns the technical direction rather than advising on it.
Talk about a CTO engagement
Two engineers examining an opened avionics module together at a technology conference.

Engagement 03

Project Delivery

~6 months typical

Scoped per project

We run the project end to end on our six-month design template — concept, prototype, field deployment, production readiness — and hand you a product and the documentation to build it again without us.

What it involves

  • Requirements and concept definition, working from the operational problem rather than a spec handed down.
  • Design across all five disciplines in step, with production intent present from the first concept.
  • Prototype build, tuning and an instrumented flight-test campaign.
  • Supplier selection from an existing qualified network, production planning, and the build documentation to make it repeatable.
Suits
Companies who need the product and do not intend to build a full hardware engineering team to get it — or not yet.
You get
A working product and a handover package your team, or your manufacturer, can build from without us.
Scope a project
A carbon-fibre quadrotor on a landing pad at a netted flight-test site, with its controller alongside.

The bench

Not a menu.
The team behind every engagement.

These are not separate placements you buy one at a time. They are the disciplines standing behind whichever engagement you start with, brought onto your project when it needs them and off it when it does not.

You meet the person before they start. No substitutions mid-project, and nobody learning the discipline on your budget.

Fractional CTO / engineering leadOngoing
Mechanical design engineerProject or ongoing
Electrical / PCB design engineerProject or ongoing
Firmware & software engineerProject or ongoing
Test engineerCampaign
Drone pilotCampaign

Capabilities

Sixteen disciplines.
One engagement.

All sixteen are available inside one engagement, under one contract. A drone project fails at the seams between disciplines, and covering every one of them is how those failures get found at the design stage instead of on a test range.

01

Industrial design

Form, ergonomics and field usability — designed alongside the engineering, not applied to it afterwards.

02

Mechanical design

Airframes, mechanisms and enclosures, engineered for stiffness, mass, serviceability and manufacture.

03

PCB & electrical

Schematic through layout for power, control and payload boards, including flight-critical hardware.

04

Power & energy

Pack and BMS design, cell selection, thermal behaviour and charging — the constraint that shapes every other decision.

05

Firmware & software

Embedded firmware, ground software and the interfaces that hold a system together.

06

Flight stack & control

Controller selection, configuration and control-system work on open and proprietary stacks.

07

RF & communications

Link budget, antenna placement and integration, command-and-control and video links, coexistence and spectrum.

08

Sensor integration

Payload and sensor selection, mounting, synchronisation and data path — through to usable output.

09

Harness & cabling

Looms designed and built for vibration, EMI, serviceability and repeatable assembly.

10

Safety & failure modes

FMEA, redundancy architecture and containment — what the aircraft does when a motor, cell or link drops out.

11

UAV tuning

Getting an aircraft from flyable to stable, efficient and predictable across its real envelope.

12

Flight testing

Structured test campaigns with instrumented results — not a pilot reporting that it felt fine.

13

Certification & regulatory

Operational authorisation and the product side of compliance: EMC, radio equipment, and lithium transport.

14

Prototype builds

Hands on the hardware: machining, assembly, soldering and rework, in-house.

15

Production planning

Design for manufacture, assembly process, jigs, test rigs and build documentation.

16

Supply chain

A supplier network built specifically around these systems, across Europe, China, the US and Australasia.

Twenty minutes,
straight to an engineer.

Bring a drawing, a board, a flight log or a plan, and we will get into the technical questions on your project. No discovery deck, no sales sequence — if we are not the right people we will say so on the call.

Book a technical callSend a message