企画、営業、経理、法務、プロジェクト管理（3,981 件）
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
日本語の概要は準備中です。原文の説明を表示しています。
Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.
日本語の概要は準備中です。原文の説明を表示しています。
Construct a compelling job offer. Use when the user says "write an offer letter", "help me make an offer", "how should I structure this offer", "what should we include in the offer", "how do I explain the equity", "the candidate is negotiating", or wants to convert a candidate from interested to accepted - even if they don't explicitly say "offer letter". Also use when a recruiter needs to explain comp philosophy or total compensation to a candidate.
日本語の概要は準備中です。原文の説明を表示しています。
Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Run a recruiter-hiring manager intake meeting to kick off a search. Use when the user says "I need to kick off hiring", "run the intake call", "prepare for the intake meeting", "align with the hiring manager on this role", "we're opening a req", or wants to define hiring criteria and process before sourcing begins - even if they don't explicitly say "intake meeting". Also use when a recruiter needs to get a hiring manager aligned on what "great" looks like before anyone talks to a single candidate.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and prepare for a sales discovery call. Use when the user says "prep for discovery call", "discovery call questions", "how to structure my discovery call", "first call with a prospect", "what to ask on a discovery call", "sales call prep", "plan my discovery call", "initial call framework", or wants to prepare for or debrief a first sales conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Qualify a sales opportunity using the MEDDIC framework. Use when the user says "qualify this deal", "is this deal real", "MEDDIC qualification", "MEDDICC framework", "should I pursue this opportunity", "deal review", "how qualified is this prospect", "pipeline review prep", "forecast this deal", "sanity check on this opportunity", or wants to assess whether a sales opportunity is worth pursuing and at what pipeline stage.
日本語の概要は準備中です。原文の説明を表示しています。
Write a performance-based job description. Use when the user says "write a JD", "draft a job posting", "create a job description", "help me post this role", "write requirements for this position", or wants to define what success looks like in a role - even if they don't explicitly say "job description". Also use when a hiring manager says "I need someone who can do X, Y, Z" and needs that translated into a structured posting.
日本語の概要は準備中です。原文の説明を表示しています。
Build a structured interview scorecard for a role. Use when the user says "create an interview scorecard", "build an interview guide", "what questions should I ask for this role", "help me evaluate candidates consistently", "design the interview process", or wants to assess candidates against defined criteria - even if they don't explicitly say "scorecard". Also use when a recruiter or hiring manager wants to prevent gut-feel hiring.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and run a post-interview candidate debrief. Use when the user says "run the debrief", "how do we decide on this candidate", "let's calibrate", "we need to make a hire/no-hire call", "prep the debrief meeting", or wants to structure the decision-making process after interviews are complete - even if they don't explicitly say "debrief". Also use when a recruiter wants to prevent groupthink or HiPPO effect (highest paid person's opinion) from dominating the decision.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "map out our business model", "business model canvas", "how does our business work", "what are our key resources", "define our value proposition", "revenue model design", "cost structure", "who are our key partners", "lean canvas", "business model design", "how do we make money", or wants to document, stress-test, or redesign how [your startup] creates, delivers, and captures value.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.
日本語の概要は準備中です。原文の説明を表示しています。
Build a business case with costs, benefits, and ROI. Use when the user says "cost-benefit analysis", "business case", "ROI calculation", "is this worth it", "justify the investment", "payback period", "benefits realization", "financial justification", "total cost of ownership", "should we build or buy", "investment appraisal" - even if they don't explicitly say "CBA".
日本語の概要は準備中です。原文の説明を表示しています。
Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering", "functional spec" - even if they don't explicitly say "FRD".
日本語の概要は準備中です。原文の説明を表示しています。
Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.
日本語の概要は準備中です。原文の説明を表示しています。
Write structured use cases with main and alternate flows. Use when the user says "write a use case", "document the user flow", "use case diagram", "actor goal list", "main success scenario", "fully dressed use case", "what does the user do step by step", "system behavior for this feature", "interaction flow" - even if they don't explicitly say "use case".
日本語の概要は準備中です。原文の説明を表示しています。
Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".
日本語の概要は準備中です。原文の説明を表示しています。
Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".
日本語の概要は準備中です。原文の説明を表示しています。
Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the business need", "vision and scope document", "business case for this feature", "what does the business need", "strategic requirements", "document why we need this" - even if they don't explicitly say "BRD".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a User Acceptance Testing plan with scenarios and sign-off criteria. Use when the user says "UAT plan", "acceptance testing", "user testing plan", "how do we test this with users", "test scenarios for business validation", "sign-off criteria", "go/no-go for release", "acceptance test cases", "validate with stakeholders" - even if they don't explicitly say "UAT".
日本語の概要は準備中です。原文の説明を表示しています。
Find the root cause of a problem, not just symptoms. Use when the user says "root cause", "why does this keep happening", "5 whys", "fishbone diagram", "cause analysis", "problem investigation", "defect analysis", "incident analysis", "A3 problem solving", "what's causing this", "ishikawa" - even if they don't explicitly say "root cause analysis".
日本語の概要は準備中です。原文の説明を表示しています。
Map stakeholders by influence, interest, and communication needs. Use when the user says "stakeholder analysis", "stakeholder map", "power interest grid", "who are the stakeholders", "RACI matrix", "stakeholder engagement plan", "who needs to be involved", "communication plan for stakeholders", "influence mapping" - even if they don't explicitly say "stakeholder map".
日本語の概要は準備中です。原文の説明を表示しています。
Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Map business processes as-is and to-be. Use when the user says "map the process", "draw the workflow", "BPMN diagram", "process flow", "swimlane", "how does this process work", "document the current process", "redesign this process", "process improvement", "value stream map", "workflow analysis" - even if they don't explicitly say "process mapper".
日本語の概要は準備中です。原文の説明を表示しています。