Research
---
title: Slack — Account Research
owner: unassigned
status: populated
volatility: stable
last_reviewed: 2026-06-28
inject_into: [slack-workflows]
tokens_approx: 0
---
# Slack — Account Research
Task: produce a short internal research brief on a prospect or account, posted in Slack to prep a teammate for a conversation.
## Structure
1. **Who they are** — segment and likely persona (`personas.md`), inferred from the vocabulary and metrics in the request.
2. **Likely application** — best guess at volume tier and menu, with the gaps called out (we scope, we don't assume).
3. **Probable fit** — which equipment family and which attach motion (training / café-in-a-box / standardized rollout).
4. **Likely objections** — pull from `objections.md` with the framed response.
5. **Open questions** — exactly what to ask to scope responsibly.
## Rules
- Mark every inference as an inference. Distinguish what's known from what's assumed.
- No invented specs, prices, or SLAs; flag with `[REVIEW: ...]`.
- End with the single most important discovery question.
See `examples/slack/research.example.md` for the gold-standard shape.when to use it
Community prompt sourced from the open-source GitHub repo matthewjbis/context-kit (no explicit license). A "Research" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
matthewjbis/context-kit · no explicit license
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar