Documentation Index
Fetch the complete documentation index at: https://docs.tryearmark.com/llms.txt
Use this file to discover all available pages before exploring further.
What a workflow actually is
A single meeting in Earmark gives you finished work from one call — a brief, a ticket, a recap. That’s an artifact. A workflow is what happens when you stop reinventing the prompt every time and start running the same task on every meeting of the same kind. Three pieces hold it together:| Piece | What it is | Where it lives |
|---|---|---|
| A saved template | The prompt that shapes the artifact | Templates or your own custom template |
| A pre-seed habit | Adding that task before the meeting starts | Before a meeting |
| A destination | Where the artifact lands after the call ends | Integrations, or paste into the tool your team already uses |
What the output looks like
Every workflow ends with the same kind of structured output for that meeting type. The headings differ by workflow; the property that matters is same shape, every call. A worked example for a weekly team sync:Why it matters
A single artifact ages out the moment the meeting ends. Action items get done or forgotten. The recap scrolls past in Slack. Next meeting, you start over. Repeatable patterns compound. Discovery call ten sharpens the picture from calls one through nine. Quarter three of 1:1 recaps shows trends in your team you’d miss week to week. Twenty stakeholder reviews expose the same blocker showing up under different names. Same shape, same place, every time, so the next person who needs the answer can find it.How to stand one up
Pick the meeting you already run most
Twice a week beats twice a quarter. Volume is what creates the compounding. Strategic-sounding workflows you’d touch four times a year don’t build the muscle.
Find the closest built-in template
Open the template library and pick the closest match. Run it in a real meeting before customizing.
Refine in the Composer, then save it
Use the Composer to shape the output to your exact format. When the prompt reliably gives you what you want, open the Composer menu and choose Save as template. Set visibility to Workspace if the whole team should produce the same shape. See Custom templates.
Pre-seed the next meeting
Add the saved template as a task to the next meeting of this kind before it starts. Earmark generates the artifact live during the call. See Before a meeting.
Pick a destination
Decide where the artifact goes after the meeting. Linear ticket? Cursor prompt? Slack post? See Integrations for formats Earmark generates with the right destination in mind.
Common starting points
| If you run… | Template to start from | Where the output goes |
|---|---|---|
| Sprint planning | Engineering Specs + Ticket Generator | Linear |
| Discovery or customer calls | Client Call + Topic Outcome Tracker | Slack, Notion, your CRM |
| Stakeholder reviews | Stakeholder Review + Executive Summary | Email to leadership |
| Design reviews | PRD Outline | v0 or meeting-to-prototype |
| Engineering syncs | Engineering Specs + Decision Summary | Cursor or Codex |
| Weekly team sync | Real-Time Meeting Minutes + Slack Update Post Generator | Slack |
| 1:1s | People and team meetings | Shared with your report same day |
Build the habit
The same template plus the same destination is the workflow. The habit is what makes it compound.- Before each meeting: pre-seed the same task. Five seconds of setup beats five minutes of post-meeting cleanup.
- Right after: send the artifact to its destination while the conversation is fresh.
- Weekly: scan your last few outputs. If they keep needing the same edit, update the template once.
- Monthly: revisit your personalization settings so tone and terminology stay current.
When the output needs a pass
The model gets things wrong. Every workflow assumes a few minutes of curation, not none.- Structure drift: headings missing or merged. Promote each item to its own line; if it happens every call, sharpen the template in the Composer.
- Over-confident tags or severity: downgrade unless the conversation supported it. After a few weeks of consistent curation, the model calibrates to the bar your team actually uses.
- Paraphrase instead of quote: replace from the transcript before sending to the destination — verbatim is the asset when your workflow depends on it.
- Three people, three prompts: outputs stop aggregating. Lock the template at the workspace level and update it deliberately.
What workflows don’t do
Each artifact is tied to the meeting it came from. Earmark refines outputs within a single meeting, not across many — so a question like “summarize every pain point we heard this quarter” isn’t a one-click action inside Earmark today. Practical workarounds:- Search across meetings with the command menu (
Cmd+K/Ctrl+K) to find specific discussions, decisions, or action items. - Aggregate in the destination tool. Twenty artifacts in the same Notion table is one filter away from a quarterly view. This is the payoff for the stable template shape.
- Use local transcript files with an external agent if you want a rollup you control end-to-end.
Guides
Step-by-step guides for specific meeting types. Each is an instance of the three-piece pattern above.Essentials
Start here for outputs every team needs — use ad-hoc Q&A when you need a grounded answer from a single call, or pre-meeting prep when you need context before the next one.Advanced meeting recaps
The universal default — turn any meeting into a readable recap, and know when to graduate to something more specialized.
Action items
Turn every conversation into a clean list of what needs to happen next, who owns it, and when.
Structured meeting notes
Turn every working meeting into decisions, todos, open questions, and a shareable summary — same shape, every time.
Ad-hoc Q&A
Ask any recorded meeting a question and get a grounded answer — patterns, verification, and cross-call workarounds.
Pre-meeting prep
Use your captured archive before the next meeting — open threads, commitments, and a recommended opening, not a cold start.
Product and engineering
From feature conversations to shipped work — specs, tickets, prototypes, architecture docs, and prompts for your AI dev tools.Meeting-to-prototype
Turn a feature conversation into a working prototype the same day — meeting transcript to paste-ready prompt for Figma Make, v0, or similar tools.
AI tool orchestration
Turn meetings into well-shaped prompts for Claude Code, Cursor, v0, Perplexity, and the rest of your AI tool stack — code, analysis, documents, and persistent assistants.
Meeting-to-PRD
Convert discovery, kickoffs, and design reviews into one-pagers, full PRDs, and technical specs — the document layer between research and tickets.
Roadmap synthesis
Synthesize customer signal, strategy, capacity, and competitive context into a defensible Now / Next / Later roadmap — and keep it current as the world changes.
Meeting-to-tickets
Convert refinement, triage, and escalation calls into tracker-ready stories, spikes, bugs, and epics — same day, with context intact.
Architecture documentation
Turn design reviews and technical debates into ADRs, SDDs, sequence diagrams, and integration specs — with alternatives, validation criteria, and source links.
Communication and leadership
Audience-tuned outputs for people who were not in the room — or who need the executive version.Shareable summaries
Turn meeting outputs into audience-tuned messages for people who were not in the room.
Slide decks
Convert strategy discussions, customer calls, and exec briefings into slide-by-slide content with narrative arc, speaker notes, and evidence — ready for visual layout.
Email follow-up
Turn customer calls and partner meetings into warm, specific, same-day follow-up emails that honor what was promised.
Leadership readouts
Produce weekly digests, business reviews, board pre-reads, and decision memos on a reliable cadence.
Go-to-market
Research, messaging, and pipeline intelligence from customer-facing conversations.Customer research
Turn discovery, usability, and win/loss calls into structured pain, asks, and verbatim quotes — call by call.
Customer onboarding and training
Turn training and implementation sessions into categorized follow-up queues, same-day customer emails, and cross-session implementation snapshots.
Marketing collateral
Turn customer calls, strategy discussions, and launch planning into GTM artifacts — capability briefs, customer-facing copy, launch announcements, and messaging pillars.
Sales calls
Turn every sales conversation into structured deal intelligence that lands in your CRM and survives pipeline review.
People and operations
Relationship meetings, hiring loops, repeatable demos, and operational knowledge your team runs on.People and team meetings
Run 1:1s, skip-levels, interviews, and standups so relationship conversations stop running on memory.
Hiring
Turn interview conversations into evidence-grounded scorecards your loop can calibrate on.
Demo and facilitator scripts
Turn excellent demos, workshops, and trainings into replicable scripts — beats, phrasing, recovery moves, and what not to do.
SOPs and playbooks
Convert operational discussions into SOPs, playbooks, runbooks, and policies your team executes against — with owners, review cadences, and audit trails.
Where to go next
- Before a meeting — pre-seeding so the artifact runs live
- After a meeting — generating audience-specific outputs from the same transcript
- Custom templates — visibility, sharing, and edit permissions
- Templates — built-in starting points and the template library