Pick a Squad Demo
Each demo is a runnable script that drives one workload end to end from the single
/squad entry point — research → plan → implement → review underneath, with a
human gate on every action that matters. Choose a chevron above, or pick a card below; the
walkthrough opens on its own page so you can run it beat by beat.
The demos#
Azure Squad
One Azure workload from cost estimate through architecture, IaC, a governance-checked deploy, as-built documentation, and diagnosis. MCP-optional with graceful fallbacks; every deploy stays behind a human gate; as-built and diagnose are strictly read-only.
Technical · Azure · profile=azureMigration Autopilot
A single autopilot request plans a Contoso Inc. → Azure migration end to end — research, plan, council, Bicep IaC, cost, security, and HLD/LLD diagrams — then the review gate catches five production blockers and stops, escalating instead of shipping broken work.
Technical · Migration · mode=autopilotProduct Squad
One business idea from discovery through a requirements document, a roadmap and backlog, a cheap validation experiment, a readiness review, and a board-ready deck. No cloud, no code, no spend — built to pitch to a non-technical audience.
Non-technical · Product · profile=productModernize .NET
A single autopilot request upgrades a legacy app in place from .NET Framework 4.8 to .NET 10 — research, a pre-implementation council, a security Risk Gate a human approves, the SDK-style upgrade, and a review loop that remediates every finding to zero before Go.
Technical · Modernization · mode=autopilotWant to run the full arc yourself? The HVE Squad hands-on workshop turns the Product, Migration and Modernize .NET demos into one guided exercise on a ready-to-download starter solution. A product squad writes the requirements and a backlog tagged by delivery track, with one Git-tagged release per track. You choose the tracks — Azure, .NET and Power Platform — and after promotion to a federation each track's squad builds from its own release, independently of the others. It always targets the latest HVE Squad release, with progress tracking, review keys and an optional Azure DevOps step.
How to read a demo#
Both demos share the same shape, so once you have run one the others feel familiar:
| Section | What it gives you |
|---|---|
| What you are proving | The narration backbone — each beat mapped to the squad role that owns it. |
| Before you start | Prerequisites and the safe, zero-spend way to run it live. |
| Beat 0 → Beat N | The runnable /squad requests, in order, with what to narrate at each. |
| The one-request version | The same arc as a single autopilot run that stops only where it must. |
| Failure-safe fallbacks | What to do when tooling hiccups, so the narrative never breaks. |
Same methodology, different audience. The Azure demo proves the squad on infrastructure; the Product demo proves the same research → plan → build → review spine on non-technical business work. Pick the one that matches who is in the room.