frontier-consultancy-public

The client — Nordwind Aerospace

You are walking into this exercise as a solution architect on a new partner-consultancy engagement.

Your firm was introduced to Nordwind Aerospace two weeks ago through a warm reference from their chair. Last Thursday you ran a 90-minute discovery call at their Stockholm office. You took scrappy notes. Those notes are in meeting-notes.md. Read them now.

The CTO, Ingrid Aslaug, asked you one thing: come back with a one-pager the board can read, answering “can we just use ChatGPT for this, or do we need something more?” — and being specific about what Nordwind should buy, build, or stop doing.

The board meets in ten days. You have about fifteen minutes before your next call to produce a draft worth sending to Ingrid tonight.

Your deliverable is brief.md at the repo root, based on the structure in brief-template.md.

Ground your brief in real Microsoft guidance

You are going to use the Microsoft Learn MCP from Copilot so the brief is grounded in current, verifiable Azure documentation — specifically:

• Azure Landing Zone for AI (aka.ms/aiazurelandingzone)
• Microsoft Agent Framework (learn.microsoft.com/agent-framework)

You do not need to know these two topics cold. That is the point of the exercise — Copilot + Learn MCP bring the ground truth. Your job is to frame it for Nordwind.

What makes a good brief

• Answers Ingrid’s question in the first two sentences. No preamble.
• Talks to Nordwind specifically. “You have 18 satellites and 6 ops engineers” beats “satellite operators typically have…”.
• Three honest next steps. Not ten. Not “do everything”. Specific, sequenced, costed in weeks.
• Says what not to do. A consultant who never says “no” is a bad consultant.

Go to SETUP-tier1.md or SETUP-vscode.md to wire up your tools, then run the exercise.