01  /  09 A Point of View
For DeepLearning.AI  ·  AI Dev Conference

Not a conference.
A business line.

Reframing AI Dev as a scalable, revenue-generating platform at the center of the AI builder ecosystem — and a category waiting to be owned.

Charlotte Prepared for the COO  ·  2026
Vibe-coded Built with Claude
02  /  09 The Thesis

Event
Business line.

Treat AI Dev like a product, not a project. The event is the artifact; the business is the system around it.

The goal isn't a great conference.
It's to own the category of practical AI builders shipping real products.
North Star
POV AI Dev / DeepLearning.AI
03  /  09 Market

A clear gap in the
AI event landscape.

The major events serve research, theory, and platform launches. None of them serve the people actually shipping.

NeurIPS Academic / Research
ICML Technical / Theoretical
Google I/O Platform-driven
Builders shipping AI products ↳ Open
Competitive Landscape The category is unclaimed
04  /  09 Audience

Who this is for.

Sharp ICP. Sharp value prop. Everything else flows from this.

Learn Build Ship
Not passive talks.
Not high-level inspiration.
01 AI engineers
02 Product builders
03 Startup founders
04 Technical operators
Product definition Utility > inspiration
05  /  09 Economics

Three revenue streams.
One compounding platform.

Designed for recurring revenue, not one-off events.

01 / Tickets

Ticketing

  • Dev tier
  • Pro tier
  • VIP tier
02 / Sponsorship

Real usage, not logos

  • Product demos
  • API integrations
  • Builder partnerships
03 / Ecosystem

Content + community

  • Recordings
  • Workshops
  • Community extensions
Revenue model Recurring, not transactional
06  /  09 Experience Design

Why developers
will choose this.

The format is the differentiator. Builders pay for environments where they leave with something working — not a notebook full of quotes.

Utility > Inspiration
01 Hands-on build sessions
02 Live coding environments
03 "Ship something in 48 hours" tracks
Format Leave with something working
07  /  09 Scale

From flagship
to global platform.

Built on modular, repeatable systems — not heroics.

Phase 01 Perfect the model One flagship event. Tight ICP.
Establish the format.
Phase 02 Validate repeatability 2–3 cities.
Prove the system travels.
Phase 03 Global rollout Platform mode.
Local operators, central system.
Scale model Modular & repeatable
08  /  09 Operating System

Systemizing growth.

Treat events like a product, not a project. The job is to build the engine — the events come out the other end.

Each event makes the next one cheaper, faster, and better.
01 / Sponsors

Recurring pipeline

Multi-event partnerships. Renewals, not cold pitches.

02 / Speakers

Speaker ecosystem

A bench of builders, not one-off outreach every cycle.

03 / Production

Repeatable model

Documented playbook. Same system, different city.

Operating system Product, not project
09  /  09 First 90 Days

Immediate focus.

Less talking. More framing, structuring, and pricing. The first ninety days are about getting the operating system on paper.

Day 01 → Day 90
01 W 1–2 Audit the current event.
02 W 2–4 Define ICP + positioning.
03 W 4–6 Build sponsor framework.
04 W 6–9 Lock pricing model.
05 W 9–12 Prep expansion roadmap.
90-day plan Build the system, then scale it
Navigate  ·  P Print
01 / 09