0001 - Demo Script: Uncrew Unified Operations Presentation
CONFIDENTIAL | DroneUp | April 2026
1. Purpose
Provide a complete, rehearsable demo script that walks a presenter through the Uncrew platform in 15–20 minutes. The audience is potential customers and sales prospects evaluating DroneUp’s drone operations platform.
What We Are Selling
We are selling end-to-end operational confidence — the ability to run complex drone missions safely, efficiently, and at scale, from environmental data and path planning through autonomous flight execution and ground logistics.
“Whether you’re delivering a package, searching for a missing person, or inspecting critical infrastructure — every role, every handoff, every decision is tracked, managed, and executed in one platform. Your operators aren’t managing software. They’re managing operations.”
Mission Type
Demo Structure
The demo follows a reveal narrative — we show the simple part first, then progressively expose the complexity that makes it possible.
Part 1 — The Flight (Hook): We open with the RPIC executing a mission in real time. The aircraft is in the air within the first two minutes. The audience sees the outcome before they understand the depth behind it.
Part 2 — Behind the Flight: We then work backwards. We show the Supervisor layer that managed and assigned the mission, the ground crew layer that prepared the vehicle, and finally the Environment Manager layer that built the operational world the platform runs in. Each layer adds depth to what the audience already saw fly.
Constraints
- 15–20 minutes total presentation time. Part 1 targets ~3 min; Part 2 targets ~12–15 min across three acts.
- Four separate authenticated browser sessions are required — prepare all before the demo
- All missions, orders, and environmental data should be pre-seeded in the demo environment
- The audience does not need to know which data is simulated vs. live
2. User Roles
The demo presents four user roles across two products (Uncrew and HubOps):
| Role | Product | Screens | Purpose in Demo |
|---|---|---|---|
| RPIC / Pilot | Uncrew | My Missions, Mission Execution, Flight Monitor | Opens the demo — initiates and executes the autonomous mission, confirms key in-flight actions |
| Supervisor | Uncrew | Mission Board, Path Planning, Pilot Assignment, Watching Brief | Manages the team mission queue, reviews path plans, assigns flights to available pilots, monitors in-flight status |
| Hub Operator / Ground Crew | HubOps | Daily Ops, Order Intake, Asset Management, Battery Management | Prepares the operation — LZ assignment, order intake, vehicle and battery configuration, mission submission |
| Environment Manager | Uncrew / Airspace Management | Ground Risk, Obstacle Management, UTM Integration, GeoBound Locations & Data | Builds and maintains the data layer that makes safe operations possible — ground and air risks, operational boundaries, UTM linkage |
3. Pre-Demo Setup
Complete all of the following before the presentation begins. The audience should never see setup activity.
3.1 Environment
- Verify demo environment is stable and all services are healthy
- RPIC session: Hero mission is assigned, status is
Assigned — Ready to Initiate. Path plan is complete. RPIC is logged in and on the My Missions view. - Supervisor session: Mission board shows 3 missions. Hero mission status is
Assigned(will change toIn Flightwhen RPIC initiates during the demo). Watching brief / map view is available. - HubOps session: Live hub with pre-configured LZs, available vehicles, and at least one inbound order in the intake queue. Battery assignment pending.
- Environment Manager session: Operational area is configured with ground risk overlays, at least one obstacle/exclusion zone, UTM link active, and at least two GeoBound locations defined.
- Confirm the ATOMx / Live Map session is accessible and will display the hero mission’s aircraft as authorized once the RPIC initiates.
3.2 Pre-Configured Data
| Item | State | Notes |
|---|---|---|
| Hero mission | Assigned to RPIC, ready to initiate | Delivery example (or SAR/inspection — match to prospect’s use case). Full path plan configured. |
| 2 additional missions | Assigned to second pilot | Shown briefly on the Supervisor’s board to illustrate a full operational picture. |
| 2 available pilots | Online | RPIC is the hero pilot. Second pilot has their missions. |
| 1 inbound order / task | Intake queue in HubOps | Pre-loaded. Not yet assigned to a vehicle (shown during HubOps segment). |
| 1 delivery vehicle | Available, battery not yet assigned | Configured for the LZ. Battery assignment shown during HubOps segment. |
| Charged battery pack(s) | Available in HubOps inventory | Assigned to the vehicle during the HubOps segment. |
| Ground risk overlay | Active in Environment Manager | Shows assessed ground risk for the operational area. |
| Obstacle / exclusion zone | Pre-configured | At least one obstacle visible in the Environment Manager session. |
| GeoBound locations | Configured (min. 2) | Operational boundaries visible and labeled. |
| UTM authorization | Pre-authorized | Hero mission’s airspace is pre-authorized. |
| ATOMx / Live Map | Loaded and showing demo area | Hero mission aircraft will appear as authorized once RPIC initiates. |
| Scale simulation | Pre-configured, ready to trigger | 50+ missions pre-seeded across 10+ simulated pilots and multiple hubs. Triggered by a single action at the start of Act 4. |
3.3 Talk Track Orientation
The demo tells a single story across four roles. The pivot sentence for each section:
- RPIC (opening): “Let’s start with the flight itself.”
- Supervisor: “Now let’s look at who put that mission together.”
- HubOps: “And here’s what made the aircraft ready to fly.”
- Environment Manager: “Finally — here’s the foundation everything else is built on.”
- Outputs: “And here’s what all of that produces.”
4. Demo Flow — Part 1: The Flight
The demo opens with the RPIC. No preamble about the platform. No feature list. The first thing the audience sees is a drone about to fly.
Opening: RPIC — Mission Execution (~3 min)
Set the scene — RPIC view
Open the RPIC session. The My Missions view is showing the hero mission as Assigned — Ready to Initiate.
Talk track (Presenter): “This is the pilot’s view. A mission has been assigned to them. It’s ready to go. Let’s watch what happens when they initiate it.”
Review the mission
Open the mission detail. Show the path plan, the destination or operational area, and the key mission parameters.
Talk track: “Before they start, the RPIC reviews the mission. The route is already planned. The aircraft is prepped. Their job right now is to confirm — and then initiate.”
Initiate the mission
Press the initiate/start control. Show the status transition to In Flight or Active.
Talk track: “Mission initiated. The aircraft is executing the path autonomously. The RPIC isn’t flying it — they’re overseeing it. The platform is running the flight.”
Monitor the flight
Show the live flight monitoring view — aircraft position, telemetry, progress tracking against the path plan.
Talk track: “Here’s the flight in progress. Position, telemetry, path conformance. If anything deviates, the system flags it. Until then — the pilot watches.”
Perform the key in-flight action
As the aircraft reaches the action point, show the RPIC completing the required in-flight step.
Talk track: “This is the human moment in the flight. The platform brought the aircraft here — the RPIC makes the call. Package confirmed. Mission continues.”
Mission complete — aircraft returns
Show the aircraft returning to hub and the mission status closing out.
Talk track: “Aircraft is returning. Mission complete. And everything that just happened — every second of that flight — is in the record. We’ll come back to that.”
Pause briefly. Let the flight land with the audience before pivoting.
Talk track: “That was the easy part. Let me show you what made it possible.”
5. Demo Flow — Part 2: Behind the Flight
Act 1: Supervisor — Mission Management & Watching Brief (~4 min)
Switch to the Supervisor session
Open the Supervisor session. The mission board is visible. The hero mission now shows Complete.
Talk track: “This is the Supervisor’s view. The mission we just watched complete is here — closed out on the board. But let’s wind back. Let me show you where that mission came from.”
Review the mission board
Point out the mission list — statuses, assigned pilots, mission types, hub assignments.
Talk track: “Every mission for this operation is on this board. Status, assignment, timing. The Supervisor doesn’t need to call anyone to know what’s in the air. It’s here.”
Open the hero mission — path planning
Click into the hero mission’s detail. Show the path plan on the map.
Talk track: “Here’s the path plan the RPIC flew. The Supervisor reviewed this before assigning it. They’re not handing their pilot a coordinate — they’re handing them a complete, reviewed, validated flight plan.”
Assign a mission
Return to the mission board. Show an unassigned mission. Show the pilot availability view and complete an assignment.
Talk track: “Here’s the assignment workflow. Available pilots, their current state. One action — the pilot is notified, the mission is on their queue. That’s the handoff.”
Watching brief
Navigate to the Supervisor’s watching brief / live map view.
Talk track: “And this is where the Supervisor spends most of their time during operations. Watching. Not managing — watching. The platform manages.”
Demo simulation beat: If the demo environment supports it, trigger a simulated mission status change from Assigned to In Flight in real time.
Talk track: “Watch this — a pilot just initiated their mission. The board updated. The Supervisor didn’t get a radio call. The platform told them. That’s the difference.”
Act 2: HubOps — Ground Operations & Vehicle Readiness (~5 min)
Switch to the HubOps session
Open HubOps. Show the daily operations dashboard.
Talk track: “One layer further back. Before the Supervisor had a mission to assign, someone had to prepare the aircraft and set up the day. This is HubOps — the ground operations layer.”
Weekly Risk Assessment
Talk track: “Every week, the operation completes a hub risk assessment. This is the operational baseline — what conditions this hub is approved to operate under this week.”
Daily Operational Control
Talk track: “And every day, the hub confirms it’s clear to fly. NOTAMs, weather, maintenance flags. No daily confirmation — no missions.”
Assign Assets to Landing Zones
Talk track: “Before any mission can be planned, vehicles need to be allocated to their landing zones. Each LZ has its own configuration — approach geometry, clearance requirements, weight limits.”
Order / Mission Intake
Talk track: “Here’s where the mission itself enters the platform. For a delivery, it’s an order. For a SAR operation, it’s a task. The workflow is the same.”
Assign the Mission to a Vehicle
Talk track: “The platform knows which vehicle serves which landing zone. The operator confirms the assignment — the system handles the routing logic.”
Assign Batteries to the Vehicle
Talk track: “Battery assignment. The platform tracks charge state, cycle count, and health status for every battery in the fleet. If a pack is below threshold or flagged, the operator can’t assign it.”
Vehicle Reset
Talk track: “Any battery change triggers a configuration reset. Every reset is logged. Every configuration change is in the record.”
Send the Mission to Supervisor
Talk track: “Vehicle prepped, mission logged, batteries assigned. The ground crew submits it to the Supervisor. That’s the mission that appeared on the board in Act 1. Ground crew built it, Supervisor reviewed it and assigned it, RPIC flew it.”
Act 3: Environment Manager — The Foundation (~4 min)
Switch to the Environment Manager session
Talk track: “And here’s the layer that none of the other roles see directly — but everything they do depends on. Ground risk. Air obstacles. Operational boundaries. UTM linkage. This is the foundation.”
Ground Risk Assessment
Talk track: “Ground risk isn’t guesswork. The Environment Manager has assessed the operational area — population density, terrain, infrastructure — and that assessment is encoded in the platform.”
Obstacles and Exclusion Zones
Talk track: “Obstacles and exclusion zones are managed here. They’re not just map decorations — the path planner treats them as hard constraints. A route that crosses an exclusion zone doesn’t get planned.”
UTM Integration
Talk track: “UTM isn’t bolted on after the fact. When a mission is planned and submitted, the UTM authorization is requested through this configuration.”
GeoBound Locations
Talk track: “GeoBound locations are the named operational areas the platform uses to scope everything from path planning to risk assessment to authorization requests. Change a GeoBound location here, and the effect propagates across the entire operation.”
The connection back to the flight
Talk track: “That path plan the Supervisor reviewed and the RPIC flew? It was built inside these boundaries, around these obstacles, based on this risk assessment, with this UTM authorization attached. The Environment Manager built the world. Everyone else operated in it.”
Closing: What the Platform Produces (~3 min)
Open the Operations Dashboard
Talk track: “Everything we just walked through ends up here. This is the dashboard for this location.”
Telemetry summary
| Metric | What It Shows |
|---|---|
| Deliveries Completed | Missions that reached successful delivery confirmation |
| Flights Completed | Total flights executed |
| Failed Flights | Derived from gap between Flights Completed and Deliveries Completed |
| Issues Reported | Flagged anomalies, maintenance flags, operational exceptions |
Talk track: “Four numbers that tell you the health of this operation at a glance. None of this is manually compiled.”
Time per delivery
| Phase | What It Measures |
|---|---|
| Pre-flight | Order intake to mission initiation — ground ops efficiency |
| Outbound | Initiation to delivery confirmation — flight time |
| Total Mission Time | End-to-end including return |
Talk track: “Time per delivery broken into phases — because the causes of slowness are different at each stage.”
Daily delivery view
Talk track: “Every mission that ran at this location today. The most important column is time against SLA — per mission, not as an average.”
Toggle to map view, then drill into the hero mission record.
Talk track: “Every row is a door. Click through, and you get the full mission record — path flown, telemetry, every action, the UTM record.”
Transition to scale
Talk track: “Let me show you what the platform looks like when it’s not one mission — when it’s running at scale.”
Act 4: The Full Operational Picture — Scale Demo (~3 min)
Launch the scale simulation
Talk track: “This is the same platform. Same Supervisor view. Same mission board. But now we’re looking at a full operational deployment — 50 missions, across more than 10 pilots. Watch the board.”
Pause 10–15 seconds. Let the board update without speaking.
Walk the mission board
Talk track: “Every one of these missions is at a different stage. The Supervisor isn’t managing any of this manually — they’re watching. The platform is managing it.”
Switch to the live map
Talk track: “Every aircraft, live. Each one executing its path autonomously. Each one linked to a UTM authorization. The Supervisor sees all of it — one screen.”
Sweep the map slowly.
Show pilot workload panel
Talk track: “The Supervisor can also see their team. Who’s flying. Who’s available. Who’s about to complete and needs a next assignment.”
Final statement
Let the live map run. End with aircraft still moving.
Talk track: “Whether it’s a delivery, a search, or an inspection — the platform is the same. The RPIC doesn’t navigate manually. The Supervisor doesn’t chase status updates. The ground crew doesn’t work from a whiteboard.”
Pause.
Talk track: “That’s Uncrew.”
6. Talk Track Tips
What to Emphasize
- Execution is simple because the foundation is hard: The flight looked easy because of everything underneath it.
- Role clarity: Every role has a clear lane. The platform handles the handoffs.
- Human in the loop, intentionally: The RPIC makes the decisions that matter. The automation handles everything else.
- Mission type flexibility: It’s not a delivery platform or a SAR platform. It’s an autonomous operations platform.
- Compliance as a byproduct: The audit trail is created as the work happens.
- Environment data as the foundation: Safe operations start when the Environment Manager defines the operational world.
What to Avoid
- Don’t walk through every UI field — hit the hero moments and move
- Don’t frame Uncrew as a remote pilot tool
- Don’t skip the Environment Manager section — significant differentiator
- Don’t apologize for simulated data
- Don’t let “delivery” language dominate if the prospect’s use case is SAR or inspection
Handling Questions
| Question | Suggested Response |
|---|---|
| “Does this work for missions other than delivery?” | “Yes — the platform is mission-agnostic. The roles, workflows, and environmental data layer are the same.” |
| “Can operators still manually fly if needed?” | “The RPIC always has the ability to intervene. Automation handles the routine; humans handle the exceptions.” |
| “How does this connect to UTM and FAA compliance?” | “Every flight is linked to a UTM authorization configured by the Environment Manager. The executed telemetry is bound to the authorized route.” |
| “What happens if a battery fails mid-flight?” | “The platform monitors vehicle telemetry throughout. Battery assignment in HubOps validates health before the vehicle is cleared.” |
| “Who manages the Environment Manager role?” | “Typically a small team — one or two people. They don’t need to be involved day-to-day once the foundation is established.” |
| “How do you handle multiple simultaneous flights?” | “The Supervisor’s mission board manages the full shift queue. The platform is designed for concurrent operations.” |
| “Is the scale view real or simulated?” | “The missions are simulated for the demo. But the platform is real, the data flow is real, and the Supervisor view is the same your team would use on day one.” |
7. Current State vs. Uncrew + HubOps
| Capability | Current State (Manual) | Uncrew + HubOps |
|---|---|---|
| Mission assignment to pilots | Radio calls, text messages, whiteboard | Supervisor assigns via mission board; pilot notified in real time |
| Supervisor situational awareness | Radio check-ins, no live status | Live mission board; status updates automatically |
| Path plan review | PDF or verbal briefing | Interactive map with route, environmental overlays, airspace context |
| Flight execution | Manual RPIC control or scripted waypoints | Autonomous execution with human oversight at key decision points |
| UTM authorization linkage | Separate workflow, often post-flight | Real-time binding configured by Environment Manager |
| Ground risk assessment | Periodic manual review, not platform-integrated | Managed by Environment Manager; enforced by path planner |
| Obstacle and exclusion zone management | GIS tools separate from flight operations | Managed in-platform; directly enforced by path planner |
| Battery management | Physical logbook or spreadsheet | In-platform with charge history, cycle count, and health validation |
| Order / task intake | Email, phone, or external system | Structured HubOps intake; guided assignment to vehicle and LZ |
| Mission audit trail | Manually assembled from multiple sources | Complete lifecycle record created automatically |
8. Relationship to Other Documents
| Document | Relationship |
|---|---|
| ATOMx Demo Script (0003) | ATOMx is referenced during the RPIC’s flight when the authorized aircraft appears on the Live Map. |
| Uncrew Demo Project Plan | Defines overall demo strategy, delivery format, and phase timeline. This script is the execution layer. |
| HubOps Product Documentation | Source of ground truth for Act 2 capabilities. |
| Airspace Management Documentation | Source of ground truth for Act 3 capabilities. |
| Builder’s Brief (0002) | The build companion to this script — same acts, engineering audience. |