Adopt AI-SDLC with the people who built it
The framework is free. These three fixed-scope engagements get it running in your organization.
Delivered by the maintainer of AI-SDLC, who wrote the framework and runs these engagements personally.
AI SDLC Audit
A clear picture of how work moves from idea to production today, and where AI agents can safely take over.
For
Engineering leaders who are adopting AI coding tools without a shared view of the lifecycle, the rework it creates or the governance it needs.
What you get
- Stakeholder and team interviews
- A map of your software lifecycle as it actually runs
- Rework and review bottlenecks, measured
- Governance gaps against the EU AI Act, NIST AI RMF and ISO 42001
- A prioritized roadmap with the first pilot scoped
Duration
2 to 3 weeks, fixed fee
North Star Pilot
AI-SDLC running on one real team, end to end, with the evidence to decide on a wider rollout.
For
Teams ready to move from assisted coding to governed, autonomous delivery, with an audit or equivalent baseline in hand.
What you get
- A Definition-of-Ready gate on incoming work
- Autonomous dispatch to developer agents in isolated environments
- Independent AI review with signed attestations
- Quality gates and autonomy policies tuned to your risk
- Before and after metrics
- A rollout plan for the next teams
Duration
6 to 8 weeks, one team
Decision Context Engine
The context layer that lets agents make decisions the way your organization would.
For
Organizations whose agents need durable knowledge of the business, not just the codebase, to prioritize and decide well.
What you get
- Ontology and taxonomy for your domain
- Hybrid retrieval with an evaluation harness
- Persistent agent memory
- Signal ingestion into a priority score
- Integration with the DoR gate
Duration
Scoped from the Audit or Pilot
The engagements build on each other. Most teams start with the Audit, which maps where the lifecycle leaks and scopes a first pilot. The North Star Pilot then proves the framework on one team with before and after numbers. The Decision Context Engine is scoped from what the Audit or the Pilot surfaced, so it comes last. You can enter at the Pilot if you already know your bottlenecks.