Starter Data skill
Research a sales account
Build a dated, source-backed brief for one prospective customer account without inventing personalization.
Create a brief that supports better questions and routing. Distinguish public facts, first-party history, reasonable hypotheses, and information that can only be learned from the account.
Inputs
- Gather the target organization, region, relevant offering, relationship history, and research deadline.
- Prefer official company pages, filings, job posts, technical documentation, and attributable public statements.
- Define the minimum facts needed for the next decision rather than collecting a complete company profile.
Procedure
- Record legal or operating name, business model, locations, scale indicators, and source dates.
- Identify the relevant team, responsibilities, public contacts, and known relationship history.
- Capture current initiatives, changes, hiring, technology, or constraints only from attributable sources.
- Map verified facts to potential product relevance without asserting a need the account did not state.
- List likely stakeholders and buying-process questions as hypotheses.
- Note disqualifying signals, conflicts, existing commitments, and evidence against fit.
- Build a source table with claim, URL, publisher, date, and confidence.
- End with a short account summary, open questions, and the next ethical research or contact action.
Boundaries
Use only lawful, appropriate sources and approved first-party records. Do not collect sensitive personal data, infer protected traits, evade access controls, or describe speculation as fact. Respect contact preferences and suppression lists.
--- name: research-a-sales-account category: data description: Build a dated, source-backed brief for one prospective customer account without inventing personalization. Use when preparing outreach, discovery, account planning, or qualification that depends on current organizational context. --- # research-a-sales-account Create a brief that supports better questions and routing. Distinguish public facts, first-party history, reasonable hypotheses, and information that can only be learned from the account. ## Inputs - Gather the target organization, region, relevant offering, relationship history, and research deadline. - Prefer official company pages, filings, job posts, technical documentation, and attributable public statements. - Define the minimum facts needed for the next decision rather than collecting a complete company profile. ## Procedure 1. Record legal or operating name, business model, locations, scale indicators, and source dates. 2. Identify the relevant team, responsibilities, public contacts, and known relationship history. 3. Capture current initiatives, changes, hiring, technology, or constraints only from attributable sources. 4. Map verified facts to potential product relevance without asserting a need the account did not state. 5. List likely stakeholders and buying-process questions as hypotheses. 6. Note disqualifying signals, conflicts, existing commitments, and evidence against fit. 7. Build a source table with claim, URL, publisher, date, and confidence. 8. End with a short account summary, open questions, and the next ethical research or contact action. ## Boundaries Use only lawful, appropriate sources and approved first-party records. Do not collect sensitive personal data, infer protected traits, evade access controls, or describe speculation as fact. Respect contact preferences and suppression lists. ## Done - Every material account fact has a current source and date - Product relevance, stakeholder guesses, and risks are visibly labeled as hypotheses - Evidence for and against fit is included in the brief - The next user can verify the sources and act without repeating the research