research-an-account

name	research-an-account
description	Research a company, account, or person to understand what matters, what has changed, the existing relationship, and useful ways to move forward. Use before outreach, qualification, account strategy, territory planning, or a meeting that needs deeper company or stakeholder research.

Research an Account

Help the user understand an account well enough to make a better decision or take a useful next step. Adapt the depth and output to their question rather than producing the same company profile every time.

Workflow

1. Understand the question

Clarify which company, organization, or person the user means and what decision the research should support. They may need an overview, way into the account, current priorities, technology or vendor context, decision-makers, relationship history, or deeper work before outreach or strategy.

Agree on depth when time, cost, or breadth matters. Answer the most useful question first and go deeper when it could change the decision.

2. Start with what the user already knows

Use relevant CRM records, email, meetings, files, notes, tabs, memory, and connected apps before asking the user to repeat available context. Check whether the account is already a customer, prospect, partner, past opportunity, or known relationship. Existing history may matter more than a fresh public signal.

If the user only needs a concise brief for a scheduled meeting, use strawberry/sales/prepare-for-sales-meetings. Continue here when the account needs deeper investigation.

3. Investigate the sources that fit the question

Research the public web and relevant logged-in sources with a curious, evidence-led approach. Useful places include company and product pages, LinkedIn, news, job listings, customer stories, documentation, privacy and security pages, public databases, directories, and market-specific sources.

Because Strawberry works in the browser, follow links, search inside sites, compare pages, and keep digging when the first result is incomplete. Stop when the question is answered or more research is unlikely to change the decision.

4. Resolve identities and keep the evidence trustworthy

Confirm the company, domain, and people before combining records. Resolve ambiguity with multiple signals such as current role, employer, location, prior work, or an official company source.

Keep source links for material findings and dates where freshness matters. Separate facts, relationship context, and useful hypotheses. Surface meaningful contradictions or gaps.

5. Turn the research into a useful point of view

Prioritize what could change the user's next move. Depending on the goal, the result may include:

• a concise account overview and what has changed;
• the existing relationship and relevant prior activity;
• likely priorities, needs, or risks clearly marked as hypotheses;
• useful stakeholders, decision-makers, or paths into the account;
• technology, vendors, initiatives, or market context relevant to the user's question;
• questions worth answering next; and
• a recommended next step with the evidence behind it.

Do not manufacture an outreach angle, force a recent detail, or turn every public fact into a sales signal. Prefer a few useful findings over a long generic profile.

6. Deliver and connect the next step

Return a concise, sourced brief in the format that best supports the decision: chat, document, table, CRM note, or another agreed destination. Lead with the quick take.

If the next step is a meeting brief, use strawberry/sales/prepare-for-sales-meetings. If the user needs missing contacts or fields, use strawberry/sales/enrich-lead-list. If they want to contact someone, use strawberry/sales/send-personalized-outreach. Keep research separate from external actions and ask before writing to a shared system.

When the approved brief would help others working the account, offer to share it with the relevant teammates. Keep private relationship context and unreviewed hypotheses out of the shared version.

After useful feedback, offer to save the accepted sources, depth, fields, output, and criteria as a custom or shared team skill. When teammates need ongoing access to the same account context and several workflows, offer to share the full companion. For an ongoing monitoring need, suggest a Routine that checks agreed sources for meaningful account changes and prepares a reviewable update.