The Pilot Network

The autonomous fleet is the destination — not the day-one product.

• Today, UK rules require a qualified pilot keeping the drone within visual line of sight. Fully autonomous, beyond-line-of-sight (BVLOS) flight over client sites isn't permitted yet.
• The coordinated aerial-ground autonomy in the Fleet Command briefing is real, and it's built — but it can't be turned loose unattended under the current framework.
• BVLOS frameworks for commercial drone operations are maturing, with agriculture a cited priority. The direction is set; the timing isn't ours to control.

So the question that decides the next few years: how do we deliver the value now — at scale, legally — and be positioned to flip to autonomy the moment the rules allow?

A human pilot network is the bridge.

Terravect Pilots fly the sites in person, within line of sight, running the same Fleet Command software that will one day fly them autonomously. The client receives the full insight today — surface-health maps, detections, the digital twin — delivered as a managed service.

Managed service is the primary go-to-market. The client doesn't buy hardware, hire a pilot, or run the console — a local Terravect Pilot turns up on cadence and delivers the result. (Self-serve, where a client's own team runs the software, is a later enterprise option.)

Every flight builds the client base and the labelled data asset now — so we arrive at autonomy with customers, coverage and training data already in hand.

The contract model de-risks the whole build-out.

• Cost tracks revenue. Pilots are paid for the scans they fly, so field cost scales with signed clients — never a fixed payroll running ahead of demand.
• Growth in fine-grained increments. Capacity is added one pilot at a time, exactly where clients are appearing — no step-change hiring commitments.
• Genuinely flexible for the pilot, too. They choose the slots that suit them and top up with overflow — flexibility that drives sign-up and retention rather than churn.

Zero-hours here is a feature for both sides, not a compromise: elastic supply for us, real flexibility for them.

Density before breadth — fill a zone before opening the next.

• We carve the map into zones and concentrate sign-ups until a zone carries a viable pilot calendar — only then do we open the neighbouring one.
• Density means short hops between nearby sites, high pilot utilisation, and local brand presence that compounds referrals.
• Each filled zone self-funds the next: recurring revenue from an established zone underwrites the ramp of the one beside it.

Expansion becomes a repeatable, self-financing move — zone by zone — rather than a national land-grab bankrolled up front.

One standard, whoever flies — and invisible to the end consumer.

• The software holds the standard. Fleet Command plans the flight and does the analysis; the pilot ensures safe, compliant, on-cadence operation. The output is consistent regardless of who's on site.
• Uniform, ID and training make every Terravect Pilot a credentialled professional — never a gig-economy unknown turning up at a premium club or estate.
• The client's brand stays untouched. As in the product briefing, the technology is invisible to the golfer, spectator or wine buyer — no "powered by" on the scorecard, jersey or label.

The network isn't throwaway — it's the beachhead autonomy rolls out onto.

• As BVLOS frameworks mature, the same software that a pilot flies today begins to fly itself — first with one pilot supervising more flights, then remote and progressively autonomous operation.
• Autonomy arrives on top of an established footprint: the zones are mapped, the clients are signed, and the data asset is already trained on real sites and seasons.
• Pilots don't disappear — they become fleet and hub supervisors, overseeing more sites per person as the human-to-drone ratio inverts.

Every pound spent building the pilot network buys both revenue today and the runway that autonomy lands on.