
Preflight is the delivery OS for software projects. From intake gap analysis to capability mapping, journey drafting, and quality commitments — every stage structured, validated, and gate-approved before your team builds on it.
Built on open RFC schemas. Integrates with Jira, Miro, Figma, and your existing stack.

Protocol, not just tooling
Preflight is built on open RFC schemas — a structured specification protocol for software delivery decisions. Every artifact your team produces is machine-readable, versioned, and traceable across the full chain.
Most tools give you a place to store information. Preflight gives you a protocol for producing it — so that when your team commits to scope, capability, and quality, those commitments are grounded in a validated chain, not a shared document and a handshake.
The SOW looked fine. The proposal was thorough. Six weeks into development, the team discovers the integration wasn't defined, the timeline assumed work that wasn't in scope, and two sections contradict each other.
These weren't surprises. They were in the document. Nobody had time to find them.
Run a PreflightPreflight analyzes your project proposal and automatically generates a comprehensive risk assessment.
Project intake analysis
6 warnings • 2 recommended
Every analysis produces a structured report highlighting delivery risks before kickoff.
Preflight Report
Project Readiness: 72%
Gate Status
Upload a SOW, proposal, or discovery document and see what issues Preflight detects.
Drag & drop here
or browse files
PDF, DOCX, Markdown · Up to 5 MB
A structured artifact chain — from intake through quality commitments — where every output is validated against every other and every gate is earned, not assumed.
Stage 1 output: what's established, what's missing, and the authoritative scope boundary for everything that follows.
Stage 2 output: the domain model and functional capability set — what the system must do, who does it, and what data it touches.
Actor-led, capability-grounded flows — the end-to-end paths your team builds stories and acceptance criteria from.
Measurable NFR baselines — performance, accessibility, security, reliability — tied to scope tier and specific capabilities.
Cross-artifact consistency checks that fire automatically: broken references, coverage gaps, and constraint violations surfaced as typed blockers.
At every stage gate, Preflight checks the full artifact chain. Your team reviews, resolves, approves — or documents why a risk is accepted.
Pilot your first project free. No tiers, no credit card, no commitment. When you're ready to roll it out to your team, talk to us.
Built by Michael Smith, author of The Technical Leader's Field Guide. Preflight is designed around the real struggles of software delivery — scope disputes, margin erosion, and projects that start broken before anyone writes a line of code.
Pilot your first project free. Talk to us about your team.