nClouds | All-Hands · AI Native
nClouds All-Hands · Thought Leadership

AI Native — Laying the Foundation

Defining what AI native means — for an organization, for a person, and for the practice we're standing up at nClouds. Not a pitch. The vocabulary first.

May 28, 2026 8 minutes · 5–10 min cap Patrick Falvey + Jason Martin
Three phrases to land

The vocabulary we're teaching today

These are the lines that should still be quoted in the hallway after the talk ends.

01

"Cloud native was about where compute runs. AI native is about where decisions get made."

The term-distinction
02

"The fabric is the codified business processes, and the agents executing them autonomously, with humans in the loop where necessary."

Patrick's definition (5/27)
03

"A competitor with their own agents and your intelligence layer would eat you alive."

Why the layer must be protected
Narrative arc

The 8 sections

Hook → why this term → attributes (org + individual) → intelligence layer + fabric → external exemplars → internal proof → forward-look close.

#
Section
Speaker
Time
1
HookSet the contract. Pull the room in.
Jason
0:45
2
Why "AI native"What makes this term different from cloud / digital native
Patrick
1:15
3
Attributes of an AI-native orgThree attributes: work decomposition, reasoning as primitive, the intelligence layer
Patrick
1:30
4
Attributes at the individual level"Am I AI native as a person?" — Jason answers from the builder's seat
Jason
0:45
5
Intelligence layer + fabricPatrick anchors the layer (the moat). Jason defines the fabric — he's building it.
Patrick+Jason
1:15
6
External exemplarsRamp (product/ops AI-native) and Block (engineering AI-native)
Jason
1:30
7
Internal proof + Alex tee-upOperator Fabric, customer agents, hand the baton to Alex
Jason
0:30
8
Forward-look closeName the practice. Give the room one ask.
Patrick
0:45
Σ
Total runtime
~8:15
Section deep-dive

What each beat actually does

The job each section is doing in service of the foundation-laying goal.

01

Hook

Jason 0:45
Show-of-hands opener on who's heard "AI native" vs "cloud native." Plants the contract: "we want to spend the next eight minutes telling you why that matters." Inviting, not aggressive. The job: get permission to teach.
02

Why "AI native" — not "cloud native"

Patrick 1:15
Position AI native in the lineage of "digital native" and "cloud native," then land the distinction: "cloud native was about where compute runs. AI native is about where decisions get made." The job: make the term feel inevitable, not invented.
03

Three attributes of an AI-native org

Patrick 1:30
Three attributes — each a single sentence with a one-line elaboration:
  • Work is decomposed for agents. Every team asks weekly: where could an agent take the first pass?
  • Reasoning is a primitive. In the foundation, not bolted on.
  • The intelligence layer is protected. Crown-jewel posture.
The job: give the audience the litmus test they'll start applying to themselves and their teams tomorrow.
04

Individual AI native — "Am I AI native as a person?"

Jason 0:45
Kelly's explicit ask, answered from Jason's builder perspective — his own practice (knowledge-base build overnight) as evidence. Three signals: reach for an agent before a colleague when the problem fits; write prompts before code or docs; articulate the decisions you'd never delegate. The job: make this personal and embodied, not abstract.
05

Intelligence layer + fabric

Patrick+Jason 1:15
Two terms, defined cleanly. Patrick anchors the intelligence layer = codified business state (the moat). Jason takes the fabric = layer + agents executing autonomously with humans in the loop — he's the one building it. Land that nCite is literally our fabric as the implementation marker. The job: give the audience a shared mental model for everything we ship next year, with the handoff itself signaling builder-and-strategist together.
Patrick Intelligence layer · the moat 0:40
Jason Fabric · nCite as implementation 0:35
06

External exemplars — Ramp + Block

Jason 1:30
Two companies. Ramp: AI-native fintech where agents handle anomaly detection, expense categorization, vendor research — finance ops scales without headcount. Block: open-sourced an internal agent framework (Goose); engineers use agents as collaborators, not assistants. Common thread: neither has "an AI team" — AI is the layer underneath every team. The job: make AI native real, not theoretical.
07

Internal proof + Alex tee-up

Jason 0:30
Operator Fabric is deployed in our own AWS. Customer agents shipping. Mention Alex's later talk on Insights and the project health dashboard — "same pattern." The job: claim the proof without dwelling on it. Next month's all-hands will go deep on the how.
08

Forward-look close

Patrick 0:45
Name the practice: AI Native Practice. Frame it as direction, not a side bet. Tee up next month's deep-dive on methodology. End with one ask: start using the vocabulary, and start asking "where could an agent take the first pass?" The job: leave them with a habit, not a slogan.
Contingency

What to cut if we're running long

In order. Doing all four buys back ~95 seconds and lands the talk at ~6:45.

  1. Drop the "digital native" sidebar in Section 2. Go straight from "AI native is about something different" to the cloud-vs-AI-native contrast.
    Saves ~20 sec
  2. Drop Block in Section 6. Ramp alone carries the "AI native company" picture.
    Saves ~30 sec
  3. Collapse Section 4 to one sentence. "And at the individual level — you reach for an agent before a colleague when the problem fits, and you can articulate the decisions you'd never delegate."
    Saves ~30 sec
  4. Drop the "vocabulary alignment" line in the close. Just hit the "ask an agent to take the first pass" ask.
    Saves ~15 sec

Two more views

The full speaker-by-speaker transcript with stage directions and timing, plus visual companions — diagrams, comparisons, and the industry data behind the points.

Open the transcript →   See the visuals →