One growth system.
Every idea in its place.

0–2s: paper charts and browser tabs — “Planning your first cross-country?”
2–6s: enter two airports in Ascent — “Route, weather, airspace and fuel.”
6–10s: open weather and 3D terrain — “One clear picture.”
10–13s: save the offline region — “Still there when the signal isn’t.”
13–15s: product + CTA — “Plan your next flight with Ascent.”

Slide 1: “Your first cross-country should not begin with twelve open tabs.”
Slide 2: chart, weather, fuel and terrain shown separately.
Slide 3: the same route inside Ascent.
Slide 4: “Same planning questions. One clear picture.”
Caption: “Complex flight information can stay professional without feeling scattered.”

Hook: “Your route can look short on a chart and still be a bad first cross-country choice.”
Middle: “Before committing, look at terrain, weather and airspace together—not as three unrelated checks.” Show each layer on the same Ascent route.
Close: “Ascent does not make the go/no-go decision. It helps you see the picture you need to discuss with your CFI.”

Opening to camera: “The first EFB lesson should be about planning a flight—not memorizing where every button lives.”
Screen demo: the CFI assigns one student route and asks the student to identify weather, airspace and terrain.
Close: “I would use this beside the tools I already teach, then ask which view helped the student explain the plan back to me.”

“Professional software does not have to make beginners feel lost. Aviation data can remain complete, current and serious while the interface explains what belongs together. Ascent’s position: lower the software-learning barrier—not the standard of pilot judgment.”

Headline: “What AI should—and should not—do in a cockpit.”
Body: “It can help organize and explain information. It should show its source, freshness and limitations. It should never hide uncertainty or replace the pilot in command.”
CTA: “Pilots: what would you need to see before trusting an assisted briefing?”

Episode 1: “What I download before leaving Wi-Fi.” Mack introduces the flight, saves the offline region and explains what he still carries as a backup.
Ending: “I fly, I work on Ascent, and this is the part I still want us to improve.” The honest limitation becomes the hook for Episode 2.

Post 1: “New pilots told us this screen made them hesitate. Which version makes the next action clearer—A or B?”
Follow-up: “68 pilots voted; 41 explained why. Here is the version we are testing next, and the request we could not solve yet.” Use real numbers and screenshots only after the test.

Give a young CFI one real first-cross-country route. Ask them to score: time to build the plan, questions a student still asks, confidence explaining weather and airspace, and what is missing. Publish the screen recording plus the CFI’s unedited conclusion: “Who I would recommend this to—and who I would not.”

Title: “Build Note 07: one small change, one less hesitation.”
Post: show the old screen, the new screen and the pilot question that motivated the test. Label each item clearly: “Available now,” “In beta,” or “Concept only.” End with one specific beta request.

Episode 1: a student chooses the route with a CFI.
Episode 2: the student explains weather, airspace and backups in their own words.
Episode 3: post-flight reflection: what felt clear and what still felt hard.
Caption: “Ascent is learning alongside the pilots learning to fly.”

Founder/team member to camera: “We kept route, weather and terrain close because pilots were switching context to answer one planning question.”
Cut to the product decision and a real route.
Close: “This is our reasoning. What would you challenge?” The story centers on the decision, not a generic company origin.