Briefing Room with Navid

Choose a route.

Start with Work, Notes, Letters, or direct context when the next step is unclear.

If sending context

Keep it to three things.

The email draft opens with these fields. They are there to reduce back-and-forth, not to turn this page into a form.

01

Business pressure

What decision or constraint is creating pressure?

Name the operating reason AI is being considered: speed, quality, review load, cost, customer experience, risk, or a product promise.

Clarify in Briefing Room
02

Current workflow

What work happens before AI enters the room?

Trace the repeated work, owner, handoffs, sources, judgment moments, current workaround, and failure paths before choosing model behavior.

Read workflow logic
03

Proof needed

What would make progress visible?

Set the smallest artifact, eval, case note, or reviewable output that can prove the workflow improved before claiming maturity or business impact.

Inspect proof records

Boundary

Static route guide, not a live assistant.

Boundary

No hidden retrieval, private sources, personalization, or account access.

Boundary

Specific company context should go through direct review.

Contact

Send the working context.

Send the business pressure, workflow, source boundary, or proof question. Best fit: hiring, AI roadmap, product-system work, and collaboration where evidence matters before claims.

Navid