Setting up custom templates is the only way to make Fireflies actually useful for different teams. Generic summaries waste time.
Here’s my quick setup for sales, project review, and sprint planning.
**For Sales Calls:**
* Track: Customer pain points, next steps, pricing discussions.
* Action items: Assign with a deadline directly in the note.
* Summary format: One-line "deal status" at the top (e.g., "Qualified - Proposal Sent").
**For Project Reviews:**
* Track: Decisions made, blockers identified, resource requests.
* Action items: Tag by department (engineering, design).
* Summary format: Bulleted list of key decisions only.
**For Sprint Planning:**
* Track: Ticket numbers, scope clarifications, volunteer assignments.
* Action items: Link to Jira/GitLab issues in the note.
* Summary format: Two sections: "Committed Tickets" and "Open Questions."
Pro tip: Create a separate Fireflies workspace for each meeting type. Apply the template at the workspace level so it auto-applies to all meetings in that category. No more manual template selection.
Ship fast, review slower
Absolutely spot on about the separate workspaces, that's a game-changer for automation. I'd just add one thing from our sales team's experience.
For the sales call template, we also force-include a "Competition Mentioned" field, even if it's just a "None discussed." It's shocking how often that gets glossed over in a generic summary, but seeing it pop up in every single meeting note makes the team consistently ask the question. Over time, it builds a really valuable competitive intel log right in the CRM.
And I love your sprint planning format. We do something similar, but we also add a "Risks & Dependencies" line item right under "Open Questions." It helps preempt the "wait, this ticket is blocked by another team" discovery two days into the sprint.
hannah
Great breakdown of the core structure for different meetings. The separate workspace trick is solid advice - it prevents template bleed and saves a ton of admin time.
I'd gently suggest one tweak on the action items, particularly for project reviews. Tagging by department is useful, but it can sometimes let items fall through the cracks if a department is just meant to be "informed" versus "responsible." We've had better luck using a RACI code right in the action item title, like "[R] Devin: Update spec by Friday." It adds a second to set up, but it eliminates the "I was just tagged for visibility" confusion later.
Your sprint planning format is almost identical to what our product team uses. It works.
Keep it civil, keep it real
Love that you start with the one-line deal status. It forces the whole team to get aligned on the most important metric immediately.
The separate workspace trick is clutch. We tried applying templates per meeting at first and the manual step killed adoption.
One thing we added to our sales template after a few months: a "Key Quotes" section. It captures the prospect's own words about their pain point or excitement. It's pure gold for the next follow-up email or proposal intro. Generic summaries never pick the right quotes, but a custom field reminds everyone to listen for it.
The "Key Quotes" field is an excellent addition. It turns qualitative data into a repeatable process. We structured ours to capture not just the quote, but the context that triggered it. For example, the template prompts the note-taker to briefly note the question or topic that preceded the quote. This helps our sales managers coach on which discovery questions are most effective at eliciting those powerful statements.
I'd add a workflow note: we push that "Key Quotes" field directly to a custom object in Salesforce via Zapier. This creates a timeline view of a prospect's own language across every touchpoint, which is incredibly powerful for deal reviews.
connected