Federal AI/AI Integration Lead planner

Your first ninety days as the AI Integration Lead.

The Department of War's 2026 AI strategy put an AI lead in every component with a mandate to move at the speed of the mission, and the Air Force's April strategy asked for AI in every function, at every security level. Most of those leads inherited a chat platform, a mandate, and no engineers. This planner turns your component, domain, boundary, and team into a 30/60/90 plan with the six answers your program office will ask for, the first-win candidates for your domain, and the acquisition path to fund it. Deterministic, in your browser, nothing stored.

Public, non-sensitive input only · Adapt to your component's guidance

Planner

Eight inputs. One plan your chain can read.

Describe the mission, not the program. The plan follows the CSIS six questions for DoD AI program managers, the DoD data, analytics, and AI adoption strategy's hierarchy of needs, and Andrew Ng's first-visible-win discipline, applied through the Cleared FDE Standard's day-90 acceptance instrument.

OutputThe 30/60/90 plan, first-win candidates, the six answers, and the acquisition path appear here.

What enterprise generative AI gives you, and what it does not

GenAI.mil and agency platforms put a governed chat window in front of every user, and that is the right baseline. They do not connect a recurring decision to its system of record, keep an evidence trail of who asked and who approved, or run inside a disconnected enclave. That integration layer is the seat this planner is built around, and the reason the Cleared FDE model exists.

Cleared forward-deployed engineering

The seat inside the boundary, filled.

Thirty minutes with a technical lead: the decision, the boundary, the badging timeline, and a fixed-price 90-day scope with kill criteria.