01  /  10 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  /  10 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 opportunity isn't a great conference.
It's to define and own the category of practical AI builders shipping real products.
North Star
POV AI Dev / DeepLearning.AI
03  /  10 Vision

The home for
AI builders.

Within three years, AI Dev becomes the default place where developers learn, ship, and launch — and the most important convening in the category.

3-Year Horizon
01 The flagship event for developers shipping AI products.
02 A year-round community, not an annual moment.
03 A global series across major tech hubs.
04 The default place companies launch.
End state An ecosystem, not an event
04  /  10 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
05  /  10 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
06  /  10 Economics

Designed as a
profitable business.

Three streams. One compounding platform. Built for recurring revenue, not one-off events.

01 / Tickets

Ticketing

  • Dev / Pro / VIP tiers
  • Volume + premium mix
  • Early-bird mechanics
02 / Sponsorship

High-margin, recurring

  • Real usage, not logos
  • Multi-event partnerships
  • Sponsor ROI as North Star
03 / Ecosystem

Content + community

  • Recordings + workshops
  • Year-round programming
  • Community extensions
Operating Principle Profitability by Year 2.
North-Star Metric Sponsor renewal rate.
Unit Economics Revenue per attendee > attendance.
P&L Discipline Margin per event, tracked.
Revenue + P&L Sponsors as customers
07  /  10 AI-Native Operating Model

Run the business
with AI inside.

The conference for AI builders should itself be operated with AI. Lean team. Higher output. Scalable globally.

01 / Audience growth

Targeted, not blasted.

AI-driven segmentation across the builder community. Personalized outreach by role, stack, and shipping stage — not generic email blasts.

02 / Speaker sourcing

Signal over rolodex.

Identify emerging voices through GitHub, papers, podcasts, and product launches. The next great speaker isn't on a list — they're shipping right now.

03 / Agenda design

Demand-driven programming.

AI-assisted track design based on registration signals, survey data, and topic momentum. Build the agenda the audience is actually asking for.

04 / Sponsor ROI

Real-time, not retro.

Live engagement dashboards. Lead capture and attribution at the booth. Sponsors see ROI during the event, which is how renewals happen.

05 / Operations

Run-of-show, automated.

AI handles comms, schedule changes, attendee Q&A, vendor coordination. Production team focuses on the moments AI can't.

06 / Post-event

Content as a flywheel.

Every session becomes searchable, summarized, clipped, and distributed. The event ships content for twelve months — not just three days.

Lean team · higher output · scalable globally Built with AI, not just about it
08  /  10 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 in 48 hours" tracks
04 Product demos with real usage
Format Leave with something working
09  /  10 Scale + Operating System

From flagship
to global platform.

Phases on top. The operating system underneath is what makes them possible.

Phase 01 Perfect the model One flagship. Tight ICP.
Establish format.
Phase 02 Validate repeatability 2–3 cities.
System travels.
Phase 03 Global rollout Local operators.
Central system.
OS / Sponsors

Recurring pipeline

Multi-event partnerships. Renewals, not cold pitches.

OS / Speakers

Speaker ecosystem

A bench of builders, not one-off outreach.

OS / Production

City-launch playbook

Documented model. Same system, different city.

Modular & repeatable Each event makes the next one cheaper, faster, better
10  /  10 First 90 Days

Execution roadmap.

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

Clarity → System → Scale
01 Day 0–30 Audit current event: P&L, audience, sponsors.
02 Day 0–30 Define ICP + positioning.
03 Day 30–60 Build sponsor framework.
04 Day 30–60 Lock ticketing + pricing.
05 Day 60–90 Design repeatable format.
06 Day 60–90 Prepare expansion roadmap.
90-day plan Build the system, then scale it
Navigate  ·  P Print
01 / 10