🚀 Launch Control

A Product Launch Coordinator built with Microsoft Dataverse — from data model to agents to dashboard.

This repo is the companion to the Launch Control LinkedIn series by James Oleinik, Product Director for Microsoft Dataverse. Over 12 episodes (3/week for 4 weeks), we build a complete product launch coordination system from scratch — and open-source every line of code.

The Problem

Engineering teams are automating code reviews, DRIs, and incident response. But up the stack? Executives still want status. Cross-team projects still mean passing spreadsheets around. What if we applied the same agentic thinking to project coordination?

The Solution: Three Layers

┌──────────────────────────────────────────────────────┐
│  LAYER 3: MANAGEMENT & OPERATIONS                    │
│  Power App Dashboard  │  Python SDK/pandas  │  CLI   │
│  Admin Skills (agentic administration at scale)      │
├──────────────────────────────────────────────────────┤
│  LAYER 2: INTELLIGENCE                               │
│  Business Skills  │  Agents (Copilot Studio, Claude) │
│  Agent Flows  │  Custom Actions  │  BYO MCP Servers  │
│  MCP Server (universal) │ CLI │ SDK (coding agents)  │
├──────────────────────────────────────────────────────┤
│  LAYER 1: BUSINESS SYSTEM OF RECORD                  │
│  Dataverse Tables & Relationships │ Prompt Columns   │
│  Virtual Entities (real-time, no data replication)   │
│  Dataverse Intelligence (native M365 Copilot)        │
└──────────────────────────────────────────────────────┘

Episode Guide

Full series index with links to each episode's README, preflight, and scripts: episodes/README.md.

Each episode is also tagged in git: git checkout ep-09 to see the repo as it was at that episode's ship.

Quick Start

Prerequisites

• Python 3.10+ with pip install PowerPlatform-Dataverse-Client
• Node.js 18+ with npm install -g @microsoft/dataverse
• PAC CLI
• A Microsoft Dataverse environment with System Administrator role

Setup

git clone https://github.com/jamesoleinik/launch-control.git
cd launch-control
cp .env.example .env
# Edit .env with your Dataverse environment URL and credentials
pip install -r scripts/python/requirements.txt

To verify any episode is set up correctly, run its preflight:

python episodes/ep-09-the-dashboard/preflight.py

Repo Structure

launch-control/
├── episodes/                  # 12 per-episode folders (READMEs + preflights + scripts)
├── datamodel/                 # Table definitions, mappings, sample data
├── solutions/LaunchControl/   # Exported managed solution
├── business-skills/           # Launch readiness, escalation, status rules
├── data/knowledge/            # Sanitized KB articles for RAG
├── agents/
│   ├── launch-coordinator/    # Declarative Copilot Studio agent (Ep 6)
│   ├── launch-sentinel/       # Autonomous agent (Ep 7)
│   ├── launch-coordinator-py/ # Code-first agent (Ep 8)
│   └── agent-flows/           # Agent flow configurations
├── apps/launch-command-center/# Generative Power Apps page (Ep 9)
├── plugins/                   # Custom Dataverse plugins & actions
└── scripts/                   # auth.py + shared Python utilities

Key Themes

Skills All the Way Down

• Build skills — AI creates your data model, plugins, and agents
• Process skills — Business knowledge agents follow at runtime (portable across agent platforms)
• Operate skills — Scripted automation and agentic administration at scale

Master the Process in Dataverse

The launch spans GitHub, SharePoint, email — but mastering the business process state in Dataverse (think dynamic programming) means every agent, app, and Copilot reads the same truth.

Contributing

See CONTRIBUTING.md for how to fork and adapt this for your own scenario — customer onboarding, release management, incident response, or anything else.

See also

• CHANGELOG.md — what shipped in each episode (with git tags)
• SECURITY.md — how to report a security issue
• CODE_OF_CONDUCT.md — Microsoft Open Source Code of Conduct

License

MIT

Built by James Oleinik | Product Director, Microsoft Dataverse