Building a drone team from scratch: the first 90 days

The first 90 days of a drone team determines whether the program reaches production or stays stuck running pilot projects two years later. Most programs treat the launch as a series of decisions to make in parallel and end up making most of them late and several of them twice. A 90-day project plan with concrete milestones forces the order that actually works.

This playbook assumes the strategic decisions are already in place: executive sponsorship, scope of the program, in-house versus outsourced approach, regulatory baseline (Part 107 as a floor under the FAA's small UAS rule), and budget authority. What follows is the tactical sequence for getting from a signed program charter to first independent missions in twelve weeks.

Week 1: Foundation

The first week is administrative work that the team will regret skipping later if it tries to skip it now.

Confirm scope with the executive sponsor in writing. What the program does, what it does not do, what success looks like at 90 days and at twelve months. The conversation often surfaces gaps in alignment that were not visible in the original charter.

Establish initial role assignments. The program lead. The first pilot or operations contact. The administrative owner of records and documentation. Even a team of two needs explicit roles, because the alternative is two people both assuming the other handles compliance.

Set up the operations platform with role-based access from day one. This is the moment to define how access will work across the program as it grows, not after the first contractor needs to be added with no permissions model in place. This is part of why pilots should only see the jobs they are assigned to, and getting the access model right in Week 1 saves the program from a painful retrofit at month nine.

Schedule the regulatory baseline review. Confirm which FAA authorizations the program will need (Part 107 for all pilots, plus any waivers for night, BVLOS, operations over people, or controlled airspace). Identify any state or local restrictions that apply to the operating area.

Open the documentation. Begin the document vault for permits, insurance, certifications, and operating manuals. Most of this is empty in Week 1, but the framework needs to exist before content starts arriving in Week 2.

Weeks 2 to 4: Build the bench

The second through fourth weeks are about getting the operational pieces in place that the program needs before flying.

First pilot hires or internal transfers. For in-house programs, this is recruiting the first one or two pilots. For programs that move existing staff into the role, this is the formal transition with updated job descriptions and certification timelines. Either way, the first pilots should be in seat by end of week four with a clear path to Part 107 currency.

Equipment procurement decisions. Working from the use case document, finalize the airframe and payload spec, place orders, and confirm lead times. Equipment that ships in week four arrives during Month 2, which aligns with the production readiness phase.

Software selection and setup. The operations platform decision should be largely settled by week one (per the foundation step), but the configuration work happens in weeks two to four. Project structure, role assignments, document templates, integration with existing systems. Configuration done now becomes the operating baseline; configuration done later becomes ongoing maintenance.

Insurance binding. Commercial drone insurance with hull and liability coverage appropriate to the program scope. Bind coverage before any flights occur, even training flights. Some carriers want to see the SOPs and pilot certifications before binding; build that timeline into the procurement plan.

SOP drafting starts. SOPs do not need to be finished in week four, but the drafting work should be underway. Pre-flight procedures, in-flight protocols, post-flight documentation, incident response. The first version is what the team will operate under in Month 2.

Month 2: Production readiness

The second month is where the program transitions from setup to operations.

First supervised flights. As equipment arrives and pilots reach currency, run supervised training flights against the SOPs. The supervision should come from someone with operational experience, whether internal or contracted. Treat these flights as the testing ground for the SOPs, not the start of production work.

SOP refinement based on operational reality. The first ten flights will surface gaps and ambiguities in the SOPs. Update the documents based on what actually happened, not what the draft assumed.

Training program kickoff. For programs hiring multiple pilots, the training program needs to exist before the second cohort arrives. Documented curriculum, defined currency requirements, instructor designation, and records of who completed what. Training that gets improvised becomes a compliance gap later.

Equipment delivery and check-out. As airframes and payloads arrive, register them, log them in the equipment registry, and complete acceptance testing. Equipment that enters service without acceptance testing has unknown history when something goes wrong later.

First incident report drill. Before a real incident occurs, walk the team through the incident reporting process. What the report looks like, who fills it out, where it lives, what gets reported externally and on what timeline.

Month 3: Production launch

The third month is the actual transition to independent operations.

First independent missions. Pilots fly without direct supervision against the SOPs, with the operations lead reviewing the flight records and any incidents after the fact. The reviews are part of the operational rhythm, not a temporary measure.

Formal handoff from setup to operations. The program transitions from "we are launching" to "we are operating." This is the point at which the operations lead owns the day-to-day and the program lead can step back into the longer-term strategy work.

Baseline reporting cycle. The first regular operational reports go to the executive sponsor. Flight hours, missions completed, incidents, equipment status, pilot currency. These reports establish the metrics the program will run on going forward.

90-day retrospective. With the program in active operations, the team reviews what worked, what did not, and what the next 90 days should focus on. The retrospective is the input to the next planning cycle. Programs that skip it end up running the same setup mistakes twice when they add the next business unit or use case.

Common mistakes in the first 90 days

Trying to make every decision in parallel. Equipment, software, hiring, SOPs, insurance, training. Programs that pursue all of these simultaneously in Week 1 end up with all of them late and several of them incompatible. The week-by-week sequence is the discipline.

Skipping the role and access setup in Week 1. Programs that defer the access model until "we have more people" end up with no model when the first contractor needs scoped access. The access framework belongs at the start, even when the team is small enough that nothing about it matters yet.

Buying equipment before the use case is documented. Equipment that arrives without a defined mission profile gets used for whatever shows up first. The use case document drives the spec, not the other way around.

Treating SOPs as a Month 3 deliverable. SOPs that exist only after the program is flying are SOPs that were written around what the team already does, not the safety floor the team operates under. Draft them before the first supervised flights.

Launching without a defined retrospective. A 90-day plan that does not end with a structured review produces a program that never updates its baseline. The retrospective is what makes the next 90 days better than the first.

FAQ

Is 90 days enough to launch an enterprise drone program? For a small to mid-size program with executive support and clear scope, yes. For a program that needs BVLOS authorizations, multi-site rollout, or specialty equipment with long lead times, plan for 120 to 180 days. The sequence is the same; the timeline stretches.

Should the program hire internally or contract for the first 90 days? Most programs benefit from a mix: contract operational experience for the supervision phase, and hire or transfer the pilots who will be in the seats long-term. Programs that hire everyone in Week 1 spend the first 90 days teaching the team work that an experienced operator could have led through.

What if equipment delivery slips past Month 2? Equipment delivery is the most common slippage in the 90-day plan. Build float into the Month 2 timeline by ordering in Week 2 rather than Week 4, and have a contingency plan for renting or borrowing equipment if first supervised flights are at risk.

Who owns the 90-day plan? The program lead owns the plan; the executive sponsor owns the outcome. The operations lead (once in seat) owns Month 2 and Month 3 execution. Plans that have unclear ownership tend to have unclear delivery.

Closing thought

Building a drone team from scratch in 90 days is a project plan, not an aspiration. The sequence matters: foundation in Week 1, building the bench through Week 4, production readiness in Month 2, and production launch in Month 3. Programs that follow the sequence reach independent operations on schedule. Programs that compress the foundation or skip the retrospective end up running setup work in Month 6 that should have happened in Week 1.

If you are building a drone team from scratch, FlybyOps was built for the operational record problem at the center of regulated drone work. Role-based access control configured in Week 1 across Admin, Project Manager, Operation Lead, Pilot, and Ground Staff roles, a document vault that holds the certifications and insurance the program accumulates through Month 2, an equipment registry that captures airframes as they enter service, and an append-only audit log are all part of how the platform supports the launch and the years of operation that follow.