How to brief an AI agent studio (email template)
Copy-paste brief template for a first contact with an AI agent studio: workflow, systems, volume, risks, sensitivity, approver, and safe attachments.
Written by Northstar
Northstar is an AI agent systems studio. Alex leads engineering and product systems; Jordan leads operations and workflow fit. We ship production agents inside tools teams already use.
Alex Morgan · LinkedIn · Northstar
Direct answer
Northstar recommends keeping the first note short.
The goal is not to impress a studio.
The goal is to give it enough context to ask good scoping questions.
Brief an AI agent studio with one workflow, the systems it touches, typical volume, failure cases, and the exact definition of success.
If the task is still a deterministic form, queue, or lookup, do not force an agent brief.
OpenAI's practical guide is useful here because it frames agents as the right choice when rule-based approaches are no longer enough.
When to use this page
Use this page when you want a first-contact email or a lightweight kickoff brief.
Use how to hire an AI agent agency when you are already running a full vendor-selection process.
Use how to write AI agent RFP when procurement needs a formal package.
Copy-paste email template
Subject: Pilot brief - {workflow}
Body:
- We want help with {workflow}.
- Today the workflow runs through {tools and systems}.
- The weekly or monthly volume is {volume}.
- The cases that always need a human are {exceptions}.
- The risky actions that must be gated are {risky actions}.
- The data sensitivity level is {public, internal, confidential, restricted}.
- The internal owner or approver is {name or role}.
- A successful pilot means {success definition}.
- We want to start by {timeline or first call date}.
- Our budget band is {optional budget band}.
- If your procurement process requires NDA before sharing sensitive examples, we can do that.
Northstar recommends keeping the body short.
Northstar's default is to keep the first-contact brief to one page.
The goal is to make the studio ask the right follow-up questions.
What to attach
| Attachment | Why it helps |
|---|---|
| Redacted examples | Shows the real input and output shape without leaking secrets. |
| Field list | Lets the studio map structured data into the workflow. |
| Role map | Clarifies who approves what. |
| Current SOP or checklist | Shows the present process and where it breaks. |
| Volume snapshot | Helps the studio estimate capacity and model usage. |
If you have no clean attachments yet, send only the email body.
Do not stall the conversation waiting for a perfect packet.
What to answer if they ask for more detail
Answer in the same order you wrote the brief.
Start with the workflow.
Then explain the systems, the exceptions, the risky actions, the data sensitivity level, and the named owner.
If the studio asks for examples, send only redacted examples that match the exact workflow you want to scope.
If the studio asks for a broader vision, keep that separate from the first brief so the first call stays narrow and useful.
What not to send
- A wishlist of twenty agents.
- Secrets, tokens, or raw credentials.
- A vague "make us more efficient" note.
- Screenshots without context.
- A budgetless note if your procurement process needs a range.
If the studio cannot understand the workflow from what you sent, the brief is too vague.
What to ask the studio to include
Treat the reply as useful when it includes:
- Clarifying questions about steps, tools, exceptions, and approvals.
- A pilot boundary that names one workflow.
- An acceptance test draft.
- A logging and monitoring outline.
- A handoff and support plan.
- A clear note on what is out of scope.
That is the difference between a real scoping conversation and a sales deck.
Why this works
IBM says deployment is about moving a prototype into real-world operation.
Dataiku's production-ready guidance adds that live systems need monitoring, access controls, rollback, and defined success metrics.
NIST's AI Risk Management Framework frames the work as trust and risk management, not novelty.
OWASP's 2026 agentic Top 10 gives the current security language for autonomous agent systems.
That is why the brief should be concrete enough to support a pilot, not just a pitch.
How Northstar fits
Use this page to get a usable first response.
Use how to choose a production AI agent partner when you are already comparing teams that can ship.
Use solutions if you want to start from one real workflow and move toward a scoped engagement.
Related reading:
FAQ
Northstar's default is to include a budget band when procurement needs one. Do not force a fixed quote before scope is clear.