Ready-made mandates
Start with the outcome you need. Each Recipe defines the work, what it uses, and the boundaries it keeps.
Prepare a proposal from a labeled customer quote request.
Unify scattered operating signals into a faithful weekly digest.
Qualify current prospect signals against CRM evidence.
Build traceable dispute evidence packs from commerce records.
Prepare complex renewal portfolios from overlapping CRM evidence.
Test whether releases explain emerging customer problems.
Compress long support histories into decision-ready escalation briefs.
Connect order, support, and operations signals into early risk warnings.
Find material mismatches across CRM and payment records.
Turn a dense calendar into decision-ready preparation.
Track and compare fast-moving product launch signals.
Audit whether implementation work covers each design state.
Map archived assets to campaign requirements.
Review portfolio capacity and workload from Asana.
Audit Airtable operations data before acting on it.
Prepare board agendas from Outlook context.
Reconcile Jira, Notion, and Figma release evidence.
Surface emerging delivery risk from Linear activity.
Compare agreements across document repositories.
Triage incoming customer escalations with product context.
Reconcile company context into an executive brief.
Turn the calendar into a focused, context-aware daily agenda.
Keep incident timelines and stakeholder updates accurate and reviewable.
Create evidence-led account briefs before customer conversations.
Turn customer messages into evidence-weighted product themes.
Turn new GitHub issues into consistent, reviewable triage.
Build executable weekly content calendars from campaign briefs.
Find defensible insights in small CSV exports.
Shape ambiguous choices into decision-ready memos.
Convert raw meeting notes into accountable follow-up.
Prepare a proposal from a labeled customer quote request.
Outcome
Turn a labeled quote-request email into a ready-to-review proposal package.
Delivery
Markdown
Published by
@fkrein1
Unify scattered operating signals into a faithful weekly digest.
Outcome
Create a dense cross-channel operations digest from meetings, repository work, and discussion.
Delivery
Markdown
Published by
@crewhelm-stress
Qualify current prospect signals against CRM evidence.
Outcome
Research ambiguous account signals and compare them with current CRM context for prospecting.
Delivery
Markdown
Published by
@crewhelm-stress
Build traceable dispute evidence packs from commerce records.
Outcome
Assemble long-form payment dispute evidence from transaction and storefront records.
Delivery
Markdown
Published by
@crewhelm-stress
Prepare complex renewal portfolios from overlapping CRM evidence.
Outcome
Prepare enterprise renewal reviews from overlapping CRM histories and calendar commitments.
Delivery
Markdown
Published by
@crewhelm-stress
Test whether releases explain emerging customer problems.
Outcome
Correlate release changes with customer reports across two support systems and GitHub.
Delivery
Markdown
Published by
@crewhelm-stress
Compress long support histories into decision-ready escalation briefs.
Outcome
Summarize unusually long support histories into escalation facts, uncertainty, and next action.
Delivery
Markdown
Published by
@crewhelm-stress
Connect order, support, and operations signals into early risk warnings.
Outcome
Correlate storefront orders, support tickets, and operational chatter for emerging risks.
Delivery
Markdown
Published by
@crewhelm-stress
Find material mismatches across CRM and payment records.
Outcome
Reconcile long CRM opportunity records against payment evidence to identify possible leakage.
Delivery
Markdown
Published by
@crewhelm-stress
Turn a dense calendar into decision-ready preparation.
Outcome
Prepare unusually dense executive calendars with context, decisions, and follow-up drafts.
Delivery
Markdown
Published by
@crewhelm-stress
Track and compare fast-moving product launch signals.
Outcome
Compare crowded launch signals across the web, repositories, and internal discussion.
Delivery
Markdown
Published by
@crewhelm-stress
Audit whether implementation work covers each design state.
Outcome
Compare detailed Figma states with implementation issue coverage.
Delivery
Markdown
Published by
@crewhelm-stress
Map archived assets to campaign requirements.
Outcome
Map campaign plans to archived assets and identify coverage gaps.
Delivery
Markdown
Published by
@crewhelm-stress
Review portfolio capacity and workload from Asana.
Outcome
Analyze cross-project workload and propose a balanced review plan.
Delivery
Markdown
Published by
@crewhelm-stress
Audit Airtable operations data before acting on it.
Outcome
Audit wide operational tables for data quality, bottlenecks, and exceptions.
Delivery
Markdown
Published by
@crewhelm-stress
Prepare board agendas from Outlook context.
Outcome
Prepare a compact daily board agenda from Outlook context and public evidence.
Delivery
Markdown
Published by
@crewhelm-stress
Reconcile Jira, Notion, and Figma release evidence.
Outcome
Reconcile launch plans, delivery issues, and designs into a release risk map.
Delivery
Markdown
Published by
@crewhelm-stress
Surface emerging delivery risk from Linear activity.
Outcome
Detect sprint risk from incoming Linear issues and current workload.
Delivery
Markdown
Published by
@crewhelm-stress
Compare agreements across document repositories.
Outcome
Compare long agreements across active and archived document stores.
Delivery
Markdown
Published by
@crewhelm-stress
Triage incoming customer escalations with product context.
Outcome
Triage urgent customer email against related product work and evidence.
Delivery
Markdown
Published by
@crewhelm-stress
Reconcile company context into an executive brief.
Outcome
Combine scattered executive context into a concise weekly decision brief.
Delivery
Markdown
Published by
@crewhelm-stress
Turn the calendar into a focused, context-aware daily agenda.
Outcome
Prepare a short daily agenda with meeting purpose, context gaps, and the most useful preparation prompts.
Delivery
Markdown
Published by
@crewhelm-labs
Keep incident timelines and stakeholder updates accurate and reviewable.
Outcome
Maintain a concise incident brief from a noisy response channel and prepare reviewable stakeholder updates.
Delivery
Markdown
Published by
@crewhelm-labs
Create evidence-led account briefs before customer conversations.
Outcome
Prepare an account brief from CRM evidence and public company context before a sales conversation.
Delivery
Markdown
Published by
@crewhelm-labs
Turn customer messages into evidence-weighted product themes.
Outcome
Synthesize a bounded stream of customer feedback into themes, evidence, opportunities, and open questions.
Delivery
Markdown
Published by
@crewhelm-labs
Turn new GitHub issues into consistent, reviewable triage.
Outcome
Inspect incoming GitHub issues, summarize reproducibility and impact, and propose a bounded triage decision.
Delivery
Markdown
Published by
@crewhelm-labs
Build executable weekly content calendars from campaign briefs.
Outcome
Turn a campaign goal and source material into a practical weekly content calendar with reusable briefs.
Delivery
Markdown
Published by
@crewhelm-labs
Find defensible insights in small CSV exports.
Outcome
Analyze a bounded CSV export and return trustworthy patterns, caveats, and recommended follow-up questions.
Delivery
Markdown
Published by
@crewhelm-labs
Shape ambiguous choices into decision-ready memos.
Outcome
Structure a consequential choice into options, tradeoffs, assumptions, and a clear recommendation.
Delivery
Markdown
Published by
@crewhelm-labs
Convert raw meeting notes into accountable follow-up.
Outcome
Transform a meeting transcript or notes into decisions, owners, actions, and a polished follow-up.
Delivery
Markdown
Published by
@crewhelm-labs
