Use case · Your team · Sales prep
Build an account brief from emails, meetings, and notes
You've had three threads with this account. Two meetings. Notes you took on a flight. Magnis pulls all of it into one brief — stakeholders, pain points, talk track, open questions — and runs in the time it takes to walk to the call.
Demo workspace — uses simulated UrbanGrid Logistics account data. Connect your Gmail and Calendar to run the same brief on your own accounts.
Step 1
Describe the task
One line. Magnis figures out what UrbanGrid is, what tomorrow's call is, and what you should know going in.
You ask
Build a crisp UrbanGrid account brief for tomorrow's call.
Step 2
Give Magnis context
Magnis reads your project graph: UrbanGrid is linked to Ethan Brooks (Director of Dispatch), the prep meeting on tomorrow's calendar, the incident-triage notes you took last week, and three email threads.
Required context
- ·Project entity for UrbanGrid Account Brief
- ·Email threads with the company tagged via Gmail source
- ·Calendar event for tomorrow's call linked to the project
Optional context
- ·Notes attached to the project (incident triage)
- ·CRM stage field — opportunity value, deal stage
- ·Triggers — auto-run brief 1h before any call
Step 3
What Magnis creates
Five sections. Every claim links back to the source — meeting, email, or note.
Company profile
Last-mile logistics company evaluating AI-assisted incident triage. Mid-market — <500 fleet vehicles, distributed dispatchers across 4 metros. Pilot conversations active for ~6 weeks.
Key stakeholders
- Ethan Brooks · Director of Dispatch · last email 4d ago, requested incident triage focus for this call
- Sara Patel · Lumen Labs · attending as product lead
Pain points
- ·Dispatcher handoff visibility — incidents drop between shifts
- ·No unified summary of unresolved escalations day-over-day
- ·Current tool: ad-hoc Slack threads + Google Sheet
Suggested talk track
- Open with their dispatcher-handoff pain — show you read the last email
- Demo the incident-triage flow on Magnis (use sample event log)
- Pitch trigger-based escalation summary as a 30-day pilot
- Ask for their current SOC vendor — likely overlap with our integrations
Open questions
- ?What does success look like for the pilot — incidents resolved? handoff time reduction?
- ?Who else from their side is involved — VP Ops? CIO?
- ?Procurement timeline — same as Meridian (Friday)?
Step 4
Follow-up prompts
Brief everyone tomorrow
“Run this brief for every account on tomorrow's calendar. Email me the summary tonight.”
Brief on a trigger
“Set a trigger — generate the brief automatically 1 hour before any meeting tagged with a project.”
Push to call notes
“After the call, append my notes to this brief and update the project state.”
Step 5
Tips & troubleshooting
Brief depth scales with the call.
For a discovery call — short brief (3-4 bullets per section). For a renewal — Magnis pulls 12 months of context. Same prompt, depth follows project age.
Open questions matter as much as answers.
Magnis flags what it couldn't resolve — gaps in your context. Treat that section as the prompt for your call.
Provenance every claim.
Click any line in the brief — Magnis jumps to the source email, meeting, or note. No hallucinated stakeholder names.
Brief every account on your own data.
Connect Magnis to your Gmail and Calendar — same brief structure, your accounts, on your machine.