Chapter 1 · Changelog

The tarmac

On September 25, 2025, a delayed flight at DCA turned into the first working version of our AI-native platform. I built it myself, with AI, before anyone wrote a spec.

On Thursday, September 25, 2025, my flight was delayed. I sat on the tarmac at DCA for hours, on my way home from a conference.

I was frustrated. I was mad. I had just watched other companies present what they were doing with agentic development, and I wanted to know why we couldn’t move that fast.

So I opened my laptop and started building. I didn’t write a spec. I didn’t wait for a team.

Shipped

A prototype, built in Lovable.

I had started using Lovable on side projects, just to learn the tooling. On the tarmac and the flight home I built the front end of our solution the way I wanted it, designed around agents. It took a few hours.

I’m not an engineer, and I don’t know how to code.

I started with output from Devin and ran it through a custom GPT I had built, called AI Product Prompt Creator, to write the opening prompts. Then I iterated in Lovable until it worked, and I kept building all weekend.

I didn’t save the very first prompts. I wish I had. When our VP of Engineering asked for them, I could only share the later ones.

On Saturday, September 27, I posted it to the team as the “initial lovable mvp.”

Changed

Who builds the first version.

Before the tarmac, we had already put AI tools in every engineer’s hands. It helped. It fell short of the velocity I was reading about at AI-native companies. Our product team worked from long requirement documents and high-fidelity designs, and engineering built what the documents said.

On the tarmac I skipped all of that. The CEO built the first version, with AI, during one flight delay.

The team didn’t wait either. About 30 hours after I started, there was a team around the build. Our VP of Engineering opened a Slack channel for the project at 9:58 pm on Friday, September 26, and started adding platform goals to a shared doc. The channel stayed busy all weekend.

A working prototype changed the conversation. People build on a prototype.

Numbers

  • Days from the tarmac to a working prototype in front of the team: 2 (September 25 to 27).
  • Hours until the project had its own channel and shared doc: about 30.
  • AI tools in the chain that wrote the first version: 3 (Devin, a custom GPT, Lovable).
  • Specs written before the prototype: 0.

Next

Four days after the tarmac, I demoed the prototype to the whole company. I used the same meeting to launch the rebuild. My question to the room: if I can build this in days, what are our competitors doing with full engineering teams?

Lesson: Build the first version yourself, then let the team build the real one.

AR, Ashley Rose

All notes