📈260 prompts · 13 categories

The Business Prompt Pack

260 prompts to start, run, and grow a company.

Strategy, market research, operations, finance, hiring and decision-making — the operator's prompt library for every part of the business.

Get all 260 prompts — free

Drop your email and the full library unlocks instantly.

No spam. Instant access. Unsubscribe anytime.

  • 260 copy-paste prompts across 13 categories
  • Works with ChatGPT, Claude & Gemini
  • Built for founders, operators and managers

Joined by 5,100+ founders & marketers

260 prompts

#001Business Strategy Operating System

BUSINESS STRATEGY & PLANNINGFounders, CEOs, operators, strategy teams, consultants, startups, small businesses, and leadership teams planning the next stage of growth.

Build a complete business strategy system that connects market context, positioning, goals, priorities, resources, execution cadence, and decision-making.

You are a senior business strategist. Build a complete business strategy operating system for [COMPANY NAME] that turns scattered ideas, market pressure, goals, resources, and constraints into a clear strategy leadership can execute. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Industry: [INDUSTRY] Current revenue: [REVENUE] Target revenue: [TARGET] Core products / services: [PRODUCTS / SERVICES] Audience / customers: [CUSTOMERS] Current positioning: [POSITIONING] Main competitors: [COMPETITORS] Team size: [TEAM SIZE] Budget: [BUDGET] Current challenges: [CHALLENGES] Growth opportunities: [OPPORTUNITIES] Operational constraints: [CONSTRAINTS] Time horizon: [TIME HORIZON] Leadership priorities: [PRIORITIES] Create the strategy operating system: 1. Strategic diagnosis Identify the current business situation across: - market position - customer demand - revenue quality - margin structure - competitive pressure - operational capacity - team capability - product strength - distribution strength - brand strength - financial constraints - execution discipline 2. Strategic choices Define the big choices the company must make: - who to serve - what to sell - where to compete - what to stop doing - what to prioritize - what capabilities to build - what risks to accept - what tradeoffs to make 3. Growth logic Explain how the business is expected to grow: - acquisition path - conversion path - retention path - expansion path - operational scale path - margin improvement path 4. Priority architecture Create 3-5 strategic pillars. For each pillar include: - objective - why it matters - key initiatives - owner - resources required - success metrics - risks - decision checkpoints 5. Execution cadence Build a cadence for: - weekly operating review - monthly strategy review - quarterly planning - budget review - performance review - risk review - leadership decision meetings 6. Measurement system Define: - north star metric - revenue metrics - profit metrics - customer metrics - operational metrics - leading indicators - guardrail metrics 7. 90-day execution plan Create a practical 90-day plan with: - priorities - actions - owners - deadlines - required resources - dependencies - metrics - expected outcomes 8. Leadership summary Write a direct executive summary: - where the business is now - what the strategy is - what must change - what must be protected - what decision leadership must make next Rules: - Do not create a generic strategy. - Do not recommend priorities without tradeoffs. - Do not ignore financial, team, or operational constraints. - Mark assumptions as [ASSUMPTION] and missing data as [NEEDS DATA]. Done when the company has a strategy that can guide decisions, budgets, and execution. --------------------------------------------------------------------------------

#002Strategic Diagnosis Map

BUSINESS STRATEGY & PLANNINGFounders, executives, consultants, operators, business coaches, and leadership teams who need clarity before making strategic decisions.

Diagnose the current business situation and identify the real constraints blocking growth, profitability, focus, or execution.

Act as an independent strategic advisor. Diagnose [COMPANY NAME] and identify the real business constraints, not just the visible symptoms. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Customers: [CUSTOMERS] Revenue streams: [REVENUE STREAMS] Recent performance: [PERFORMANCE] Known problems: [PROBLEMS] Customer feedback: [CUSTOMER FEEDBACK] Team structure: [TEAM] Financial context: [FINANCIALS] Competitive context: [COMPETITION] Operational bottlenecks: [BOTTLENECKS] Leadership concerns: [CONCERNS] Run the diagnosis: A. Symptom vs root cause Separate visible symptoms from deeper causes. Use this format: Symptom: [WHAT IS HAPPENING] Possible root causes: [CAUSES] Evidence available: [EVIDENCE] Evidence missing: [MISSING] Business risk: [RISK] Confidence level: [HIGH / MEDIUM / LOW] B. Business system review Review the business across: - market - customer - offer - pricing - sales - marketing - delivery - operations - team - finance - technology - leadership C. Constraint hierarchy Rank the biggest constraints using: - impact on revenue - impact on profit - impact on execution speed - impact on customer experience - urgency - ease of improvement - confidence D. Strategic tension map Identify tensions such as: - growth vs profitability - speed vs quality - focus vs diversification - premium positioning vs volume - founder control vs delegation - short-term revenue vs long-term capability - customization vs scalability E. Decision implications For each top constraint, explain: - what leadership must decide - what happens if ignored - what data is needed - what action should happen first F. Diagnosis summary Write a one-page plain-English diagnosis with: - the hard truth - the real bottleneck - the biggest opportunity - the biggest risk - the next strategic decision Rules: - Do not accept the stated problem as the root cause without testing it. - Do not invent evidence. - Do not recommend tactics before diagnosing constraints. - Use [LOW CONFIDENCE] when evidence is weak. --------------------------------------------------------------------------------

#003Market Opportunity Prioritizer

BUSINESS STRATEGY & PLANNINGFounders, product teams, investors, executives, consultants, and companies evaluating multiple growth paths.

Compare business opportunities and decide which markets, segments, products, or initiatives deserve focus.

You are a market opportunity strategist. Evaluate and prioritize the opportunities below for [COMPANY NAME] so leadership can decide where to focus. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current capabilities: [CAPABILITIES] Current customers: [CUSTOMERS] Opportunities to evaluate: [OPPORTUNITIES] Market data: [MARKET DATA] Customer demand signals: [DEMAND SIGNALS] Competitors: [COMPETITORS] Budget: [BUDGET] Team capacity: [CAPACITY] Time horizon: [TIME HORIZON] Risk tolerance: [RISK TOLERANCE] Strategic goals: [GOALS] Evaluate each opportunity through this lens: 1. Opportunity description Define: - what the opportunity is - who it serves - what problem it solves - how money is made - why now - what must be true for it to work 2. Market attractiveness Score: - market size - growth rate - urgency of need - willingness to pay - competitive intensity - regulatory or operational complexity - timing - margin potential 3. Company fit Score: - capability fit - brand fit - customer fit - distribution fit - operational fit - capital fit - team fit - strategic fit 4. Risk analysis Identify: - demand risk - execution risk - financial risk - competitive risk - operational risk - reputational risk - opportunity cost 5. Prioritization table Create a table with: - opportunity - attractiveness score - fit score - risk score - effort - time to impact - expected upside - confidence - recommendation 6. Strategic recommendation Classify each opportunity as: - pursue now - test first - monitor - partner - postpone - reject 7. First test For the top opportunity, design a fast validation test: - hypothesis - target customer - offer - test method - success metric - budget - timeline - decision rule Rules: - Do not recommend every opportunity. - Do not confuse market size with accessible opportunity. - Do not ignore execution capacity. - Mark unsupported assumptions as [ASSUMPTION]. --------------------------------------------------------------------------------

#004Strategic Positioning & Competitive Advantage Builder

BUSINESS STRATEGY & PLANNINGStartups, service businesses, SaaS companies, local businesses, agencies, consultants, and leadership teams clarifying strategic positioning.

Define where the business should compete, what makes it different, and how to turn strengths into a defensible advantage.

Act as a competitive strategy advisor. Build a positioning and competitive advantage strategy for [COMPANY NAME] that explains why customers should choose this business over alternatives. Inputs: Company: [COMPANY NAME] Products / services: [PRODUCTS / SERVICES] Target customers: [CUSTOMERS] Customer problems: [PROBLEMS] Current positioning: [CURRENT POSITIONING] Competitors / alternatives: [COMPETITORS] Strengths: [STRENGTHS] Weaknesses: [WEAKNESSES] Proof points: [PROOF] Pricing level: [PRICING] Distribution channels: [CHANNELS] Brand personality: [BRAND] Business goals: [GOALS] Create the strategy: A. Competitive arena Define where the company competes: - category - customer segment - use case - price tier - geography - buying situation - alternative solutions B. Alternative analysis Analyze competitors and alternatives: - direct competitors - indirect competitors - internal workaround - doing nothing - low-cost options - premium options - legacy options For each include: - why customers choose it - where it is strong - where it is weak - what customers may dislike - where [COMPANY NAME] can win C. Advantage inventory Identify potential advantages: - product advantage - service advantage - speed advantage - cost advantage - trust advantage - specialization advantage - distribution advantage - brand advantage - data advantage - operational advantage - relationship advantage D. Defensibility test For each advantage evaluate: - is it real? - is it valuable to customers? - is it hard to copy? - is it easy to explain? - is there proof? - can it scale? E. Positioning statement Create 5 positioning statement options: For [CUSTOMER], [COMPANY] is the [CATEGORY] that helps [OUTCOME] because [DIFFERENCE]. F. Strategic message map Create: - core promise - differentiation points - proof points - competitor contrast - customer language - claims to avoid Rules: - Do not claim differentiation without proof. - Do not attack competitors unfairly. - Do not position only around features. - The strategy must explain where the company wins and where it should not compete. --------------------------------------------------------------------------------

#005Business Model Stress Test

BUSINESS STRATEGY & PLANNINGFounders, investors, operators, consultants, startups, acquisition analysis, and businesses preparing for growth.

Stress-test a business model for revenue quality, cost structure, margins, scalability, customer concentration, and operational risk.

You are a business model analyst. Stress-test the business model of [COMPANY NAME] and identify where it is strong, fragile, scalable, or financially risky. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue streams: [REVENUE STREAMS] Pricing: [PRICING] Customer segments: [CUSTOMERS] Cost structure: [COST STRUCTURE] Gross margin: [GROSS MARGIN] Operating expenses: [OPEX] Customer acquisition channels: [CHANNELS] Retention / repeat purchase: [RETENTION] Delivery process: [DELIVERY] Team structure: [TEAM] Operational constraints: [CONSTRAINTS] Growth goal: [GOAL] Stress-test the business model: 1. Revenue quality Analyze: - recurring vs one-time revenue - predictability - customer concentration - contract length - expansion potential - churn risk - seasonality - pricing power 2. Cost structure Analyze: - fixed costs - variable costs - gross margin drivers - labor intensity - fulfillment costs - marketing costs - sales costs - technology costs - hidden costs 3. Scalability Evaluate: - what scales well - what breaks under growth - what requires headcount - what requires capital - what becomes more efficient - what becomes more complex 4. Unit economics Create a unit economics framework: - revenue per customer - cost to acquire - cost to serve - gross margin - contribution margin - payback period - lifetime value - break-even point Use [NEEDS DATA] where numbers are missing. 5. Risk scenarios Model qualitative scenarios: - revenue drops 20% - costs rise 15% - top customer leaves - CAC doubles - churn increases - supplier costs increase - team capacity becomes constrained - competitor lowers prices 6. Strategic recommendations Recommend how to improve: - pricing - margin - retention - customer mix - recurring revenue - operational efficiency - risk resilience - scalability Rules: - Do not assume growth improves profitability. - Do not ignore cost to serve. - Do not hide customer concentration risk. - Mark missing financial inputs clearly. --------------------------------------------------------------------------------

#006Strategic Goals & OKR Builder

BUSINESS STRATEGY & PLANNINGLeadership teams, startups, scaleups, department heads, operators, consultants, and quarterly or annual planning.

Convert broad business ambitions into clear strategic goals, measurable OKRs, initiatives, owners, and review cadence.

Act as a strategic planning facilitator. Convert the business ambition below into a focused goal system for [COMPANY NAME]. Inputs: Company: [COMPANY NAME] Time period: [QUARTER / YEAR] Business ambition: [AMBITION] Current performance: [PERFORMANCE] Leadership priorities: [PRIORITIES] Constraints: [CONSTRAINTS] Team structure: [TEAM] Available budget: [BUDGET] Current initiatives: [INITIATIVES] Risks: [RISKS] Build the goal system: A. Goal clarification Rewrite the broad ambition into 3-5 strategic goals. Each goal must be: - specific - measurable - time-bound - strategically important - realistic under constraints - connected to business outcomes B. OKR design For each goal create: - objective - 3-5 key results - metric definition - baseline - target - owner - confidence level - leading indicator - guardrail metric C. Initiative map For each objective define: - initiatives - why each initiative matters - required resources - dependencies - owner - deadline - expected impact - risk D. Priority conflict check Identify conflicts between goals, such as: - revenue vs margin - speed vs quality - acquisition vs retention - expansion vs focus - short-term cash vs long-term capability E. Review cadence Create: - weekly check-in - monthly progress review - quarterly reset - decision escalation rule - scorecard format F. Leadership alignment summary Write a short summary that explains what the company is committing to and what it is not committing to. Rules: - Do not create too many goals. - Do not use vague key results. - Do not make every department priority a company strategy. - Every OKR must support a decision or behavior change. --------------------------------------------------------------------------------

#007Resource Allocation Decision Matrix

BUSINESS STRATEGY & PLANNINGCEOs, COOs, founders, operators, department leaders, consultants, and teams choosing between competing initiatives.

Decide where time, money, team capacity, and leadership attention should go based on impact, constraints, risk, and strategic fit.

You are an operating strategy advisor. Build a resource allocation matrix for [COMPANY NAME] to decide which initiatives deserve time, budget, people, and leadership attention. Inputs: Company: [COMPANY NAME] Strategic goals: [GOALS] Initiatives under consideration: [INITIATIVES] Available budget: [BUDGET] Available team capacity: [CAPACITY] Leadership bandwidth: [BANDWIDTH] Expected impact: [EXPECTED IMPACT] Risks: [RISKS] Dependencies: [DEPENDENCIES] Time horizon: [TIME HORIZON] Must-do obligations: [OBLIGATIONS] Create the decision matrix: 1. Resource inventory List available resources: - budget - people - skills - technology - leadership attention - time - partnerships - operational capacity 2. Initiative profile For each initiative include: - initiative name - strategic goal supported - expected business impact - customer impact - revenue impact - profit impact - operational complexity - resources required - time to value - risk - reversibility - confidence 3. Scoring model Score each initiative using: - impact - strategic fit - urgency - confidence - resource efficiency - risk - opportunity cost - dependency complexity 4. Portfolio classification Classify initiatives into: - fund now - run as test - maintain - pause - stop - delegate - outsource - revisit later 5. Tradeoff analysis For the top recommendations explain: - what gets funded - what gets delayed - what gets stopped - what risk is accepted - what capacity is freed 6. Allocation plan Create a plan showing: - budget allocation - people allocation - owner - timeline - review metric - decision checkpoint Rules: - Do not allocate resources to everything. - Do not ignore opportunity cost. - Do not assign work without capacity. - The output must make tradeoffs explicit. --------------------------------------------------------------------------------

#008Scenario Planning Workshop

BUSINESS STRATEGY & PLANNINGLeadership planning, annual strategy, risk management, volatile markets, startups, operators, and board-level discussion.

Create business scenarios and strategic responses for uncertain markets, demand shifts, cost changes, competition, or operational disruption.

Act as a scenario planning facilitator. Build a scenario planning workshop for [COMPANY NAME] that helps leadership prepare for uncertainty and make stronger strategic choices. Inputs: Company: [COMPANY NAME] Industry: [INDUSTRY] Business model: [BUSINESS MODEL] Current strategy: [STRATEGY] Planning horizon: [HORIZON] Key uncertainties: [UNCERTAINTIES] Market risks: [MARKET RISKS] Operational risks: [OPERATIONAL RISKS] Financial risks: [FINANCIAL RISKS] Competitive risks: [COMPETITIVE RISKS] Leadership concerns: [CONCERNS] Design the workshop: A. Critical uncertainties Identify the uncertainties that matter most: - demand growth or decline - pricing pressure - cost inflation - supply constraints - regulation - technology change - competitor moves - customer behavior - labor availability - capital access B. Scenario matrix Create 4 scenarios using two high-impact uncertainties. For each scenario include: - scenario name - description - what happens in the market - customer behavior - competitor behavior - operational pressure - financial pressure - early warning signals C. Strategic response For each scenario define: - what to protect - what to stop - what to accelerate - what to test - what capabilities are needed - what financial moves are required - what leadership decisions are triggered D. No-regret moves Identify actions that make sense across most scenarios. E. Contingency triggers Define measurable signals that trigger a strategy shift. F. Workshop agenda Create a 2-hour leadership workshop agenda with exercises, discussion questions, and outputs. Rules: - Do not create fantasy scenarios with no decision value. - Do not make every scenario equally likely if evidence suggests otherwise. - Do not ignore financial and operational constraints. - Scenarios must improve readiness, not create fear. --------------------------------------------------------------------------------

#009Business Plan Builder

BUSINESS STRATEGY & PLANNINGFounders, small business owners, startups, consultants, investors, lenders, and operators creating a clear plan.

Create a practical business plan with strategy, market, offer, operations, sales, marketing, financial logic, milestones, and risks.

You are a business planning consultant. Create a practical business plan for [BUSINESS NAME] that can guide execution and explain the business clearly to stakeholders. Inputs: Business name: [BUSINESS NAME] Business idea / current business: [DESCRIPTION] Products / services: [PRODUCTS / SERVICES] Target customers: [CUSTOMERS] Market: [MARKET] Problem solved: [PROBLEM] Value proposition: [VALUE PROPOSITION] Business model: [BUSINESS MODEL] Pricing: [PRICING] Sales channels: [SALES CHANNELS] Marketing channels: [MARKETING CHANNELS] Operations model: [OPERATIONS] Team: [TEAM] Startup / operating costs: [COSTS] Revenue assumptions: [REVENUE ASSUMPTIONS] Funding needs: [FUNDING] Time horizon: [TIME HORIZON] Create the business plan: 1. Executive summary Write a clear summary of: - what the business does - who it serves - why it exists - how it makes money - why it can win - what it needs next 2. Market and customer Define: - target market - customer segments - customer problems - buying triggers - competitors - alternatives - market opportunity 3. Offer and positioning Define: - products / services - value proposition - differentiation - pricing logic - proof needed - customer objections 4. Go-to-market plan Create: - sales strategy - marketing strategy - channel priorities - launch plan - partnership opportunities - retention plan 5. Operations plan Define: - delivery process - suppliers - tools - staffing - quality control - customer support - risks 6. Financial logic Create a financial planning framework: - revenue streams - cost structure - margin assumptions - break-even drivers - cash flow risks - funding needs Use [NEEDS DATA] for missing numbers. 7. Milestones Create a 12-month milestone plan. 8. Risk plan Identify top risks and mitigation actions. Rules: - Do not write a decorative business plan with no operational value. - Do not invent market statistics. - Do not hide weak assumptions. - The plan must be useful for execution, not just presentation. --------------------------------------------------------------------------------

#010Annual Strategic Planning Facilitator

BUSINESS STRATEGY & PLANNINGCEOs, founders, leadership teams, operators, consultants, department heads, and companies preparing annual plans.

Run an annual planning process that converts business performance, market shifts, goals, budget, and constraints into a focused yearly plan.

Act as an annual strategic planning facilitator. Build a complete annual planning process for [COMPANY NAME] that creates alignment, focus, and a practical execution plan for [YEAR]. Inputs: Company: [COMPANY NAME] Year: [YEAR] Previous year performance: [PERFORMANCE] Revenue / profit results: [FINANCIALS] Customer results: [CUSTOMER RESULTS] Team results: [TEAM RESULTS] Market changes: [MARKET CHANGES] Strategic wins: [WINS] Strategic misses: [MISSES] Current opportunities: [OPPORTUNITIES] Current risks: [RISKS] Budget constraints: [BUDGET] Leadership priorities: [PRIORITIES] Create the planning process: A. Pre-work Create a pre-work package for leadership: - performance review - customer insights - financial review - market review - competitor review - team capacity review - initiative review - lessons learned B. Planning questions Create strategic questions around: - where did we win? - where did we lose? - what changed in the market? - what customers need next? - what must we stop? - what must we double down on? - what capabilities must we build? - what risks must we prepare for? C. Annual strategy Create: - annual theme - strategic pillars - annual goals - key metrics - priority initiatives - major tradeoffs - budget logic D. Quarterly roadmap Break the year into quarters. For each quarter include: - focus - initiatives - milestones - owner - budget - success metric - decision checkpoint E. Operating rhythm Define: - weekly leadership review - monthly performance review - quarterly strategy review - annual reset F. Final annual plan Write a leadership-ready plan summary. Rules: - Do not let annual planning become a wish list. - Do not carry over old initiatives without justification. - Do not create goals without owners. - The annual plan must guide resource allocation. --------------------------------------------------------------------------------

#011Quarterly Business Review Builder

BUSINESS STRATEGY & PLANNINGLeadership teams, operators, investors, boards, agencies, consultants, department heads, and business owners.

Create a quarterly business review that explains performance, strategic progress, risks, decisions, and next-quarter priorities.

You are a quarterly business review strategist. Create a QBR for [COMPANY NAME] that helps leadership understand what happened, why it happened, what changed, and what should happen next. Inputs: Company: [COMPANY NAME] Quarter: [QUARTER] Business goals: [GOALS] Performance data: [DATA] Financial results: [FINANCIALS] Customer results: [CUSTOMERS] Sales / marketing results: [SALES / MARKETING] Operations results: [OPERATIONS] Team results: [TEAM] Initiatives completed: [INITIATIVES] Risks and blockers: [RISKS] Decisions needed: [DECISIONS] Next-quarter priorities: [PRIORITIES] Create the QBR: 1. Executive summary Write a concise summary covering: - performance vs goal - biggest win - biggest miss - biggest learning - biggest risk - recommended decision 2. Scorecard Create a scorecard with: - metric - target - actual - variance - trend - interpretation - owner 3. Strategic progress Review progress against strategic pillars: - what moved forward - what stalled - why - what needs leadership attention 4. Root cause analysis For major misses, explain: - symptom - likely cause - evidence - missing evidence - recommended fix - confidence level 5. Risk review Identify: - financial risks - customer risks - operational risks - team risks - competitive risks - execution risks 6. Next-quarter plan Create: - top priorities - initiatives - owners - metrics - milestones - budget needs - decision points 7. Leadership decisions List the decisions leadership must make before the next quarter starts. Rules: - Do not make the review only a performance recap. - Do not hide bad news. - Do not report metrics without interpretation. - Every section must support a decision or priority. --------------------------------------------------------------------------------

#012Strategic Initiative Charter

BUSINESS STRATEGY & PLANNINGStrategy execution, PMOs, operators, leadership teams, consultants, founders, and cross-functional projects.

Turn a strategic initiative into a clear charter with objective, scope, owner, milestones, resources, risks, metrics, and decision gates.

Act as a strategic initiative designer. Create a complete initiative charter for [INITIATIVE NAME] so the team can execute it with clear ownership, scope, and success criteria. Inputs: Company: [COMPANY NAME] Initiative name: [INITIATIVE NAME] Strategic goal supported: [GOAL] Problem / opportunity: [PROBLEM / OPPORTUNITY] Desired outcome: [OUTCOME] Scope: [SCOPE] Out of scope: [OUT OF SCOPE] Owner: [OWNER] Team involved: [TEAM] Budget: [BUDGET] Timeline: [TIMELINE] Dependencies: [DEPENDENCIES] Risks: [RISKS] Success metrics: [METRICS] Create the charter: A. Initiative summary Write: - initiative purpose - strategic reason - expected outcome - owner - timeline - success definition B. Scope lock Define: - in scope - out of scope - assumptions - constraints - dependencies - approval requirements C. Workstreams Break the initiative into workstreams. For each workstream include: - objective - tasks - owner - milestones - resources - risks - deliverables D. Metrics Define: - primary metric - secondary metrics - leading indicators - guardrail metrics - reporting cadence E. Decision gates Create gates for: - kickoff - validation - resourcing - launch - performance review - scale / stop / adjust decision F. Communication plan Create stakeholder updates: - weekly update - milestone update - risk escalation - final review G. Risk register Create a risk table with: - risk - likelihood - impact - mitigation - owner - trigger Rules: - Do not create a charter without clear owner and metric. - Do not let scope expand silently. - Do not confuse activities with outcomes. - The charter must be executable by a team. --------------------------------------------------------------------------------

#013SWOT-to-Strategy Converter

BUSINESS STRATEGY & PLANNINGConsultants, founders, leadership teams, business planning, annual planning, and strategy workshops.

Convert a SWOT analysis into strategic priorities, initiatives, risks, and decisions instead of leaving it as a static exercise.

You are a strategy facilitator. Convert the SWOT information below into a practical strategy for [COMPANY NAME]. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Strengths: [STRENGTHS] Weaknesses: [WEAKNESSES] Opportunities: [OPPORTUNITIES] Threats: [THREATS] Business goals: [GOALS] Market context: [MARKET] Customer context: [CUSTOMER] Financial constraints: [FINANCIALS] Team constraints: [TEAM] Convert SWOT into strategy: 1. SWOT cleanup Rewrite each SWOT item so it is specific, evidence-based, and decision-relevant. Mark items as: - verified - assumed - vague - not strategic - needs evidence 2. Strategic implications For each category answer: - what does this mean for growth? - what does this mean for profit? - what does this mean for customers? - what does this mean for operations? - what does this mean for risk? 3. Strategic moves Create strategic moves using: - use strengths to capture opportunities - use strengths to defend against threats - fix weaknesses that block opportunities - reduce weaknesses that increase threats 4. Priority ranking Rank strategic moves by: - business impact - urgency - confidence - feasibility - risk - resource requirement 5. Initiative creation Turn top moves into initiatives with: - objective - owner - actions - timeline - metric - risk - first step 6. Decision list Identify strategic decisions leadership must make. Rules: - Do not treat SWOT as the final strategy. - Do not include generic strengths like "great team" without evidence. - Do not overreact to threats without probability and impact. - The output must become an action plan. --------------------------------------------------------------------------------

#014Strategic Risk Register

BUSINESS STRATEGY & PLANNINGLeadership teams, founders, investors, boards, operators, annual planning, crisis preparation, and scaling businesses.

Identify, prioritize, and manage strategic risks across market, financial, operational, customer, competitive, legal, and execution areas.

Act as a strategic risk advisor. Build a risk register for [COMPANY NAME] that helps leadership see, prioritize, and manage risks before they become crises. Inputs: Company: [COMPANY NAME] Industry: [INDUSTRY] Business model: [BUSINESS MODEL] Current strategy: [STRATEGY] Growth goals: [GOALS] Financial situation: [FINANCIALS] Customer concentration: [CUSTOMER CONCENTRATION] Key dependencies: [DEPENDENCIES] Operational constraints: [CONSTRAINTS] Competitive environment: [COMPETITION] Regulatory context: [REGULATION] Leadership concerns: [CONCERNS] Create the risk register: A. Risk categories Identify risks across: - market risk - customer risk - revenue risk - margin risk - cash flow risk - operational risk - supply risk - team risk - technology risk - competitive risk - legal / regulatory risk - reputation risk - execution risk - strategic focus risk B. Risk table For each risk include: - risk statement - cause - potential impact - likelihood - severity - early warning signal - mitigation - contingency plan - owner - review cadence C. Risk scoring Score risks using: Risk Priority = Likelihood x Impact x Urgency D. Top risk response plans For the top 5 risks create: - prevention plan - monitoring plan - response plan - decision trigger - communication plan E. Board / leadership summary Write a concise risk summary: - biggest risk - fastest-moving risk - most ignored risk - highest financial risk - highest execution risk - decision needed Rules: - Do not list risks without owners. - Do not treat all risks as equal. - Do not ignore early warning signals. - Risk planning must lead to decisions, not fear. --------------------------------------------------------------------------------

#015Business Expansion Strategy Planner

BUSINESS STRATEGY & PLANNINGGrowing companies, franchises, retail businesses, SaaS teams, service businesses, ecommerce brands, and founders considering expansion.

Plan expansion into new markets, locations, products, channels, or customer segments with clear logic, tests, resources, and risk controls.

You are an expansion strategy consultant. Build an expansion plan for [COMPANY NAME] into [EXPANSION AREA] that balances growth potential with operational, financial, and execution risk. Inputs: Company: [COMPANY NAME] Current business model: [BUSINESS MODEL] Expansion area: [NEW MARKET / LOCATION / PRODUCT / CHANNEL / SEGMENT] Current customers: [CUSTOMERS] Current capabilities: [CAPABILITIES] Expansion hypothesis: [HYPOTHESIS] Market demand signals: [DEMAND SIGNALS] Competitive context: [COMPETITION] Budget: [BUDGET] Team capacity: [CAPACITY] Operational requirements: [OPERATIONS] Timeline: [TIMELINE] Success target: [TARGET] Create the expansion plan: 1. Expansion logic Explain: - why this expansion makes sense - what customer need it serves - what advantage the company brings - what must be true for success - what would make it fail 2. Fit assessment Evaluate fit across: - customer fit - brand fit - capability fit - channel fit - operational fit - financial fit - leadership fit - timing fit 3. Market entry options Create options: - pilot - partnership - limited launch - acquisition - franchise / licensing - direct expansion - online launch - wholesale / channel partner - new product line For each include: - upside - downside - cost - speed - risk - learning value 4. Validation plan Design a test before full expansion: - hypothesis - test audience - offer - channel - budget - timeline - success metric - stop condition 5. Resource plan Define: - team - budget - tools - operations - suppliers - marketing - sales - support - management attention 6. Expansion roadmap Create a phased roadmap: - research - validation - pilot - review - scale - optimize Rules: - Do not recommend full expansion before validation unless evidence is strong. - Do not ignore operational capacity. - Do not assume current success transfers automatically. - Expansion must be tied to a clear strategic advantage. --------------------------------------------------------------------------------

#016Profitability Improvement Strategy

BUSINESS STRATEGY & PLANNINGCEOs, CFOs, operators, founders, consultants, agencies, restaurants, retail, SaaS, service companies, and small businesses.

Identify practical ways to improve profitability through pricing, cost structure, customer mix, product mix, operations, retention, and resource allocation.

Act as a profitability strategist. Analyze [COMPANY NAME] and create a practical strategy to improve profit without damaging long-term customer trust or growth potential. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue: [REVENUE] Gross margin: [GROSS MARGIN] Operating expenses: [OPEX] Product / service mix: [PRODUCT MIX] Customer segments: [CUSTOMERS] Pricing: [PRICING] Cost drivers: [COST DRIVERS] Operational bottlenecks: [BOTTLENECKS] Retention / repeat purchase: [RETENTION] Sales / marketing costs: [SALES / MARKETING COSTS] Capacity constraints: [CAPACITY] Profit target: [TARGET] Analyze profitability: A. Profit bridge Break down profit drivers: - revenue volume - price - product mix - customer mix - gross margin - cost to serve - labor efficiency - marketing efficiency - retention - overhead - waste / leakage B. Margin opportunity map Identify opportunities to improve: - pricing - packaging - upsell - product mix - supplier costs - labor scheduling - process efficiency - automation - customer retention - customer selection - discount control - overhead reduction C. Customer and product economics Classify customers/products as: - high revenue / high margin - high revenue / low margin - low revenue / high margin - low revenue / low margin - strategic but unprofitable - should be redesigned or exited D. Profit improvement initiatives Create 15 initiatives. For each include: - initiative - profit driver - expected impact - effort - risk - customer impact - owner - metric - timeline E. Prioritized action plan Create a 30/60/90-day profit plan. F. Leadership warning List profit improvements that look attractive but could hurt the business. Rules: - Do not recommend cost cutting without understanding customer impact. - Do not ignore revenue quality. - Do not assume price increases are safe without positioning logic. - Mark missing financial data as [NEEDS DATA]. --------------------------------------------------------------------------------

#017Strategic Partnership Planner

BUSINESS STRATEGY & PLANNINGStartups, agencies, SaaS companies, ecommerce brands, local businesses, consultants, and business development teams.

Identify, evaluate, and plan partnerships that can expand distribution, credibility, product capability, revenue, or market access.

You are a strategic partnerships advisor. Build a partnership strategy for [COMPANY NAME] that identifies the right partners and creates a practical plan to make partnerships valuable. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Target customers: [CUSTOMERS] Current channels: [CHANNELS] Strategic goals: [GOALS] Potential partner types: [PARTNER TYPES] Current relationships: [RELATIONSHIPS] Value the company can offer partners: [PARTNER VALUE] Desired partner value: [DESIRED VALUE] Constraints: [CONSTRAINTS] Create the partnership strategy: 1. Partnership objective Define what partnerships should achieve: - customer acquisition - distribution - credibility - product capability - operational capacity - geographic access - content / audience access - referral flow - revenue - retention 2. Partner type map Identify partner categories: - complementary product - service provider - distributor - reseller - affiliate - community - influencer / creator - platform - local business - enterprise partner - supplier - data or technology partner 3. Partner scoring For each potential partner type score: - audience fit - value exchange - strategic fit - ease of activation - trust level - revenue potential - operational complexity - risk - long-term potential 4. Partnership offers Create partnership models: - referral partnership - co-marketing - bundle - integration - reseller - white-label - joint event - content collaboration - marketplace listing For each include: - partner benefit - company benefit - customer benefit - revenue logic - required assets - risks 5. Outreach plan Write: - partner pitch - email - LinkedIn message - follow-up - meeting agenda - proposal outline 6. Partnership management Define: - owner - onboarding - tracking - communication cadence - success metrics - renewal or exit criteria Rules: - Do not pursue partnerships without clear value exchange. - Do not treat partner logos as strategy. - Do not ignore operational complexity. - Partnership success must be measurable. --------------------------------------------------------------------------------

#018Decision Framework for Strategic Tradeoffs

BUSINESS STRATEGY & PLANNINGCEOs, founders, boards, leadership teams, operators, consultants, and teams facing difficult business decisions.

Create a decision-making framework for high-stakes strategic choices with options, evidence, risks, tradeoffs, and decision rules.

Act as a strategic decision advisor. Build a decision framework for the business choice below so leadership can make a clear, evidence-based decision. Decision question: [DECISION QUESTION] Context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current situation: [SITUATION] Options being considered: [OPTIONS] Business goal: [GOAL] Financial context: [FINANCIALS] Customer impact: [CUSTOMER IMPACT] Operational impact: [OPERATIONS] Team impact: [TEAM] Risks: [RISKS] Timeline: [TIMELINE] Stakeholders: [STAKEHOLDERS] Create the decision framework: A. Decision statement Rewrite the decision clearly: We need to decide whether to [OPTION] in order to [GOAL] by [DATE], while protecting [CONSTRAINT]. B. Option analysis For each option include: - what it means - expected upside - expected downside - financial impact - customer impact - operational impact - team impact - risk - reversibility - time to impact - evidence supporting it - evidence against it - confidence level C. Tradeoff map Compare options across: - growth - profit - cash flow - customer trust - speed - quality - focus - risk - complexity - strategic fit D. Decision criteria Create weighted criteria based on leadership priorities. E. Recommendation Choose the recommended option and explain: - why it wins - what tradeoff is accepted - what must be monitored - what would change the recommendation F. Implementation plan Create: - first action - owner - timeline - metrics - decision checkpoint - communication plan Rules: - Do not recommend an option without naming what is sacrificed. - Do not hide uncertainty. - Do not treat reversible and irreversible decisions the same. - A good decision framework must reduce ambiguity, not create more analysis. --------------------------------------------------------------------------------

#019Strategic Execution Scorecard

BUSINESS STRATEGY & PLANNINGLeadership teams, operators, strategy teams, consultants, quarterly planning, annual planning, and company operating rhythms.

Create a scorecard that tracks whether strategy is turning into execution, results, learning, and better decisions.

You are a strategy execution analyst. Build a strategic execution scorecard for [COMPANY NAME] that tracks whether the strategy is actually being executed and producing results. Inputs: Company: [COMPANY NAME] Current strategy: [STRATEGY] Strategic pillars: [PILLARS] Goals / OKRs: [GOALS / OKRS] Initiatives: [INITIATIVES] Owners: [OWNERS] Metrics: [METRICS] Current performance: [PERFORMANCE] Review cadence: [CADENCE] Known execution issues: [ISSUES] Leadership questions: [QUESTIONS] Build the scorecard: 1. Strategy-to-execution map Connect: - strategic pillar - objective - initiative - owner - milestone - metric - expected business outcome 2. Execution health metrics Create metrics for: - initiative progress - milestone completion - resource allocation - decision speed - blocker resolution - budget usage - quality of execution - customer impact - financial impact - learning generated 3. Scorecard table For each strategic pillar include: - goal - owner - current status - target - actual - trend - risk - blocker - next decision - confidence level 4. Execution issue diagnosis Classify issues as: - unclear strategy - too many priorities - weak ownership - resource gap - poor coordination - bad metric - decision delay - execution discipline problem - external constraint - wrong initiative 5. Review meeting format Create a monthly strategy execution review agenda. 6. Escalation rules Define when a pillar or initiative needs leadership action. 7. Summary narrative Write a plain-English summary of whether the strategy is on track. Rules: - Do not confuse activity with execution. - Do not allow green status without evidence. - Do not track metrics nobody uses. - The scorecard must trigger decisions. --------------------------------------------------------------------------------

#020Full Business Strategy & Planning Audit

BUSINESS STRATEGY & PLANNINGStrategy resets, annual planning, founder reviews, investor preparation, consulting diagnostics, leadership alignment, and business performance improvement.

Audit the full business strategy and planning system across market, positioning, goals, business model, resources, execution, risks, and decision quality.

Act as an independent business strategy and planning auditor. Review the full strategy system for [COMPANY NAME] and identify the highest-leverage improvements. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Market / industry: [MARKET] Target customers: [CUSTOMERS] Products / services: [PRODUCTS / SERVICES] Current strategy: [STRATEGY] Current positioning: [POSITIONING] Revenue and profit data: [FINANCIALS] Customer data: [CUSTOMER DATA] Competitors: [COMPETITORS] Team and operations: [TEAM / OPERATIONS] Current goals / OKRs: [GOALS] Current initiatives: [INITIATIVES] Budget and resources: [RESOURCES] Risks: [RISKS] Planning cadence: [CADENCE] Leadership concerns: [CONCERNS] Audit the strategy system across 14 dimensions: 1. Market clarity 2. Customer focus 3. Positioning and differentiation 4. Business model strength 5. Revenue quality 6. Profitability logic 7. Competitive advantage 8. Strategic priorities 9. Resource allocation 10. Goal and metric quality 11. Execution cadence 12. Risk management 13. Decision-making quality 14. Leadership alignment For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - business risk - strategic risk - recommended fix - confidence level Then synthesize: A. Top 5 strategic constraints Rank the biggest issues by impact, urgency, risk, confidence, and ease of improvement. B. Root cause analysis Identify whether the main problem is: - unclear customer focus - weak positioning - weak business model - poor margins - too many priorities - poor execution discipline - weak resource allocation - missing data - leadership misalignment - wrong market choice - poor decision cadence - unmanaged risk C. Rebuilt strategy snapshot Create: - strategic diagnosis - target customer - positioning - business model improvement - strategic pillars - priority initiatives - resource allocation - risk plan - scorecard D. 30/60/90-day repair plan Create a practical plan with: - actions - owners - milestones - decisions - resources - metrics - review points E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with the hard truth, the opportunity, and the next strategic decision. Rules: - Do not invent performance data. - Do not judge strategy only by ambition or revenue growth. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on clarity, tradeoffs, execution, profitability, resilience, and decision quality.

#021Market Research Operating System

MARKET RESEARCH & COMPETITIVE ANALYSISFounders, strategy teams, consultants, product marketers, business analysts, startups, agencies, and leadership teams evaluating markets or planning growth.

Build a complete market research system that turns scattered signals into clear market understanding, customer insight, competitor intelligence, and strategic decisions.

You are a senior market research strategist. Build a complete market research operating system for [COMPANY NAME] that helps leadership understand the market, customers, competitors, risks, opportunities, and strategic choices. Inputs: Company: [COMPANY NAME] Industry / category: [INDUSTRY / CATEGORY] Business model: [BUSINESS MODEL] Target customers: [CUSTOMERS] Products / services: [PRODUCTS / SERVICES] Geography: [GEOGRAPHY] Current competitors: [COMPETITORS] Current assumptions: [ASSUMPTIONS] Known customer problems: [PROBLEMS] Current market signals: [MARKET SIGNALS] Available data sources: [DATA SOURCES] Research budget: [BUDGET] Time horizon: [TIME HORIZON] Strategic decision to support: [DECISION] Create the market research operating system: 1. Research objective Define the exact business decision this research must support. Output: - decision question - what must be learned - what is already known - what is assumed - what would change the decision - what evidence is required 2. Market structure map Analyze: - category definition - subcategories - customer segments - buying situations - demand drivers - market maturity - growth forces - barriers to entry - substitution threats - regulation or constraints - technology shifts 3. Customer research plan Design research around: - pains - desired outcomes - buying triggers - decision criteria - objections - alternatives - willingness to pay - switching behavior - language customers use 4. Competitor intelligence system Build a competitor tracking model across: - positioning - pricing - offers - products - channels - content - customer reviews - sales process - partnerships - strengths - weaknesses - recent moves 5. Research methods Recommend methods: - desk research - customer interviews - surveys - review mining - competitor teardown - pricing research - social listening - search demand analysis - sales call analysis - mystery shopping - expert interviews For each method include: - purpose - data needed - expected output - time required - confidence level - risk of bias 6. Insight synthesis system Create a process for converting raw research into: - market themes - customer segments - competitor patterns - opportunity areas - risks - assumptions to test - strategic recommendations 7. Decision framework Create a final decision model that answers: - should we enter this market? - which segment should we prioritize? - where can we win? - what should we avoid? - what must be validated first? - what strategy should leadership choose? 8. Research cadence Create a cadence for: - weekly signal scan - monthly competitor update - quarterly market review - annual strategy refresh Rules: - Do not invent data. - Do not treat assumptions as facts. - Do not confuse market noise with market evidence. - Mark weak evidence as [LOW CONFIDENCE]. - Every research output must support a business decision. Done when leadership can explain the market, the customer, the competitors, the opportunity, and the next decision clearly. --------------------------------------------------------------------------------

#022Customer Problem Landscape Scanner

MARKET RESEARCH & COMPETITIVE ANALYSISEarly-stage founders, product teams, consultants, marketers, customer researchers, and businesses validating demand before building or repositioning an offer.

Discover and organize the real customer problems, frustrations, goals, triggers, and buying motivations shaping market demand.

Act as a customer problem researcher. Your job is to map the problem landscape for [TARGET CUSTOMER] in [MARKET / CATEGORY] so the business can understand what customers actually care about before making strategic decisions. Research context: Target customer: [TARGET CUSTOMER] Market / category: [MARKET] Product or service idea: [PRODUCT / SERVICE] Current customer assumptions: [ASSUMPTIONS] Existing customer data: [PASTE DATA] Reviews / forums / social comments: [PASTE COMMENTS] Sales or support notes: [NOTES] Competitor products: [COMPETITORS] Decision to support: [DECISION] Analyze the customer problem landscape in six layers: Layer A - Spoken problems List the problems customers directly say they have. For each problem include: - exact customer language - frequency signal - emotional intensity - context where it appears - affected customer segment - evidence source - confidence level Layer B - Hidden problems Infer deeper problems behind the visible complaints. For each hidden problem include: - surface complaint - deeper tension - why it matters - what customers may not say directly - risk of misinterpretation Layer C - Desired outcomes Identify what customers want instead: - functional outcome - emotional outcome - social outcome - financial outcome - time-saving outcome - risk-reduction outcome - status or identity outcome Layer D - Trigger moments Identify what causes customers to start looking for a solution: - pain threshold - event - deadline - failure - life or business change - competitor disappointment - cost increase - new priority - external pressure Layer E - Current alternatives Map what customers do today: - competitor product - manual workaround - internal process - agency / consultant - free tool - spreadsheet - doing nothing - ignoring the problem For each alternative explain why customers choose it and why they may leave it. Layer F - Demand quality Score each problem by: - urgency - frequency - willingness to pay - current dissatisfaction - switching likelihood - competitive saturation - strategic fit Final output: 1. Problem landscape map 2. Top 10 customer problems ranked 3. Highest-value customer segment 4. Most important buying triggers 5. Language bank with exact phrases 6. Product or offer implications 7. Research gaps to validate next Rules: - Do not invent customer quotes. - Keep exact phrases in quotation marks only if provided. - Separate observed evidence from interpretation. - Do not assume the loudest complaint is the biggest market opportunity. - Mark every inferred insight as [INFERENCE]. --------------------------------------------------------------------------------

#023Competitive Battlefield Map

MARKET RESEARCH & COMPETITIVE ANALYSISBusiness strategy, product marketing, founders, category analysis, market entry, positioning work, and investor or leadership research.

Map the full competitive landscape, including direct competitors, indirect competitors, substitutes, customer workarounds, and strategic threats.

You are a competitive intelligence analyst. Build a competitive battlefield map for [COMPANY NAME] in [MARKET / CATEGORY] that shows who competes for the same customer decision and where the company can win. Inputs: Company: [COMPANY NAME] Market / category: [MARKET] Target customer: [CUSTOMER] Product / service: [PRODUCT / SERVICE] Known competitors: [KNOWN COMPETITORS] Customer alternatives: [ALTERNATIVES] Geography: [GEOGRAPHY] Price range: [PRICE RANGE] Primary buying decision: [BUYING DECISION] Available competitor data: [DATA] Strategic question: [QUESTION] Create the battlefield map: Battlefield 1 - Direct competitors Identify competitors that sell a similar solution to the same customer. For each include: - competitor name - target customer - core offer - positioning - pricing signal - distribution channels - strengths - weaknesses - proof used - likely customer reason to choose them - likely customer reason to leave them Battlefield 2 - Indirect competitors Identify solutions that solve the same problem differently. For each include: - solution type - customer use case - why it competes - where it wins - where it fails - switching difficulty Battlefield 3 - Substitutes and workarounds Map: - spreadsheets - manual processes - internal teams - consultants - free tools - generic platforms - doing nothing - cheaper alternatives - status quo For each explain what belief keeps customers there. Battlefield 4 - Category power map Analyze the category by: - premium players - low-cost players - niche specialists - broad platforms - legacy incumbents - new entrants - community-led players - channel-dominant players Battlefield 5 - Competitive pressure zones Identify where competition is strongest: - price - speed - features - trust - brand - distribution - integrations - service - convenience - specialization - proof Battlefield 6 - Strategic implications Answer: - where is the market overcrowded? - where are competitors over-serving customers? - where are customers underserved? - which competitors are most dangerous? - which competitors are easiest to beat? - which battles should [COMPANY NAME] avoid? - which battle can [COMPANY NAME] win with proof? Final artifact: Create a battlefield table, a competitor grouping map, and a strategic recommendation. Rules: - Do not limit competition to companies that look similar. - Do not assume the biggest competitor is the most dangerous. - Do not exaggerate competitor weaknesses without evidence. - Use [NEEDS DATA] where competitor information is missing. --------------------------------------------------------------------------------

#024Market Size & Opportunity Model

MARKET RESEARCH & COMPETITIVE ANALYSISStartups, investors, founders, consultants, business planning, new market entry, product launches, and expansion decisions.

Estimate market potential using TAM, SAM, SOM, accessible demand, adoption constraints, and realistic capture assumptions.

Act as a market sizing analyst. Build a realistic market size and opportunity model for [PRODUCT / SERVICE] in [MARKET] without relying on inflated top-down numbers. Inputs: Product / service: [PRODUCT / SERVICE] Market / category: [MARKET] Target customer: [CUSTOMER] Geography: [GEOGRAPHY] Pricing / revenue model: [PRICING] Estimated customer count: [CUSTOMER COUNT] Customer spend data: [SPEND DATA] Adoption assumptions: [ADOPTION] Competitive landscape: [COMPETITORS] Distribution constraints: [DISTRIBUTION] Operational constraints: [OPERATIONS] Time horizon: [TIME HORIZON] Available data: [DATA SOURCES] Build the model using four passes: Pass 1 - Define the market boundary Clarify: - what is included - what is excluded - target customer definition - buying situation - use case - geography - price tier - category substitutes Pass 2 - Estimate TAM Create a top-down and bottom-up TAM estimate. For each include: - formula - assumptions - data needed - confidence level - risk of overstatement Pass 3 - Estimate SAM Define the serviceable available market based on: - target segment - geography - price fit - buying readiness - channel access - product fit - regulatory or operational constraints Pass 4 - Estimate SOM Estimate realistic obtainable market based on: - current resources - distribution strength - sales capacity - marketing reach - competitor pressure - switching friction - brand trust - time horizon Scenario table: Create three scenarios: - conservative - realistic - aggressive For each include: - customer count - conversion assumption - average revenue - annual revenue potential - market share assumption - confidence level - key risk Opportunity quality score: Score the opportunity across: - size - urgency - ability to reach customers - willingness to pay - competitive intensity - margin potential - retention potential - execution feasibility Final output: - market sizing summary - assumption table - scenario model - key sensitivity variables - recommendation - data to validate next Rules: - Do not invent market statistics. - Do not present TAM as a revenue forecast. - Do not use unrealistic market share assumptions. - Mark all unsupported inputs as [ASSUMPTION]. - Prefer honest ranges over fake precision. --------------------------------------------------------------------------------

#025Segment Attractiveness Prioritizer

MARKET RESEARCH & COMPETITIVE ANALYSISFounders, B2B companies, SaaS teams, agencies, consultants, ecommerce brands, and companies choosing a beachhead market.

Compare customer segments and decide which segment should be prioritized based on pain, willingness to pay, access, competition, profitability, and strategic fit.

You are a segmentation strategist. Prioritize the best customer segments for [COMPANY NAME] using structured market evidence, customer value, accessibility, and competitive advantage. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Potential segments: [SEGMENTS] Current customers: [CUSTOMERS] Revenue by segment: [REVENUE] Customer feedback: [FEEDBACK] Sales notes: [SALES NOTES] Competitors by segment: [COMPETITORS] Pricing / margins: [PRICING / MARGINS] Channels available: [CHANNELS] Team capabilities: [CAPABILITIES] Strategic goal: [GOAL] Use this evaluation canvas for each segment: Segment identity: - segment name - who they are - defining traits - buying context - decision maker - user - budget holder - current alternatives Pain and demand: - primary pain - urgency - frequency - cost of inaction - trigger event - desired outcome - existing dissatisfaction Commercial attractiveness: - willingness to pay - deal size / order value - margin potential - sales cycle - retention potential - expansion potential - referral potential - support burden Go-to-market feasibility: - reachability - channel access - message clarity - proof needed - sales complexity - onboarding difficulty - trust barriers Competitive dynamics: - competitor saturation - dominant alternatives - underserved needs - switching difficulty - differentiation opportunity Strategic fit: - capability fit - brand fit - product fit - operational fit - long-term value - risk Scoring output: Create a ranked table with: - segment - demand score - commercial score - reachability score - competitive score - strategic fit score - risk score - total score - recommendation Then create: 1. Primary segment recommendation 2. Secondary segment recommendation 3. Segment to avoid 4. Segment-specific positioning angle 5. First validation test for the top segment 6. Data gaps to close Rules: - Do not choose the largest segment automatically. - Do not prioritize a segment the company cannot reach. - Do not ignore cost to serve. - Mark missing segment data as [NEEDS DATA]. --------------------------------------------------------------------------------

#026Competitor Positioning Reverse Engineer

MARKET RESEARCH & COMPETITIVE ANALYSISProduct marketers, copywriters, founders, competitive intelligence teams, consultants, agencies, and positioning projects.

Reverse-engineer how competitors position themselves, what customer beliefs they target, and where their messaging creates strategic openings.

Act as a positioning intelligence analyst. Reverse-engineer the positioning of the competitors below and identify how [COMPANY NAME] can differentiate. Competitors to analyze: [PASTE COMPETITOR WEBSITES / MESSAGING / ADS / LANDING PAGES / SALES MATERIALS] Company context: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customer: [CUSTOMER] Current positioning: [POSITIONING] Customer problem: [PROBLEM] Proof available: [PROOF] Strategic goal: [GOAL] Analyze each competitor through this structure: A. The promise Extract: - headline promise - implied customer problem - implied desired outcome - main value proposition - emotional promise - rational promise B. The customer belief shift Identify: - what the competitor assumes the customer already believes - what the competitor wants the customer to believe - what fear or aspiration they activate - what objection they preempt C. The proof system List: - claims - proof types - testimonials - metrics - logos - case studies - guarantees - product evidence - unsupported claims Mark claims without proof as [UNSUPPORTED]. D. The differentiation frame Identify whether the competitor differentiates through: - price - speed - quality - simplicity - specialization - features - service - trust - status - technology - community - convenience - risk reduction E. Messaging weaknesses Find openings: - vague language - overused claims - underserved segment - unsupported proof - confusing category - weak objection handling - missing emotional angle - weak comparison - too much jargon - lack of specificity F. Strategic contrast For [COMPANY NAME], recommend: - positioning angle to avoid - positioning angle to own - claims to support with proof - competitor contrast line - message pillar opportunities - website messaging implications Final output: 1. Competitor positioning table 2. Category message patterns 3. Overused language list 4. Differentiation opportunities 5. Recommended positioning direction for [COMPANY NAME] Rules: - Do not copy competitor language. - Do not attack competitors without evidence. - Do not call something differentiated if several competitors claim it. - Separate observed copy from interpretation. --------------------------------------------------------------------------------

#027Voice-of-Market Signal Synthesizer

MARKET RESEARCH & COMPETITIVE ANALYSISResearchers, founders, product marketers, category analysts, content strategists, agencies, and teams with fragmented customer and competitor data.

Turn messy market signals from reviews, forums, social posts, reports, calls, and search behavior into strategic insight.

You are a market signal synthesis expert. Analyze the raw market signals below and convert them into a usable strategic intelligence brief. Raw signals: [PASTE REVIEWS / FORUM POSTS / REDDIT THREADS / SOCIAL COMMENTS / SUPPORT NOTES / SALES CALL NOTES / SURVEY ANSWERS / SEARCH QUERIES / NEWS / REPORT EXCERPTS] Context: Market: [MARKET] Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customer: [CUSTOMER] Competitors: [COMPETITORS] Business decision: [DECISION] Synthesize the signals in this exact format: Signal Inventory Create a table with: - signal - source - who said or produced it - customer segment - theme - sentiment - intensity - frequency - business relevance - confidence Theme Clustering Cluster signals into: - pain themes - desire themes - objection themes - competitor complaint themes - category confusion themes - buying trigger themes - pricing themes - trust themes - innovation themes - retention themes Contradiction Finder Identify contradictions such as: - customers say they want low price but complain about quality - customers want simplicity but request advanced features - buyers want speed but fear implementation risk - users love the product but decision makers resist - market buzz is high but purchase intent is low For each contradiction explain: - why it matters - what it could mean - what research would resolve it Strategic Translation Convert themes into: - segment opportunities - positioning ideas - product implications - pricing implications - content opportunities - sales enablement needs - risk warnings - validation tests Evidence Grading Grade each insight as: - strong evidence - repeated signal - directional signal - anecdote - weak signal - needs validation Final Intelligence Brief Write: - 5 strongest market insights - 5 customer language phrases - 5 competitor weakness signals - 5 opportunity hypotheses - 5 research questions to answer next Rules: - Do not overgeneralize from one signal. - Do not invent sources. - Keep customer language exact when quoted. - Use [WEAK SIGNAL] when evidence is thin. --------------------------------------------------------------------------------

#028Category Trend & Timing Radar

MARKET RESEARCH & COMPETITIVE ANALYSISFounders, investors, strategists, market researchers, consultants, product teams, and leadership teams evaluating timing.

Identify market trends, timing signals, adoption drivers, risks, and strategic implications for entering or expanding in a category.

Act as a category trend analyst. Build a trend and timing radar for [CATEGORY / MARKET] so [COMPANY NAME] can understand whether now is the right time to enter, expand, or reposition. Inputs: Category / market: [CATEGORY] Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Geography: [GEOGRAPHY] Known trends: [TRENDS] Technology shifts: [TECHNOLOGY] Regulatory shifts: [REGULATION] Customer behavior shifts: [BEHAVIOR] Competitor activity: [COMPETITOR ACTIVITY] Investment / funding signals: [FUNDING] Search / demand signals: [DEMAND] Time horizon: [HORIZON] Decision to support: [DECISION] Build the radar: Ring 1 - Customer behavior shifts Identify what customers are doing differently: - new pains - new expectations - new buying criteria - new channels - new willingness to pay - new trust concerns - new switching behavior Ring 2 - Competitive movement Identify: - new entrants - incumbent moves - pricing changes - product launches - partnership activity - acquisitions - messaging shifts - channel shifts Ring 3 - Technology and capability shifts Analyze: - enabling technologies - cost reductions - automation - infrastructure improvements - adoption barriers falling - capability gaps remaining Ring 4 - Market and economic forces Analyze: - budget cycles - cost pressure - labor changes - regulation - supply shifts - macro pressure - category maturity Ring 5 - Timing signals Classify signals as: - early - accelerating - mainstreaming - saturated - declining - hype without adoption For each signal include: - evidence - implication - confidence - risk of misreading Strategic timing conclusion: Answer: - is this market too early, timely, late, or declining? - what must be true for success? - what should the company do now? - what should it wait on? - what should it monitor? Final output: - trend radar table - timing diagnosis - adoption drivers - adoption barriers - strategic recommendation - early warning signals Rules: - Do not treat hype as demand. - Do not assume a trend benefits every company. - Do not ignore regulation, economics, or operational capacity. - Mark uncertain trends as [UNCERTAIN]. --------------------------------------------------------------------------------

#029Demand Validation Sprint Planner

MARKET RESEARCH & COMPETITIVE ANALYSISStartups, new products, market entry, service launches, consultants, founders, and teams validating offers before building.

Design a fast validation sprint to test demand, willingness to pay, messaging, channel access, and customer urgency before committing resources.

You are a demand validation sprint coach. Design a practical research sprint for [PRODUCT / SERVICE IDEA] that tests whether the market wants it, understands it, and may pay for it. Inputs: Product / service idea: [IDEA] Target customer: [CUSTOMER] Problem hypothesis: [PROBLEM HYPOTHESIS] Value proposition: [VALUE PROPOSITION] Price hypothesis: [PRICE] Target geography: [GEOGRAPHY] Available channels: [CHANNELS] Budget: [BUDGET] Timeline: [TIMELINE] Team capacity: [CAPACITY] Existing audience or list: [AUDIENCE] Decision after sprint: [DECISION] Design the sprint: Sprint North Star Define: - primary validation question - highest-risk assumption - minimum evidence needed - decision rule - stop condition Sprint Board Create a sprint board with columns: - assumption - test method - audience - asset needed - channel - metric - pass threshold - fail threshold - owner - deadline Test Menu Design 8 validation tests, including: - customer interview test - landing page test - waitlist test - paid traffic smoke test - direct outreach test - pricing conversation test - competitor switching test - concierge offer test For each test include: - what it validates - how to run it - script or prompt - sample size target - success signal - false positive risk - false negative risk Customer Interview Script Create: - screener questions - problem discovery questions - current alternative questions - urgency questions - buying process questions - price sensitivity questions - closing question Signal Interpretation Define what to do if: - people love the idea but will not pay - people click but do not convert - people complain about the problem but do nothing - one segment responds strongly - feedback is positive but vague - competitors already satisfy the need Final Decision Memo Create a template for: - validated - partially validated - invalidated - pivot required - more research required Rules: - Do not validate demand only by asking if people like the idea. - Do not count compliments as purchase intent. - Do not overbuild before testing. - Make the sprint cheap, fast, and decision-focused. --------------------------------------------------------------------------------

#030Competitive Pricing & Packaging Benchmark

MARKET RESEARCH & COMPETITIVE ANALYSISSaaS teams, service businesses, ecommerce brands, consultants, founders, product marketers, pricing teams, and market researchers.

Compare competitor pricing, packaging, tiers, value metrics, discounts, guarantees, and monetization logic to improve pricing decisions.

Act as a pricing and packaging intelligence analyst. Benchmark the pricing and packaging of competitors in [MARKET / CATEGORY] and identify strategic implications for [COMPANY NAME]. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Market / category: [MARKET] Target customer: [CUSTOMER] Current pricing: [CURRENT PRICING] Current packaging: [PACKAGING] Competitors to benchmark: [COMPETITORS] Competitor pricing pages or notes: [PASTE DATA] Customer objections about price: [OBJECTIONS] Margin or cost constraints: [MARGINS / COSTS] Strategic goal: [GOAL] Analyze pricing using this framework: Section 1 - Competitor pricing inventory For each competitor capture: - pricing model - entry price - premium price - tiers - included features / services - limits - add-ons - contract terms - discounts - free trial / free plan - guarantee - value metric - hidden costs - sales-led vs self-serve motion Section 2 - Packaging logic Identify what each competitor uses to separate tiers: - usage - seats - features - support - service level - speed - integrations - volume - customization - outcomes - customer size - risk reduction Section 3 - Price positioning map Classify competitors as: - budget - value - premium - enterprise - specialist - bundle-led - freemium-led - custom quote-led Section 4 - Customer interpretation Explain what customers may infer from each pricing strategy: - quality - trust - complexity - affordability - scalability - hidden risk - seriousness - flexibility Section 5 - Strategic openings Identify: - overcomplicated pricing - underserved entry segment - premium gap - bundle opportunity - risk reversal opportunity - better value metric - clearer packaging - stronger guarantee - less confusing tier structure Section 6 - Recommendation for [COMPANY NAME] Recommend: - pricing position - packaging structure - tier names - value metric - what to include - what to hold back - objection handling - testing plan Rules: - Do not copy competitor pricing blindly. - Do not recommend lower prices unless strategically justified. - Do not ignore margin and cost to serve. - Mark unknown competitor data as [NEEDS DATA]. --------------------------------------------------------------------------------

#031Buyer Journey Research Blueprint

MARKET RESEARCH & COMPETITIVE ANALYSISB2B companies, SaaS teams, service businesses, agencies, consultants, sales-led organizations, and complex buying journeys.

Research how buyers move from problem awareness to vendor selection, including triggers, stakeholders, criteria, objections, and proof needs.

You are a buyer journey researcher. Create a research blueprint for understanding how [TARGET CUSTOMER] buys [PRODUCT / SERVICE CATEGORY]. Inputs: Target customer: [CUSTOMER] Category: [CATEGORY] Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Current sales process: [SALES PROCESS] Known buyer roles: [BUYER ROLES] Average deal size / order value: [DEAL SIZE] Sales cycle: [SALES CYCLE] Lost deal reasons: [LOST DEAL REASONS] Customer interviews available: [INTERVIEWS] Sales call notes: [CALL NOTES] CRM data: [CRM DATA] Strategic decision: [DECISION] Build the blueprint as a research field guide: Field Guide Part 1 - Buying stages Map the journey: - status quo - problem awareness - internal discussion - research - shortlist - evaluation - approval - purchase - implementation - renewal or repeat purchase For each stage capture: - buyer mindset - question asked - trigger - stakeholder involved - information needed - proof needed - objection - competitor risk - content or sales asset needed - success metric Field Guide Part 2 - Stakeholder map Identify: - end user - economic buyer - technical evaluator - influencer - blocker - executive sponsor - procurement - external advisor For each include: - motivation - fear - decision criteria - proof trusted - language used - influence level Field Guide Part 3 - Interview questions Write research questions for: - recent buyers - lost prospects - current customers - sales team - customer success - competitor switchers Field Guide Part 4 - Evidence capture template Create a template to record: - exact quote - buying stage - stakeholder - trigger - objection - proof need - competitor mentioned - confidence level Field Guide Part 5 - Strategic outputs Show how research will update: - positioning - website - sales deck - nurture emails - case studies - pricing page - objection handling - product roadmap Rules: - Do not assume the buyer journey is linear. - Do not ignore internal politics or approval steps. - Do not treat users and buyers as the same person unless evidence supports it. - Keep research tied to sales and marketing decisions. --------------------------------------------------------------------------------

#032Jobs-to-Be-Done Interview Synthesizer

MARKET RESEARCH & COMPETITIVE ANALYSISProduct teams, founders, UX researchers, product marketers, consultants, innovation teams, and positioning projects.

Analyze customer interviews through a Jobs-to-Be-Done lens to reveal triggers, desired progress, tradeoffs, anxieties, and alternatives.

Act as a Jobs-to-Be-Done research analyst. Analyze the interview material below and identify the real job customers are hiring a solution to do. Interview material: [PASTE CUSTOMER INTERVIEWS / NOTES / TRANSCRIPTS] Context: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customer: [CUSTOMER] Market category: [CATEGORY] Research goal: [GOAL] Use this JTBD analysis structure: 1. Timeline reconstruction For each interview, reconstruct: - first thought - passive looking - active looking - deciding event - purchase or adoption - first use - success or disappointment 2. Four forces analysis Identify: Push of the current situation: - what made the old way painful? Pull of the new solution: - what attracted them to change? Anxiety of the new solution: - what made them hesitate? Habit of the present: - what kept them stuck? 3. Job statement Write job statements in this format: When [SITUATION], I want to [MOTIVATION], so I can [DESIRED PROGRESS]. Create multiple versions if segments differ. 4. Progress definition Define what progress means: - functional progress - emotional progress - social progress - financial progress - operational progress 5. Competing solutions List what customers hired before: - competitor - workaround - internal process - doing nothing - manual method - friend / expert / agency - free resource 6. Buying language Extract exact phrases for: - trigger - frustration - desired outcome - anxiety - comparison - value - success 7. Strategic implications Translate findings into: - positioning - messaging - product improvements - onboarding - pricing - sales questions - content topics - competitive differentiation Rules: - Do not force one job if interviews show multiple jobs. - Do not invent quotes. - Do not ignore anxieties and tradeoffs. - Mark weak patterns as [WEAK SIGNAL]. --------------------------------------------------------------------------------

#033Review Mining & Objection Map

MARKET RESEARCH & COMPETITIVE ANALYSISEcommerce, SaaS, local businesses, agencies, product marketers, founders, copywriters, and customer research teams.

Mine competitor and category reviews to reveal customer expectations, satisfaction drivers, complaints, objections, and language.

You are a review mining analyst. Analyze the reviews below to uncover what customers value, dislike, compare, fear, and expect in [CATEGORY]. Review data: [PASTE REVIEWS FROM COMPETITORS / MARKETPLACES / G2 / CAPTERRA / AMAZON / GOOGLE / APP STORES / REDDIT / FORUMS] Context: Category: [CATEGORY] Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customer: [CUSTOMER] Competitors reviewed: [COMPETITORS] Strategic decision: [DECISION] Mine the reviews in this output format: A. Review source summary Create: - source - competitor / product - review type - customer type, if visible - review volume - rating pattern - confidence level B. Positive driver map Identify what customers praise: - feature - outcome - service experience - speed - quality - ease - price - reliability - support - trust - status - convenience For each driver include representative phrases and strategic implication. C. Complaint map Identify what customers criticize: - missing feature - poor quality - complexity - cost - support - delivery - onboarding - reliability - hidden fees - unmet expectation - poor fit - switching difficulty D. Objection map Convert review complaints into likely objections: - customer fear - objection wording - proof needed - message response - product or service fix - sales enablement use E. Language bank Extract customer language for: - pain - delight - comparison - regret - surprise - frustration - value - trust - switching F. Opportunity map Identify: - competitor weaknesses to exploit - product gaps to consider - messaging angles - FAQ topics - proof assets needed - market expectations - non-negotiable table stakes G. Final recommendations Create: - top 10 insights - top 5 objections - top 5 product implications - top 5 positioning opportunities - top 5 claims to avoid Rules: - Do not invent review quotes. - Do not overgeneralize from a small number of reviews. - Do not use private or sensitive data. - Label insights as [REPEATED PATTERN], [SINGLE SIGNAL], or [NEEDS VALIDATION]. --------------------------------------------------------------------------------

#034White Space Opportunity Finder

MARKET RESEARCH & COMPETITIVE ANALYSISMarket entry, new product planning, repositioning, innovation strategy, competitive analysis, and growth planning.

Identify underserved customer needs, market gaps, weak competitor positions, and strategic white space where a company can win.

Act as a white space strategist. Find market gaps in [MARKET / CATEGORY] where [COMPANY NAME] may have a realistic opportunity to win. Inputs: Company: [COMPANY NAME] Market / category: [MARKET] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Competitors: [COMPETITORS] Competitor data: [COMPETITOR DATA] Customer research: [CUSTOMER RESEARCH] Review mining insights: [REVIEWS] Trend signals: [TRENDS] Company strengths: [STRENGTHS] Company constraints: [CONSTRAINTS] Strategic goal: [GOAL] Run the white space analysis through 7 filters: Filter 1 - Unserved needs Identify customer needs competitors do not address. Filter 2 - Underserved needs Identify needs competitors address poorly. Filter 3 - Overserved needs Identify where competitors add complexity, cost, or features customers do not value. Filter 4 - Audience gaps Identify customer segments that are ignored, misunderstood, or poorly served. Filter 5 - Experience gaps Identify gaps in buying, onboarding, delivery, support, trust, or retention. Filter 6 - Pricing and packaging gaps Identify opportunities in: - simpler pricing - premium packaging - entry-level offer - bundle - guarantee - service level - transparent pricing Filter 7 - Positioning gaps Identify messages nobody clearly owns. For each white space opportunity include: - opportunity name - customer need - evidence - competitors failing - why the gap exists - company fit - difficulty - risk - expected upside - first validation test - confidence level Prioritize opportunities with this scoring model: Opportunity Score = Customer Pain x Market Size x Company Fit x Differentiation Potential x Reachability - Execution Risk Final output: 1. White space opportunity table 2. Top 3 recommended opportunities 3. Opportunity to reject 4. Positioning angle for each top opportunity 5. Validation roadmap 6. Strategic recommendation Rules: - Do not treat every competitor weakness as a viable opportunity. - Do not recommend gaps the company cannot credibly fill. - Do not ignore why the white space exists. - Mark speculative opportunities as [HYPOTHESIS]. --------------------------------------------------------------------------------

#035Channel & Distribution Research Analyzer

MARKET RESEARCH & COMPETITIVE ANALYSISGo-to-market planning, startups, B2B SaaS, ecommerce, agencies, local businesses, consultants, and market entry strategies.

Research where customers discover, evaluate, and buy solutions, and which channels competitors use to reach them.

You are a distribution research analyst. Analyze the market to identify how [TARGET CUSTOMER] discovers, evaluates, and buys [CATEGORY / SOLUTION], and which channels [COMPANY NAME] should prioritize. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Market / category: [MARKET] Target customer: [CUSTOMER] Competitors: [COMPETITORS] Known channels: [KNOWN CHANNELS] Customer journey data: [CUSTOMER JOURNEY] Search demand data: [SEARCH DATA] Social / community data: [SOCIAL DATA] Sales data: [SALES DATA] Budget: [BUDGET] Team capability: [CAPABILITY] Strategic goal: [GOAL] Create the channel research analysis: Discovery Map Where customers first become aware: - search - social - communities - referrals - influencers - events - marketplaces - app stores - directories - review sites - sales outreach - partners - paid ads - media / PR Evaluation Map Where customers compare options: - competitor websites - review platforms - YouTube - analyst reports - comparison pages - forums - peer groups - sales calls - trials - demos - marketplaces - case studies Purchase Map Where customers convert: - website - sales team - marketplace - distributor - retail - partner - procurement process - app platform - direct message - subscription checkout Competitor Channel Audit For each competitor identify: - visible channels - strongest channel - weakest channel - content strategy - paid presence - SEO presence - partner presence - marketplace presence - community presence - sales motion - evidence level Channel Fit Score Score each channel by: - customer presence - intent level - cost - speed - scalability - trust - competition - capability fit - measurement ease - strategic value Channel Recommendation Classify channels as: - primary - secondary - test - monitor - avoid For each recommended channel include: - why it matters - first experiment - content or asset needed - metric - timeline - risk Rules: - Do not choose channels because competitors use them unless customer behavior supports it. - Do not ignore sales and partner channels. - Do not assume social attention equals buying intent. - Mark channel assumptions as [ASSUMPTION]. --------------------------------------------------------------------------------

#036Market Entry Risk Brief

MARKET RESEARCH & COMPETITIVE ANALYSISFounders, leadership teams, investors, consultants, expansion planning, new product launches, and geographic market entry.

Assess whether entering a market is strategically sound by analyzing demand, competition, economics, regulation, operations, timing, and execution risk.

Act as a market entry risk advisor. Create a decision-ready risk brief for [COMPANY NAME] entering [TARGET MARKET]. Inputs: Company: [COMPANY NAME] Target market: [MARKET] Product / service: [PRODUCT / SERVICE] Target customer: [CUSTOMER] Geography: [GEOGRAPHY] Entry strategy under consideration: [ENTRY STRATEGY] Market evidence: [MARKET EVIDENCE] Customer evidence: [CUSTOMER EVIDENCE] Competitors: [COMPETITORS] Financial assumptions: [FINANCIAL ASSUMPTIONS] Operational requirements: [OPERATIONS] Regulatory constraints: [REGULATION] Team capability: [CAPABILITY] Timeline: [TIMELINE] Write the brief as a leadership risk memo: Opening verdict Start with one of: - Enter now - Enter through a limited test - Delay entry - Do not enter - More research required Then explain why in 5 sentences or fewer. Risk Register Create a risk register with: - risk - category - likelihood - impact - early warning signal - mitigation - owner - confidence level Use these categories: - demand risk - competitive risk - pricing risk - margin risk - channel risk - regulatory risk - operational risk - brand risk - timing risk - capital risk - execution risk Entry Assumption Test List the assumptions that must be true: - customers have urgent pain - current alternatives are insufficient - willingness to pay exists - company can reach the market - unit economics work - operations can deliver - differentiation is credible - timing is favorable For each include: - evidence for - evidence against - validation method - pass/fail threshold Competitive Reaction Scenario Predict likely competitor reactions: - ignore - copy - discount - outspend - partner - lock distribution - attack positioning - improve product Entry Options Compare: - full launch - pilot - partnership - acquisition - distributor - niche beachhead - wait-and-monitor Final Recommendation Provide: - recommended entry path - first 30 days - first validation milestone - stop condition - scale condition - next leadership decision Rules: - Do not recommend market entry just because the market is large. - Do not hide operational or regulatory risk. - Do not treat competitor silence as safety. - Use [LOW CONFIDENCE] where evidence is weak. --------------------------------------------------------------------------------

#037Competitive Moat & Vulnerability Audit

MARKET RESEARCH & COMPETITIVE ANALYSISLeadership strategy, investor preparation, competitive defense, product strategy, SaaS, agencies, service businesses, and scaling companies.

Identify where a company has durable advantage, where competitors can attack, and what strategic defenses should be built.

You are a competitive strategy auditor. Audit the moat and vulnerabilities of [COMPANY NAME] against current and future competitors. Inputs: Company: [COMPANY NAME] Market / category: [MARKET] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Business model: [BUSINESS MODEL] Current advantages: [ADVANTAGES] Competitors: [COMPETITORS] Customer loyalty signals: [LOYALTY] Switching costs: [SWITCHING COSTS] Brand strength: [BRAND] Distribution channels: [DISTRIBUTION] Data / technology assets: [ASSETS] Operational strengths: [OPERATIONS] Financial constraints: [FINANCIALS] Audit in two columns: Moat vs Vulnerability. Moat Inventory Evaluate potential moats: - brand - distribution - switching cost - network effect - proprietary data - technology - operational excellence - cost advantage - customer relationships - community - regulation / certification - partnerships - speed - specialization - service quality For each moat include: - evidence - strength score - durability - customer value - copyability - investment needed - risk Vulnerability Inventory Identify where competitors could attack: - lower price - better features - faster service - easier onboarding - stronger brand - better distribution - better proof - stronger partnerships - vertical specialization - superior customer experience - better financing - aggressive content or SEO Attack Simulation For the top 5 threats, simulate: - competitor move - why it would work - customers most at risk - early warning signal - defensive response - proactive move Moat-Building Plan Recommend actions to strengthen: - customer lock-in ethically - brand trust - product differentiation - distribution access - data advantage - service experience - partnerships - operational efficiency Final output: - moat scorecard - vulnerability map - competitor attack scenarios - defensive priorities - 12-month moat-building roadmap Rules: - Do not call something a moat if it is easy to copy. - Do not confuse current traction with durable advantage. - Do not recommend unethical lock-in. - Mark weak moat claims as [UNPROVEN]. --------------------------------------------------------------------------------

#038Strategic Intelligence Weekly Brief

MARKET RESEARCH & COMPETITIVE ANALYSISFounders, CMOs, product marketers, competitive intelligence teams, consultants, agencies, and leadership teams that need ongoing market awareness.

Create a repeatable weekly intelligence brief that tracks competitor moves, customer signals, market changes, and strategic implications.

Act as a strategic intelligence analyst. Create a weekly market and competitive intelligence brief for [COMPANY NAME] using the updates below. Weekly inputs: Company: [COMPANY NAME] Market / category: [MARKET] Competitors tracked: [COMPETITORS] Customer signals observed: [CUSTOMER SIGNALS] Competitor updates: [COMPETITOR UPDATES] Pricing changes: [PRICING CHANGES] Product launches: [PRODUCT LAUNCHES] Marketing / content changes: [MARKETING CHANGES] Funding / hiring / partnership news: [NEWS] Search / social / review signals: [DEMAND SIGNALS] Sales team observations: [SALES NOTES] Customer support observations: [SUPPORT NOTES] Leadership priorities: [PRIORITIES] Create the weekly brief: Headline Summary Write 5 bullets: - most important market change - most important competitor move - most important customer signal - biggest risk - recommended leadership action Signal Log Create a table with: - date - signal - source - category - competitor / customer / market - importance - confidence - strategic implication - owner to follow up Competitor Watch For each tracked competitor include: - new move - what changed - likely reason - customer segment affected - threat level - recommended response Customer Signal Watch Summarize: - new pains - repeated objections - buying triggers - review themes - lost deal reasons - support themes - customer language Market Movement Summarize: - trend changes - regulation changes - funding signals - technology shifts - channel shifts - pricing pressure Decision Implications Classify actions: - act now - investigate - monitor - ignore - escalate Next Week Research Agenda List: - 5 questions to investigate - data needed - owner - expected decision impact Rules: - Do not include news with no strategic implication. - Do not confuse competitor activity with competitor success. - Do not overreact to one signal. - Keep the brief short enough for leadership to read in 5 minutes. --------------------------------------------------------------------------------

#039Research-to-Decision Memo Builder

MARKET RESEARCH & COMPETITIVE ANALYSISLeadership teams, founders, consultants, product marketers, business analysts, investor updates, strategy meetings, and go/no-go decisions.

Convert market research and competitive analysis into a clear decision memo with evidence, options, risks, recommendation, and next steps.

You are a strategy memo writer. Convert the market research below into a decision-ready memo for leadership. Research materials: [PASTE MARKET RESEARCH / COMPETITOR ANALYSIS / CUSTOMER INSIGHTS / SURVEY RESULTS / INTERVIEW FINDINGS / MARKET SIZE MODEL] Decision context: Company: [COMPANY NAME] Decision to make: [DECISION] Options being considered: [OPTIONS] Business goal: [GOAL] Timeline: [TIMELINE] Budget / resource constraints: [CONSTRAINTS] Risk tolerance: [RISK TOLERANCE] Audience for memo: [CEO / BOARD / INVESTORS / TEAM / CLIENT] Write the memo in this structure: 1. Decision headline One sentence: We recommend [ACTION] because [REASON], with [RISK] as the main uncertainty. 2. Context Explain: - why this decision matters now - what prompted the research - what was analyzed - what was not analyzed - what constraints matter 3. Evidence summary Create an evidence table: - finding - evidence - source - strength - implication - confidence level 4. Options For each option include: - description - upside - downside - cost - time to impact - operational requirements - competitive risk - customer risk - evidence supporting it - evidence against it 5. Recommendation State the recommended option and explain: - why it is best - what tradeoff it accepts - what assumption matters most - what would change the recommendation 6. Risk and uncertainty List: - known risks - unknowns - assumptions - weak evidence - possible false positives - possible false negatives 7. Next actions Create: - immediate next step - owner - timeline - validation needed - budget - success metric - decision checkpoint 8. Executive version Rewrite the memo as a 150-word executive summary. Rules: - Do not hide weak evidence. - Do not turn research into a data dump. - Do not recommend without naming the tradeoff. - Use [LOW CONFIDENCE] where evidence is limited. - The memo must help leadership make a decision. --------------------------------------------------------------------------------

#040Full Market Research & Competitive Analysis Audit

MARKET RESEARCH & COMPETITIVE ANALYSISStrategy resets, market entry, product launches, investor preparation, consulting diagnostics, annual planning, and leadership alignment.

Audit the full research and competitive intelligence system across market clarity, customer insight, demand, segmentation, competitors, pricing, channels, risks, and decision quality.

Act as an independent market research and competitive analysis auditor. Review the full research system for [COMPANY NAME] and identify the highest-leverage improvements. Inputs: Company: [COMPANY NAME] Market / category: [MARKET] Business model: [BUSINESS MODEL] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Current market research: [MARKET RESEARCH] Customer research: [CUSTOMER RESEARCH] Competitor analysis: [COMPETITOR ANALYSIS] Market size assumptions: [MARKET SIZE] Segmentation: [SEGMENTATION] Pricing research: [PRICING RESEARCH] Channel research: [CHANNEL RESEARCH] Trend analysis: [TRENDS] Strategic decisions supported: [DECISIONS] Known assumptions: [ASSUMPTIONS] Leadership concerns: [CONCERNS] Audit the research system across 14 dimensions: 1. Market definition clarity 2. Customer problem understanding 3. Segment prioritization 4. Demand evidence 5. Buyer journey insight 6. Competitive landscape coverage 7. Competitor positioning analysis 8. Pricing and packaging intelligence 9. Channel and distribution insight 10. Market size realism 11. Trend and timing analysis 12. White space identification 13. Research quality and bias control 14. Decision usefulness For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - strategic risk - decision risk - recommended fix - confidence level Then synthesize: A. Top 5 research gaps Rank the biggest gaps by decision impact, revenue risk, strategic risk, urgency, and ease of fixing. B. Root cause analysis Identify whether the main issue is: - unclear market boundary - weak customer evidence - shallow competitor analysis - inflated market sizing - no segmentation discipline - poor pricing intelligence - missing channel research - unvalidated demand - trend misreading - research not tied to decisions - leadership using assumptions as facts C. Rebuilt research strategy Create: - priority research questions - research methods - data sources - competitor tracking system - customer research plan - pricing research plan - channel research plan - decision memo format D. 30/60/90-day research repair plan Create a practical plan with: - research projects - owners - data needed - methods - outputs - decision checkpoints - expected strategic use E. Stop / Start / Continue List what the team should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with the hard truth, the opportunity, and the next research decision. Rules: - Do not invent market facts. - Do not treat competitor lists as competitive analysis. - Do not accept research that does not improve a decision. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on market truth, customer evidence, competitive reality, and better strategic choices.

#041Business Model Blueprint Architect

BUSINESS MODEL & MONETIZATIONFounders, CEOs, startup teams, consultants, business strategists, product leaders, and operators designing or rebuilding a business model.

Build a complete business model blueprint that explains how the company creates value, delivers value, captures value, scales, and protects margin.

You are a senior business model strategist. Build a complete business model blueprint for [COMPANY NAME] that makes the logic of value creation, delivery, monetization, cost structure, scalability, and profitability clear enough for leadership decisions. Inputs: Company: [COMPANY NAME] Business idea or current business: [DESCRIPTION] Target customers: [CUSTOMERS] Customer problem: [PROBLEM] Product / service: [PRODUCT / SERVICE] Current revenue streams: [REVENUE STREAMS] Pricing: [PRICING] Cost structure: [COST STRUCTURE] Delivery model: [DELIVERY MODEL] Sales channels: [SALES CHANNELS] Marketing channels: [MARKETING CHANNELS] Team and operations: [TEAM / OPERATIONS] Competitors / alternatives: [COMPETITORS] Financial goals: [GOALS] Constraints: [CONSTRAINTS] Create the business model blueprint: 1. Value creation logic Define: - customer problem - customer outcome - why the problem matters - how the business solves it - what makes the solution valuable - what proof is needed - what customers must believe before paying 2. Value delivery logic Explain how the business delivers the promised value: - product or service workflow - onboarding - fulfillment - customer success - support - quality control - technology or labor requirements - operational bottlenecks - delivery risks 3. Value capture logic Map how the company captures revenue: - revenue streams - pricing model - payment timing - contract structure - upsell paths - cross-sell paths - renewal or repeat purchase paths - expansion potential 4. Cost and margin logic Break down: - fixed costs - variable costs - cost to acquire - cost to serve - gross margin drivers - operating leverage - hidden costs - margin risks 5. Scalability logic Evaluate what happens as the business grows: - what becomes easier - what becomes harder - what requires more headcount - what can be automated - what can be standardized - what creates quality risk - what creates cash flow risk 6. Business model scorecard Score the model from 1 to 10 across: - customer value - willingness to pay - revenue quality - margin potential - operational scalability - defensibility - customer retention - channel access - risk resilience - simplicity 7. Model improvement plan Create: - top 5 weaknesses - top 5 monetization improvements - top 5 margin improvements - top 5 scalability improvements - 90-day action plan Rules: - Do not assume revenue means profit. - Do not ignore cost to serve. - Do not create a model that depends on perfect execution. - Mark missing financial information as [NEEDS DATA]. Done when leadership can explain how the business makes money, where margin comes from, what breaks at scale, and what to improve first. --------------------------------------------------------------------------------

#042Revenue Stream Portfolio Designer

BUSINESS MODEL & MONETIZATIONFounders, operators, consultants, SaaS teams, service businesses, ecommerce brands, creators, agencies, and companies expanding revenue options.

Identify, evaluate, and prioritize revenue streams so the business is not dependent on a weak or fragile monetization model.

Act as a revenue portfolio strategist. Design a revenue stream portfolio for [COMPANY NAME] that balances predictability, margin, growth potential, customer value, and operational complexity. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Current customers: [CUSTOMERS] Current revenue streams: [CURRENT REVENUE] Customer needs: [NEEDS] Assets or capabilities: [ASSETS / CAPABILITIES] Distribution channels: [CHANNELS] Pricing constraints: [CONSTRAINTS] Operational capacity: [CAPACITY] Margins: [MARGINS] Strategic goals: [GOALS] Build the revenue stream portfolio in this structure: A. Current revenue diagnosis Review each existing revenue stream: - how it works - customer segment served - payment timing - margin profile - predictability - scalability - risk - customer value - operational burden B. Revenue stream idea bank Create 20 potential revenue streams across: - one-time purchase - subscription - usage-based - tiered plans - retainers - licensing - marketplace fees - affiliate or referral revenue - training - certification - premium support - implementation - consulting - templates or digital products - bundles - memberships - maintenance - financing - data or insights - partnerships C. Portfolio scoring Score each revenue stream by: - customer demand - willingness to pay - gross margin - recurring potential - ease of launch - channel fit - strategic fit - operational complexity - cannibalization risk - trust risk D. Portfolio design Classify revenue streams as: - core revenue - growth revenue - experimental revenue - defensive revenue - premium revenue - retention revenue - not recommended E. Monetization roadmap Create a phased plan: - launch now - test next - build later - reject - monitor F. Leadership recommendation Write a recommendation that explains: - which revenue stream should become the core - which stream should be tested - which stream should be avoided - what tradeoff is being accepted - what data is needed next Rules: - Do not recommend revenue streams that confuse the customer. - Do not add monetization that damages the core offer. - Do not ignore operational burden. - Mark speculative ideas as [HYPOTHESIS]. --------------------------------------------------------------------------------

#043Unit Economics Forensic Audit

BUSINESS MODEL & MONETIZATIONStartups, SaaS companies, ecommerce brands, marketplaces, service businesses, investors, finance teams, and founders checking growth quality.

Analyze unit economics to understand whether each customer, order, contract, product, or transaction is profitable and scalable.

You are a unit economics forensic analyst. Audit the unit economics of [COMPANY NAME] and determine whether the business can grow profitably. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Unit of analysis: [CUSTOMER / ORDER / CONTRACT / PROJECT / TRANSACTION / LOCATION] Revenue per unit: [REVENUE PER UNIT] Gross margin: [GROSS MARGIN] Variable costs: [VARIABLE COSTS] Cost to acquire: [CAC / CPA] Cost to serve: [COST TO SERVE] Retention / churn: [RETENTION / CHURN] Repeat purchase: [REPEAT PURCHASE] Average order value / contract value: [AOV / ACV] Discounts: [DISCOUNTS] Refunds / returns / cancellations: [RETURNS] Support costs: [SUPPORT COSTS] Operational costs: [OPERATIONS] Time period: [PERIOD] Run the forensic audit: 1. Define the unit Clarify: - what the unit is - why this unit matters - what revenue belongs to it - what costs belong to it - what costs are excluded - what assumptions are being made 2. Unit economics table Calculate or structure: - gross revenue - discounts - net revenue - direct variable costs - gross profit - acquisition cost - fulfillment cost - support cost - payment / platform fees - refunds or returns - contribution margin - payback period - lifetime value - break-even point Use [NEEDS DATA] where numbers are missing. 3. Profit leak investigation Identify leaks from: - underpricing - excessive discounts - high acquisition cost - high support burden - weak retention - low repeat purchase - costly customization - returns or refunds - fulfillment inefficiency - payment or platform fees - sales commissions - onboarding complexity 4. Segment comparison Compare unit economics by: - customer segment - product - plan - channel - geography - cohort - sales motion - order size 5. Sensitivity test Show what happens if: - CAC rises - price increases - churn increases - gross margin improves - support cost increases - repeat purchase improves - discounting decreases - fulfillment cost changes 6. Decision output Recommend: - what to scale - what to fix - what to stop - what to reprice - what to automate - what segment to prioritize - what data to track next Rules: - Do not average away bad customer segments. - Do not call growth healthy if contribution margin is negative. - Do not ignore cost to serve. - Separate media-only CAC from fully loaded CAC. --------------------------------------------------------------------------------

#044Pricing Model Selection Lab

BUSINESS MODEL & MONETIZATIONSaaS, AI tools, marketplaces, agencies, service businesses, platforms, memberships, ecommerce subscriptions, and new product launches.

Choose the right pricing model by comparing flat fee, tiered, usage-based, subscription, freemium, licensing, commission, and hybrid options.

Act as a pricing model strategist. Help [COMPANY NAME] choose the best pricing model for [PRODUCT / SERVICE] based on customer value, usage behavior, willingness to pay, cost structure, and growth goals. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Customer value received: [VALUE] Usage behavior: [USAGE] Current or planned pricing: [PRICING] Cost structure: [COST STRUCTURE] Competitor pricing: [COMPETITORS] Sales motion: [SALES MOTION] Customer objections: [OBJECTIONS] Growth goal: [GOAL] Margin target: [MARGIN] Constraints: [CONSTRAINTS] Evaluate these pricing models: Model 1 - Flat fee Model 2 - Tiered pricing Model 3 - Usage-based pricing Model 4 - Per-seat pricing Model 5 - Subscription Model 6 - Freemium Model 7 - Free trial Model 8 - Licensing Model 9 - Transaction or commission fee Model 10 - Retainer Model 11 - Project-based pricing Model 12 - Hybrid pricing For each model include: - how it would work - customer logic - revenue logic - margin logic - expansion potential - risk of undercharging - risk of customer confusion - operational requirements - best-fit customer segment - when not to use it Then create: A. Pricing model scorecard Score each model by: - value alignment - predictability - scalability - customer acceptance - expansion potential - simplicity - margin protection - sales fit - competitive differentiation - implementation difficulty B. Recommended pricing architecture Define: - primary pricing model - secondary monetization lever - value metric - billing frequency - tier logic - add-on logic - discount rules - upgrade path C. Pricing test plan Create a test to validate the model: - hypothesis - audience - offer - price points - method - success metric - risk - decision rule Rules: - Do not choose a model only because competitors use it. - Do not recommend usage-based pricing if customers cannot predict value or cost. - Do not recommend freemium without a conversion path. - Mark unvalidated assumptions as [ASSUMPTION]. --------------------------------------------------------------------------------

#045Value Metric Finder

BUSINESS MODEL & MONETIZATIONSaaS, AI products, API businesses, platforms, marketplaces, subscription businesses, and usage-based monetization.

Identify the best value metric for pricing so customers pay in proportion to the value they receive.

You are a monetization architect specializing in value metrics. Find the best value metric for [PRODUCT NAME] so pricing scales with customer value without creating confusion or friction. Inputs: Product: [PRODUCT NAME] Company: [COMPANY NAME] Target customers: [CUSTOMERS] Core value delivered: [VALUE] Customer usage patterns: [USAGE] Customer segments: [SEGMENTS] Current pricing metric: [CURRENT METRIC] Competitor pricing metrics: [COMPETITOR METRICS] Cost drivers: [COST DRIVERS] Expansion goals: [EXPANSION GOALS] Customer objections: [OBJECTIONS] Data available: [DATA] Run the value metric discovery: Step 1 - Value event map Identify the moments where customers receive value: - setup - first use - repeated use - collaboration - automation - transaction - output generated - result achieved - risk reduced - time saved - revenue increased - cost reduced Step 2 - Candidate value metrics Generate candidate metrics such as: - seats - usage volume - transactions - revenue processed - contacts - projects - storage - API calls - workflows - reports - locations - orders - assets - automations - outcomes Step 3 - Metric quality test For each candidate metric evaluate: - does it track value? - is it easy to understand? - is it easy to measure? - does it scale with customer success? - does it protect margin? - does it create customer anxiety? - can customers predict cost? - can competitors copy it? - does it support expansion? Step 4 - Customer fairness test Explain how each metric feels to: - small customers - growing customers - power users - enterprise buyers - finance / procurement - admins - end users Step 5 - Recommendation Choose: - primary value metric - secondary packaging limits - add-on metric - guardrail metric - metric to avoid Step 6 - Messaging Write customer-facing copy that explains the pricing metric simply. Rules: - Do not choose a metric that punishes successful usage. - Do not choose a metric customers cannot understand. - Do not ignore cost drivers. - Do not force one metric if a hybrid model is more logical. --------------------------------------------------------------------------------

#046Offer Packaging Ladder Builder

BUSINESS MODEL & MONETIZATIONSaaS, agencies, consultants, service businesses, ecommerce brands, memberships, education products, and B2B offers.

Create a packaging ladder with entry, core, premium, enterprise, add-on, and expansion offers that increase conversion and monetization.

Act as an offer packaging strategist. Build a packaging ladder for [COMPANY NAME] that helps customers buy at the right level and gives the business clear paths to expand revenue. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Customer segments: [SEGMENTS] Customer maturity levels: [MATURITY] Current offers: [CURRENT OFFERS] Pricing: [PRICING] Cost to deliver: [COSTS] Customer objections: [OBJECTIONS] Competitor packages: [COMPETITORS] Revenue goal: [GOAL] Brand positioning: [POSITIONING] Design the packaging ladder: Tier 1 - Entry offer Define: - who it is for - problem it solves - what is included - what is excluded - price logic - risk reversal - upgrade path - reason it exists Tier 2 - Core offer Define: - ideal customer - main outcome - included features / services - proof needed - price anchor - margin logic - conversion logic - success metric Tier 3 - Premium offer Define: - premium buyer - additional value - service level - exclusivity or depth - price justification - delivery requirements - margin protection Tier 4 - Enterprise / custom offer Define: - qualification criteria - customization rules - sales process - implementation scope - contract structure - support level - minimum price Add-on architecture Create add-ons for: - speed - support - implementation - training - analytics - customization - extra usage - premium access - maintenance - consulting Package comparison Create a package table with: - tier - customer type - outcome - includes - excludes - price range - margin risk - upgrade trigger - CTA Rules: - Do not create tiers that differ only by arbitrary features. - Do not put high-cost delivery into low-priced tiers. - Do not make the entry offer so generous that upgrades are unnecessary. - Packages must guide buying decisions, not create confusion. --------------------------------------------------------------------------------

#047Subscription Monetization Engine

BUSINESS MODEL & MONETIZATIONSaaS, memberships, ecommerce subscriptions, communities, content products, service retainers, and recurring revenue businesses.

Design or improve a subscription model with acquisition, activation, retention, expansion, churn prevention, and pricing logic.

You are a subscription monetization strategist. Design a subscription engine for [COMPANY NAME] that creates recurring revenue while keeping customers active, satisfied, and profitable. Inputs: Company: [COMPANY NAME] Subscription product: [PRODUCT] Target customers: [CUSTOMERS] Current subscription plans: [PLANS] Price points: [PRICE POINTS] Billing cycle: [BILLING] Activation data: [ACTIVATION] Usage data: [USAGE] Retention / churn data: [RETENTION / CHURN] Expansion data: [EXPANSION] Customer objections: [OBJECTIONS] Competitor subscriptions: [COMPETITORS] Cost to serve: [COST TO SERVE] Growth goal: [GOAL] Build the subscription engine: 1. Subscription promise Define the ongoing value customers pay for: - continuous access - convenience - outcomes - status - savings - replenishment - community - expertise - automation - risk reduction 2. Plan architecture Design: - free / trial option, if relevant - starter plan - core plan - premium plan - enterprise or custom plan - annual plan - add-ons - upgrade triggers 3. Activation economics Identify what must happen in the first: - 5 minutes - first day - first week - first billing cycle - first renewal cycle For each stage include: - customer action - value moment - metric - risk - intervention 4. Retention mechanics Create retention systems for: - usage habit - product education - reporting value - renewal reminders - success milestones - support intervention - community engagement - personalization - loyalty 5. Expansion paths Design: - usage expansion - seat expansion - feature expansion - service expansion - annual upgrade - premium support - account growth 6. Churn defense Create churn-risk signals and save offers. 7. Subscription scorecard Define metrics: - MRR / ARR - net revenue retention - gross revenue retention - churn - activation - usage - expansion - CAC payback - LTV - support burden Rules: - Do not sell subscriptions if value is not recurring. - Do not hide cancellation rules. - Do not focus only on acquisition while ignoring churn. - Subscription monetization must create ongoing customer value. --------------------------------------------------------------------------------

#048Freemium & Free Trial Conversion Designer

BUSINESS MODEL & MONETIZATIONSaaS, AI tools, apps, marketplaces, creator tools, productivity products, and software-led businesses.

Design a freemium or free trial model that increases adoption without giving away too much value or attracting the wrong users.

Act as a freemium and trial monetization designer. Build a free plan or trial strategy for [PRODUCT NAME] that converts the right users into paid customers. Inputs: Product: [PRODUCT NAME] Company: [COMPANY NAME] Target customers: [CUSTOMERS] Core value: [VALUE] Current free plan / trial: [CURRENT FREE] Paid plans: [PAID PLANS] Activation events: [ACTIVATION] Usage limits: [USAGE LIMITS] Conversion data: [CONVERSION] Support burden: [SUPPORT] Cost drivers: [COSTS] Competitor free models: [COMPETITORS] Revenue goal: [GOAL] Design the free-to-paid system: A. Free model decision Choose the best model: - free trial - freemium - reverse trial - demo-first - waitlist - limited free credits - free tool - free community - no free option Explain why. B. Free value boundary Define: - what users can experience for free - what must be reserved for paid - what usage limits apply - what features create conversion tension - what support is included - what risks exist C. Activation path Map the free user journey: - signup - setup - first value - repeated value - limit encounter - upgrade prompt - paid conversion - expansion D. Upgrade triggers Create triggers based on: - usage - team growth - advanced features - export needs - collaboration - reporting - automation - support - commercial use - risk reduction E. Conversion messaging Write: - upgrade page copy - in-product upgrade prompts - email sequence - limit warning copy - trial expiration copy - annual upgrade copy F. Free-user economics Evaluate: - acquisition cost - product cost - support cost - conversion rate needed - payback risk - abuse risk - customer quality Rules: - Do not give away the full paid outcome for free. - Do not create upgrade prompts before users experience value. - Do not hide limits. - The free model must support paid conversion, not just user volume. --------------------------------------------------------------------------------

#049Marketplace Monetization & Liquidity Model

BUSINESS MODEL & MONETIZATIONMarketplaces, platforms, directories, two-sided networks, service marketplaces, creator platforms, and transaction businesses.

Design monetization for marketplaces while balancing supply, demand, liquidity, trust, take rate, incentives, and growth.

You are a marketplace monetization strategist. Design a monetization model for [MARKETPLACE NAME] that captures value without damaging liquidity, trust, or network growth. Inputs: Marketplace: [MARKETPLACE NAME] Market category: [CATEGORY] Demand side: [BUYERS / DEMAND] Supply side: [SELLERS / SUPPLY] Transaction type: [TRANSACTION] Average transaction value: [AOV] Current liquidity: [LIQUIDITY] Current monetization: [CURRENT MODEL] Trust and safety needs: [TRUST] Competitors: [COMPETITORS] Supply acquisition channels: [SUPPLY CHANNELS] Demand acquisition channels: [DEMAND CHANNELS] Operational costs: [COSTS] Growth goal: [GOAL] Build the marketplace monetization model: 1. Marketplace value flow Map: - what buyers want - what sellers want - what the marketplace enables - what trust problem it solves - what transaction friction it removes - where value is created - where value can be captured 2. Liquidity diagnosis Evaluate: - demand density - supply density - match rate - time to match - transaction completion - repeat usage - geographic or category concentration - cold-start risk 3. Monetization options Evaluate: - commission / take rate - listing fee - subscription for sellers - subscription for buyers - featured placement - lead fee - transaction processing fee - premium tools - verification fee - advertising - financing - data insights - service layer For each include: - who pays - why they would pay - revenue potential - liquidity risk - trust risk - implementation complexity 4. Take rate strategy Recommend: - initial take rate - mature take rate - category variation - seller tier variation - buyer fee logic - incentive periods - fee transparency 5. Incentive design Create incentives for: - first transaction - repeat transaction - high-quality supply - verified supply - fast response - buyer retention - referral 6. Metrics Define: - GMV - net revenue - take rate - match rate - liquidity - repeat rate - CAC - seller retention - buyer retention - trust incidents Rules: - Do not monetize before marketplace liquidity is strong enough. - Do not create fees that push transactions off-platform. - Do not ignore trust and safety costs. - Marketplace revenue must grow with successful matches. --------------------------------------------------------------------------------

#050Service Business Productization Planner

BUSINESS MODEL & MONETIZATIONAgencies, consultants, freelancers, professional services, B2B service companies, studios, and operators reducing custom work.

Turn custom services into scalable packages, retainers, productized offers, implementation models, and recurring revenue.

Act as a service business monetization strategist. Productize [SERVICE BUSINESS NAME] so the business can sell clearer offers, protect margins, reduce custom scope, and increase recurring revenue. Inputs: Business: [SERVICE BUSINESS NAME] Services offered: [SERVICES] Target clients: [CLIENTS] Current pricing: [PRICING] Current delivery process: [DELIVERY] Common custom requests: [CUSTOM REQUESTS] Team capacity: [CAPACITY] Margins: [MARGINS] Client objections: [OBJECTIONS] Best client outcomes: [OUTCOMES] Competitors: [COMPETITORS] Growth goal: [GOAL] Productize the service business: A. Service inventory List current services and classify them as: - high-margin repeatable - high-margin custom - low-margin necessary - low-margin problematic - strategic but hard to scale - should be removed - should be automated - should become an add-on B. Productized offer design Create 5 productized offers. For each include: - offer name - target client - problem solved - promised outcome - included scope - excluded scope - timeline - deliverables - price logic - margin risk - upsell path C. Retainer model Design a recurring revenue model: - monthly scope - service levels - response times - deliverables - reporting - renewal logic - expansion path - cancellation rules D. Scope control system Create: - scope boundaries - change request rules - approval process - add-on pricing - client communication language - red flag requests E. Delivery standardization Define: - templates - SOPs - checklists - client intake - review gates - quality control - automation opportunities F. Sales messaging Write: - offer positioning - pricing explanation - proposal structure - FAQ - objection responses Rules: - Do not productize by simply renaming custom work. - Do not include unlimited labor in fixed pricing. - Do not remove customization where it creates premium value. - Productization must improve clarity, margin, and delivery quality. --------------------------------------------------------------------------------

#051Monetization Experiment Backlog

BUSINESS MODEL & MONETIZATIONGrowth teams, founders, product teams, SaaS, ecommerce, agencies, marketplaces, and monetization teams.

Create a prioritized backlog of pricing, packaging, upsell, trial, discount, bundling, and revenue experiments with clear hypotheses and guardrails.

You are a monetization experimentation lead. Build a prioritized experiment backlog for [COMPANY NAME] that tests ways to increase revenue, margin, conversion, retention, and expansion. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current pricing: [PRICING] Current offers: [OFFERS] Revenue data: [REVENUE DATA] Conversion data: [CONVERSION] Retention data: [RETENTION] Customer feedback: [FEEDBACK] Sales objections: [OBJECTIONS] Margin data: [MARGINS] Traffic or lead volume: [VOLUME] Risk tolerance: [RISK] Business goal: [GOAL] Create the backlog: Experiment categories: 1. Pricing level 2. Tier structure 3. Bundle design 4. Add-ons 5. Annual plan 6. Free trial / freemium 7. Discounting 8. Upsell 9. Cross-sell 10. Payment terms 11. Guarantee 12. Onboarding offer 13. Premium support 14. Usage limits 15. Sales-assisted plan For each experiment include: - experiment name - monetization lever - hypothesis - target segment - change being tested - primary metric - guardrail metric - expected upside - customer risk - margin risk - data needed - effort - confidence - decision rule Prioritize using: Priority Score = Impact x Confidence x Learning Value - Risk - Effort Create: A. Top 10 experiment backlog B. First 30-day test plan C. Tests to avoid D. Metrics dashboard E. Post-test interpretation rules Rules: - Do not run pricing experiments without guardrail metrics. - Do not test too many monetization changes at once. - Do not sacrifice trust for short-term revenue. - Use [INCONCLUSIVE] if results are weak or sample size is too small. --------------------------------------------------------------------------------

#052Willingness-to-Pay Research Kit

BUSINESS MODEL & MONETIZATIONPricing research, new offers, SaaS, service businesses, consultants, ecommerce products, education products, and B2B sales teams.

Research what customers are willing to pay, why they value the offer, what price feels fair, and what proof is needed to justify pricing.

Act as a willingness-to-pay research designer. Build a research kit for [PRODUCT / SERVICE] that helps [COMPANY NAME] understand customer value perception and pricing tolerance. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Current price or price idea: [PRICE] Competitors / alternatives: [ALTERNATIVES] Customer outcomes: [OUTCOMES] Customer costs of inaction: [COST OF INACTION] Sales objections: [OBJECTIONS] Segments to test: [SEGMENTS] Research method preference: [METHOD] Business decision: [DECISION] Create the research kit: Part 1 - Research hypotheses Write hypotheses about: - perceived value - acceptable price range - premium triggers - discount expectations - budget ownership - switching cost - proof required - alternative comparisons Part 2 - Interview guide Create questions that uncover: - current alternative - current spend - cost of the problem - decision criteria - budget source - value moments - price reaction - tradeoffs - risk perception - buying process Part 3 - Survey design Create a survey with: - segment questions - problem urgency questions - alternative spend questions - value ranking - price sensitivity questions - package preference - objection questions - open-ended language capture Part 4 - Price testing methods Recommend whether to use: - Van Westendorp - Gabor-Granger - conjoint-lite - sales conversation testing - landing page smoke test - proposal testing - A/B pricing page test For each include when it works and where it misleads. Part 5 - Analysis plan Create a framework to interpret: - cheap - acceptable - expensive but possible - too expensive - premium value - segment differences - proof gaps Part 6 - Pricing recommendation template Create a final report structure. Rules: - Do not ask only "would you pay?" - Do not treat stated willingness as guaranteed purchase behavior. - Do not average together segments with different budgets. - Separate price resistance from value confusion. --------------------------------------------------------------------------------

#053Discount & Promotion Governance System

BUSINESS MODEL & MONETIZATIONEcommerce, SaaS, B2B sales, agencies, service businesses, retail, marketplaces, and companies with inconsistent discounting.

Create rules for discounts, promotions, coupons, incentives, negotiation, and price exceptions without damaging margin or brand trust.

You are a monetization governance advisor. Build a discount and promotion governance system for [COMPANY NAME] that protects margin, brand positioning, customer trust, and sales discipline. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current pricing: [PRICING] Current discounts: [DISCOUNTS] Promotion history: [PROMOTION HISTORY] Sales negotiation process: [SALES PROCESS] Margins: [MARGINS] Customer segments: [SEGMENTS] Competitor discounting: [COMPETITORS] Brand positioning: [POSITIONING] Revenue goals: [GOALS] Known problems: [PROBLEMS] Create the governance system: 1. Discount diagnosis Identify current discount risks: - margin erosion - customer training - sales dependency - brand damage - channel conflict - unfair pricing - poor tracking - discount stacking - unclear approval - fake urgency - low-quality customers 2. Discount policy Define rules for: - allowed discount types - maximum discount - approval thresholds - eligible segments - excluded products or plans - expiration rules - stacking rules - negotiation rules - renewal discount rules - loyalty discount rules 3. Promotion menu Create approved promotion types: - launch offer - seasonal offer - volume discount - annual prepay discount - bundle savings - loyalty incentive - referral credit - winback offer - first-order incentive - non-monetary bonus For each include: - when to use - when not to use - margin impact - customer message - approval owner - metric 4. Sales exception system Create a process for price exceptions: - request form - business case - margin check - approval path - documentation - expiration - review 5. Discount analytics Define metrics: - discount rate - revenue after discount - gross margin - conversion lift - retention quality - customer segment - deal size - payback - promotion fatigue 6. Communication templates Write: - discount approval response - discount rejection response - customer negotiation response - price integrity explanation Rules: - Do not use discounts to hide weak value communication. - Do not approve discounts without margin context. - Do not create fake urgency. - Discounts must have a strategic purpose and a review date. --------------------------------------------------------------------------------

#054Upsell, Cross-Sell & Expansion Revenue Map

BUSINESS MODEL & MONETIZATIONSaaS, ecommerce, subscriptions, agencies, service businesses, marketplaces, education products, and customer success teams.

Design expansion revenue paths through upgrades, add-ons, bundles, renewals, usage growth, premium support, and complementary products.

Act as an expansion revenue strategist. Build an upsell and cross-sell map for [COMPANY NAME] that grows customer value while improving customer outcomes. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Customer segments: [SEGMENTS] Current customer journey: [JOURNEY] Current pricing / plans: [PRICING] Customer usage or purchase data: [USAGE / PURCHASE DATA] Retention data: [RETENTION] Support or success notes: [NOTES] Customer goals: [CUSTOMER GOALS] Margins: [MARGINS] Expansion goal: [GOAL] Create the expansion revenue map: A. Customer outcome ladder Map the customer's progression: - first problem solved - next problem discovered - deeper value needed - more usage needed - team or household expansion - premium outcome - long-term success B. Expansion inventory Identify possible expansion offers: - plan upgrade - add-on feature - usage expansion - more seats - bundle - premium support - implementation - training - maintenance - refill / replenishment - companion product - service layer - annual commitment - enterprise plan C. Trigger map For each expansion offer define: - trigger event - customer behavior signal - value reason - message - channel - timing - proof needed - risk of being too early D. Expansion sequence Create expansion paths for: - new customer - activated customer - power user - at-risk customer - loyal customer - high-value customer - enterprise customer - seasonal buyer E. Revenue impact model Create a framework to estimate: - attach rate - upgrade rate - expansion revenue - margin - retention impact - customer satisfaction impact - support burden F. Messaging Write expansion copy for email, in-product, sales call, product page, and account review. Rules: - Do not upsell before the customer has received initial value. - Do not sell irrelevant add-ons. - Do not confuse expansion revenue with customer success. - Expansion should feel like the next logical step. --------------------------------------------------------------------------------

#055Margin Architecture & Profit Lever Map

BUSINESS MODEL & MONETIZATIONFounders, CFOs, operators, ecommerce, SaaS, service companies, restaurants, retail, agencies, and businesses under margin pressure.

Identify the practical levers that improve gross margin, contribution margin, and operating profit without weakening customer value.

You are a margin architecture strategist. Build a profit lever map for [COMPANY NAME] that shows how to improve margin through pricing, cost structure, product mix, customer mix, delivery, and monetization design. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue: [REVENUE] Gross margin: [GROSS MARGIN] Contribution margin: [CONTRIBUTION MARGIN] Operating expenses: [OPEX] Product / service mix: [MIX] Customer segments: [CUSTOMERS] Pricing: [PRICING] Discounts: [DISCOUNTS] Variable costs: [VARIABLE COSTS] Fixed costs: [FIXED COSTS] Cost to serve: [COST TO SERVE] Operational constraints: [CONSTRAINTS] Profit goal: [GOAL] Build the margin architecture: 1. Margin waterfall Create a margin waterfall: Gross revenue minus discounts minus refunds / returns / credits minus direct product / delivery cost minus payment / platform fees minus fulfillment / labor minus support / success minus acquisition cost equals contribution margin Use [NEEDS DATA] where values are missing. 2. Margin leak map Identify leaks across: - underpricing - discounting - poor product mix - costly customers - inefficient fulfillment - high support burden - low retention - low AOV / ACV - supplier costs - payment fees - scope creep - returns / refunds - unused capacity 3. Profit lever library Create profit levers: - price increase - package redesign - minimum order / contract size - bundle - premium tier - cost renegotiation - delivery standardization - automation - customer segmentation - discount governance - retention improvement - add-on monetization - channel mix shift 4. Lever scorecard Score each lever by: - profit impact - speed - customer risk - operational effort - confidence - reversibility - strategic fit 5. Recommended action stack Create: - quick wins - medium-term projects - structural changes - do-not-do moves 6. Leadership summary Write a plain-English profit recommendation. Rules: - Do not improve margin by damaging core customer value. - Do not cut costs blindly. - Do not ignore mix effects. - Margin strategy must be measurable and operationally realistic. --------------------------------------------------------------------------------

#056Enterprise Monetization & Contract Strategy

BUSINESS MODEL & MONETIZATIONB2B SaaS, agencies, consulting firms, platforms, infrastructure products, AI tools, and companies moving upmarket.

Design enterprise pricing, packaging, minimums, contracts, implementation fees, renewals, expansion, and procurement-friendly value communication.

Act as an enterprise monetization strategist. Create an enterprise pricing and contract strategy for [COMPANY NAME] that captures larger customer value while managing delivery risk and sales complexity. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Current customer base: [CUSTOMERS] Target enterprise buyer: [ENTERPRISE BUYER] Current pricing: [PRICING] Current plans: [PLANS] Implementation requirements: [IMPLEMENTATION] Support requirements: [SUPPORT] Security / compliance needs: [SECURITY / COMPLIANCE] Sales cycle: [SALES CYCLE] Procurement process: [PROCUREMENT] Competitor enterprise pricing: [COMPETITORS] Gross margin / cost to serve: [MARGINS / COSTS] Enterprise revenue goal: [GOAL] Design the enterprise monetization system: A. Enterprise value case Define: - business outcome - economic buyer value - user value - risk reduction - productivity gain - revenue gain - compliance value - strategic value - proof required B. Enterprise package Create: - enterprise plan structure - minimum contract value - included usage - premium features - admin controls - security requirements - SLA - support level - implementation scope - training - reporting - renewal terms C. Pricing architecture Recommend: - base platform fee - usage component - seat component - implementation fee - support fee - add-ons - annual commitment - multi-year discount rules - expansion pricing D. Contract guardrails Define: - minimum price - discount approval - custom feature rules - implementation boundaries - cancellation terms - renewal escalation - payment terms - success criteria E. Enterprise sales assets Write: - pricing explanation - ROI narrative - procurement-friendly summary - security value summary - implementation scope language - negotiation response F. Risk controls Identify risks: - custom scope creep - low-margin enterprise deals - long implementation - buyer mismatch - procurement pressure - support burden - delayed payment Rules: - Do not move upmarket by simply raising price. - Do not include unlimited customization. - Do not discount enterprise deals without contract value logic. - Enterprise monetization must reflect value, complexity, and risk. --------------------------------------------------------------------------------

#057Monetization Scenario War Game

BUSINESS MODEL & MONETIZATIONLeadership teams, pricing committees, founders, CFOs, growth teams, SaaS, ecommerce, service businesses, and strategic planning.

Stress-test monetization choices through scenarios such as price increases, churn, competitor discounts, cost increases, weak conversion, and market shifts.

You are a monetization war-game facilitator. Stress-test the monetization strategy of [COMPANY NAME] under multiple market, customer, and competitor scenarios. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current pricing: [PRICING] Revenue streams: [REVENUE STREAMS] Customer segments: [CUSTOMERS] Gross margin: [MARGIN] CAC / acquisition costs: [CAC] Retention / churn: [RETENTION / CHURN] Competitors: [COMPETITORS] Planned monetization change: [CHANGE] Risk tolerance: [RISK TOLERANCE] Decision to make: [DECISION] Run the war game: Scenario 1 - Price increase succeeds Explain: - why customers accept it - which segments stay - which segments leave - margin effect - growth effect - next move Scenario 2 - Price increase fails Explain: - objections - churn risk - conversion drop - brand risk - mitigation - rollback plan Scenario 3 - Competitor undercuts price Explain: - customers at risk - response options - value defense - discount rules - product or service response Scenario 4 - Costs increase Explain: - margin pressure - pricing response - packaging response - operational response - customer communication Scenario 5 - Acquisition costs rise Explain: - payback impact - channel mix response - retention response - pricing response Scenario 6 - High-value segment responds strongly Explain: - expansion strategy - premium packaging - sales motion - product implications Scenario 7 - Low-quality customers flood in Explain: - support burden - qualification rules - price floor - packaging changes For each scenario include: - early warning signals - metrics to monitor - decision trigger - recommended action - confidence level Final output: - safest monetization move - highest-upside move - riskiest move - no-regret moves - leadership decision recommendation Rules: - Do not evaluate monetization only in the best-case scenario. - Do not ignore customer trust. - Do not create a price strategy without a rollback or mitigation plan. - Use [ASSUMPTION] where data is missing. --------------------------------------------------------------------------------

#058Monetization Messaging & Pricing Page Builder

BUSINESS MODEL & MONETIZATIONSaaS pricing pages, service offer pages, ecommerce bundles, memberships, creator products, agencies, and consultants.

Communicate pricing, packaging, value, guarantees, comparisons, and upgrade paths clearly so customers understand why the offer is worth paying for.

Act as a monetization messaging strategist. Build the pricing and offer communication system for [PRODUCT / SERVICE] so customers understand the value, choose the right package, and feel confident buying. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Pricing / packages: [PRICING / PACKAGES] Value proposition: [VALUE] Customer objections: [OBJECTIONS] Competitor alternatives: [ALTERNATIVES] Proof points: [PROOF] Guarantee / risk reversal: [GUARANTEE] Brand voice: [BRAND VOICE] Sales motion: [SELF-SERVE / SALES-LED / HYBRID] Desired action: [CTA] Create the monetization messaging system: 1. Pricing page job Define what the pricing page must help customers decide: - which plan fits - why the price is fair - what is included - what is not included - what result they can expect - what risk is reduced - what happens after purchase - how to upgrade later 2. Package positioning For each package write: - package name - best-fit customer - outcome promised - key inclusions - exclusions - price framing - proof required - CTA - upgrade trigger 3. Value explanation Write copy that explains: - why this costs what it costs - what customer receives - what problem it replaces - what cost of inaction looks like - why cheaper alternatives may fail - why premium options may be worth it 4. Objection handling Create answers for: - too expensive - not sure which plan - need approval - need proof - need implementation clarity - fear of lock-in - comparison to competitor - fear of hidden costs 5. Pricing page structure Create: - headline - subheadline - plan cards - comparison table - FAQ - proof block - guarantee section - enterprise CTA - final CTA 6. Conversion QA Create a checklist for clarity, trust, simplicity, proof, mobile readability, and decision confidence. Rules: - Do not hide important limits. - Do not use vague value claims. - Do not create confusing plan names. - Pricing communication should reduce friction, not pressure buyers. --------------------------------------------------------------------------------

#059Business Model Pivot Decision Framework

BUSINESS MODEL & MONETIZATIONFounders, startups, struggling businesses, leadership teams, investors, operators, and consultants evaluating a business model change.

Decide whether to keep, adjust, or pivot the business model based on customer demand, economics, retention, margin, channel access, and execution reality.

You are a business model pivot advisor. Help [COMPANY NAME] decide whether to keep, adjust, or pivot its current business model. Inputs: Company: [COMPANY NAME] Current business model: [CURRENT MODEL] Current customers: [CUSTOMERS] Revenue data: [REVENUE] Margin data: [MARGINS] Customer acquisition data: [ACQUISITION] Retention / churn: [RETENTION / CHURN] Customer feedback: [FEEDBACK] Sales objections: [OBJECTIONS] Operational constraints: [OPERATIONS] Market alternatives: [ALTERNATIVES] New model ideas: [NEW MODEL IDEAS] Runway / financial pressure: [RUNWAY] Decision deadline: [DEADLINE] Create the pivot decision framework: A. Current model truth Assess whether the current model has: - real demand - repeatable acquisition - willingness to pay - healthy unit economics - manageable delivery - retention or repeat purchase - differentiation - scalability - founder / team fit - enough runway B. Failure pattern classification Classify the main issue as: - wrong customer - weak problem - weak offer - weak pricing - bad channel - poor retention - poor margin - delivery too complex - market too small - sales cycle too long - timing issue - execution issue C. Pivot options Evaluate possible pivots: - customer segment pivot - problem pivot - offer pivot - pricing pivot - channel pivot - delivery model pivot - revenue model pivot - productization pivot - premium pivot - niche pivot For each include: - what changes - what stays - evidence for - evidence against - risk - time required - cost - validation test D. Decision criteria Create a weighted decision table across: - demand - economics - speed - risk - capability fit - customer evidence - market size - runway fit - strategic upside E. Recommendation Choose: - keep current model - adjust current model - run a pivot test - pivot now - stop the model F. Next 30 days Create a practical validation plan. Rules: - Do not recommend a pivot just because growth is hard. - Do not recommend staying the course if economics are structurally broken. - Do not ignore runway. - Use evidence, not founder preference, as the decision base. --------------------------------------------------------------------------------

#060Full Business Model & Monetization Audit

BUSINESS MODEL & MONETIZATIONFounders, CEOs, investors, consultants, CFOs, strategy teams, SaaS companies, ecommerce brands, service businesses, marketplaces, and business planning.

Audit the full business model and monetization system across value creation, revenue streams, pricing, packaging, unit economics, margins, retention, and scalability.

Act as an independent business model and monetization auditor. Review the full business model of [COMPANY NAME] and identify the highest-leverage improvements to revenue quality, profitability, scalability, and customer value. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Target customers: [CUSTOMERS] Customer problem: [PROBLEM] Revenue streams: [REVENUE STREAMS] Pricing: [PRICING] Packaging: [PACKAGING] Sales channels: [CHANNELS] Customer acquisition data: [ACQUISITION] Retention / repeat purchase: [RETENTION] Gross margin: [GROSS MARGIN] Contribution margin: [CONTRIBUTION MARGIN] Cost structure: [COST STRUCTURE] Cost to serve: [COST TO SERVE] Competitors / alternatives: [COMPETITORS] Growth goals: [GOALS] Known concerns: [CONCERNS] Audit the system across 15 dimensions: 1. Customer value clarity 2. Problem urgency 3. Willingness to pay 4. Revenue stream quality 5. Pricing model fit 6. Packaging clarity 7. Value metric alignment 8. Unit economics 9. Gross margin 10. Contribution margin 11. Cost to serve 12. Retention and repeat revenue 13. Expansion revenue 14. Scalability 15. Monetization risk For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - revenue risk - margin risk - customer trust risk - recommended fix - confidence level Then synthesize: A. Top 5 monetization constraints Rank the biggest constraints by: - revenue impact - profit impact - urgency - customer risk - ease of improvement - confidence B. Root cause analysis Identify whether the main problem is: - weak customer value - poor pricing model - underpricing - over-discounting - unclear packages - bad value metric - weak retention - poor unit economics - high cost to serve - low-margin customer mix - limited expansion path - business model complexity - lack of data C. Rebuilt monetization strategy Create: - recommended revenue streams - pricing model - packaging ladder - value metric - margin improvement plan - expansion revenue plan - discount policy - experiment roadmap - dashboard metrics D. 30/60/90-day monetization improvement plan Create: - actions - owners - tests - pricing changes - package changes - customer research - margin fixes - metrics - decision checkpoints E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard truth - the biggest revenue opportunity - the biggest margin risk - the monetization move to make next - the data needed before major changes Rules: - Do not invent financial data. - Do not judge the model only by revenue growth. - Do not recommend price changes without customer and margin logic. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on customer value, clean revenue, strong margins, retention, and scalable profit.

#061Operations System Blueprint

OPERATIONS & PROCESS OPTIMIZATIONCEOs, COOs, founders, operators, consultants, department heads, service businesses, agencies, SaaS teams, ecommerce teams, and growing companies with messy operations.

Build a complete operating system that connects workflows, roles, capacity, standards, KPIs, decision rhythms, and continuous improvement.

You are a senior operations strategist. Build a practical operating system for [COMPANY NAME] that turns scattered work, unclear ownership, bottlenecks, inconsistent quality, and reactive management into a clear, measurable, repeatable system. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Departments / functions: [FUNCTIONS] Core products / services: [PRODUCTS / SERVICES] Current workflows: [WORKFLOWS] Current bottlenecks: [BOTTLENECKS] Customer experience issues: [CUSTOMER ISSUES] Quality issues: [QUALITY ISSUES] Tools used: [TOOLS] Decision cadence: [CADENCE] Growth goals: [GOALS] Operational constraints: [CONSTRAINTS] Create the operations system: 1. Operating model diagnosis Analyze how work currently moves through the business: - customer request to delivery - sale to fulfillment - order to payment - issue to resolution - idea to execution - task to approval - data to decision - strategy to action Identify where work is slow, duplicated, unclear, risky, or dependent on one person. 2. Core workflow map Map the 5-10 most important workflows. For each workflow include: - workflow name - purpose - trigger - starting point - ending point - owner - participants - inputs - outputs - systems used - current failure points - customer impact - business impact 3. Role and ownership architecture Create clear ownership for: - process owner - task owner - reviewer - approver - backup owner - escalation owner - metric owner Mark every unclear ownership gap as [OWNERSHIP GAP]. 4. Standards and SOP layer Define which processes need: - SOP - checklist - template - automation - quality gate - training document - escalation rule - dashboard 5. Operating cadence Design: - daily operating check - weekly execution review - monthly KPI review - monthly process improvement review - quarterly capacity review - quarterly operating system reset For each meeting include purpose, attendees, agenda, decision rights, inputs, outputs, and what must never happen. 6. KPI system Create operational metrics across: - speed - quality - cost - capacity - workload - customer impact - rework - error rate - backlog - throughput - employee workload - SLA performance 7. Improvement loop Design a continuous improvement system: - how issues are captured - how root causes are diagnosed - how fixes are prioritized - how SOPs are updated - how training changes - how improvements are measured 8. 90-day implementation plan Create a 30/60/90-day plan with: - workflows to document - bottlenecks to remove - SOPs to create - meetings to change - metrics to launch - owners to assign - risks to monitor Rules: - Do not design operations that require perfect discipline to work. - Do not add meetings unless they create decisions or remove blockers. - Do not create SOPs for broken processes before redesigning them. - Do not ignore team capacity. Done when the company has an operating system that improves speed, quality, accountability, and execution clarity. --------------------------------------------------------------------------------

#062Process Bottleneck Diagnostic Lab

OPERATIONS & PROCESS OPTIMIZATIONOperations managers, founders, department leads, consultants, support teams, fulfillment teams, agencies, and teams with slow or unreliable processes.

Find the true bottlenecks inside a workflow and separate symptoms from root causes, capacity constraints, decision delays, quality failures, and tool problems.

Act as a process bottleneck diagnostician. Analyze the workflow below and identify the real reasons work gets delayed, blocked, repeated, escalated, or delivered with inconsistent quality. Workflow to diagnose: Workflow name: [WORKFLOW NAME] Purpose of workflow: [PURPOSE] Trigger: [TRIGGER] Current steps: [STEPS] People involved: [PEOPLE] Tools used: [TOOLS] Average volume: [VOLUME] Expected completion time: [EXPECTED TIME] Actual completion time: [ACTUAL TIME] Known delays: [DELAYS] Known errors: [ERRORS] Customer impact: [CUSTOMER IMPACT] Business impact: [BUSINESS IMPACT] Run the diagnostic lab: Station 1 - Flow reconstruction Rebuild the workflow as a step-by-step flow. For each step include: - step name - owner - input - action - output - tool - handoff - wait time - failure point - rework risk Station 2 - Bottleneck identification Classify each bottleneck as: - capacity bottleneck - approval bottleneck - information bottleneck - tool bottleneck - handoff bottleneck - decision bottleneck - quality bottleneck - training bottleneck - policy bottleneck - dependency bottleneck - customer-caused delay - supplier-caused delay Station 3 - Symptom vs cause For every visible issue, separate: - symptom - likely root cause - evidence - missing evidence - impact - confidence level Station 4 - Constraint ranking Rank constraints by: - time lost - error created - customer impact - cost impact - frequency - difficulty to fix - speed of improvement Station 5 - Root cause questions Generate specific questions to validate the root cause: - who should be interviewed? - what data should be checked? - what examples should be reviewed? - what logs or timestamps matter? - what decision records are missing? Station 6 - Fix design For each top bottleneck recommend: - immediate fix - process redesign - role change - template or checklist - automation possibility - quality gate - training need - metric to monitor Station 7 - Final diagnosis memo Write a concise memo with: - main bottleneck - real root cause - highest-impact fix - fastest fix - risky fix to avoid - owner - timeline - expected operational result Rules: - Do not blame people before testing process design. - Do not recommend automation for a process that is undefined. - Do not treat every delay as a staffing problem. - Mark uncertain causes as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#063SOP Builder for Repeatable Work

OPERATIONS & PROCESS OPTIMIZATIONOperations teams, agencies, service businesses, support teams, fulfillment teams, assistants, managers, new hires, and companies documenting repeatable work.

Turn a recurring task into a clear standard operating procedure with steps, owners, inputs, outputs, quality checks, escalation rules, and update cadence.

You are an operations documentation specialist. Convert the recurring task below into a practical SOP that a trained team member can follow without constant supervision. Task to document: Task name: [TASK NAME] Business purpose: [PURPOSE] Who performs it: [ROLE / OWNER] How often it happens: [FREQUENCY] Trigger: [TRIGGER] Inputs required: [INPUTS] Tools used: [TOOLS] Expected output: [OUTPUT] Quality standards: [STANDARDS] Current mistakes: [MISTAKES] Approval requirements: [APPROVAL] Escalation conditions: [ESCALATION] Examples of good output: [GOOD EXAMPLES] Examples of bad output: [BAD EXAMPLES] Create the SOP: A. SOP header Include: - SOP title - version - process owner - last updated - review cadence - purpose - scope - out of scope - expected completion time B. Inputs and readiness checklist Create: - required inputs - optional inputs - access required - tool permissions - source materials - conditions that must be true before starting C. Step-by-step procedure Write the procedure as numbered steps. For each step include: - action - responsible role - tool or system - exact input used - expected output - quality check - common mistake - fix D. Decision points Create a decision tree for: - missing information - conflicting information - urgent request - edge case - customer complaint - approval delay - tool issue E. Quality control checklist Create a final checklist with pass/fail criteria. F. Escalation rules Define: - when to escalate - who to escalate to - what information to include - expected response time - what not to do while waiting G. Training notes Create notes for new team members: - what matters most - what usually goes wrong - what good looks like - what to ask before improvising H. Improvement log Create a template for updating the SOP after errors or process changes. Rules: - Do not write vague steps like "handle the request." - Do not skip edge cases. - Do not assume tribal knowledge. - The SOP must be specific enough to reduce rework and training time. --------------------------------------------------------------------------------

#064Workflow Automation Opportunity Scanner

OPERATIONS & PROCESS OPTIMIZATIONCOOs, operations managers, founders, consultants, automation builders, agencies, admin teams, support teams, and teams choosing automation priorities.

Identify which operational workflows should be automated, assisted, templated, standardized, delegated, or kept manual.

Act as an automation opportunity analyst. Audit the operational tasks below and decide which ones should be automated, assisted, standardized, or left manual. Inputs: Company: [COMPANY NAME] Department: [DEPARTMENT] Tasks or workflows: [TASKS / WORKFLOWS] Frequency: [FREQUENCY] Time spent: [TIME SPENT] People involved: [PEOPLE] Tools used: [TOOLS] Current process: [PROCESS] Error rate: [ERROR RATE] Volume: [VOLUME] Data sensitivity: [SENSITIVITY] Approval requirements: [APPROVAL] Customer impact: [CUSTOMER IMPACT] Budget: [BUDGET] Technical capability: [CAPABILITY] Evaluate each task through the Automation Lens: Lens 1 - Repeatability Is the task rule-based, pattern-based, judgment-heavy, creative, relationship-based, or exception-heavy? Lens 2 - Input quality Are inputs structured, complete, reliable, standardized, and accessible? Lens 3 - Risk level What happens if automation fails? Classify risk as: - low operational risk - medium operational risk - high operational risk - customer trust risk - financial risk - compliance risk - should not automate Lens 4 - Value Estimate: - time saved - error reduction - faster cycle time - lower cost - better customer experience - better reporting - reduced dependency on one person Lens 5 - Feasibility Assess: - tool availability - data access - integration difficulty - process maturity - training requirement - maintenance burden Create the automation recommendation table: - task - current pain - automation type - AI role - human role - required data - tools needed - risk level - expected benefit - implementation effort - QA requirement - recommendation Classify recommendations: - automate now - AI-assisted only - template first - standardize before automation - delegate - keep manual - do not automate Create a 30-day action plan: - quick wins - workflow to document first - automation prototype - QA gate - owner - metric - rollout step Rules: - Do not automate broken processes. - Do not automate judgment-heavy decisions without human review. - Do not ignore data privacy. - Automation must reduce complexity, not hide it. --------------------------------------------------------------------------------

#065Capacity & Workload Balancer

OPERATIONS & PROCESS OPTIMIZATIONOperations leaders, agency owners, service teams, support teams, delivery teams, founders, department managers, and scaling businesses.

Diagnose team capacity, workload imbalance, resource constraints, overload risk, and staffing needs before operations break.

You are a capacity planning advisor. Analyze the workload and capacity of [TEAM / DEPARTMENT] and create a realistic plan to balance work, reduce overload, and improve throughput. Inputs: Team / department: [TEAM] Business function: [FUNCTION] Team members and roles: [ROLES] Current responsibilities: [RESPONSIBILITIES] Recurring work: [RECURRING WORK] Project work: [PROJECT WORK] Average weekly volume: [VOLUME] Deadlines / SLAs: [SLAS] Current backlog: [BACKLOG] Overtime or burnout signals: [BURNOUT] Upcoming demand: [UPCOMING DEMAND] Skill gaps: [SKILL GAPS] Tools used: [TOOLS] Hiring or budget constraints: [CONSTRAINTS] Analyze capacity in this format: 1. Workload inventory Break work into: - recurring operational work - customer-facing work - project work - admin work - rework - meetings - urgent interruptions - management work - invisible work 2. Capacity estimate For each team member estimate: - available working hours - meeting load - deep work time - recurring task load - project load - context switching burden - skills used - overload risk Use [NEEDS DATA] where time data is missing. 3. Demand vs capacity gap Compare: - current demand - available capacity - peak demand - future demand - backlog growth - SLA risk 4. Workload imbalance diagnosis Identify: - overloaded roles - underused roles - single points of failure - approval chokepoints - skill bottlenecks - unnecessary work - work that should be automated - work that should be stopped 5. Capacity actions Recommend: - rebalance responsibilities - remove low-value work - batch tasks - reduce meetings - improve templates - automate - outsource - hire - cross-train - change SLA - adjust priorities 6. Capacity plan Create: - immediate relief actions - 30-day workload rebalance - 60-day process improvement - 90-day staffing or automation recommendation 7. Capacity dashboard Define metrics: - workload by role - backlog - cycle time - utilization - SLA performance - overtime - rework - interruption rate - forecasted demand Rules: - Do not solve capacity problems only by telling people to work faster. - Do not ignore invisible work. - Do not assign new work without removing old work. - Protect quality and customer experience while improving throughput. --------------------------------------------------------------------------------

#066Swimlane Process Mapper

OPERATIONS & PROCESS OPTIMIZATIONProcess redesign, onboarding, cross-functional operations, support workflows, fulfillment workflows, sales-to-delivery handoffs, agencies, and consultants.

Create a clear swimlane map showing how work moves across roles, teams, tools, approvals, handoffs, decisions, and failure points.

Act as a process mapping facilitator. Build a swimlane process map for [PROCESS NAME] so the team can see ownership, handoffs, delays, decision points, and improvement opportunities. Process context: Process name: [PROCESS NAME] Business purpose: [PURPOSE] Start trigger: [TRIGGER] End state: [END STATE] Roles involved: [ROLES] Departments involved: [DEPARTMENTS] Tools / systems: [TOOLS] Current steps: [CURRENT STEPS] Approvals: [APPROVALS] Known delays: [DELAYS] Known errors: [ERRORS] Customer-facing impact: [CUSTOMER IMPACT] Create the swimlane map as text: Part 1 - Lane setup Create lanes for: - customer / requester - sales / intake - operations - fulfillment / delivery - finance - support - manager / approver - system / automation - external vendor, if relevant Part 2 - Process flow For each step include: - step number - lane / owner - action - input - output - tool - handoff recipient - decision point - expected time - failure risk Part 3 - Decision diamonds List decision points separately: - decision - decision owner - criteria - possible paths - data needed - escalation rule Part 4 - Handoff audit For every handoff evaluate: - what is transferred - how it is transferred - what information is often missing - wait time - rework risk - fix Part 5 - Waste identification Identify: - duplicate entry - unnecessary approval - waiting - overprocessing - manual copying - unclear ownership - tool switching - preventable rework - unnecessary customer follow-up Part 6 - Future-state map Create a simplified future-state process with: - removed steps - combined steps - automated steps - clearer ownership - quality gates - reduced handoffs Rules: - Do not hide informal workarounds. - Do not draw a perfect process if reality is messy. - Do not redesign before showing the current state. - Make the map useful for a team workshop. --------------------------------------------------------------------------------

#067Quality Control & Error Prevention System

OPERATIONS & PROCESS OPTIMIZATIONOperations teams, fulfillment teams, service businesses, agencies, ecommerce teams, support teams, manufacturing-adjacent teams, and process owners.

Build a quality control system that prevents errors, reduces rework, defines standards, and creates review gates without slowing the team unnecessarily.

You are a quality systems designer. Build a practical quality control and error prevention system for [PROCESS / TEAM] that improves consistency without creating unnecessary bureaucracy. Inputs: Process / team: [PROCESS / TEAM] Output produced: [OUTPUT] Customers affected: [CUSTOMERS] Current errors: [ERRORS] Error frequency: [FREQUENCY] Cost of errors: [COST] Current review process: [REVIEW PROCESS] Quality standards: [STANDARDS] People involved: [PEOPLE] Tools used: [TOOLS] Volume: [VOLUME] Risk tolerance: [RISK TOLERANCE] Design the quality system: A. Error taxonomy Classify errors into: - missing information - incorrect information - late delivery - wrong format - poor quality - wrong customer / order - broken promise - compliance issue - financial error - communication error - tool or system error - handoff error For each include likely cause and impact. B. Quality standard definition Define what "good" means: - required output - acceptable range - unacceptable defects - format standard - customer experience standard - timing standard - documentation standard C. Prevention controls Create controls before work starts: - input checklist - readiness check - template - system validation - training requirement - approval rule - data source rule D. In-process controls Create controls while work is happening: - checkpoint - peer review - automated check - exception flag - progress review - sample inspection E. Final controls Create final review gates: - reviewer - checklist - pass/fail criteria - escalation rule - sign-off record F. Error response loop When an error happens, define: - immediate containment - customer communication - root cause analysis - SOP update - training update - metric update - prevention action G. Quality dashboard Define metrics: - defect rate - rework rate - customer complaints - first-pass quality - review time - error cost - repeat error rate - SLA impact Rules: - Do not rely only on final review. - Do not blame individuals for system errors without evidence. - Do not make low-risk work go through high-friction review. - Quality should be built into the process, not inspected at the end. --------------------------------------------------------------------------------

#068Decision & Meeting Cadence Optimizer

OPERATIONS & PROCESS OPTIMIZATIONLeadership teams, operations teams, managers, agencies, startups, remote teams, scaling teams, and organizations suffering from meeting overload.

Redesign meetings and decision rhythms so teams spend less time talking and more time making clear operational decisions.

Act as an operating cadence consultant. Audit the current meeting and decision system for [COMPANY NAME / TEAM] and redesign it for speed, accountability, and fewer unnecessary meetings. Inputs: Company / team: [COMPANY / TEAM] Current meetings: [MEETING LIST] Meeting frequency: [FREQUENCY] Attendees: [ATTENDEES] Meeting purpose: [PURPOSE] Typical agenda: [AGENDA] Decisions made: [DECISIONS] Follow-up process: [FOLLOW-UP] Known problems: [PROBLEMS] Tools used: [TOOLS] Team size: [TEAM SIZE] Operating goals: [GOALS] Run the cadence optimization: 1. Meeting inventory For each meeting identify: - purpose - owner - attendees - decision rights - input required - output expected - duration - frequency - current value - problems - recommendation 2. Meeting classification Classify each meeting as: - keep - shorten - combine - replace with async update - change attendance - change frequency - redesign agenda - eliminate 3. Decision audit Identify decisions that are: - not being made - made too slowly - made by the wrong person - revisited too often - made without data - made in meetings that are too large - stuck due to unclear ownership 4. New cadence design Create a meeting system with: - daily operating check, if needed - weekly execution review - weekly blocker review - monthly KPI review - monthly improvement review - quarterly planning review For each include: - purpose - attendees - agenda - required pre-work - decisions made - output artifact - owner - duration - cancellation rule 5. Async rules Define what should move to: - dashboard - written update - task comment - decision memo - SOP update - recorded walkthrough 6. Decision log Create a decision log template: - decision - owner - date - options considered - chosen action - reason - follow-up owner - review date 7. Meeting hygiene rules Write 15 operating rules for better meetings. Rules: - Do not keep meetings with no decisions, learning, or coordination value. - Do not invite people "just in case." - Do not use meetings to compensate for unclear documentation. - Every recurring meeting needs a cancellation rule. --------------------------------------------------------------------------------

#069Handoff & Ownership Repair Kit

OPERATIONS & PROCESS OPTIMIZATIONSales-to-operations handoffs, project handoffs, support escalations, agency workflows, onboarding, fulfillment, customer success, and cross-functional teams.

Fix broken handoffs by clarifying roles, required information, timing, acceptance criteria, escalation paths, and accountability.

You are a handoff repair specialist. Diagnose and redesign the handoff between [TEAM / ROLE A] and [TEAM / ROLE B] so work does not get lost, delayed, duplicated, or misunderstood. Handoff context: From: [TEAM / ROLE A] To: [TEAM / ROLE B] Work being handed off: [WORK] Current trigger: [TRIGGER] Current handoff method: [METHOD] Information included: [INFO INCLUDED] Information often missing: [MISSING INFO] Tools used: [TOOLS] Current problems: [PROBLEMS] Customer impact: [CUSTOMER IMPACT] SLA or deadline: [SLA] Escalation path: [ESCALATION] Build the repair kit: 1. Handoff truth table Create a table showing: - what is handed off - from whom - to whom - when - how - required information - acceptance criteria - confirmation method - deadline - backup owner 2. Failure pattern analysis Identify failure patterns: - incomplete information - unclear owner - late handoff - duplicate work - wrong format - no confirmation - no escalation - no quality standard - unclear priority - tool mismatch - assumption mismatch 3. Required handoff packet Design the exact handoff packet: - summary - context - customer / project details - status - completed work - open questions - deadlines - risks - files / links - required next action - acceptance criteria 4. Acceptance rules Define when the receiving team can: - accept the handoff - reject the handoff - request clarification - escalate - proceed with assumptions 5. RACI repair Create a RACI table for: - task ownership - decision ownership - quality ownership - communication ownership - escalation ownership 6. Handoff templates Write: - standard handoff message - urgent handoff message - incomplete handoff response - clarification request - escalation message - completion confirmation 7. Metrics Track: - handoff completeness - handoff delay - clarification rate - rework rate - missed SLA - customer complaints - first-pass acceptance Rules: - Do not solve handoff issues only with reminders. - Do not allow work to move forward without acceptance criteria. - Do not let both teams assume the other owns the next step. - The handoff must be visible, trackable, and auditable. --------------------------------------------------------------------------------

#070Cycle Time Reduction Sprint

OPERATIONS & PROCESS OPTIMIZATIONOperations managers, project managers, fulfillment teams, agencies, support teams, product teams, manufacturing-adjacent teams, and delivery organizations.

Reduce the time it takes to complete a process by identifying delays, waiting, rework, approvals, batching issues, and flow constraints.

Act as a cycle time reduction coach. Design a focused sprint to reduce the cycle time of [PROCESS NAME] without sacrificing quality or customer trust. Inputs: Process name: [PROCESS NAME] Current average cycle time: [CURRENT TIME] Target cycle time: [TARGET TIME] Process steps: [STEPS] Volume: [VOLUME] People involved: [PEOPLE] Tools used: [TOOLS] Wait times: [WAIT TIMES] Approval points: [APPROVALS] Rework points: [REWORK] Batching practices: [BATCHING] Quality standards: [QUALITY] Constraints: [CONSTRAINTS] Design the sprint: Sprint Goal Write one clear goal: Reduce [PROCESS NAME] cycle time from [CURRENT TIME] to [TARGET TIME] by removing [PRIMARY CONSTRAINT], while protecting [QUALITY GUARDRAIL]. Phase 1 - Baseline measurement Define how to measure: - start time - end time - active work time - wait time - approval time - rework time - queue time - handoff time - exception time Phase 2 - Delay map Categorize delays: - waiting for information - waiting for approval - waiting for capacity - waiting for customer - waiting for vendor - system delay - batching delay - unclear priority - rework delay Phase 3 - Elimination moves Recommend actions: - remove step - combine steps - parallelize steps - pre-approve low-risk items - create template - automate check - reduce batch size - change handoff - create SLA - clarify decision rights Phase 4 - Sprint experiments Create 10 cycle-time experiments. For each include: - hypothesis - change - owner - test duration - metric - guardrail - success threshold Phase 5 - Future-state workflow Redesign the process with fewer waits and clearer ownership. Phase 6 - Sprint dashboard Create a dashboard for: - cycle time - wait time - active time - first-pass quality - rework rate - SLA performance - customer satisfaction Rules: - Do not reduce time by skipping necessary quality checks. - Do not optimize one step while slowing the whole system. - Do not rely only on averages; identify outliers. - The sprint must produce measurable improvement. --------------------------------------------------------------------------------

#071Operational KPI Dashboard Builder

OPERATIONS & PROCESS OPTIMIZATIONCOOs, founders, department heads, operations teams, support teams, fulfillment teams, agencies, SaaS teams, ecommerce teams, and leadership reporting.

Create an operational dashboard that shows flow, quality, capacity, cost, backlog, SLA health, risks, and decisions needed.

You are an operations analytics designer. Build an operational KPI dashboard for [TEAM / PROCESS / COMPANY] that helps leaders make better decisions, not just look at numbers. Inputs: Company / team: [COMPANY / TEAM] Business model: [BUSINESS MODEL] Process or function: [PROCESS / FUNCTION] Operational goals: [GOALS] Current metrics: [CURRENT METRICS] Available data sources: [DATA SOURCES] Current problems: [PROBLEMS] SLAs: [SLAS] Quality standards: [QUALITY STANDARDS] Team capacity: [CAPACITY] Leadership decisions needed: [DECISIONS] Reporting cadence: [CADENCE] Build the dashboard: A. Dashboard purpose Define: - who uses it - what decisions it supports - what questions it answers - what actions it should trigger - what it should not be used for B. Metric architecture Create metrics across: Flow: - volume - throughput - cycle time - wait time - backlog Quality: - error rate - rework rate - first-pass quality - complaints - audit failures Capacity: - workload by person/team - utilization - overtime - capacity forecast - single points of failure Cost: - cost per unit - cost to serve - cost of rework - tool cost - labor cost Service: - SLA performance - response time - resolution time - customer satisfaction Risk: - overdue work - bottlenecks - aging items - unresolved escalations - trend warnings C. Metric definitions For each metric include: - definition - formula - data source - owner - update frequency - good / warning / bad threshold - action triggered D. Dashboard layout Design sections: - executive snapshot - workload - speed - quality - capacity - cost - risk - decisions needed E. Interpretation guide Write guidance for: - what a spike means - what a decline means - what to investigate - when not to overreact - when to escalate F. Review cadence Create a weekly and monthly dashboard review process. Rules: - Do not track vanity metrics. - Do not include metrics nobody owns. - Do not show numbers without thresholds. - Every dashboard section should support a decision. --------------------------------------------------------------------------------

#072Customer Experience Operations Audit

OPERATIONS & PROCESS OPTIMIZATIONCustomer support, service businesses, ecommerce, SaaS, hospitality, agencies, clinics, restaurants, retail, and any business where operations affect customer trust.

Audit the operational processes behind customer experience to find delays, confusion, missed promises, support issues, and broken service moments.

Act as a customer experience operations auditor. Audit the operational journey customers experience with [COMPANY NAME] and identify where the internal process creates friction, disappointment, or trust loss. Inputs: Company: [COMPANY NAME] Customer type: [CUSTOMER] Product / service: [PRODUCT / SERVICE] Customer journey: [JOURNEY] Internal processes: [PROCESSES] Support issues: [SUPPORT ISSUES] Complaints: [COMPLAINTS] Reviews: [REVIEWS] SLA / promise: [PROMISE] Tools used: [TOOLS] Teams involved: [TEAMS] Known operational problems: [PROBLEMS] Audit the customer experience: 1. Promise-to-process map For each customer promise, identify: - promise made - process that must deliver it - owner - system used - failure point - customer-facing impact - evidence - risk level 2. Customer journey friction map Audit stages: - awareness - purchase / signup - onboarding - delivery / fulfillment - usage - support - billing - renewal / repeat purchase - complaint resolution - cancellation / return For each stage identify: - customer expectation - internal process - friction point - delay - confusion - missing communication - trust risk - improvement 3. Service recovery audit Review what happens when things go wrong: - who notices - who owns the issue - how customer is informed - escalation process - compensation / correction policy - follow-up - root cause capture 4. Internal cause analysis Classify issues as: - unclear ownership - weak handoff - missing SOP - poor tool visibility - unrealistic promise - capacity constraint - training gap - quality failure - policy problem - communication gap 5. Fix roadmap Create prioritized fixes: - immediate customer-facing fix - internal process fix - SOP or checklist - communication template - automation opportunity - ownership change - metric 6. Customer trust dashboard Define metrics: - complaint rate - response time - resolution time - repeat issue rate - missed promise rate - refund rate - NPS / CSAT - review themes - service recovery satisfaction Rules: - Do not treat customer complaints as isolated if patterns repeat. - Do not improve internal efficiency by making the customer experience worse. - Do not blame support if upstream processes create the problem. - Every fix must connect to customer trust. --------------------------------------------------------------------------------

#073Resource Flow & Constraint Optimizer

OPERATIONS & PROCESS OPTIMIZATIONEcommerce, retail, food service, manufacturing-adjacent teams, fulfillment, logistics, agencies, field teams, project operations, and multi-location businesses.

Optimize the movement of inventory, materials, information, people, tasks, or approvals through an operational system.

You are a resource flow optimizer. Analyze how [RESOURCE TYPE] moves through [OPERATION / BUSINESS] and redesign the flow to reduce shortages, overload, waiting, waste, and coordination failures. Inputs: Resource type: [INVENTORY / MATERIALS / INFORMATION / PEOPLE / TASKS / APPROVALS / CASH / EQUIPMENT] Operation: [OPERATION] Current flow: [CURRENT FLOW] Demand pattern: [DEMAND] Supply pattern: [SUPPLY] Storage / queue points: [STORAGE / QUEUES] Handoffs: [HANDOFFS] Constraints: [CONSTRAINTS] Waste or shortages: [WASTE / SHORTAGES] Tools / systems: [TOOLS] Forecasting method: [FORECASTING] Service standard: [STANDARD] Cost pressure: [COST] Analyze the flow: Flow Map Create a visual-style text map: Source -> Intake -> Queue -> Processing -> Handoff -> Output -> Feedback For each point include: - owner - capacity - volume - wait time - failure point - visibility level - control method Constraint Equation Explain the system constraint: The flow is limited by [CONSTRAINT] because [CAUSE], which creates [EFFECT]. Buffer Analysis Identify where buffers exist: - inventory buffer - time buffer - staffing buffer - approval buffer - information buffer - financial buffer For each buffer explain whether it protects the system or hides inefficiency. Waste Scan Identify: - overproduction - waiting - excess movement - excess inventory - rework - overprocessing - unused capacity - missed information - avoidable escalation Control System Recommend controls: - reorder point - capacity trigger - escalation threshold - dashboard - checklist - forecast rule - queue priority rule - exception rule - daily review Future-State Flow Redesign the flow to improve: - speed - reliability - visibility - quality - cost - flexibility Action Plan Create: - immediate fixes - data needed - system changes - SOP changes - owner - metric Rules: - Do not optimize one resource point while increasing system-wide waste. - Do not reduce buffers without understanding demand variability. - Do not ignore visibility gaps. - Flow optimization must improve reliability, not just speed. --------------------------------------------------------------------------------

#074Standardization vs Customization Decision Framework

OPERATIONS & PROCESS OPTIMIZATIONService businesses, agencies, SaaS onboarding, enterprise delivery, consulting, operations teams, productized services, and growing companies.

Decide which work should be standardized, customized, templatized, automated, or kept flexible based on value, cost, risk, and customer expectations.

Act as an operations design advisor. Decide where [COMPANY NAME] should standardize and where it should preserve customization. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Customer segments: [CUSTOMERS] Current custom work: [CUSTOM WORK] Current standard work: [STANDARD WORK] Delivery process: [DELIVERY] Cost to serve: [COST TO SERVE] Customer expectations: [EXPECTATIONS] Quality issues: [QUALITY ISSUES] Margin concerns: [MARGINS] Team capacity: [CAPACITY] Strategic positioning: [POSITIONING] Evaluate work using the Customization Grid: Quadrant 1 - Standardize Work that is repeated often, low differentiation, high error risk, or expensive to improvise. For each item include: - why standardize - template / SOP needed - owner - quality standard - metric Quadrant 2 - Template with flexibility Work that benefits from structure but needs adaptation. For each item include: - fixed elements - flexible elements - decision rules - examples - guardrails Quadrant 3 - Customize deliberately Work that creates premium value, strategic differentiation, or customer-specific advantage. For each item include: - why customization matters - who approves it - price implication - delivery risk - margin protection Quadrant 4 - Stop customizing Work that creates scope creep, low-margin complexity, inconsistency, or delivery risk. For each item include: - why stop - alternative offer - customer communication - transition plan Decision Rules Create rules for: - when to customize - when to refuse - when to charge more - when to use a template - when to escalate - when to create a new standard package Pricing and Margin Link Explain how customization should affect: - price - timeline - scope - approval - staffing - contract terms Final Output Create: - standardization roadmap - customization policy - customer communication scripts - SOP / template backlog - margin protection recommendations Rules: - Do not standardize work that creates true customer value. - Do not customize work that customers do not value. - Do not allow hidden customization inside fixed-price work. - Every customization should have a strategic or economic reason. --------------------------------------------------------------------------------

#075Continuous Improvement Backlog Builder

OPERATIONS & PROCESS OPTIMIZATIONOperations teams, COOs, department leads, consultants, agencies, support teams, fulfillment teams, and companies building continuous improvement discipline.

Create a prioritized backlog of process improvements using problems, root causes, expected impact, effort, owners, and measurable outcomes.

You are a continuous improvement facilitator. Turn the operational issues below into a prioritized improvement backlog for [COMPANY NAME / TEAM]. Inputs: Company / team: [COMPANY / TEAM] Operational issues: [ISSUES] Customer complaints: [COMPLAINTS] Team frustrations: [FRUSTRATIONS] Process metrics: [METRICS] Backlog / delays: [BACKLOG] Quality problems: [QUALITY PROBLEMS] Cost issues: [COST ISSUES] Tools used: [TOOLS] Available capacity: [CAPACITY] Business goals: [GOALS] Create the improvement backlog: 1. Issue capture Convert each issue into an improvement candidate. For each candidate include: - problem statement - where it happens - who is affected - evidence - frequency - business impact - customer impact - likely root cause - confidence level 2. Improvement type Classify as: - process redesign - SOP creation - checklist - automation - tool change - training - role clarification - quality gate - reporting - capacity change - policy change - communication fix 3. Impact scoring Score each item by: - customer impact - time saved - cost reduction - quality improvement - risk reduction - employee frustration reduction - strategic importance - urgency 4. Effort scoring Score effort by: - time required - complexity - stakeholder involvement - tool dependency - change management required - cost 5. Prioritization Create categories: - do now - schedule next - test first - document first - monitor - reject 6. Improvement cards For top 10 items create: - title - problem - root cause hypothesis - proposed fix - owner - metric - first step - deadline - risk - expected result 7. Improvement cadence Create a monthly improvement review process. Rules: - Do not create an improvement backlog with no owners. - Do not prioritize only the loudest complaints. - Do not fix symptoms without root cause. - Every improvement must have a measurable result. --------------------------------------------------------------------------------

#076Tool Stack & Systems Integration Audit

OPERATIONS & PROCESS OPTIMIZATIONOperations teams, RevOps, agencies, SaaS companies, ecommerce teams, service businesses, admin teams, and companies with too many disconnected tools.

Audit operational tools, data flow, duplicate work, manual transfers, reporting gaps, integration needs, and system ownership.

Act as a systems operations auditor. Audit the tool stack for [COMPANY NAME] and identify where tools, data, workflows, and ownership should be simplified or integrated. Inputs: Company: [COMPANY NAME] Departments: [DEPARTMENTS] Current tools: [TOOLS] Workflows supported: [WORKFLOWS] Data sources: [DATA SOURCES] Manual transfers: [MANUAL TRANSFERS] Duplicate data entry: [DUPLICATE ENTRY] Reporting needs: [REPORTING] Security / permission concerns: [SECURITY] Known tool problems: [PROBLEMS] Budget: [BUDGET] Technical capability: [CAPABILITY] Audit the system: A. Tool inventory For each tool list: - tool name - owner - users - purpose - workflows supported - data stored - integrations - cost - pain points - criticality - replacement risk B. Workflow-tool map Map each core workflow to: - tools used - handoffs between tools - duplicate entry - missing data - manual copy/paste - reporting gaps - failure points C. Data flow diagnosis Identify: - source of truth - duplicate sources - conflicting data - stale data - missing fields - permission issues - integration gaps - reporting delays D. Tool rationalization Classify tools as: - keep - consolidate - integrate - replace - retire - restrict access - evaluate later E. Integration roadmap Recommend integrations or automations: - trigger - data transferred - destination - expected benefit - risk - owner - QA requirement F. Governance system Create rules for: - tool ownership - new tool approval - access management - data definitions - integration review - documentation - training - cost review G. 90-day cleanup plan Create a phased plan to reduce tool chaos. Rules: - Do not recommend new tools before understanding current tools. - Do not remove tools without checking critical workflows. - Do not ignore data ownership. - A simpler system is only better if it improves reliability and visibility. --------------------------------------------------------------------------------

#077Cost-to-Serve Process Optimizer

OPERATIONS & PROCESS OPTIMIZATIONCOOs, CFOs, founders, agencies, service businesses, ecommerce, SaaS, support teams, logistics, fulfillment, and margin improvement projects.

Identify which processes, customers, products, services, channels, or exceptions drive operational cost and how to reduce cost without hurting value.

You are a cost-to-serve analyst. Analyze the operational cost of serving [CUSTOMER / SEGMENT / PRODUCT / SERVICE] and find ways to improve profitability without damaging customer value. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Customer / segment / product / service: [FOCUS] Revenue: [REVENUE] Gross margin: [GROSS MARGIN] Processes involved: [PROCESSES] People involved: [PEOPLE] Time spent: [TIME] Tools / systems: [TOOLS] Support volume: [SUPPORT] Returns / refunds / rework: [RETURNS / REWORK] Custom requests: [CUSTOM REQUESTS] Delivery costs: [DELIVERY COSTS] Customer expectations: [EXPECTATIONS] Profit goal: [GOAL] Analyze cost-to-serve: 1. Service activity map Break the full service process into activities: - acquisition - onboarding - setup - fulfillment - delivery - communication - support - billing - issue resolution - renewal / repeat purchase - offboarding For each activity include: - owner - time cost - direct cost - tool cost - frequency - rework risk - customer value - necessity 2. Cost driver identification Identify cost drivers: - high-touch communication - customization - unclear requirements - low order value - high support burden - rework - exceptions - returns - manual processing - low automation - poor self-service - complex billing - fragmented tools 3. Value vs cost classification Classify activities as: - high value / low cost - high value / high cost - low value / low cost - low value / high cost - required compliance - waste - premium-only work 4. Profit improvement options Recommend: - standardization - self-service - automation - minimum order size - tiered service levels - paid support - onboarding improvement - clearer requirements - scope control - pricing adjustment - customer segmentation - process redesign 5. Customer impact check For each cost reduction idea explain: - customer benefit - customer risk - brand risk - communication required - guardrail metric 6. Action plan Create: - immediate cost fixes - process redesign items - pricing or packaging changes - metrics to monitor - owner - timeline Rules: - Do not cut costs that customers strongly value unless pricing changes. - Do not hide cost-to-serve inside averages. - Do not blame customers if the process creates unnecessary work. - Profit improvement must protect trust. --------------------------------------------------------------------------------

#078Operational Risk & Escalation Playbook

OPERATIONS & PROCESS OPTIMIZATIONOperations teams, support teams, fulfillment, logistics, service businesses, SaaS ops, agencies, multi-location businesses, and leadership teams.

Build a risk and escalation system that defines what can go wrong, early warning signals, severity levels, owners, response steps, and communication rules.

Act as an operational risk manager. Create a practical risk and escalation playbook for [PROCESS / TEAM / COMPANY] so issues are detected early, handled consistently, and prevented from recurring. Inputs: Company / team: [COMPANY / TEAM] Process area: [PROCESS AREA] Operational risks: [RISKS] Known incidents: [INCIDENTS] Customer impact: [CUSTOMER IMPACT] Financial impact: [FINANCIAL IMPACT] Compliance constraints: [COMPLIANCE] Teams involved: [TEAMS] Current escalation process: [CURRENT PROCESS] Communication channels: [CHANNELS] SLA / service promise: [SLA] Decision owners: [OWNERS] Build the playbook: 1. Risk catalog Identify risks across: - customer issue - delivery failure - quality failure - staffing shortage - supplier failure - tool outage - data error - billing error - compliance issue - capacity overload - security issue - reputation issue - missed deadline - financial loss 2. Severity levels Create severity levels: - Level 1: minor issue - Level 2: operational disruption - Level 3: customer-impacting issue - Level 4: major business risk - Level 5: crisis For each define: - criteria - response time - owner - escalation path - communication requirement - documentation requirement 3. Early warning signals For each risk define: - leading indicator - threshold - monitoring method - owner - review cadence 4. Response playbooks For top risks create: - first 15 minutes - first hour - same day - next business day - customer communication - internal communication - leadership update - root cause review 5. Escalation templates Write templates for: - internal escalation - customer update - leadership alert - vendor escalation - incident summary - post-incident review 6. Prevention loop Define how incidents update: - SOPs - checklists - training - dashboards - staffing - vendor rules - customer communication Rules: - Do not wait for a crisis to define escalation. - Do not escalate everything to leadership. - Do not leave severe issues without a named owner. - Every incident should produce a prevention lesson. --------------------------------------------------------------------------------

#079Scaling Operations Readiness Test

OPERATIONS & PROCESS OPTIMIZATIONStartups, agencies, ecommerce, service businesses, SaaS, franchises, retail, operations leaders, founders, and companies preparing to scale.

Test whether operations can handle growth before adding more customers, volume, locations, orders, projects, or team members.

You are a scaling readiness examiner. Test whether [COMPANY NAME] is operationally ready to scale from [CURRENT STATE] to [TARGET STATE]. Inputs: Company: [COMPANY NAME] Current state: [CURRENT STATE] Target state: [TARGET STATE] Growth plan: [GROWTH PLAN] Current volume: [CURRENT VOLUME] Target volume: [TARGET VOLUME] Team size: [TEAM SIZE] Processes: [PROCESSES] Tools: [TOOLS] Customer experience standards: [STANDARDS] Quality metrics: [QUALITY] Capacity metrics: [CAPACITY] Financial constraints: [FINANCIALS] Known bottlenecks: [BOTTLENECKS] Timeline: [TIMELINE] Run the readiness test: Test 1 - Process repeatability Are core workflows documented, followed, measured, and improvable? Score and explain. Test 2 - Capacity resilience Can the team handle more volume without overload, backlog, or quality failure? Score and explain. Test 3 - Quality stability Will quality remain stable as speed and volume increase? Score and explain. Test 4 - Tool and data readiness Can current systems support increased volume, reporting, and coordination? Score and explain. Test 5 - Management layer readiness Are ownership, decision rights, escalation paths, and metrics clear enough? Score and explain. Test 6 - Customer experience readiness Will customers still receive the promised experience at higher volume? Score and explain. Test 7 - Financial and margin readiness Does scaling improve or damage profitability? Score and explain. Test 8 - Single point of failure test Identify people, tools, suppliers, or processes that would break under scale. Test 9 - Failure simulation Simulate: - volume doubles - key employee leaves - top supplier fails - support tickets triple - tool goes down - quality issue spikes - customer complaints increase - cash is delayed For each include response and weak point. Final output: - readiness score - scale blockers - scale enablers - must-fix-before-scaling list - safe-to-scale areas - 90-day readiness plan Rules: - Do not recommend scaling if the current process is unstable. - Do not confuse sales demand with operational readiness. - Do not ignore profitability under scale. - Mark assumptions as [ASSUMPTION]. --------------------------------------------------------------------------------

#080Full Operations & Process Optimization Audit

OPERATIONS & PROCESS OPTIMIZATIONCOOs, founders, consultants, department heads, agencies, service businesses, ecommerce teams, SaaS operations, multi-location businesses, and companies preparing for growth or operational cleanup.

Audit the full operations system across workflows, ownership, capacity, quality, tools, cost, customer experience, risk, metrics, and scaling readiness.

Act as an independent operations and process optimization auditor. Review the full operations system for [COMPANY NAME] and identify the highest-leverage improvements. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Team structure: [TEAM STRUCTURE] Products / services: [PRODUCTS / SERVICES] Core workflows: [WORKFLOWS] Current SOPs: [SOPS] Tools and systems: [TOOLS] Operational KPIs: [KPIS] Customer experience data: [CUSTOMER DATA] Quality issues: [QUALITY ISSUES] Backlog / delays: [BACKLOG] Capacity constraints: [CAPACITY] Cost concerns: [COSTS] Risk / incidents: [RISKS / INCIDENTS] Growth plans: [GROWTH PLANS] Leadership concerns: [CONCERNS] Audit the operations system across 15 dimensions: 1. Workflow clarity 2. Process documentation 3. Ownership and accountability 4. Handoff quality 5. Cycle time 6. Capacity planning 7. Quality control 8. Rework and error prevention 9. Tool and system fit 10. Data visibility 11. Cost-to-serve 12. Customer experience operations 13. Meeting and decision cadence 14. Risk and escalation management 15. Scaling readiness For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - operational risk - customer risk - financial risk - recommended fix - confidence level Then synthesize: A. Top 5 operational constraints Rank the biggest constraints by: - customer impact - cost impact - speed impact - quality impact - scaling risk - urgency - ease of improvement B. Root cause analysis Identify whether the main problem is: - unclear process - unclear ownership - capacity shortage - poor handoffs - weak SOPs - tool fragmentation - poor data visibility - excessive customization - weak quality controls - slow decisions - no improvement cadence - unmanaged risk - scaling too early C. Future-state operations model Create: - priority workflows - process owner map - SOP backlog - automation opportunities - KPI dashboard - QA gates - escalation system - capacity plan - improvement cadence D. 30/60/90-day optimization plan Create a practical plan with: - actions - owners - workflows to fix - SOPs to create - tools to improve - metrics to launch - risks to address - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard truth - the biggest operational constraint - the fastest improvement - the highest-risk issue - the next leadership decision Rules: - Do not invent operational data. - Do not recommend automation as the default fix. - Do not treat symptoms as root causes. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on speed, quality, accountability, customer trust, cost, and scaling readiness.

#081Financial Operating Model Architect

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, finance leads, operators, consultants, startups, agencies, SaaS teams, ecommerce companies, service businesses, and leadership teams building financial discipline.

Build a practical financial operating model that connects revenue, costs, margins, cash flow, unit economics, budget ownership, and decision-making.

You are a senior financial operating model architect. Build a clear financial operating model for [COMPANY NAME] that helps leadership understand how the business makes money, spends money, protects margin, manages cash, and makes better financial decisions. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue streams: [REVENUE STREAMS] Products / services: [PRODUCTS / SERVICES] Customer segments: [CUSTOMER SEGMENTS] Current revenue: [REVENUE] Current gross margin: [GROSS MARGIN] Current operating expenses: [OPEX] Current cash position: [CASH POSITION] Current burn or profit: [BURN / PROFIT] Key costs: [KEY COSTS] Team size: [TEAM SIZE] Financial goals: [GOALS] Planning period: [PLANNING PERIOD] Known concerns: [CONCERNS] Build the financial operating model: 1. Financial logic map Explain the business in plain English: - how revenue is created - when cash is collected - what costs scale with revenue - what costs are fixed - what drives gross margin - what drives operating profit - what creates cash pressure - what must be true for the business to become more profitable 2. Revenue architecture Break revenue into: - revenue stream - customer segment - pricing model - average order value / contract value - volume driver - frequency / retention - expansion potential - collection timing - risk 3. Cost architecture Break costs into: - cost of goods sold - fulfillment cost - payment / platform fees - sales and marketing - payroll - tools and software - rent / facilities - contractors - logistics - support - admin - taxes or compliance - other overhead Classify each as fixed, variable, semi-variable, discretionary, strategic, or risky. 4. Margin bridge Show how the business moves from: Gross revenue minus discounts / refunds minus direct costs equals gross profit minus acquisition cost minus cost to serve equals contribution profit minus operating expenses equals operating profit Use [NEEDS DATA] for missing numbers. 5. Financial responsibility system Assign ownership for: - revenue - gross margin - payroll - marketing spend - vendor costs - software costs - collections - inventory or working capital - budget variances - reporting 6. Decision rules Create rules for: - when to hire - when to cut spend - when to increase price - when to stop a channel - when to approve new tools - when to renegotiate vendors - when to delay expansion - when to raise capital 7. Financial dashboard Define metrics for: - revenue - gross margin - contribution margin - operating profit - cash runway - burn rate - CAC - payback period - LTV - budget variance - cost per unit - working capital 8. 90-day implementation plan Create: - first finance cleanup actions - reports to build - budget owners to assign - metrics to define - decisions to standardize - risks to monitor Rules: - Do not invent financial data. - Do not confuse revenue with cash. - Do not average away unprofitable segments. - Mark assumptions as [ASSUMPTION]. Done when leadership can explain the financial engine, see where money is made or lost, and know what decisions to make next. --------------------------------------------------------------------------------

#082Zero-Based Budget Rebuild

FINANCE, BUDGETING & UNIT ECONOMICSCFOs, founders, finance teams, department heads, consultants, agencies, startups, nonprofits, and companies cutting waste or resetting spend discipline.

Rebuild a budget from the ground up so every expense has a reason, owner, expected return, and clear connection to business priorities.

Act as a zero-based budgeting advisor. Rebuild the budget for [COMPANY NAME] from zero instead of copying last year's spend. Budget context: Company: [COMPANY NAME] Planning period: [MONTH / QUARTER / YEAR] Business goals: [GOALS] Current budget: [CURRENT BUDGET] Revenue forecast: [REVENUE FORECAST] Cash constraints: [CASH CONSTRAINTS] Departments: [DEPARTMENTS] Current expenses: [EXPENSES] Required commitments: [COMMITMENTS] Growth initiatives: [INITIATIVES] Cost concerns: [CONCERNS] Decision deadline: [DEADLINE] Run the zero-based rebuild: Phase 1 - Budget purpose Define what this budget must accomplish: - protect core operations - fund growth - improve margin - extend runway - reduce waste - improve quality - support hiring - stabilize cash flow - prepare for investment Phase 2 - Expense inventory Group every expense into: - required to operate - required to deliver customer value - required for compliance - growth investment - efficiency investment - optional - legacy spend - unclear value - should stop - needs renegotiation Phase 3 - Justification test For each expense ask: - what business outcome does this support? - who owns this spend? - what happens if we remove it? - what happens if we reduce it? - what metric proves it works? - is there a cheaper way? - is it still aligned with strategy? - is it fixed by contract or flexible? Phase 4 - Budget package design Create three budget packages: 1. Survival budget - only critical spend - risk accepted - runway impact 2. Base operating budget - supports stable execution - tradeoffs - expected result 3. Growth budget - funds priority bets - expected ROI - stop conditions Phase 5 - Department budget cards For each department create: - budget owner - total requested - must-have spend - optional spend - cuts proposed - investments proposed - expected outcome - KPI - approval status Phase 6 - Budget decision table Create a table with: - expense - owner - amount - category - decision - reason - risk - metric - review date Phase 7 - Governance rules Create rules for: - new spend approval - budget changes - vendor renewals - hiring approvals - emergency spend - monthly variance review Rules: - Do not cut strategic spend just because it is large. - Do not keep legacy spend without a current purpose. - Do not approve expenses without an owner and metric. - Make tradeoffs explicit. --------------------------------------------------------------------------------

#083Unit Economics Microscope

FINANCE, BUDGETING & UNIT ECONOMICSSaaS, ecommerce, marketplaces, agencies, service businesses, restaurants, retail, startups, investors, finance teams, and operators checking growth quality.

Analyze whether each customer, order, contract, project, location, or transaction is profitable after acquisition, delivery, support, refunds, and retention.

You are a unit economics analyst. Put [UNIT TYPE] under a financial microscope and determine whether growth is creating profit or hiding losses. Unit to analyze: Company: [COMPANY NAME] Unit type: [CUSTOMER / ORDER / CONTRACT / PROJECT / LOCATION / TRANSACTION / SUBSCRIPTION] Business model: [BUSINESS MODEL] Revenue per unit: [REVENUE PER UNIT] Discounts: [DISCOUNTS] Refunds / returns: [REFUNDS / RETURNS] Direct costs: [DIRECT COSTS] Fulfillment costs: [FULFILLMENT COSTS] Payment / platform fees: [FEES] Support costs: [SUPPORT COSTS] Onboarding costs: [ONBOARDING COSTS] Acquisition cost: [CAC / CPA] Retention / churn: [RETENTION / CHURN] Repeat purchase: [REPEAT PURCHASE] Expansion revenue: [EXPANSION] Time period: [PERIOD] Analyze the unit in 9 views: View 1 - Unit definition Clarify: - what counts as one unit - why this unit matters - what revenue belongs to it - what costs belong to it - what is excluded - what assumptions are required View 2 - Revenue quality Calculate or structure: - gross revenue - discounts - net revenue - recurring revenue - one-time revenue - expansion revenue - refund risk - collection timing View 3 - Direct cost load Break down: - product cost - service delivery cost - labor cost - hosting or infrastructure - logistics - commissions - tools - payment fees - refunds - support View 4 - Contribution economics Show: Net revenue minus variable cost minus cost to acquire minus cost to serve equals contribution profit Use [NEEDS DATA] where numbers are missing. View 5 - Payback Estimate: - CAC payback period - gross margin payback - contribution payback - break-even volume - break-even retention View 6 - Lifetime value logic Define LTV using: - retention - repeat purchase - expansion - margin - churn - discounting - support burden View 7 - Segment comparison Compare unit economics by: - customer segment - channel - product - geography - order size - plan - cohort - sales motion View 8 - Profit leak map Find where profit disappears: - underpricing - discounting - low retention - high acquisition cost - expensive fulfillment - high support burden - rework - refunds - low utilization - low expansion View 9 - Action recommendation State: - unit is healthy / weak / negative / unclear - what to scale - what to fix - what to stop - what to reprice - what to measure next Rules: - Do not use blended averages if segments behave differently. - Do not ignore customer support and onboarding costs. - Do not calculate LTV from revenue only. - Mark every unsupported assumption as [ASSUMPTION]. --------------------------------------------------------------------------------

#084Cash Flow Stress Test Simulator

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, operators, small businesses, startups, agencies, ecommerce teams, restaurants, retail, and companies managing cash uncertainty.

Stress-test cash flow under realistic shocks such as late payments, revenue drops, cost increases, payroll pressure, inventory needs, and expansion costs.

Act as a cash flow stress-test simulator. Test whether [COMPANY NAME] can survive and operate under multiple cash pressure scenarios. Inputs: Company: [COMPANY NAME] Current cash balance: [CASH BALANCE] Monthly revenue: [MONTHLY REVENUE] Revenue collection timing: [COLLECTION TIMING] Monthly fixed costs: [FIXED COSTS] Monthly variable costs: [VARIABLE COSTS] Payroll: [PAYROLL] Debt payments: [DEBT PAYMENTS] Vendor payment terms: [VENDOR TERMS] Customer payment terms: [CUSTOMER TERMS] Inventory / working capital needs: [INVENTORY / WORKING CAPITAL] Taxes / obligations: [TAXES] Expected major expenses: [MAJOR EXPENSES] Current runway: [RUNWAY] Planning horizon: [HORIZON] Create the stress test: Scenario Board Build 8 scenarios: 1. Base case 2. Revenue drops by 15% 3. Revenue drops by 30% 4. Customers pay 30 days late 5. Top customer delays payment 6. Cost of goods rises by 10% 7. Payroll increases faster than revenue 8. Emergency expense appears For each scenario calculate or structure: - starting cash - monthly inflows - monthly outflows - net cash movement - ending cash - runway - minimum cash point - breach month - risk level Liquidity Risk Map Identify: - cash cliff - payment timing gap - payroll risk - tax risk - vendor pressure - inventory pressure - debt service risk - receivables risk - seasonality risk Decision Triggers Define thresholds: - cash below [X] - runway below [X] months - AR aging above [X] - gross margin below [X] - burn above [X] - payroll ratio above [X] - inventory cash locked above [X] Response Options Create a response menu: - accelerate collections - renegotiate vendor terms - reduce discretionary spend - delay hiring - increase prices - reduce inventory - pause campaigns - secure credit line - collect deposits - change payment terms - cut low-margin work - raise capital Cash Control Plan Create: - weekly cash review - owner - dashboard - approval rules - collection actions - vendor actions - emergency playbook Rules: - Do not assume revenue equals cash. - Do not ignore timing of collections and payments. - Do not recommend cuts without showing operational risk. - Use [NEEDS DATA] where inputs are missing. --------------------------------------------------------------------------------

#085Revenue Forecast Scenario Engine

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, sales leaders, marketing leaders, agencies, SaaS teams, ecommerce teams, service businesses, and annual or quarterly planning.

Build a revenue forecast with drivers, assumptions, scenarios, confidence levels, leading indicators, and decision triggers.

You are a revenue forecasting strategist. Build a driver-based revenue forecast for [COMPANY NAME] that leadership can trust for planning, hiring, budgeting, and cash decisions. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue streams: [REVENUE STREAMS] Historical revenue: [HISTORICAL REVENUE] Current pipeline / demand: [PIPELINE / DEMAND] Customer segments: [SEGMENTS] Sales cycle: [SALES CYCLE] Conversion rates: [CONVERSION RATES] Average order value / contract value: [AOV / ACV] Retention / churn: [RETENTION / CHURN] Repeat purchase behavior: [REPEAT PURCHASE] Seasonality: [SEASONALITY] Marketing channels: [CHANNELS] Sales capacity: [SALES CAPACITY] Forecast horizon: [HORIZON] Build the forecast engine: A. Forecast driver tree Create a revenue equation for each revenue stream. Examples: - Leads x conversion rate x average deal value - Customers x purchase frequency x average order value - Starting MRR + new MRR + expansion MRR - churned MRR - Locations x average revenue per location - Projects sold x average project value B. Assumption library For every forecast driver list: - assumption - evidence - historical baseline - upside factor - downside factor - owner - confidence level C. Scenario forecast Build three scenarios: 1. Conservative 2. Base case 3. Aggressive For each include: - revenue by month - key assumptions - required resources - cash impact - risk - probability - leading indicators D. Forecast accuracy system Define how to compare forecast vs actual: - monthly variance - driver variance - timing variance - price variance - volume variance - churn variance - channel variance E. Forecast decision triggers Create triggers for: - hiring - spend increases - spend cuts - inventory planning - cash conservation - sales hiring - marketing budget changes F. Forecast memo Write a leadership summary: - forecast range - most likely case - biggest upside lever - biggest downside risk - weakest assumption - next data needed Rules: - Do not make one-point forecasts without ranges. - Do not hide assumptions. - Do not forecast revenue from hope or targets alone. - Mark weak assumptions as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#086Cost Structure X-Ray

FINANCE, BUDGETING & UNIT ECONOMICSCFOs, founders, operators, consultants, finance teams, agencies, ecommerce, SaaS, service businesses, restaurants, retail, and companies under cost pressure.

Examine fixed, variable, semi-variable, direct, indirect, discretionary, and hidden costs to understand margin risk and cost flexibility.

Act as a cost structure investigator. X-ray the cost structure of [COMPANY NAME] and reveal what costs are essential, flexible, wasteful, risky, hidden, or scaling incorrectly. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Cost list: [COST LIST] Revenue: [REVENUE] Gross margin: [GROSS MARGIN] Operating expenses: [OPEX] Payroll: [PAYROLL] Vendor costs: [VENDORS] Software/tools: [TOOLS] Marketing spend: [MARKETING] Fulfillment costs: [FULFILLMENT] Facilities / rent: [FACILITIES] Debt or financing costs: [DEBT] Growth plans: [GROWTH PLANS] Cost concerns: [CONCERNS] Run the cost x-ray: Layer 1 - Cost classification Classify each cost as: - fixed - variable - semi-variable - direct - indirect - discretionary - strategic investment - required compliance - customer-value cost - waste - hidden cost - risk cost Layer 2 - Cost behavior Explain how each cost changes when: - revenue grows - volume grows - customer count grows - team size grows - quality requirements increase - seasonality changes - the company enters a new market Layer 3 - Cost ownership For each cost identify: - owner - approval authority - contract term - renewal date - metric linked to it - review cadence Layer 4 - Cost risk scan Find risks: - costs growing faster than revenue - vendor dependency - underutilized tools - duplicate tools - expensive manual labor - hidden rework - unnecessary customization - margin leakage - poor purchasing discipline - long-term commitments Layer 5 - Cost action map Classify actions: - keep - reduce - renegotiate - replace - automate - shift to variable - consolidate - eliminate - invest more - review later Layer 6 - Cost reduction guardrails For every proposed reduction, explain: - customer impact - quality impact - team impact - revenue impact - risk - metric to monitor Final output: - cost structure summary - top 10 cost risks - top 10 savings opportunities - costs not to cut - vendor renegotiation list - 30-day cost cleanup plan Rules: - Do not recommend cuts that damage revenue or customer trust without warning. - Do not treat all expenses as equal. - Do not ignore contract terms. - Use [NEEDS DATA] for missing cost details. --------------------------------------------------------------------------------

#087Break-Even & Payback Decision Lab

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, operators, marketing leaders, sales leaders, agencies, ecommerce, SaaS, retail, restaurants, and businesses deciding whether to invest.

Calculate break-even points, payback periods, investment thresholds, and decision rules for products, hires, campaigns, locations, tools, or projects.

You are a financial decision lab analyst. Help [COMPANY NAME] decide whether [INVESTMENT / INITIATIVE] is financially justified by calculating break-even, payback, risk, and decision thresholds. Decision context: Company: [COMPANY NAME] Investment / initiative: [INVESTMENT] Purpose: [PURPOSE] Initial cost: [INITIAL COST] Ongoing monthly cost: [ONGOING COST] Expected revenue impact: [REVENUE IMPACT] Expected cost savings: [SAVINGS] Gross margin: [GROSS MARGIN] Capacity impact: [CAPACITY] Timeline: [TIMELINE] Alternative options: [ALTERNATIVES] Risk tolerance: [RISK TOLERANCE] Available data: [DATA] Build the decision lab: Experiment Table Create a financial model with: - investment amount - monthly cost - expected monthly benefit - gross margin - contribution benefit - break-even volume - break-even revenue - break-even timeline - payback period - cash low point - expected ROI range Scenario Cards Build four scenarios: 1. Best case 2. Base case 3. Slow case 4. Failure case For each include: - assumptions - result - payback - downside - cash impact - decision implication Threshold Rules Define: - minimum revenue required - minimum margin required - minimum utilization required - maximum acceptable payback - stop-loss threshold - scale threshold - review date Sensitivity Switchboard Test what happens if: - revenue impact is 25% lower - costs are 20% higher - timeline doubles - conversion is lower - churn increases - savings are delayed - utilization is weaker Decision Memo Write: - approve / reject / test first / delay - why - biggest assumption - financial risk - operational risk - first validation milestone Rules: - Do not approve investments without payback logic. - Do not count optimistic benefits without confidence levels. - Do not ignore ongoing cost. - Mark uncertain inputs as [ASSUMPTION]. --------------------------------------------------------------------------------

#088CAC, LTV & Payback Cohort Interpreter

FINANCE, BUDGETING & UNIT ECONOMICSSaaS, ecommerce, subscription businesses, marketplaces, agencies, digital products, growth teams, CFOs, investors, and founders evaluating acquisition quality.

Analyze customer acquisition cost, lifetime value, payback period, retention, expansion, and cohort quality by segment or channel.

Act as a customer economics interpreter. Analyze CAC, LTV, payback, and cohort quality for [COMPANY NAME] and explain whether acquisition is creating durable profit. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Acquisition channels: [CHANNELS] Marketing spend: [MARKETING SPEND] Sales spend: [SALES SPEND] New customers: [NEW CUSTOMERS] Revenue by cohort: [REVENUE BY COHORT] Gross margin: [GROSS MARGIN] Retention / churn: [RETENTION / CHURN] Expansion revenue: [EXPANSION] Refunds / cancellations: [REFUNDS] Support / onboarding costs: [SUPPORT COSTS] Customer segments: [SEGMENTS] Time period: [PERIOD] Interpret using this method: 1. CAC definitions Calculate or define: - paid media CAC - blended CAC - fully loaded CAC - sales-assisted CAC - channel CAC - segment CAC Explain which one is most useful for the decision. 2. LTV construction Build LTV from: - average revenue - gross margin - retention - repeat purchase - expansion - churn - support burden - discounting - refunds Show where LTV is weak or inflated. 3. Payback logic Calculate or structure: - gross margin payback - contribution payback - cash payback - payback by channel - payback by segment 4. Cohort quality table For each cohort or segment include: - customers acquired - CAC - first purchase / first month revenue - gross margin - retention - expansion - refunds - support burden - contribution profit - payback - quality rating 5. Acquisition diagnosis Classify channels as: - scale - optimize - cap - fix retention first - stop - needs more data 6. Leadership interpretation Answer: - are we buying profitable customers? - which channel looks good but is weak? - which segment deserves more budget? - where is CAC acceptable only because LTV is strong? - where is LTV overstated? - what must improve before scaling? Rules: - Do not use revenue LTV when margin LTV is needed. - Do not compare channels without considering retention quality. - Do not ignore payback timing. - Use [LOW CONFIDENCE] where cohort data is incomplete. --------------------------------------------------------------------------------

#089Department Budget Negotiation Pack

FINANCE, BUDGETING & UNIT ECONOMICSCEOs, CFOs, COOs, department heads, finance business partners, agencies, startups, and companies running quarterly or annual budget reviews.

Prepare department budget decisions by clarifying priorities, tradeoffs, required spend, optional spend, ROI logic, risks, and approval questions.

You are a finance business partner. Prepare a budget negotiation pack for [DEPARTMENT] so leadership can approve, reduce, defer, or redesign the request with clear reasoning. Inputs: Company: [COMPANY NAME] Department: [DEPARTMENT] Planning period: [PERIOD] Department goals: [GOALS] Requested budget: [REQUESTED BUDGET] Current budget: [CURRENT BUDGET] Actual spend: [ACTUAL SPEND] Previous performance: [PERFORMANCE] Headcount request: [HEADCOUNT] Tool / vendor request: [TOOLS / VENDORS] Project request: [PROJECTS] Revenue or operational impact: [IMPACT] Risks if not funded: [RISKS] Company financial constraints: [CONSTRAINTS] Create the budget pack: Opening Summary Write: - total requested budget - change vs current budget - main reason for increase or decrease - business outcome expected - leadership decision needed Budget Request Breakdown Create a table: - line item - amount - owner - category - must-have / should-have / nice-to-have - expected outcome - metric - risk if removed - approval recommendation ROI / Value Logic For each major request explain: - financial return - productivity return - risk reduction - customer impact - revenue impact - margin impact - time horizon - confidence level Tradeoff Menu Create three budget versions: 1. Minimum viable budget 2. Recommended budget 3. Accelerated growth budget For each include: - included items - excluded items - expected results - risks - staffing impact - timeline impact Hard Questions for the Department Head Write 15 questions leadership should ask before approval. Approval Decision Classify each request as: - approve - approve with metric - reduce - defer - reject - replace with cheaper option - needs more data Governance Define: - spending owner - monthly review - success metric - stop condition - variance threshold Rules: - Do not approve budget because the department asks confidently. - Do not reject spend without understanding business impact. - Do not count vague productivity gains as guaranteed ROI. - Make tradeoffs clear and decision-ready. --------------------------------------------------------------------------------

#090Gross Margin Expansion Sprint

FINANCE, BUDGETING & UNIT ECONOMICSEcommerce, retail, restaurants, service businesses, SaaS, agencies, manufacturing-adjacent companies, CFOs, operators, and founders improving profitability.

Improve gross margin through pricing, product mix, vendor costs, fulfillment efficiency, waste reduction, packaging, and customer segmentation.

Act as a gross margin sprint leader. Design a focused sprint to improve gross margin for [COMPANY NAME] without damaging customer value or revenue quality. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current gross margin: [CURRENT GROSS MARGIN] Target gross margin: [TARGET GROSS MARGIN] Products / services: [PRODUCTS / SERVICES] Revenue by product / service: [REVENUE BY PRODUCT] Direct costs: [DIRECT COSTS] Vendor costs: [VENDOR COSTS] Fulfillment process: [FULFILLMENT] Discounting: [DISCOUNTS] Returns / refunds / waste: [RETURNS / WASTE] Pricing: [PRICING] Customer segments: [SEGMENTS] Constraints: [CONSTRAINTS] Design the sprint: Sprint Charter Define: - margin goal - scope - timeline - owner - teams involved - guardrail metrics - customer experience constraints Margin Decomposition Break gross margin by: - product - service - customer segment - channel - location - order size - vendor - fulfillment method Opportunity Hunt Identify margin levers: - price increase - discount reduction - vendor renegotiation - product mix shift - bundle redesign - minimum order size - waste reduction - fulfillment efficiency - packaging change - automation - service scope control - premium tier - low-margin item removal For each lever include: - expected impact - customer risk - operational effort - speed - confidence - owner - metric Sprint Experiments Create 10 margin experiments. For each: - hypothesis - change - audience / product - duration - primary metric - guardrail metric - success threshold - rollback condition Margin Protection Rules Create rules for: - discounts - custom work - low-margin products - vendor approval - pricing exceptions - minimum order / contract size Final Sprint Plan Create: - week 1 analysis - week 2 quick wins - week 3 experiments - week 4 decision review - 60-day scaling plan Rules: - Do not improve gross margin by hiding costs elsewhere. - Do not cut quality that customers value. - Do not rely only on price increases. - Use contribution margin if gross margin is misleading. --------------------------------------------------------------------------------

#091Budget Variance Root Cause Investigator

FINANCE, BUDGETING & UNIT ECONOMICSCFOs, finance managers, founders, operators, department leaders, agencies, SaaS teams, ecommerce teams, and monthly financial reviews.

Investigate why actual financial results differ from budget or forecast and turn variance into better decisions, controls, and assumptions.

You are a budget variance investigator. Analyze the variance between planned and actual results for [COMPANY NAME] and identify the true causes, decision implications, and corrective actions. Inputs: Company: [COMPANY NAME] Period: [PERIOD] Budget / forecast: [BUDGET / FORECAST] Actual results: [ACTUALS] Variance report: [VARIANCE REPORT] Revenue details: [REVENUE DETAILS] Cost details: [COST DETAILS] Department notes: [DEPARTMENT NOTES] Known events: [EVENTS] Seasonality: [SEASONALITY] Leadership concerns: [CONCERNS] Investigate in this structure: Variance Snapshot Create a table: - line item - budget - actual - variance amount - variance % - favorable / unfavorable - materiality - owner - first explanation - confidence level Root Cause Tree Classify each material variance as: Revenue variance: - volume - price - mix - timing - churn - conversion - seasonality - one-time event - forecast assumption error Cost variance: - rate - volume - timing - usage - contract change - hiring - vendor cost - waste - rework - unplanned expense - accounting classification Investigation Questions For every material variance generate: - what happened? - when did it happen? - who owns it? - was it controllable? - was it expected? - will it repeat? - what assumption was wrong? - what decision must change? Management Actions Classify responses: - no action - reforecast - reduce spend - increase investment - change owner - renegotiate vendor - adjust pricing - improve process - fix reporting - update assumptions Forecast Learning Update: - assumptions - driver model - seasonality logic - budget owner accountability - thresholds - reporting cadence Executive Summary Write: - biggest favorable variance - biggest unfavorable variance - real cause - what is temporary - what is structural - action required - next month watchlist Rules: - Do not accept vague explanations like "timing" without detail. - Do not overreact to immaterial variances. - Do not blame departments before checking assumptions. - Mark unresolved causes as [NEEDS INVESTIGATION]. --------------------------------------------------------------------------------

#092Rolling Forecast Rhythm Builder

FINANCE, BUDGETING & UNIT ECONOMICSCFOs, finance teams, founders, operators, SaaS teams, agencies, ecommerce businesses, service businesses, and leadership teams needing adaptive planning.

Create a rolling forecast process that updates assumptions, revenue, costs, hiring, cash, and scenarios continuously instead of once per year.

Act as a rolling forecast system designer. Build a rolling forecast rhythm for [COMPANY NAME] that keeps leadership planning current as actual results change. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current budgeting process: [CURRENT PROCESS] Forecast horizon: [HORIZON] Revenue drivers: [REVENUE DRIVERS] Cost drivers: [COST DRIVERS] Hiring plans: [HIRING] Cash position: [CASH] Actual results cadence: [ACTUALS CADENCE] Departments involved: [DEPARTMENTS] Current forecasting problems: [PROBLEMS] Leadership decisions supported: [DECISIONS] Design the rolling forecast system: 1. Forecast philosophy Define: - why the company needs a rolling forecast - what it replaces - what it does not replace - how leadership should use it - how often it updates 2. Forecast horizon Recommend: - 13-week cash forecast - 6-month operating forecast - 12-month financial forecast - 18-24 month strategic forecast Explain when each is needed. 3. Driver model Define forecast drivers for: - revenue - churn / retention - sales pipeline - marketing spend - headcount - payroll - cost of goods - gross margin - operating expenses - capital expenses - working capital - cash 4. Monthly rhythm Create a monthly process: - actuals close - variance review - assumption update - department input - scenario refresh - leadership review - decisions logged 5. Forecast ownership Assign: - finance owner - revenue owner - cost owner - hiring owner - cash owner - department owners - final approver 6. Scenario logic Create: - downside case - base case - upside case - trigger-based case 7. Forecast outputs Define: - dashboard - leadership memo - cash warning - hiring recommendation - budget adjustment - spend decision 8. Adoption checklist Create what must be true for the rolling forecast to work. Rules: - Do not create a forecast nobody updates. - Do not make finance own assumptions without business owners. - Do not turn forecasting into false precision. - Every forecast update should support decisions. --------------------------------------------------------------------------------

#093Working Capital & Cash Conversion Optimizer

FINANCE, BUDGETING & UNIT ECONOMICSEcommerce, retail, manufacturing-adjacent companies, agencies, service businesses, B2B companies, restaurants, distributors, and companies with cash tied up in operations.

Improve cash flow by optimizing receivables, payables, inventory, deposits, billing timing, payment terms, and cash conversion cycle.

You are a working capital optimization advisor. Analyze how cash moves through [COMPANY NAME] and recommend ways to improve the cash conversion cycle without damaging supplier or customer relationships. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue collection process: [COLLECTION PROCESS] Accounts receivable: [AR] Accounts payable: [AP] Inventory: [INVENTORY] Deposits / prepayments: [DEPOSITS] Payment terms with customers: [CUSTOMER TERMS] Payment terms with vendors: [VENDOR TERMS] Billing timing: [BILLING TIMING] Order / delivery cycle: [ORDER / DELIVERY CYCLE] Current cash pressure: [CASH PRESSURE] Customer relationship constraints: [CUSTOMER CONSTRAINTS] Supplier constraints: [SUPPLIER CONSTRAINTS] Optimize working capital: Cash Journey Map Map the path: Cash spent -> inventory / labor / delivery -> product or service delivered -> invoice issued -> payment collected -> vendor paid -> cash available again For each stage include: - timing - owner - risk - delay - cash trapped - improvement opportunity Receivables Review Analyze: - invoice timing - payment terms - overdue balances - customer concentration - collection process - disputes - payment methods - deposit opportunities Payables Review Analyze: - vendor terms - early payment discounts - late payment risks - negotiation opportunities - payment scheduling - supplier dependency - concentration risk Inventory / WIP Review Analyze: - stock levels - slow-moving inventory - reorder logic - seasonality - waste - work in progress - cash tied up - stockout risk Cash Conversion Metrics Define: - days sales outstanding - days payable outstanding - inventory days - cash conversion cycle - AR aging - inventory turnover - working capital ratio Action Menu Recommend: - faster invoicing - deposit collection - milestone billing - payment links - stricter credit terms - vendor term negotiation - inventory reduction - preorder model - subscription / retainer billing - dispute prevention - collection cadence Rules: - Do not improve cash by damaging critical supplier trust. - Do not delay payables without understanding consequences. - Do not reduce inventory below service needs. - Cash timing is as important as profit. --------------------------------------------------------------------------------

#094Financial KPI Dashboard Builder

FINANCE, BUDGETING & UNIT ECONOMICSCEOs, CFOs, founders, finance teams, investors, boards, operators, SaaS, ecommerce, agencies, service businesses, and leadership reporting.

Build a finance dashboard that shows revenue, margin, cash, burn, runway, budget variance, unit economics, acquisition efficiency, and financial risk.

You are a financial dashboard designer. Build a decision-ready financial KPI dashboard for [COMPANY NAME] that shows leadership what is happening, why it matters, and what actions are needed. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Financial goals: [GOALS] Current reports: [CURRENT REPORTS] Revenue data: [REVENUE DATA] Cost data: [COST DATA] Cash data: [CASH DATA] Budget data: [BUDGET DATA] Unit economics data: [UNIT ECONOMICS] Acquisition data: [ACQUISITION DATA] Retention data: [RETENTION DATA] Leadership decisions: [DECISIONS] Reporting cadence: [CADENCE] Build the dashboard: Dashboard Role Define: - audience - decisions supported - update frequency - level of detail - what the dashboard should trigger - what the dashboard should not include Executive Snapshot Create top-level metrics: - revenue - revenue growth - gross margin - contribution margin - operating profit / loss - cash balance - burn rate - runway - budget variance - forecast variance Performance Panels Create panels for: 1. Revenue - new revenue - recurring revenue - repeat revenue - expansion - churn - segment performance 2. Margin - gross margin - contribution margin - product margin - service margin - channel margin 3. Cash - cash balance - burn - runway - collections - payables - upcoming obligations 4. Unit economics - CAC - LTV - payback - cost to serve - retention - contribution profit 5. Budget control - budget vs actual - variance - owner - action required Metric Definitions For every metric include: - formula - source - owner - target - warning threshold - bad threshold - action triggered Leadership Review Script Write a 30-minute monthly finance review agenda. Rules: - Do not include vanity metrics. - Do not show a metric without an owner. - Do not show numbers without thresholds. - Every dashboard section must support a decision. --------------------------------------------------------------------------------

#095Product, Segment & Channel Profitability Matrix

FINANCE, BUDGETING & UNIT ECONOMICSEcommerce, SaaS, agencies, marketplaces, service businesses, retail, restaurants, multi-product companies, CFOs, and operators improving profit mix.

Identify which products, customer segments, and channels produce real profit after costs, acquisition, fulfillment, discounts, and support.

Act as a profitability matrix analyst. Build a matrix that reveals which products, segments, and channels are profitable, which are misleading, and which should be changed. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Products / services: [PRODUCTS / SERVICES] Customer segments: [SEGMENTS] Sales channels: [CHANNELS] Revenue by product / segment / channel: [REVENUE] Gross margin by product / segment / channel: [GROSS MARGIN] Acquisition cost by channel: [ACQUISITION COST] Fulfillment cost: [FULFILLMENT COST] Support cost: [SUPPORT COST] Discounts: [DISCOUNTS] Returns / refunds: [RETURNS] Retention / repeat purchase: [RETENTION] Capacity constraints: [CAPACITY] Strategic priorities: [PRIORITIES] Create the profitability matrix: Axis 1 - Product profitability For each product / service show: - revenue - gross margin - direct cost - fulfillment burden - support burden - return / refund rate - contribution profit - scalability - strategic value Axis 2 - Segment profitability For each customer segment show: - revenue - average order / contract value - acquisition cost - retention - support burden - discount level - payment behavior - contribution profit - expansion potential Axis 3 - Channel profitability For each channel show: - revenue - CAC / CPA - conversion rate - average order value - retention quality - refund rate - margin - payback - scalability Profitability Quadrants Classify each product, segment, and channel: - scale aggressively - maintain - optimize - reprice - bundle - restrict - fix cost structure - stop or sunset - needs data Hidden Profit Investigation Find: - high revenue / low profit items - low revenue / high margin opportunities - channels with weak retention - segments with high support cost - products with hidden operational burden - discount-driven false growth Action Plan Create: - what to scale - what to fix - what to stop - what to test - what data to collect - expected profit impact Rules: - Do not judge performance by revenue alone. - Do not ignore cost to serve. - Do not average together channels with different customer quality. - Mark missing cost allocations as [NEEDS DATA]. --------------------------------------------------------------------------------

#096Headcount & Payroll Planning Model

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, COOs, HR leaders, agencies, SaaS, service businesses, ecommerce teams, and companies deciding when to hire.

Plan hiring and payroll based on revenue, capacity, workload, cash, profitability, timing, productivity, and budget constraints.

You are a headcount planning finance partner. Build a headcount and payroll plan for [COMPANY NAME] that connects hiring decisions to capacity, revenue, cash, margin, and execution needs. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current team: [CURRENT TEAM] Current payroll: [PAYROLL] Open roles requested: [ROLES] Revenue forecast: [REVENUE FORECAST] Cash runway: [RUNWAY] Gross margin: [GROSS MARGIN] Operating margin: [OPERATING MARGIN] Workload / capacity data: [WORKLOAD] Revenue per employee: [REVENUE PER EMPLOYEE] Department budgets: [BUDGETS] Hiring priorities: [PRIORITIES] Constraints: [CONSTRAINTS] Build the hiring finance model: Hiring Request Card For each requested role include: - role - department - hiring manager - salary - fully loaded cost - start date - ramp time - business reason - capacity problem solved - revenue or cost impact - risk if not hired - approval recommendation Payroll Impact Model Show impact on: - monthly payroll - fully loaded people cost - operating expenses - gross margin, if delivery role - burn rate - runway - revenue per employee - manager capacity - department budget Hiring Trigger Rules Define when a hire is justified by: - revenue threshold - workload threshold - customer SLA risk - backlog level - quality risk - manager span of control - sales pipeline - operational bottleneck - strategic capability gap Alternatives to Hiring Evaluate: - automation - contractor - outsourcing - temporary help - process improvement - role redesign - scope reduction - tool upgrade - cross-training Scenario Plan Create: - conservative hiring plan - base hiring plan - aggressive hiring plan - hiring freeze plan For each include cash impact and operational tradeoffs. Approval Decision Classify each role as: - approve now - approve after trigger - defer - replace with contractor - solve with process change - reject Rules: - Do not approve hiring based only on team pain. - Do not ignore ramp time and fully loaded cost. - Do not solve every capacity issue with headcount. - Do not delay critical hires if quality, revenue, or risk will break. --------------------------------------------------------------------------------

#097Investor-Ready Financial Narrative Builder

FINANCE, BUDGETING & UNIT ECONOMICSStartup founders, CFOs, investor updates, board meetings, fundraising decks, finance teams, SaaS, marketplaces, ecommerce, and growth companies.

Turn financial metrics, assumptions, runway, growth, margin, unit economics, and capital needs into a clear investor or board narrative.

Act as an investor-facing CFO. Build a financial narrative for [COMPANY NAME] that explains the business clearly, honestly, and credibly to investors or the board. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Stage: [STAGE] Revenue: [REVENUE] Growth rate: [GROWTH RATE] Gross margin: [GROSS MARGIN] Burn rate: [BURN RATE] Runway: [RUNWAY] CAC / LTV / payback: [UNIT ECONOMICS] Retention / churn: [RETENTION / CHURN] Revenue streams: [REVENUE STREAMS] Forecast: [FORECAST] Capital need: [CAPITAL NEED] Use of funds: [USE OF FUNDS] Key risks: [RISKS] Milestones: [MILESTONES] Audience: [INVESTORS / BOARD / LENDERS / INTERNAL LEADERSHIP] Build the narrative: Financial Storyline Write the core financial story in 5 parts: 1. Where the business is now 2. What is working financially 3. What is not yet working 4. What the company is doing about it 5. What capital or decisions are needed Metric Interpretation For each major metric explain: - number - trend - why it matters - what is driving it - whether it is strong, weak, improving, or risky - next action Investor Questions Answer: - how does the company make money? - how efficient is growth? - how strong are margins? - how predictable is revenue? - how much cash is available? - how long is runway? - what milestones will the cash reach? - what must improve before the next raise? - what is the biggest risk? - what is the plan if growth is slower? Use-of-Funds Logic Break capital use into: - product - sales - marketing - operations - hiring - working capital - debt / obligations - buffer For each explain expected business result. Financial Slide Pack Outline Create 8 finance slides: - revenue model - historical performance - unit economics - margin profile - forecast - runway - use of funds - milestone plan Rules: - Do not over-polish weak metrics. - Do not hide risks. - Do not use vanity metrics instead of financial drivers. - Mark unsupported projections as [ASSUMPTION]. --------------------------------------------------------------------------------

#098Finance Controls & Approval System

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, controllers, operations leaders, agencies, small businesses, startups, nonprofits, ecommerce teams, and scaling companies needing financial discipline.

Create financial controls for spending, approvals, vendor management, budget changes, reimbursement, purchase requests, and fraud or error prevention.

You are a finance controls designer. Build a practical financial control system for [COMPANY NAME] that prevents waste, surprise expenses, errors, and uncontrolled spending without slowing the business unnecessarily. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Current approval process: [APPROVAL PROCESS] Current budget process: [BUDGET PROCESS] Spending categories: [SPENDING CATEGORIES] Known problems: [PROBLEMS] Expense tools: [TOOLS] Vendor list: [VENDORS] Bank / card setup: [BANK / CARDS] Fraud or error concerns: [CONCERNS] Monthly spend: [MONTHLY SPEND] Risk tolerance: [RISK TOLERANCE] Design the control system: Control Map Create controls for: - purchase requests - vendor onboarding - software subscriptions - credit cards - reimbursements - contractor payments - payroll changes - marketing spend - inventory purchases - travel - emergency spend - budget exceptions Approval Matrix Define approval levels by: - spend amount - category - department - risk level - recurring vs one-time - contract length - budgeted vs unbudgeted For each level include: - requester - reviewer - approver - documentation required - SLA for approval - exception rule Spend Request Form Create a template with: - business reason - amount - budget line - owner - vendor - expected outcome - alternatives considered - risk - renewal date - success metric Vendor Control Create rules for: - vendor approval - contract review - renewal tracking - duplicate vendors - price benchmarking - cancellation - ownership Monthly Control Review Design a monthly process to review: - budget variance - new vendors - recurring charges - unusual spend - missed approvals - upcoming renewals - policy violations Rules: - Do not create controls that are heavier than the risk. - Do not allow unowned recurring spend. - Do not approve unbudgeted spend without a reason and owner. - Controls should create visibility, not bureaucracy. --------------------------------------------------------------------------------

#099Runway, Burn & Funding Decision Playbook

FINANCE, BUDGETING & UNIT ECONOMICSStartups, founders, CFOs, venture-backed companies, bootstrapped businesses, agencies, growth companies, and leadership teams managing cash runway.

Manage runway, burn rate, cash conservation, hiring pace, fundraising timing, profitability targets, and contingency plans.

Act as a runway and burn advisor. Build a funding and cash decision playbook for [COMPANY NAME] that helps leadership decide how fast to spend, when to raise, what to cut, and what milestones matter. Inputs: Company: [COMPANY NAME] Stage: [STAGE] Current cash: [CASH] Monthly revenue: [REVENUE] Monthly gross margin: [GROSS MARGIN] Monthly operating expenses: [OPEX] Current burn: [BURN] Current runway: [RUNWAY] Revenue forecast: [FORECAST] Hiring plan: [HIRING] Fundraising plan: [FUNDRAISING] Profitability goal: [PROFITABILITY GOAL] Key milestones: [MILESTONES] Investor / lender constraints: [CONSTRAINTS] Risk tolerance: [RISK TOLERANCE] Build the playbook: Runway Reality Check Calculate or structure: - gross burn - net burn - current runway - runway under base case - runway under downside case - cash-out month - minimum cash buffer - fundraising deadline Burn Quality Audit Classify spend into: - essential operations - growth investment - product investment - customer success - efficiency investment - experimental spend - low-confidence spend - legacy spend - cuttable spend Milestone Funding Map For each milestone include: - milestone - why it matters - required spend - expected proof - deadline - cash required - investor / leadership relevance - risk if missed Runway Extension Levers Evaluate: - hiring slowdown - vendor cuts - marketing reallocation - pricing change - collection acceleration - customer prepayments - contractor reduction - scope reduction - fundraising - debt - profitability push For each include: - months added - business risk - team risk - growth risk - customer risk - reversibility Decision Triggers Create triggers for: - start fundraising - reduce burn - freeze hiring - cut discretionary spend - pursue bridge capital - shift to profitability - pause expansion Board / Leadership Memo Write: - current runway - biggest cash risk - recommended burn level - milestone plan - contingency plan - decision needed now Rules: - Do not calculate runway from optimistic revenue only. - Do not cut spend without understanding milestone impact. - Do not wait until runway is short to plan fundraising. - Mark projections as [ASSUMPTION]. --------------------------------------------------------------------------------

#100Full Finance, Budgeting & Unit Economics Audit

FINANCE, BUDGETING & UNIT ECONOMICSFounders, CFOs, finance teams, investors, consultants, COOs, agencies, SaaS companies, ecommerce businesses, service businesses, and leadership teams doing a finance reset.

Audit the full finance system across revenue, budget, cost structure, cash flow, unit economics, margins, forecasting, controls, runway, and decision quality.

Act as an independent finance, budgeting, and unit economics auditor. Review the full financial system of [COMPANY NAME] and identify the highest-leverage improvements for profitability, cash control, budget discipline, and decision quality. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Revenue streams: [REVENUE STREAMS] Products / services: [PRODUCTS / SERVICES] Customer segments: [SEGMENTS] Current financial statements: [FINANCIAL STATEMENTS] Budget: [BUDGET] Forecast: [FORECAST] Cash position: [CASH POSITION] Burn / profit: [BURN / PROFIT] Gross margin: [GROSS MARGIN] Contribution margin: [CONTRIBUTION MARGIN] Unit economics: [UNIT ECONOMICS] CAC / LTV / payback: [CAC / LTV / PAYBACK] Cost structure: [COST STRUCTURE] Working capital: [WORKING CAPITAL] Financial controls: [CONTROLS] Leadership concerns: [CONCERNS] Audit the finance system across 16 dimensions: 1. Revenue quality 2. Gross margin 3. Contribution margin 4. Unit economics 5. Customer acquisition efficiency 6. Retention and expansion economics 7. Cost structure 8. Budget discipline 9. Forecast accuracy 10. Cash flow 11. Working capital 12. Runway and burn 13. Department budget ownership 14. Financial controls 15. KPI dashboard quality 16. Decision usefulness For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - financial risk - cash risk - margin risk - decision risk - recommended fix - confidence level Then synthesize: A. Top 5 financial constraints Rank by: - cash impact - profit impact - urgency - strategic risk - ease of fixing - confidence B. Root cause analysis Identify whether the main issue is: - weak revenue quality - poor margin visibility - unprofitable customer segments - high CAC - weak retention - bad forecasting - uncontrolled spend - weak budget ownership - cash timing problem - cost structure problem - missing controls - poor financial reporting - assumptions treated as facts C. Finance repair strategy Create: - financial dashboard - budget governance system - unit economics model - cash flow forecast - cost reduction plan - margin improvement plan - forecast rhythm - approval controls - leadership reporting cadence D. 30/60/90-day finance improvement plan Create a practical plan with: - actions - owners - financial models to build - reports to clean - controls to implement - budget decisions - margin actions - cash actions - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard financial truth - the biggest profit leak - the biggest cash risk - the fastest improvement - the next leadership decision - the data needed before major changes Rules: - Do not invent financial data. - Do not judge the business only by revenue growth. - Do not hide weak unit economics. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on cash, profit, margin, budget discipline, and decision clarity.

#101Revenue Growth Operating Map

SALES STRATEGY & REVENUE GROWTHFounders, CEOs, CROs, sales leaders, revenue teams, consultants, agencies, SaaS companies, service businesses, B2B companies, and teams building a repeatable sales strategy.

Build a clear revenue growth system that connects target customers, sales motion, pipeline creation, conversion, deal size, retention, expansion, and operating cadence.

You are a senior revenue strategist. Build a complete revenue growth operating map for [COMPANY NAME] that shows how the company should generate, convert, retain, and expand revenue in a repeatable way. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Product / service: [PRODUCT / SERVICE] Target customers: [TARGET CUSTOMERS] Current revenue: [CURRENT REVENUE] Revenue goal: [REVENUE GOAL] Average deal size / order value: [ACV / AOV] Sales cycle: [SALES CYCLE] Current pipeline sources: [PIPELINE SOURCES] Current conversion rates: [CONVERSION RATES] Sales team size: [SALES TEAM] Marketing support: [MARKETING SUPPORT] Current sales process: [SALES PROCESS] Known revenue problems: [PROBLEMS] Time horizon: [TIME HORIZON] Create the revenue growth operating map: 1. Revenue equation Write the revenue equation for this business. Examples: - Leads x qualification rate x close rate x average deal size - Accounts targeted x meetings booked x opportunity rate x win rate x ACV - Customers x purchase frequency x AOV x retention - Starting MRR + new MRR + expansion MRR - churned MRR Then define the exact equation that fits [COMPANY NAME]. 2. Growth driver map Break revenue into drivers: - target market - lead generation - qualification - discovery - proposal / demo - negotiation - close rate - deal size - sales cycle length - onboarding - retention - expansion - referrals For each driver explain: - current state - likely bottleneck - metric to track - improvement lever - owner - confidence level 3. Sales motion diagnosis Determine whether the company should use: - founder-led sales - self-serve sales - product-led sales - inside sales - field sales - enterprise sales - channel sales - account-based sales - hybrid motion Explain the logic and tradeoffs. 4. Pipeline architecture Design pipeline sources: - outbound - inbound - referrals - partners - events - communities - content - paid acquisition - customer expansion - past lost deals - strategic accounts Classify each source as core, test, support, or avoid. 5. Conversion system Define what must happen at each sales stage: - entry criteria - buyer action - seller action - required proof - common objection - next step - exit criteria 6. Revenue cadence Create a weekly revenue operating rhythm: - pipeline review - deal review - prospecting review - forecast review - lost deal review - enablement review - experiment review 7. 90-day revenue plan Create a practical plan with: - first 30 days: diagnose and focus - days 31-60: build and test - days 61-90: scale what works Rules: - Do not recommend random tactics without connecting them to the revenue equation. - Do not confuse activity volume with revenue quality. - Do not ignore retention or expansion if the business has repeat revenue. - Mark missing data as [NEEDS DATA]. Done when leadership can explain where revenue comes from, what limits growth, and what must be improved first. --------------------------------------------------------------------------------

#102Ideal Account Revenue Targeting Lab

SALES STRATEGY & REVENUE GROWTHB2B sales teams, SaaS companies, agencies, consultants, enterprise sellers, outbound teams, founders, and teams that need better targeting before prospecting.

Identify the highest-value accounts or customer segments to target based on revenue potential, urgency, reachability, win probability, and strategic fit.

Act as an ideal account targeting analyst. Your job is to help [COMPANY NAME] stop chasing weak-fit prospects and build a focused target account strategy. Context: Company: [COMPANY NAME] Offer: [OFFER] Current customers: [CUSTOMER LIST / DESCRIPTION] Best customers: [BEST CUSTOMERS] Worst customers: [WORST CUSTOMERS] Target industries: [INDUSTRIES] Target company sizes: [COMPANY SIZES] Buyer roles: [BUYER ROLES] Current deal size: [DEAL SIZE] Win / loss notes: [WIN LOSS NOTES] Revenue goal: [GOAL] Available data: [DATA] Run the targeting lab: Lab Table 1 - Customer pattern extraction Analyze current and past customers. Identify: - most profitable customer type - fastest-to-close customer type - highest-retention customer type - highest-expansion customer type - most painful customer type - lowest-margin customer type - highest-support customer type - best-referral customer type Lab Table 2 - Fit criteria Create ideal account criteria across: - industry - company size - revenue range - team size - maturity level - technology stack - geography - urgency triggers - budget signals - buying authority - operational pain - compliance pressure - growth stage - strategic initiative Classify each criterion as must-have, strong positive, neutral, warning sign, or disqualifier. Lab Table 3 - Revenue potential score Create a scoring model: Revenue Potential Score = Pain Intensity + Budget Access + Deal Size + Expansion Potential + Retention Probability + Strategic Fit - Sales Complexity - Support Burden For each segment or account type include: - score - reason - evidence - risk - confidence Lab Table 4 - Account tiering Create account tiers: Tier A: - best-fit, highest priority, high-touch sales Tier B: - good-fit, scalable sales motion Tier C: - low-touch or automated nurture Tier D: - avoid or disqualify Lab Table 5 - Prospecting implications For each target tier define: - outreach angle - buying trigger - proof needed - likely objection - channel - first offer - qualification question - sales motion Final output: 1. Ideal account profile 2. Disqualification criteria 3. Top 5 segments to pursue 4. Top 5 segments to avoid 5. Prospect research checklist 6. First 100-account targeting plan Rules: - Do not define the ICP only by demographics. - Do not target accounts that cannot realistically buy. - Do not ignore cost to serve. - Separate proven patterns from assumptions. --------------------------------------------------------------------------------

#103Sales Funnel Friction Teardown

SALES STRATEGY & REVENUE GROWTHSales leaders, CROs, founders, growth teams, consultants, agencies, SaaS companies, service businesses, and teams with leads but weak conversion.

Diagnose where prospects drop, stall, misunderstand value, lose urgency, or fail to convert across the sales funnel.

You are a sales funnel friction auditor. Tear down the sales funnel for [COMPANY NAME] and identify the exact friction points preventing revenue growth. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target buyer: [BUYER] Sales funnel stages: [FUNNEL STAGES] Stage conversion rates: [CONVERSION RATES] Lead sources: [LEAD SOURCES] Sales scripts / emails: [SALES MATERIALS] Demo / discovery process: [PROCESS] Proposal process: [PROPOSAL PROCESS] CRM notes: [CRM NOTES] Lost deal reasons: [LOST DEAL REASONS] Objections: [OBJECTIONS] Revenue target: [TARGET] Use this teardown format: Funnel Stage 1 - Awareness to lead Audit: - traffic or prospect source - message clarity - buyer relevance - call to action - trust signals - offer strength - lead quality Funnel Stage 2 - Lead to qualified opportunity Audit: - response time - qualification criteria - discovery questions - buyer urgency - budget clarity - decision maker access - problem fit - disqualification discipline Funnel Stage 3 - Opportunity to proposal / demo Audit: - meeting quality - pain discovery - value connection - proof used - next-step clarity - stakeholder involvement - competitor comparison Funnel Stage 4 - Proposal / demo to close Audit: - proposal clarity - price framing - risk reversal - procurement friction - objection handling - follow-up cadence - urgency - decision path Funnel Stage 5 - Close to retention / expansion Audit: - onboarding handoff - expectation setting - first value - customer success - renewal risk - expansion path Create a Friction Register: For each friction point include: - stage - symptom - likely root cause - evidence - revenue impact - fix - owner - metric - priority Create a Conversion Improvement Plan: - fastest win - highest revenue impact fix - highest trust risk fix - enablement asset needed - script change - CRM change - process change - experiment to run Rules: - Do not blame salespeople before analyzing lead quality, process, and offer fit. - Do not optimize a stage without checking downstream revenue quality. - Do not assume more leads solve poor conversion. - Mark weak evidence as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#104Sales Motion Selector

SALES STRATEGY & REVENUE GROWTHStartups, SaaS companies, B2B businesses, marketplaces, agencies, enterprise teams, product-led companies, and founders deciding how to sell.

Choose the right sales motion based on buyer complexity, deal size, urgency, product education, sales cycle, customer expectations, and economics.

Act as a sales motion architect. Decide which sales motion [COMPANY NAME] should use and how to structure it for revenue growth. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Buyer complexity: [BUYER COMPLEXITY] Product complexity: [PRODUCT COMPLEXITY] Current sales motion: [CURRENT MOTION] Current conversion data: [CONVERSION DATA] Customer acquisition cost: [CAC] Gross margin: [GROSS MARGIN] Market maturity: [MARKET MATURITY] Competitors' sales motions: [COMPETITORS] Team capabilities: [CAPABILITIES] Revenue goal: [GOAL] Evaluate sales motions as decision cards: Card 1 - Self-serve - when it fits - when it fails - required product experience - required pricing clarity - required onboarding - economic logic Card 2 - Product-led sales - activation signals - sales assist triggers - upgrade path - data needed - handoff rules Card 3 - Inside sales - qualification needs - volume requirements - rep profile - process requirements - sales cycle fit Card 4 - Enterprise sales - stakeholder map - proof requirements - procurement needs - account planning - deal desk requirements Card 5 - Channel / partner sales - partner economics - training needs - conflict risk - control tradeoffs - support requirements Card 6 - Founder-led sales - when to keep it - when to transition - what to document - first sales hire timing Decision Matrix Score each motion by: - deal size fit - buyer complexity fit - cost efficiency - scalability - customer experience - speed to revenue - margin fit - team capability - forecast reliability - strategic control Recommended Sales Architecture Define: - primary sales motion - secondary sales motion - customer segment for each - handoff points - qualification rules - staffing model - tools needed - KPIs Transition Plan Create: - what to stop - what to continue - what to pilot - when to hire - when to automate - when to add sales-assisted support Rules: - Do not choose enterprise sales for low-value deals. - Do not choose self-serve if buyers need heavy trust-building. - Do not copy competitors blindly. - Use economics and buyer behavior as the decision base. --------------------------------------------------------------------------------

#105Pipeline Generation Campaign Architect

SALES STRATEGY & REVENUE GROWTHB2B sales teams, outbound teams, founders, agencies, consultants, SaaS companies, service businesses, and revenue teams building predictable pipeline.

Design a pipeline generation campaign that creates qualified meetings or opportunities through clear targeting, message-market fit, offers, channels, and follow-up.

You are a pipeline generation architect. Build a campaign that creates qualified sales opportunities for [COMPANY NAME], not just attention or replies. Campaign inputs: Company: [COMPANY NAME] Offer: [OFFER] Target segment: [TARGET SEGMENT] Buyer role: [BUYER ROLE] Primary pain: [PAIN] Business outcome: [OUTCOME] Proof available: [PROOF] Lead source: [LEAD SOURCE] Channels: [EMAIL / LINKEDIN / PHONE / EVENTS / PARTNERS / CONTENT] Sales capacity: [SALES CAPACITY] Meeting goal: [MEETING GOAL] Timeline: [TIMELINE] Current response data: [CURRENT DATA] Design the campaign: Campaign Thesis Write: We believe [TARGET BUYER] will respond to [MESSAGE ANGLE] because [PAIN / TRIGGER], and will take [CTA] if we provide [PROOF / OFFER]. Targeting Rules Define: - must-have criteria - trigger criteria - priority criteria - exclusion criteria - account research fields - contact research fields Offer Strategy Choose the first conversion offer: - discovery call - audit - benchmark report - teardown - ROI estimate - strategy session - demo - consultation - workshop - free tool - pilot Explain why this offer matches the buyer's readiness. Message Stack Create: - core message - pain angle - trigger angle - proof angle - curiosity angle - direct ROI angle - risk-reduction angle Channel Plan For each channel include: - purpose - sequence length - cadence - personalization level - asset needed - success metric - risk Follow-up System Create: - first touch - follow-up 1 - follow-up 2 - value add - breakup message - reactivation message - handoff to nurture Qualification Gate Define when a reply becomes: - not relevant - nurture - qualified lead - sales opportunity - high-priority opportunity Campaign Dashboard Track: - accounts targeted - contacts reached - open / view rate - reply rate - positive reply rate - meeting booked rate - qualified opportunity rate - close rate - revenue created Rules: - Do not optimize for reply rate alone. - Do not send generic outreach. - Do not target buyers without a relevant reason. - Every campaign must have a qualification rule and revenue metric. --------------------------------------------------------------------------------

#106Discovery Call Intelligence Builder

SALES STRATEGY & REVENUE GROWTHSales reps, founders, account executives, consultants, agencies, SaaS teams, enterprise sellers, and revenue leaders improving discovery quality.

Create a discovery call system that uncovers pain, urgency, decision process, budget, stakeholders, risks, and next steps without sounding robotic.

Act as a discovery call coach. Build a discovery call intelligence system for selling [PRODUCT / SERVICE] to [TARGET BUYER]. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target buyer: [TARGET BUYER] Typical customer problem: [PROBLEM] Typical deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current discovery questions: [CURRENT QUESTIONS] Common objections: [OBJECTIONS] Proof points: [PROOF] Qualification criteria: [QUALIFICATION] Next sales step: [NEXT STEP] Create the discovery system: Opening Frame Write a natural opening that: - sets the agenda - confirms time - lowers pressure - explains the goal - earns permission to ask direct questions - leaves room for the buyer's priorities Discovery Map Build question paths for: Path A - Problem discovery - what triggered the conversation? - what is happening now? - where does it create friction? - who is affected? - what has been tried? - why now? Path B - Business impact - cost of the problem - missed revenue - wasted time - risk - customer impact - team impact - strategic priority Path C - Current alternative - what are they using now? - what works? - what does not? - why have they not changed? - what would make change worthwhile? Path D - Decision process - stakeholders - timeline - approval process - budget source - evaluation criteria - procurement steps - competing priorities Path E - Fit and urgency - must-have outcomes - non-negotiables - success definition - consequences of delay - priority level Listening Cues For each strong buyer signal define: - phrase buyer may say - what it means - follow-up question - sales implication Red Flag Cues Identify: - no pain - no owner - no urgency - no budget path - unclear decision - unrealistic expectations - poor fit Next-Step Close Write 5 next-step transitions based on discovery outcome. Post-Call Summary Template Create a CRM-ready summary: - pain - impact - trigger - stakeholders - decision process - objections - fit score - next step - risk Rules: - Do not ask questions that sound like an interrogation. - Do not pitch before understanding the problem. - Do not qualify only by budget. - Discovery should reveal whether the deal deserves more time. --------------------------------------------------------------------------------

#107Deal Qualification Gatekeeper

SALES STRATEGY & REVENUE GROWTHSales leaders, founders, SDRs, AEs, B2B teams, agencies, consultants, enterprise sellers, and teams with bloated or low-quality pipelines.

Build a qualification system that helps sales teams focus on deals with real pain, authority, budget, urgency, fit, and win probability.

You are a deal qualification gatekeeper. Create a qualification system for [COMPANY NAME] that separates real opportunities from distractions. Inputs: Company: [COMPANY NAME] Offer: [OFFER] Target customer: [CUSTOMER] Current qualification process: [PROCESS] Current pipeline: [PIPELINE] Win rate: [WIN RATE] Lost deal reasons: [LOST REASONS] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Common poor-fit prospects: [POOR FIT] Strategic priorities: [PRIORITIES] Build the qualification system: Qualification Dimensions Create criteria for: 1. Problem Fit - what pain must exist? - what intensity matters? - what evidence confirms it? 2. Customer Fit - segment - size - maturity - use case - operating model - geography - strategic fit 3. Economic Fit - budget source - value potential - deal size - margin - expansion potential - cost to serve 4. Decision Fit - decision maker access - stakeholder clarity - approval process - timeline - competing priorities 5. Solution Fit - need matches offer - required features / services - implementation feasibility - support requirements - success conditions 6. Timing Fit - trigger event - deadline - urgency - cost of delay - buying window Fit Scorecard Create a score from 0-100 with: - scoring weights - pass threshold - disqualification threshold - escalation rule - manager review trigger Deal Stages For each pipeline stage define: - entry criteria - required evidence - exit criteria - disqualification reasons - CRM fields required - next-step requirement Disqualification Playbook Write polite language for: - poor fit - no urgency - no budget path - wrong use case - not ready - better served by another option Pipeline Hygiene Rules Create rules for: - when to move forward - when to nurture - when to close-lost - when to revive - when manager review is needed Rules: - Do not let interest alone create an opportunity. - Do not keep dead deals in the forecast. - Do not disqualify too early without checking strategic fit. - Qualification must improve focus, forecast quality, and customer experience. --------------------------------------------------------------------------------

#108Objection Handling Decision Tree

SALES STRATEGY & REVENUE GROWTHSales reps, founders, AEs, SDRs, consultants, agencies, SaaS teams, B2B sellers, and teams dealing with repeated objections.

Convert common sales objections into diagnosis questions, response frameworks, proof assets, follow-up actions, and deal-saving moves.

Act as an objection handling strategist. Build a decision tree for handling objections in sales conversations for [PRODUCT / SERVICE]. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target buyer: [BUYER] Common objections: [OBJECTIONS] Price point: [PRICE] Competitor alternatives: [ALTERNATIVES] Proof points: [PROOF] Guarantee / risk reversal: [GUARANTEE] Sales stage where objections occur: [STAGE] Lost deal reasons: [LOST DEAL REASONS] Create the objection system: Objection Library For each objection include: - objection wording - likely real meaning - stage where it appears - buyer emotion - risk level - deal implication Diagnosis Before Response For every objection, create 3-5 questions to determine whether it is: - real concern - hidden objection - budget issue - priority issue - trust issue - timing issue - authority issue - competitor comparison - polite rejection Decision Tree Create branches: If the objection is about price: - diagnose value gap - diagnose budget path - diagnose comparison point - respond with value proof - offer package option - define next step If the objection is about timing: - identify trigger - cost of delay - competing priority - nurture or close plan If the objection is about trust: - identify risk - provide proof - reduce perceived risk - suggest pilot or reference If the objection is about authority: - map stakeholders - create internal business case - ask for multi-threading Response Frameworks Create responses using different styles: - direct - consultative - proof-led - question-led - contrast-led - risk-reversal-led - executive-level Proof Asset Map For each objection recommend: - case study - ROI calculator - comparison sheet - security document - implementation plan - customer reference - demo section - FAQ - guarantee Follow-Up Actions Define: - when to send proof - when to schedule next call - when to bring in expert - when to reprice - when to disqualify - when to nurture Rules: - Do not argue with the buyer. - Do not answer before diagnosing. - Do not discount as the first response to price objections. - Objection handling should increase clarity, not pressure. --------------------------------------------------------------------------------

#109Proposal Strategy & Deal Room Builder

SALES STRATEGY & REVENUE GROWTHAgencies, consultants, B2B SaaS, enterprise sales, service providers, founders, AEs, and teams that need proposals to close more effectively.

Create a proposal strategy that connects buyer pain, business case, proof, pricing, implementation, stakeholders, risk reversal, and next steps.

You are a proposal strategist. Build a deal-specific proposal and deal room strategy for [PROSPECT / ACCOUNT] so the buyer can understand the value, justify the decision internally, and move forward with confidence. Inputs: Company selling: [COMPANY NAME] Prospect / account: [PROSPECT] Buyer roles: [BUYER ROLES] Product / service: [PRODUCT / SERVICE] Discovery notes: [DISCOVERY NOTES] Pain points: [PAINS] Business impact: [BUSINESS IMPACT] Desired outcomes: [OUTCOMES] Decision criteria: [CRITERIA] Competitors / alternatives: [ALTERNATIVES] Objections: [OBJECTIONS] Pricing / package: [PRICING] Proof points: [PROOF] Implementation requirements: [IMPLEMENTATION] Timeline: [TIMELINE] Build the proposal strategy: Executive Deal Narrative Write a short narrative: [PROSPECT] is trying to [GOAL], but [PROBLEM] is creating [BUSINESS IMPACT]. [COMPANY NAME] can help by [SOLUTION], producing [OUTCOME], with [PROOF] reducing the risk. Proposal Structure Create a proposal outline: 1. Executive summary 2. Current situation 3. Business problem 4. Desired outcomes 5. Recommended solution 6. Scope 7. Implementation plan 8. Timeline 9. Proof 10. Investment 11. Risk reversal 12. Decision process 13. Next steps Stakeholder Versioning Create message variations for: - economic buyer - end user - technical evaluator - procurement - executive sponsor - finance - operations Business Case Section Build: - cost of current problem - value of solution - ROI logic - payback logic - risk of inaction - success metrics Deal Room Assets Recommend assets to include: - proposal PDF - implementation plan - case study - ROI calculator - FAQ - security / compliance document - pricing explanation - stakeholder one-pager - timeline - contract checklist Close Plan Create: - mutual action plan - decision date - buyer tasks - seller tasks - risk points - escalation plan - final CTA Rules: - Do not send a generic proposal. - Do not hide risks or implementation requirements. - Do not make pricing appear disconnected from business value. - The proposal must help the buyer sell the decision internally. --------------------------------------------------------------------------------

#110Sales Forecast Reliability Engine

SALES STRATEGY & REVENUE GROWTHSales leaders, CROs, founders, CFOs, AEs, RevOps, revenue teams, SaaS companies, agencies, and any team with unreliable forecasts.

Improve forecast accuracy by inspecting deal stages, evidence, next steps, buyer commitment, close probability, timing, and risk.

Act as a sales forecast reliability analyst. Audit the current forecast for [COMPANY NAME] and rebuild it around evidence, not hope. Inputs: Company: [COMPANY NAME] Forecast period: [PERIOD] Revenue target: [TARGET] Current pipeline: [PIPELINE DATA] Deal list: [DEALS] Deal stages: [STAGES] Close dates: [CLOSE DATES] Deal values: [VALUES] Next steps: [NEXT STEPS] Buyer commitments: [BUYER COMMITMENTS] Historical win rates: [WIN RATES] Sales cycle length: [SALES CYCLE] Known risks: [RISKS] CRM notes: [CRM NOTES] Build the reliability engine: Forecast Evidence Checklist For every deal, verify: - real business problem - quantified impact - decision maker identified - budget path - timeline reason - decision process - next meeting scheduled - buyer-side action completed - proposal reviewed - legal / procurement status - competitor status - implementation timing - close date evidence Deal Confidence Categories Classify deals as: - Commit - Strong upside - Weak upside - Pipeline only - Nurture - Remove from forecast For each category define required evidence. Forecast Risk Score Score each deal by: - stage accuracy - buyer engagement - next-step strength - stakeholder coverage - budget clarity - urgency - competition - procurement risk - close date credibility - seller confidence bias Forecast Table Create a table: - deal - value - stage - stated close date - evidence-based close date - probability - confidence category - top risk - required action - forecast amount Slippage Analysis Identify deals likely to slip and explain: - why - what evidence is missing - what action could recover timing - whether the close date should change Forecast Review Cadence Create a weekly forecast meeting structure: - pre-work - deal inspection questions - risk review - next-step commitments - forecast changes - manager coaching actions Rules: - Do not forecast deals based only on rep confidence. - Do not accept close dates without buyer-side evidence. - Do not keep stalled deals in commit. - Forecasting should improve decisions, not punish honesty. --------------------------------------------------------------------------------

#111Sales Enablement Asset Gap Audit

SALES STRATEGY & REVENUE GROWTHSales enablement teams, product marketers, founders, agencies, consultants, B2B SaaS teams, enterprise sales, and revenue teams improving conversion.

Identify the sales assets needed to help prospects understand value, handle objections, compare options, justify purchase, and move through the buying process.

You are a sales enablement strategist. Audit the sales process of [COMPANY NAME] and identify which assets are missing, weak, or unnecessary. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target buyers: [BUYERS] Sales stages: [SALES STAGES] Current sales assets: [CURRENT ASSETS] Common objections: [OBJECTIONS] Competitors: [COMPETITORS] Customer proof: [PROOF] Lost deal reasons: [LOST REASONS] Sales team feedback: [SALES FEEDBACK] Buyer journey: [BUYER JOURNEY] Revenue goal: [GOAL] Create the asset gap audit: Buyer Question Map For each stage, list the buyer's questions: - why change? - why now? - why this solution? - why this company? - why this price? - why not competitor? - why trust implementation? - why approve internally? Asset Inventory Classify current assets: - useful - outdated - unclear - duplicated - missing proof - not used by sales - not aligned with buyer stage - should be retired Asset Gap Matrix Identify missing assets: - one-page overview - discovery guide - demo narrative - ROI calculator - case study - objection handling sheet - comparison page - security / compliance doc - implementation plan - pricing explanation - stakeholder memo - proposal template - email follow-up templates - FAQ - renewal / expansion deck For each missing asset include: - buyer question answered - sales stage - priority - owner - required inputs - format - metric of effectiveness Asset Quality Criteria Create standards for each asset: - clarity - relevance - proof - specificity - visual simplicity - objection coverage - decision usefulness - sales usability 90-Day Enablement Roadmap Create: - first 5 assets to build - assets to update - assets to remove - training needed - adoption plan - usage tracking Rules: - Do not create assets sales will not use. - Do not create generic content that fails to answer buying questions. - Do not overload reps with too many materials. - Every asset must support a specific sales moment. --------------------------------------------------------------------------------

#112Territory, Segment & Account Coverage Planner

SALES STRATEGY & REVENUE GROWTHSales leaders, CROs, RevOps teams, founders, B2B sales teams, enterprise teams, agencies, franchises, and organizations dividing revenue responsibility.

Design a sales coverage model that assigns territories, segments, accounts, reps, quotas, capacity, and focus areas logically.

Act as a sales coverage planner. Design a territory, segment, and account coverage model for [COMPANY NAME] that improves focus, fairness, capacity, and revenue accountability. Inputs: Company: [COMPANY NAME] Sales team structure: [TEAM STRUCTURE] Revenue target: [REVENUE TARGET] Customer segments: [SEGMENTS] Geographies: [GEOGRAPHIES] Industries: [INDUSTRIES] Account list: [ACCOUNTS] Current territories: [TERRITORIES] Rep capacity: [REP CAPACITY] Historical performance: [PERFORMANCE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Pipeline by segment: [PIPELINE] Strategic priorities: [PRIORITIES] Build the coverage model: Coverage Goals Define what the model must optimize for: - revenue potential - account focus - rep fairness - market coverage - expansion opportunity - specialization - speed - customer experience - management simplicity Account Universe Cleanup Classify accounts by: - named strategic accounts - high-potential accounts - active pipeline - current customers - expansion accounts - nurture accounts - low-fit accounts - disqualified accounts Segmentation Logic Choose the primary coverage basis: - geography - industry - company size - revenue potential - product line - customer lifecycle - named accounts - inbound vs outbound - enterprise vs SMB Explain why this basis is best. Rep Capacity Model Estimate: - accounts per rep - active opportunities per rep - meetings per week - prospecting time - deal management time - admin load - customer expansion load - manager coaching load Territory Design Create: - territory name - assigned rep - account count - revenue potential - current pipeline - quota logic - strategic accounts - risk - fairness rating Rules of Engagement Define: - account ownership - inbound lead routing - customer expansion ownership - account conflicts - territory changes - reassignment rules - partner conflicts Final Output Create: - coverage recommendation - territory table - quota implications - rep capacity risks - transition plan - data gaps Rules: - Do not divide territories only by equal account count. - Do not overload top reps with all best accounts. - Do not ignore customer lifecycle ownership. - Coverage should support focus and accountability. --------------------------------------------------------------------------------

#113Account Expansion Revenue Plan

SALES STRATEGY & REVENUE GROWTHAccount managers, customer success teams, sales leaders, SaaS companies, agencies, B2B services, enterprise sellers, and retention-focused revenue teams.

Build a customer account growth plan using usage, success outcomes, stakeholder mapping, upsell triggers, cross-sell opportunities, renewals, and risk signals.

You are an account growth strategist. Build an expansion revenue plan for [CUSTOMER / ACCOUNT NAME] that grows revenue by creating more customer value. Account context: Customer / account: [CUSTOMER NAME] Current products / services used: [CURRENT PRODUCTS] Current contract value: [CURRENT VALUE] Renewal date: [RENEWAL DATE] Account health: [HEALTH] Usage / engagement data: [USAGE] Business goals: [CUSTOMER GOALS] Stakeholders: [STAKEHOLDERS] Success outcomes achieved: [OUTCOMES] Open issues: [ISSUES] Support history: [SUPPORT] Potential products / services: [EXPANSION OPTIONS] Competitors / alternatives: [ALTERNATIVES] Build the account expansion plan: Account Health Snapshot Summarize: - current value delivered - adoption level - stakeholder support - unresolved risks - renewal risk - expansion readiness - confidence level Stakeholder Map Create a table: - stakeholder - role - influence level - current sentiment - business priority - value received - concern - next engagement Value Realization Map List: - promised outcomes - delivered outcomes - measurable wins - unproven value - missed expectations - proof to collect Expansion Opportunity Tree Identify opportunities: - more seats - more usage - more locations - premium plan - add-on feature - adjacent product - service layer - training - implementation - analytics - renewal upgrade - multi-year contract For each include: - customer need - trigger - value reason - price logic - proof needed - timing - risk Conversation Plan Create: - business review agenda - discovery questions - expansion positioning - objection responses - renewal tie-in - next-step ask Risk Defense Identify: - churn signals - adoption gaps - stakeholder gaps - competitor risk - budget risk - value proof gaps Final Output Create a 90-day account plan with actions, owners, dates, expected revenue impact, and success metrics. Rules: - Do not upsell before confirming value delivered. - Do not ignore unresolved customer issues. - Do not treat expansion as a sales trick. - Expansion must feel like the customer's next logical success step. --------------------------------------------------------------------------------

#114Lost Deal Autopsy System

SALES STRATEGY & REVENUE GROWTHSales leaders, founders, RevOps, product marketing, consultants, SaaS teams, agencies, enterprise sales teams, and companies improving win rate.

Analyze lost deals to uncover patterns in targeting, qualification, messaging, proof, pricing, competitors, process, and product fit.

Act as a lost deal forensic analyst. Analyze lost deals for [COMPANY NAME] and convert them into revenue learning. Inputs: Company: [COMPANY NAME] Lost deal list: [LOST DEALS] Target segment: [SEGMENT] Deal values: [VALUES] Sales stages reached: [STAGES] Lost reasons recorded: [LOST REASONS] Competitor chosen: [COMPETITOR] CRM notes: [CRM NOTES] Call notes: [CALL NOTES] Buyer feedback: [FEEDBACK] Proposal / pricing: [PROPOSAL / PRICING] Sales rep notes: [REP NOTES] Run the autopsy: Case File Summary For each lost deal create: - account - segment - deal value - stage lost - competitor / alternative - stated loss reason - likely real reason - evidence - confidence level Loss Reason Reclassification Reclassify vague reasons into specific categories: - no urgent pain - poor target fit - wrong stakeholder - weak qualification - no budget path - weak business case - unclear differentiation - competitor advantage - pricing mismatch - timing issue - procurement blocker - product gap - implementation concern - trust gap - sales process issue Pattern Detection Identify patterns by: - segment - deal size - lead source - rep - competitor - stage - objection - pricing package - sales cycle length - stakeholder type Root Cause Analysis For each major pattern identify whether it is caused by: - targeting - qualification - discovery - messaging - proof - pricing - product - process - timing - sales skill - competitive pressure Win-Back Potential Classify lost deals: - immediate win-back - nurture - revisit after trigger - lost permanently - wrong-fit, avoid Create win-back messaging for each relevant group. Revenue Learning Report Create: - top 5 patterns - changes to qualification - changes to messaging - assets needed - pricing implications - product implications - competitor response - next experiments Rules: - Do not accept CRM loss reasons at face value. - Do not blame price unless value and competition were analyzed. - Do not ignore poor-fit deals. - Lost deals should improve future strategy. --------------------------------------------------------------------------------

#115Sales Team Cadence & Coaching System

SALES STRATEGY & REVENUE GROWTHSales managers, CROs, founders, RevOps teams, agencies, SaaS sales teams, B2B sales teams, and growing revenue organizations.

Build a sales management cadence that improves rep focus, pipeline quality, coaching, accountability, CRM discipline, and revenue performance.

You are a sales management operating system designer. Build a team cadence and coaching system for [SALES TEAM] that improves performance without creating meeting overload. Inputs: Company: [COMPANY NAME] Sales team: [TEAM] Team roles: [ROLES] Revenue target: [TARGET] Current meetings: [MEETINGS] Sales process: [PROCESS] CRM fields: [CRM] Current KPIs: [KPIS] Rep performance data: [PERFORMANCE] Pipeline data: [PIPELINE] Common rep challenges: [CHALLENGES] Manager capacity: [MANAGER CAPACITY] Design the cadence: Cadence Architecture Create a weekly rhythm: - team pipeline review - one-on-one coaching - deal strategy review - prospecting block - forecast review - call review - enablement session - win / loss review For each include: - purpose - attendees - duration - required pre-work - agenda - decisions made - output - cancellation rule Rep Scorecard Build a scorecard with: - pipeline created - qualified opportunities - conversion rates - stage progression - deal hygiene - forecast accuracy - activity quality - call quality - follow-up discipline - closed revenue - learning progress Coaching System Create coaching tracks for: - prospecting - discovery - qualification - demo / pitch - objection handling - proposal - negotiation - follow-up - account expansion - forecast judgment For each track include: - coaching question - practice exercise - manager observation - success metric CRM Hygiene Rules Define: - required fields - update timing - stage exit criteria - next-step rules - close-date rules - loss reason rules - manager audit cadence Performance Intervention Create plans for: - high performer - inconsistent performer - new rep - underperforming rep - rep with strong activity but weak conversion - rep with weak pipeline but strong close rate Rules: - Do not manage only by activity count. - Do not hold meetings without decisions or coaching. - Do not let CRM become a reporting graveyard. - The cadence must improve behavior and revenue quality. --------------------------------------------------------------------------------

#116Channel Partner Revenue Strategy

SALES STRATEGY & REVENUE GROWTHSaaS companies, agencies, B2B services, marketplaces, software vendors, consultants, manufacturers, distributors, and companies adding partner revenue.

Build a partner sales strategy with partner types, incentives, enablement, rules of engagement, pipeline ownership, and revenue accountability.

Act as a channel revenue strategist. Design a partner sales strategy for [COMPANY NAME] that creates revenue without losing control of customer experience or margin. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Current sales channels: [CHANNELS] Potential partner types: [PARTNERS] Current partner revenue: [PARTNER REVENUE] Direct sales motion: [DIRECT MOTION] Margins: [MARGINS] Partner incentives: [INCENTIVES] Customer experience requirements: [REQUIREMENTS] Partner conflicts: [CONFLICTS] Revenue goal: [GOAL] Build the partner strategy: Partner Type Map Evaluate: - referral partners - reseller partners - implementation partners - affiliate partners - strategic alliances - agencies - consultants - distributors - marketplaces - technology partners - community partners For each partner type include: - why they would partner - customer access - revenue potential - enablement need - margin impact - conflict risk - control risk - best use case Partner Qualification Criteria Define: - audience fit - trust level - customer overlap - delivery capability - sales capability - brand alignment - compliance needs - support burden - minimum performance expectations Partner Economics Recommend: - referral fee - reseller margin - revenue share - implementation fee - bonus structure - co-marketing investment - minimum commitment - payment timing Partner Enablement Kit Create: - pitch deck - one-page offer summary - ICP guide - qualification checklist - objection sheet - demo access - case studies - pricing rules - onboarding guide - co-branded assets Rules of Engagement Define: - lead registration - account ownership - conflict resolution - discount authority - direct sales handoff - support ownership - customer communication - performance review Partner Scorecard Track: - partner-sourced pipeline - partner-influenced pipeline - close rate - deal size - customer quality - margin - support burden - retention - partner activity - enablement adoption Rules: - Do not launch partners without enablement. - Do not create incentives that damage margin. - Do not let partners misrepresent the offer. - Partner revenue must be measured by quality, not only volume. --------------------------------------------------------------------------------

#117Enterprise Account-Based Sales Campaign

SALES STRATEGY & REVENUE GROWTHEnterprise sales teams, B2B SaaS, strategic account teams, agencies, consultants, founders selling large deals, and teams targeting named accounts.

Build an account-based sales strategy for high-value accounts using account research, stakeholder mapping, custom messaging, multi-threading, proof, and deal orchestration.

You are an enterprise account-based sales strategist. Build a custom account-based campaign for [TARGET ACCOUNT] that creates a credible path to a strategic deal. Account Inputs: Selling company: [COMPANY NAME] Target account: [TARGET ACCOUNT] Target account industry: [INDUSTRY] Target account size: [SIZE] Known business initiatives: [INITIATIVES] Known pain signals: [PAIN SIGNALS] Current technology / vendors: [TECH STACK / VENDORS] Potential buyer roles: [BUYER ROLES] Offer: [OFFER] Proof available: [PROOF] Competitors / alternatives: [ALTERNATIVES] Desired deal size: [DEAL SIZE] Timeline: [TIMELINE] Build the ABM sales campaign: Account Thesis Write a hypothesis: [TARGET ACCOUNT] is likely to care about [BUSINESS PROBLEM] because [SIGNALS], and [COMPANY NAME] can create value by [OUTCOME]. Account Research Brief Create: - company overview - strategic priorities - likely pain points - relevant triggers - financial / operational pressures - department-level opportunities - competitor or vendor context - personalization angles - unknowns to research Stakeholder Map Map: - economic buyer - executive sponsor - department leader - end users - technical evaluator - procurement - blocker - champion candidate For each include: - likely priorities - likely objections - message angle - proof needed - outreach channel Multi-Threaded Outreach Sequence Create: - executive email - department leader message - technical evaluator message - champion message - LinkedIn message - voicemail script - follow-up with value asset - internal referral request Value Asset Strategy Recommend a custom asset: - account-specific teardown - benchmark - ROI estimate - risk report - market insight - implementation concept - executive memo Deal Orchestration Plan Create: - first meeting goal - discovery strategy - stakeholder expansion plan - proof plan - mutual action plan - procurement preparation - close path Rules: - Do not use generic personalization. - Do not contact only one stakeholder in a complex account. - Do not pitch features before account relevance is clear. - ABM must feel specific, researched, and business-relevant. --------------------------------------------------------------------------------

#118Sales Compensation & Incentive Alignment Audit

SALES STRATEGY & REVENUE GROWTHCROs, CEOs, founders, RevOps, finance leaders, sales managers, SaaS teams, agencies, B2B companies, and revenue teams changing compensation plans.

Review whether compensation, commissions, quotas, bonuses, and incentives encourage the right sales behaviors and revenue quality.

Act as a sales compensation alignment auditor. Review the sales incentive system for [COMPANY NAME] and identify whether it supports profitable, predictable revenue growth. Inputs: Company: [COMPANY NAME] Sales roles: [SALES ROLES] Current compensation plan: [COMP PLAN] Quota structure: [QUOTAS] Commission rates: [COMMISSION RATES] Bonus rules: [BONUS RULES] Revenue target: [TARGET] Gross margin: [MARGIN] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Retention / churn: [RETENTION / CHURN] Discounting behavior: [DISCOUNTS] Sales behaviors to encourage: [DESIRED BEHAVIORS] Sales behaviors to stop: [BAD BEHAVIORS] Financial constraints: [CONSTRAINTS] Audit the compensation system: Incentive Behavior Map For each incentive, identify: - behavior it rewards - behavior it accidentally encourages - customer impact - margin impact - forecast impact - retention impact - risk Quota Quality Review Evaluate quotas for: - realism - fairness - territory potential - ramp timing - seasonality - market conditions - rep capacity - product mix - strategic priorities Commission Structure Review Analyze whether commissions reward: - new revenue - expansion revenue - retained revenue - gross margin - strategic products - multi-year deals - payment collection - discount discipline - customer quality Misalignment Detector Find risks: - reps closing poor-fit customers - excessive discounting - short-term revenue over retention - channel conflict - sandbagging - weak CRM hygiene - ignoring expansion - avoiding strategic but harder deals - selling low-margin products Compensation Redesign Options Create options: - simple revenue commission - gross-margin commission - tiered accelerators - quota-based commission - team bonus - retention bonus - expansion bonus - strategic product kicker - quality gate commission - clawback rules Recommendation Define: - recommended plan - payout logic - guardrails - examples - transition plan - finance controls - rep communication Rules: - Do not design incentives that reward bad revenue. - Do not overcomplicate compensation beyond what reps can understand. - Do not ignore margin and retention. - Incentives should align seller success with company success. --------------------------------------------------------------------------------

#119Quarterly Revenue War Room

SALES STRATEGY & REVENUE GROWTHCROs, CEOs, founders, sales leaders, RevOps, marketing leaders, customer success leaders, SaaS teams, agencies, and B2B revenue teams.

Create a quarterly revenue planning system that aligns pipeline, forecast, sales capacity, campaigns, segments, deals, risks, and leadership decisions.

You are a quarterly revenue war room facilitator. Build a decision-ready quarterly revenue plan for [COMPANY NAME] that aligns the team around targets, risks, pipeline creation, conversion, and expansion. Inputs: Company: [COMPANY NAME] Quarter: [QUARTER] Revenue target: [TARGET] Previous quarter results: [RESULTS] Current pipeline: [PIPELINE] Forecast: [FORECAST] Sales capacity: [SALES CAPACITY] Marketing campaigns: [CAMPAIGNS] Customer expansion opportunities: [EXPANSION] Churn / retention risks: [RETENTION RISKS] Top deals: [TOP DEALS] Win / loss insights: [INSIGHTS] Budget: [BUDGET] Team constraints: [CONSTRAINTS] Design the war room: Opening Reality Check Answer: - what target must be hit? - what revenue is already secured? - what pipeline exists? - what gap remains? - what is the biggest risk? - what decision is needed now? Revenue Gap Math Calculate or structure: Target revenue minus committed revenue minus realistic forecast minus expansion forecast equals gap to create Then translate the gap into: - pipeline needed - meetings needed - opportunities needed - deals needed - average deal size needed - close rate required Workstream Board Create workstreams: 1. New pipeline creation 2. Existing pipeline conversion 3. Strategic deal support 4. Expansion revenue 5. Retention defense 6. Sales enablement 7. Forecast hygiene 8. Rep productivity For each include: - owner - goal - actions - metric - weekly checkpoint - risk Top Deal Desk Create a table for top deals: - account - value - stage - close likelihood - risk - next buyer action - executive help needed - close plan Campaign Plan Recommend campaigns for: - target accounts - past lost deals - referral asks - current customer expansion - event follow-up - partner pipeline - inbound conversion Weekly Operating Rhythm Create: - Monday pipeline push - Tuesday deal strategy - Wednesday prospecting block - Thursday forecast review - Friday learning review Quarter-End Rules Define: - what not to discount - what can be accelerated - what should not be forced - what to push honestly - what customer trust rules apply Rules: - Do not close the quarter by creating bad-fit revenue. - Do not rely on a single pipeline source. - Do not let forecast optimism replace pipeline math. - Every revenue gap must have an owner and action plan. --------------------------------------------------------------------------------

#120Full Sales Strategy & Revenue Growth Audit

SALES STRATEGY & REVENUE GROWTHFounders, CEOs, CROs, sales leaders, RevOps teams, consultants, agencies, SaaS companies, service businesses, B2B teams, and leadership teams doing a sales strategy reset.

Audit the full sales and revenue growth system across targeting, pipeline, sales motion, qualification, conversion, forecasting, enablement, expansion, team cadence, and revenue quality.

Act as an independent sales strategy and revenue growth auditor. Review the full revenue system for [COMPANY NAME] and identify the highest-leverage improvements. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Product / service: [PRODUCT / SERVICE] Target customers: [TARGET CUSTOMERS] Revenue target: [REVENUE TARGET] Current revenue: [CURRENT REVENUE] Sales team structure: [TEAM STRUCTURE] Sales process: [SALES PROCESS] Sales motion: [SALES MOTION] Pipeline data: [PIPELINE DATA] Conversion rates: [CONVERSION RATES] Win rate: [WIN RATE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Lead sources: [LEAD SOURCES] Forecast accuracy: [FORECAST ACCURACY] Lost deal reasons: [LOST DEAL REASONS] Sales assets: [SALES ASSETS] CRM data quality: [CRM QUALITY] Retention / expansion data: [RETENTION / EXPANSION] Leadership concerns: [CONCERNS] Audit the sales system across 16 dimensions: 1. Target customer clarity 2. Account / segment prioritization 3. Sales motion fit 4. Pipeline generation quality 5. Lead qualification discipline 6. Discovery quality 7. Objection handling 8. Proposal and close process 9. Deal velocity 10. Win rate 11. Average deal size 12. Forecast reliability 13. Sales enablement 14. CRM hygiene 15. Retention and expansion revenue 16. Sales management cadence For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - revenue risk - customer risk - operational risk - recommended fix - confidence level Then synthesize: A. Top 5 revenue constraints Rank by: - revenue impact - urgency - ease of improvement - strategic importance - confidence B. Root cause analysis Identify whether the main issue is: - wrong target customer - weak pipeline generation - poor lead quality - weak qualification - unclear value proposition - weak discovery - pricing or packaging friction - weak proof - poor follow-up - unreliable forecast - lack of enablement - rep capacity issue - sales motion mismatch - retention or expansion gap - CRM data problem C. Revenue growth strategy Create: - target customer recommendation - sales motion recommendation - pipeline generation plan - qualification system - conversion improvement plan - enablement asset plan - forecast improvement plan - expansion revenue plan - team cadence - KPI dashboard D. 30/60/90-day sales improvement plan Create a practical plan with: - actions - owners - metrics - sales process changes - campaign launches - training - asset creation - forecast reviews - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard revenue truth - the biggest sales constraint - the fastest growth lever - the biggest forecast risk - the next leadership decision - the data needed before scaling Rules: - Do not invent sales data. - Do not recommend more leads before checking conversion and fit. - Do not judge sales performance only by activity volume. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on revenue quality, repeatability, customer fit, and predictable growth.

#121Customer Journey Service Blueprint

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCustomer experience leaders, founders, COOs, support teams, service businesses, SaaS teams, ecommerce brands, agencies, hospitality teams, retail teams, and companies improving end-to-end customer experience.

Map the full customer journey and connect every customer-facing moment to the internal people, processes, tools, standards, and service gaps behind it.

You are a senior customer experience service designer. Build a complete service blueprint for [COMPANY NAME] that shows what customers experience, what the team does behind the scenes, where friction appears, and what must be redesigned. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Customer type: [CUSTOMER TYPE] Product / service: [PRODUCT / SERVICE] Customer journey stages: [JOURNEY STAGES] Main customer goals: [CUSTOMER GOALS] Current complaints: [COMPLAINTS] Support data: [SUPPORT DATA] Reviews / testimonials: [REVIEWS] Internal teams involved: [TEAMS] Tools / systems: [TOOLS] Service promises: [PROMISES] Known pain points: [PAIN POINTS] Create the service blueprint: 1. Journey stage map Map the customer journey across: - awareness - first contact - evaluation - purchase / signup - onboarding - first value - active usage / delivery - support - billing / renewal / repeat purchase - expansion / referral - cancellation / churn / return For each stage include: - customer goal - customer emotion - customer question - visible touchpoint - invisible backstage process - responsible team - tool or system - service standard - failure point - customer risk - business risk 2. Frontstage experience Identify everything the customer sees: - website - ads - sales conversations - checkout - welcome messages - onboarding - emails - product experience - service delivery - support conversations - invoices - renewal messages - cancellation flows Evaluate clarity, trust, speed, ease, empathy, and consistency. 3. Backstage operations Identify what must happen internally for the experience to work: - ownership - handoffs - data entry - approvals - fulfillment - quality checks - escalation - customer notes - billing - feedback capture - follow-up 4. Evidence and artifacts List the physical or digital evidence customers receive: - confirmation messages - receipts - status updates - help articles - contracts - reports - deliverables - tracking pages - dashboards - case summaries Explain whether each artifact builds trust or creates confusion. 5. Friction diagnosis For every friction point, classify it as: - unclear expectation - slow response - poor handoff - missing communication - bad tool visibility - policy problem - training gap - quality issue - pricing / billing confusion - emotional trust break - operational bottleneck 6. Future-state blueprint Redesign the journey with: - clearer expectations - fewer handoffs - better status visibility - stronger onboarding - proactive communication - faster support - better recovery - stronger trust signals 7. Implementation plan Create a 30/60/90-day plan with: - touchpoints to redesign - SOPs to create - templates to write - metrics to track - owners to assign - service risks to monitor Rules: - Do not design the journey from the company's perspective only. - Do not ignore backstage operations. - Do not treat complaints as isolated if they repeat. - Use [NEEDS DATA] where customer evidence is missing. Done when the team can see the full customer experience and knows exactly which service systems to improve first. --------------------------------------------------------------------------------

#122Voice of Customer Intelligence Engine

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCX teams, support leaders, product marketers, founders, customer success teams, ecommerce brands, SaaS teams, agencies, and companies that want customer feedback turned into action.

Turn messy reviews, surveys, support tickets, calls, chats, complaints, and customer interviews into clear themes, language, expectations, risks, and service improvements.

Act as a Voice of Customer intelligence analyst. Analyze the customer feedback below and turn it into a structured insight system that improves customer experience, service quality, messaging, product decisions, and retention. Customer feedback sources: Customer reviews: [REVIEWS] Support tickets: [SUPPORT TICKETS] Chat transcripts: [CHATS] Call notes: [CALL NOTES] Survey responses: [SURVEYS] NPS / CSAT comments: [NPS / CSAT] Cancellation reasons: [CANCELLATION REASONS] Social comments: [SOCIAL COMMENTS] Sales objections: [SALES OBJECTIONS] Customer interview notes: [INTERVIEWS] Time period: [TIME PERIOD] Customer segments: [SEGMENTS] Run the Voice of Customer engine: Pass 1 - Theme extraction Identify recurring themes across: - customer goals - pain points - confusion - unmet expectations - emotional frustration - delight moments - service gaps - product gaps - communication issues - price / value concerns - trust signals - reasons for loyalty - reasons for churn For each theme include frequency, example language, customer segment, severity, and business impact. Pass 2 - Customer language bank Extract exact customer phrases for: - problems - desired outcomes - objections - emotional states - expectations - praise - complaints - comparison language - switching reasons Keep exact wording in quotation marks. Do not invent quotes. Pass 3 - Expectation gap analysis Compare what customers expected vs what they experienced. Create: - promised expectation - actual experience - source of mismatch - customer reaction - fix required - owner Pass 4 - Service issue classification Classify feedback into: - product issue - process issue - communication issue - training issue - policy issue - pricing issue - delivery issue - support issue - onboarding issue - expectation-setting issue Pass 5 - Insight priority matrix Rank insights by: - frequency - severity - revenue impact - churn risk - customer trust risk - ease of fixing - strategic importance Pass 6 - Action conversion For each top insight, create: - recommended action - responsible team - service change - communication change - metric to monitor - expected customer impact - confidence level Pass 7 - Executive summary Write a concise summary with: - what customers love - what customers misunderstand - what customers complain about most - what creates churn risk - what creates loyalty - what should be fixed first Rules: - Do not summarize feedback so broadly that it loses usefulness. - Do not treat loud feedback as representative unless frequency supports it. - Do not invent customer quotes. - Mark weak patterns as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#123Service Recovery Playbook

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport teams, customer success teams, ecommerce brands, service businesses, restaurants, hospitality, SaaS teams, operations teams, and any company that needs better complaint recovery.

Create a practical system for responding when something goes wrong, including apology logic, ownership, compensation, escalation, communication, and prevention.

You are a service recovery strategist. Build a service recovery playbook for [COMPANY NAME] so the team can handle customer issues quickly, consistently, and humanely while protecting trust. Inputs: Company: [COMPANY NAME] Customer type: [CUSTOMER TYPE] Product / service: [PRODUCT / SERVICE] Common service failures: [FAILURES] Current complaint process: [CURRENT PROCESS] Current escalation process: [ESCALATION] Compensation / refund rules: [COMPENSATION RULES] Service promise: [PROMISE] Support channels: [CHANNELS] Team roles: [ROLES] High-risk situations: [HIGH-RISK SITUATIONS] Brand voice: [BRAND VOICE] Build the service recovery playbook: A. Recovery philosophy Define: - what the company believes about customer complaints - what must always be protected - when speed matters most - when empathy matters most - when policy matters most - what the team must never do B. Failure severity levels Create 5 levels: Level 1 - minor friction Level 2 - inconvenience Level 3 - missed promise Level 4 - trust-damaging failure Level 5 - crisis / public risk For each level define: - examples - response time - owner - escalation path - customer communication standard - compensation options - documentation requirement - leadership notification rule C. Recovery response sequence Create a step-by-step response flow: 1. Acknowledge 2. Own the issue 3. Clarify facts 4. Apologize appropriately 5. Explain what happens next 6. Fix or compensate 7. Confirm resolution 8. Capture root cause 9. Prevent recurrence D. Apology logic Create apology frameworks for: - company error - unclear responsibility - delayed delivery - product issue - billing mistake - communication failure - customer misunderstanding - third-party vendor issue E. Compensation decision tree Define when to offer: - no compensation - discount - credit - refund - replacement - expedited service - free add-on - manager call - custom resolution F. Templates Write templates for: - first response - delayed update - apology - compensation offer - escalation message - final resolution - follow-up after resolution - public review response G. Prevention loop For every recovered issue, capture: - root cause - process owner - SOP update - training update - dashboard metric - prevention action Rules: - Do not make apologies sound legalistic or robotic. - Do not overcompensate without rules. - Do not hide behind policy when the company broke trust. - Recovery must solve the issue and reduce future repeat failures. --------------------------------------------------------------------------------

#124Support Triage & Escalation System

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport leaders, customer success teams, SaaS companies, ecommerce brands, marketplaces, operations teams, service businesses, and teams with chaotic support queues.

Design a support intake, triage, prioritization, routing, escalation, and resolution system that improves speed, consistency, and customer trust.

Act as a support operations architect. Build a support triage and escalation system for [COMPANY NAME] that helps the team decide what to answer first, who owns each issue, and when to escalate. Inputs: Company: [COMPANY NAME] Support channels: [CHANNELS] Ticket volume: [TICKET VOLUME] Customer segments: [SEGMENTS] Common issue types: [ISSUE TYPES] Current response times: [RESPONSE TIMES] Current resolution times: [RESOLUTION TIMES] Support team roles: [ROLES] Tools used: [TOOLS] SLA / service promise: [SLA] Escalation rules: [CURRENT ESCALATION] Known problems: [PROBLEMS] Create the system: 1. Intake architecture Define how issues enter the system through: - email - chat - phone - social - help center - in-app form - sales handoff - customer success handoff - review platforms - internal team escalation For each channel define required information, auto-reply, owner, and response standard. 2. Ticket classification model Classify tickets by: - issue type - urgency - customer value / tier - emotional severity - financial risk - operational dependency - technical complexity - compliance risk - public reputation risk - churn risk 3. Priority formula Create a priority score: Priority = Urgency + Customer Impact + Business Risk + Churn Risk + SLA Risk + Public Risk - Workaround Availability Define scoring from 1 to 5 for each variable. 4. Routing map Create routing rules: - billing - technical issue - delivery issue - refund / return - complaint - product question - account issue - onboarding issue - sales-related question - legal / compliance - VIP customer - urgent operational issue 5. Escalation ladder Define escalation levels: - frontline support - senior support - specialist - manager - operations - product / engineering - finance - leadership For each level include entry criteria, response time, required context, and return path. 6. Resolution standards Define what counts as resolved: - customer confirms - issue fixed - workaround accepted - refund processed - next step scheduled - internal ticket closed - root cause logged 7. Queue health dashboard Track: - first response time - resolution time - backlog - aging tickets - reopen rate - escalation rate - SLA breaches - CSAT - complaint severity - top issue categories Rules: - Do not let urgent emotional tickets hide high-risk business issues. - Do not escalate without context. - Do not close tickets without a clear resolution standard. - The system must be usable by a real support team during a busy day. --------------------------------------------------------------------------------

#125Customer Onboarding Experience Designer

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSaaS teams, customer success teams, service businesses, agencies, ecommerce brands, membership businesses, marketplaces, and companies with activation or early churn problems.

Build an onboarding system that gets customers to first value faster with clear steps, expectations, education, milestones, support, and success tracking.

You are a customer onboarding experience designer. Create an onboarding system for [COMPANY NAME] that reduces confusion, accelerates first value, and increases retention. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Customer type: [CUSTOMER TYPE] Customer goal: [CUSTOMER GOAL] Current onboarding process: [CURRENT PROCESS] Time to first value: [TIME TO FIRST VALUE] Activation event: [ACTIVATION EVENT] Common customer confusion: [CONFUSION] Support questions during onboarding: [SUPPORT QUESTIONS] Current onboarding assets: [ASSETS] Team roles: [ROLES] Tools used: [TOOLS] Retention / churn data: [RETENTION DATA] Design the onboarding system: Onboarding Outcome Definition Define: - what "successfully onboarded" means - first value moment - activation milestone - minimum setup required - customer confidence signal - internal completion signal Customer Starting Point Segment customers by: - experience level - urgency - use case - company size - plan / package - technical ability - implementation complexity - support needs Onboarding Journey Create stages: 1. Welcome 2. Expectation setting 3. Setup / intake 4. Guided first action 5. First value 6. Education 7. Habit formation 8. Success check 9. Expansion or next-step path For each stage include: - customer question - customer emotion - required action - company action - message - asset - owner - success metric - risk Milestone System Create milestones with: - milestone name - why it matters - customer task - internal task - completion criteria - automation opportunity - failure signal - intervention Communication Sequence Write: - welcome email - setup reminder - first value encouragement - check-in message - stuck-user message - milestone celebration - support invitation - success review invitation Onboarding Dashboard Track: - activation rate - time to first value - completion rate - stuck points - support tickets - onboarding CSAT - early churn - feature adoption - milestone completion Rules: - Do not overload new customers with everything at once. - Do not assume customers understand what to do next. - Do not make onboarding only educational; it must create progress. - Every onboarding step must move the customer closer to value. --------------------------------------------------------------------------------

#126Complaint Root Cause Loop

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport leaders, CX teams, operations managers, customer success teams, service businesses, hospitality, ecommerce, SaaS, retail, and companies receiving repeated complaints.

Convert customer complaints into root cause analysis, ownership, prevention actions, SOP updates, training improvements, and measurable service fixes.

Act as a complaint root cause facilitator. Analyze the complaints below and build a system that prevents the same problems from repeating. Complaint data: Customer complaints: [COMPLAINTS] Complaint channels: [CHANNELS] Time period: [TIME PERIOD] Customer segments: [SEGMENTS] Products / services affected: [PRODUCTS / SERVICES] Current response process: [RESPONSE PROCESS] Internal notes: [INTERNAL NOTES] Resolution outcomes: [OUTCOMES] Relevant SOPs: [SOPS] Teams involved: [TEAMS] Known operational issues: [OPERATIONAL ISSUES] Run the complaint loop: Step 1 - Complaint normalization Turn messy complaints into clean issue statements. For each complaint include: - customer wording - normalized issue - customer emotion - stage of journey - product / service area - severity - repeat or one-off - evidence Step 2 - Pattern clustering Cluster complaints into themes: - expectation mismatch - delay - poor communication - quality failure - billing / pricing - support experience - onboarding confusion - product limitation - delivery / logistics - policy friction - employee behavior - tool or system failure Step 3 - Root cause drilldown For each theme, answer: - what happened? - where did it happen? - why did the customer notice? - why did the process allow it? - why was it not caught earlier? - what system condition created it? - what evidence confirms this? - what evidence is missing? Step 4 - Ownership map Assign: - customer response owner - root cause owner - process owner - SOP owner - training owner - metric owner - leadership reviewer, if needed Step 5 - Prevention action card For each top complaint theme create: - problem - root cause hypothesis - immediate customer fix - process fix - SOP update - training update - communication update - dashboard metric - deadline - owner Step 6 - Closed-loop follow-up Define how the company will: - inform customers - close tickets - review repeat issues - verify fixes worked - report improvements to leadership Rules: - Do not treat repeated complaints as customer noise. - Do not solve only the visible symptom. - Do not assign prevention actions without owners. - Mark uncertain causes as [NEEDS INVESTIGATION]. --------------------------------------------------------------------------------

#127CX Metrics Dashboard Builder

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCX leaders, support teams, customer success teams, founders, SaaS teams, ecommerce brands, agencies, service businesses, and leadership teams that need trustworthy CX reporting.

Create a customer experience dashboard that connects satisfaction, effort, response speed, resolution quality, complaints, retention, revenue, and operational action.

You are a customer experience analytics designer. Build a CX dashboard for [COMPANY NAME] that shows not only what customers feel, but what the business should do next. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Customer segments: [SEGMENTS] Customer journey: [JOURNEY] Support channels: [CHANNELS] Current CX metrics: [CURRENT METRICS] Available data sources: [DATA SOURCES] Service promises / SLAs: [SLAS] Retention data: [RETENTION DATA] Revenue data: [REVENUE DATA] Complaint data: [COMPLAINT DATA] Leadership questions: [QUESTIONS] Reporting cadence: [CADENCE] Build the dashboard: Dashboard Purpose Define: - audience - decisions it supports - questions it answers - actions it should trigger - what it should not be used for Metric Families Create metrics across: Customer Sentiment: - CSAT - NPS - customer review rating - sentiment themes - complaint severity Customer Effort: - customer effort score - number of contacts per issue - repeat contact rate - self-service success rate - onboarding friction Speed: - first response time - resolution time - wait time - SLA achievement - backlog age Quality: - first-contact resolution - reopen rate - escalation rate - defect rate - service recovery satisfaction Retention: - churn rate - renewal rate - repeat purchase - expansion - cancellation reason themes Business Impact: - revenue at risk - refunds / credits - cost per ticket - support cost by segment - complaint-driven churn Metric Definition Cards For each metric include: - definition - formula - data source - owner - update frequency - target - warning threshold - bad threshold - action triggered Insight Panels Create dashboard panels: - executive snapshot - journey stage health - support performance - complaint themes - retention risk - service recovery - customer language - decisions needed Review Rhythm Create: - weekly support review - monthly CX review - quarterly journey review Rules: - Do not use NPS as the only CX metric. - Do not track metrics nobody owns. - Do not show customer sentiment without operational causes. - Every metric must connect to an action or decision. --------------------------------------------------------------------------------

#128Omnichannel Service Standards Architect

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport leaders, customer service teams, CX teams, ecommerce brands, SaaS teams, retail, hospitality, marketplaces, and service businesses with multiple customer contact channels.

Create consistent service standards across email, chat, phone, social, in-app, help center, and in-person channels without forcing every channel to sound identical.

Act as an omnichannel service standards architect. Design service standards for [COMPANY NAME] so customers receive consistent, trustworthy help across every channel. Inputs: Company: [COMPANY NAME] Customer types: [CUSTOMER TYPES] Support channels: [CHANNELS] Brand voice: [BRAND VOICE] Service promise: [SERVICE PROMISE] Current channel problems: [PROBLEMS] Support team roles: [ROLES] Ticket volume by channel: [VOLUME] Response time data: [RESPONSE TIMES] Tools used: [TOOLS] Escalation paths: [ESCALATION] Compliance / policy constraints: [CONSTRAINTS] Create the omnichannel standards: Section A - Universal service principles Write 7 service principles that apply everywhere. For each include: - principle - customer benefit - employee behavior - example - what to avoid Section B - Channel standards For each channel define: Email: - best use - response time - tone - structure - proof / links - escalation rule - closing standard Chat: - best use - response time - tone - brevity rule - transfer rule - offline fallback - closing standard Phone: - best use - greeting - listening standard - documentation rule - escalation rule - follow-up requirement Social: - best use - public vs private rules - brand voice - risk handling - escalation rule - review response standard In-app / portal: - best use - status visibility - notification rules - self-service guidance Help center: - article standards - update cadence - search language - escalation CTA In-person, if relevant: - greeting - body language - wait-time communication - complaint handling - handoff process Section C - Consistency rules Define what must stay the same across channels: - facts - policies - expectations - next steps - ownership - empathy - service promises Define what may change: - length - tone intensity - format - CTA style - level of detail Section D - Channel switching rules Define how to move a customer from one channel to another without making them repeat themselves. Section E - Quality assurance checklist Create a review checklist for channel consistency. Rules: - Do not copy-paste the same response style into every channel. - Do not let channel switching reset customer context. - Do not let social support make promises the operations team cannot keep. - Consistency means reliable experience, not identical wording. --------------------------------------------------------------------------------

#129Knowledge Base & Self-Service System

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport teams, SaaS companies, ecommerce brands, marketplaces, customer success teams, product teams, service businesses, and companies with repeated questions.

Build a self-service system that reduces repetitive support, improves customer confidence, and makes help articles easier to find, understand, and act on.

You are a self-service knowledge base strategist. Build or improve a knowledge base for [COMPANY NAME] that helps customers solve common issues without contacting support. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Customer types: [CUSTOMER TYPES] Top support questions: [SUPPORT QUESTIONS] Support ticket categories: [TICKET CATEGORIES] Current knowledge base: [CURRENT KB] Search data: [SEARCH DATA] Product complexity: [COMPLEXITY] Customer language: [CUSTOMER LANGUAGE] Support team notes: [SUPPORT NOTES] Brand voice: [BRAND VOICE] Tools / platform: [TOOLS] Build the self-service system: 1. Article opportunity audit Identify which support questions should become: - help article - FAQ - troubleshooting guide - setup guide - video walkthrough - checklist - decision tree - policy page - contact support form - not self-service For each include expected support reduction and customer value. 2. Knowledge base structure Create categories such as: - getting started - account setup - billing - product usage - troubleshooting - integrations - orders / delivery - returns / refunds - policies - best practices - contact support Adapt categories to the business. 3. Article template Create a standard article format: - title in customer language - who this is for - short answer - before you begin - steps - screenshots / visuals needed - common mistakes - what to do if this does not work - related articles - escalation CTA 4. Search and findability Recommend: - titles customers would search - keywords - synonyms - tags - article linking - in-product placement - support macro links - homepage layout 5. Article quality rules Define standards for: - clarity - accuracy - length - screenshots - step order - tone - policy accuracy - update cadence 6. Self-service success metrics Track: - article views - search success - contact deflection - article helpfulness - repeat ticket reduction - escalation from article - outdated article rate 7. First 30 articles Create a prioritized list of the first 30 knowledge base articles to write. Rules: - Do not write articles in internal company language. - Do not hide support contact options when the issue is urgent. - Do not create self-service for issues customers cannot solve themselves. - Every article must reduce effort or increase confidence. --------------------------------------------------------------------------------

#130Customer Feedback-to-Action Pipeline

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCX teams, product teams, support leaders, customer success teams, founders, SaaS teams, ecommerce brands, agencies, and companies drowning in unorganized feedback.

Create a system that captures feedback, categorizes it, prioritizes it, routes it to owners, turns it into decisions, and closes the loop with customers.

Act as a feedback operations designer. Build a customer feedback-to-action pipeline for [COMPANY NAME] so customer input becomes better decisions instead of scattered notes. Inputs: Company: [COMPANY NAME] Feedback sources: [SOURCES] Current feedback process: [CURRENT PROCESS] Teams receiving feedback: [TEAMS] Tools used: [TOOLS] Customer segments: [SEGMENTS] Feedback volume: [VOLUME] Product / service areas: [AREAS] Current problems: [PROBLEMS] Decision makers: [DECISION MAKERS] Communication channels: [CHANNELS] Design the feedback pipeline: Pipeline Stage 1 - Capture Define how feedback is captured from: - support tickets - surveys - reviews - calls - customer success notes - sales calls - social media - user interviews - cancellation flows - community posts - employee observations For each source define required fields and owner. Pipeline Stage 2 - Normalize Create a feedback record format: - customer segment - source - date - exact quote - issue type - emotion - severity - frequency - affected product / service - revenue impact - churn risk - evidence link - owner Pipeline Stage 3 - Categorize Create categories: - bug / defect - service failure - feature request - confusion - expectation mismatch - pricing issue - billing issue - onboarding issue - policy friction - positive feedback - competitor comparison - churn reason Pipeline Stage 4 - Prioritize Rank feedback by: - customer impact - frequency - revenue impact - churn risk - strategic importance - effort to solve - urgency - confidence Pipeline Stage 5 - Route Define routing rules to: - product - operations - support - customer success - marketing - sales - finance - leadership Pipeline Stage 6 - Decide Create a decision review cadence: - weekly urgent feedback review - monthly theme review - quarterly roadmap / service review Pipeline Stage 7 - Close the loop Define how to update: - the customer - the support team - the roadmap - help center - internal SOPs - public release notes Rules: - Do not collect feedback that nobody reviews. - Do not treat every feature request as product strategy. - Do not lose exact customer language. - Feedback must become a decision, a fix, a message, or a documented reason for no action. --------------------------------------------------------------------------------

#131SLA & Service Promise Framework

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport teams, customer success teams, B2B services, SaaS teams, agencies, ecommerce brands, operations teams, logistics teams, and businesses with unclear service expectations.

Define clear service promises, response standards, resolution targets, escalation thresholds, exceptions, and customer communication rules.

You are a service promise and SLA designer. Create a practical SLA framework for [COMPANY NAME] that sets clear expectations for customers and clear operating rules for the team. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Customer segments / tiers: [SEGMENTS / TIERS] Support channels: [CHANNELS] Current response times: [RESPONSE TIMES] Current resolution times: [RESOLUTION TIMES] Service commitments: [COMMITMENTS] Customer expectations: [EXPECTATIONS] Operational capacity: [CAPACITY] Issue types: [ISSUE TYPES] Escalation process: [ESCALATION] Business risks: [RISKS] Competitor standards: [COMPETITOR STANDARDS] Build the framework: 1. Service Promise Write the external service promise in plain customer language. Include: - what customers can expect - what the company commits to - what the company does not promise - how customers will be updated - where to go for help 2. Internal SLA Matrix Create a matrix by issue type and customer tier: - issue category - severity - first response target - resolution target - update frequency - owner - escalation threshold - exception rule 3. Severity Definitions Define severity levels: - informational - low - medium - high - urgent - critical For each include customer impact, business impact, examples, and escalation rules. 4. Channel Standards Define response expectations for: - email - chat - phone - social - in-app - help center contact form - account manager / customer success 5. Exception Logic Define what happens when: - customer information is missing - vendor dependency delays resolution - issue requires engineering - customer is unresponsive - customer is high-risk - public reputation risk exists - SLA is breached 6. SLA Breach Communication Write templates for: - delay update - missed SLA apology - revised timeline - escalation notice - resolution confirmation 7. Governance Define: - SLA owner - reporting cadence - breach review - staffing review - continuous improvement loop Rules: - Do not promise response times the team cannot meet. - Do not hide SLA breaches internally. - Do not create one SLA for every customer if segments need different service levels. - A good SLA protects customer trust and team focus. --------------------------------------------------------------------------------

#132Frontline Service Coaching System

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport managers, service leaders, call center teams, retail managers, hospitality teams, customer success leaders, agencies, and anyone managing customer-facing teams.

Build a coaching system that helps support and service employees improve empathy, clarity, accuracy, speed, judgment, and customer trust.

Act as a frontline service coaching lead. Build a coaching system for [TEAM NAME] that improves customer conversations without turning employees into script readers. Inputs: Company: [COMPANY NAME] Team: [TEAM NAME] Customer channels: [CHANNELS] Service standards: [STANDARDS] Common customer issues: [ISSUES] Current scripts / macros: [SCRIPTS] Current quality problems: [QUALITY PROBLEMS] Customer feedback: [FEEDBACK] Employee skill gaps: [SKILL GAPS] Team size: [TEAM SIZE] Manager capacity: [MANAGER CAPACITY] Brand voice: [BRAND VOICE] Create the coaching system: Coaching Skill Map Define what good looks like for: - listening - empathy - issue diagnosis - clarity - accuracy - speed - ownership - expectation setting - policy explanation - de-escalation - written tone - phone tone - follow-through - judgment For each skill include observable behaviors. Conversation Review Scorecard Create a 1-5 scoring system for: - understood customer issue - used accurate information - explained next step - showed ownership - matched brand voice - resolved or routed correctly - avoided unnecessary friction - documented properly Coaching Rituals Design: - weekly conversation review - monthly calibration session - new hire shadowing - difficult case review - peer coaching - service recovery review - macro / script improvement review Coaching Scripts for Managers Write coaching prompts for: - too robotic - too defensive - too slow - inaccurate answer - weak ownership - poor documentation - over-refunding - under-escalating - strong empathy but weak resolution - strong speed but weak clarity Practice Drills Create drills for: - angry customer - confused customer - billing dispute - delayed order - technical issue - policy exception - VIP customer - public complaint Measurement Track: - CSAT - QA score - first response time - resolution quality - reopen rate - escalation quality - customer sentiment - coaching completion - improvement by agent Rules: - Do not coach only from metrics. - Do not make employees sound identical. - Do not punish honest escalations. - Coaching should improve judgment, not only script compliance. --------------------------------------------------------------------------------

#133Customer Effort Reduction Audit

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCX leaders, support teams, SaaS companies, ecommerce brands, service businesses, product teams, operations teams, and companies with customer frustration or high support volume.

Identify and remove unnecessary customer effort across buying, onboarding, usage, support, billing, returns, renewals, and cancellation.

You are a customer effort reduction auditor. Analyze [COMPANY NAME]'s customer experience and find every place customers must work too hard to get value, get help, or complete an action. Inputs: Company: [COMPANY NAME] Customer journey: [JOURNEY] Product / service: [PRODUCT / SERVICE] Customer tasks: [TASKS] Support tickets: [SUPPORT TICKETS] Customer complaints: [COMPLAINTS] Website / app flows: [FLOWS] Onboarding process: [ONBOARDING] Billing / payment process: [BILLING] Return / cancellation process: [RETURNS / CANCELLATION] Tools / systems: [TOOLS] Known friction: [FRICTION] Audit customer effort: Effort Map For each customer task, identify: - task - customer goal - steps required - channels required - information required - wait time - repeated information - confusion points - emotional load - failure rate - support dependency - effort score from 1 to 10 Friction Types Classify effort as: - too many steps - unclear instructions - hidden information - repeated data entry - slow response - channel switching - policy friction - confusing language - poor search / navigation - missing status updates - unnecessary approval - broken self-service - unclear ownership Moment of High Effort Identify the top 10 high-effort moments and explain: - why it happens - customer impact - business impact - likely root cause - owner - fix Effort Reduction Moves Recommend: - remove step - simplify form - rewrite instructions - add status update - create self-service article - automate confirmation - reduce handoff - pre-fill information - improve search - change policy - create proactive communication - redesign cancellation / return flow Customer Effort Dashboard Define metrics: - customer effort score - contacts per resolution - self-service success - repeat contact rate - abandoned flow rate - time to complete task - complaint rate - refund / cancellation reasons Rules: - Do not optimize internal convenience at the customer's expense. - Do not assume customers understand company processes. - Do not add education when the better fix is removing friction. - Customer effort reduction should improve both experience and operational efficiency. --------------------------------------------------------------------------------

#134Proactive Support & Issue Prevention System

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSaaS, ecommerce, logistics, service businesses, subscriptions, customer success teams, support teams, agencies, hospitality, and companies that want fewer reactive support issues.

Build a proactive service system that detects risks, warns customers, prevents tickets, and communicates before problems become complaints.

Act as a proactive support strategist. Build a system for [COMPANY NAME] that identifies issues before customers complain and communicates early enough to preserve trust. Inputs: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Common support issues: [ISSUES] Operational risks: [RISKS] Customer journey: [JOURNEY] Data available: [DATA] Customer segments: [SEGMENTS] Support channels: [CHANNELS] Current proactive messages: [CURRENT MESSAGES] Service promises: [PROMISES] Tools / automations: [TOOLS] Team capacity: [CAPACITY] Design the proactive support system: Risk Signal Library Identify signals that predict: - delayed delivery - failed payment - onboarding stall - low product usage - abandoned setup - upcoming renewal risk - inventory / availability issue - technical incident - billing confusion - customer dissatisfaction - repeat support contact - service quality issue For each signal include: - data source - threshold - owner - customer risk - action triggered Proactive Communication Map For each risk, define: - message timing - channel - message owner - customer-facing explanation - next step - fallback support option - internal task Prevention Playbooks Create playbooks for: 1. Customer is stuck during onboarding 2. Order / delivery is delayed 3. Payment fails 4. Usage drops 5. Renewal risk appears 6. Known product issue affects customers 7. Customer submitted repeated tickets 8. Service team may miss a promise Each playbook must include: - detection signal - internal action - customer message - escalation rule - success metric Automation Opportunities Recommend which actions should be: - fully automated - AI-assisted - templated - human-owned - manager-reviewed Trust Protection Rules Define: - when to tell customers early - when not to over-alert - how much detail to share - how to admit uncertainty - how to follow up Metrics Track: - prevented tickets - proactive message engagement - issue escalation rate - complaint reduction - CSAT after proactive contact - SLA breach reduction - churn risk reduction Rules: - Do not wait until customers ask for an update when the company already knows there is risk. - Do not send vague alerts that create more confusion. - Do not automate sensitive messages without human review. - Proactive support must reduce anxiety, not increase it. --------------------------------------------------------------------------------

#135Customer Segmentation Service Rules

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCustomer success teams, support leaders, SaaS companies, B2B services, ecommerce brands, marketplaces, agencies, and companies serving multiple customer types.

Define differentiated service levels, communication rules, support paths, escalation thresholds, and success motions by customer segment or tier.

You are a customer segmentation service architect. Create service rules for [COMPANY NAME] so different customer segments receive the right level of support without creating unfairness or operational chaos. Inputs: Company: [COMPANY NAME] Customer segments: [SEGMENTS] Customer tiers / plans: [TIERS] Revenue by segment: [REVENUE] Support volume by segment: [SUPPORT VOLUME] Customer value / LTV: [LTV] Cost to serve: [COST TO SERVE] Churn risk: [CHURN RISK] Strategic accounts: [STRATEGIC ACCOUNTS] Current service levels: [CURRENT SERVICE] Team capacity: [CAPACITY] Brand promise: [BRAND PROMISE] Build the segmentation service system: Segment Profile Cards For each segment create: - segment name - customer goals - common issues - expected service level - revenue importance - support burden - retention risk - expansion potential - preferred channels - tone needs - self-service suitability Service Tier Matrix Create service rules by segment / tier: - available channels - first response target - resolution target - onboarding support - account management - escalation access - proactive check-ins - education resources - reporting - renewal support Differentiation Logic Explain: - what all customers receive - what premium customers receive - what strategic accounts receive - what self-service customers receive - what should never vary by tier Cost-to-Serve Guardrails Identify where service levels may become unprofitable: - excessive custom support - high-contact low-value customers - unmanaged VIP expectations - free support for paid consulting needs - repeated training issues - policy exceptions Escalation Rules Define when a customer gets: - frontline support - senior specialist - manager support - customer success manager - executive sponsor - custom recovery plan Customer Communication Write clear language explaining service levels without making lower tiers feel ignored. Metrics Track by segment: - CSAT - support volume - cost to serve - response time - resolution time - churn - expansion - complaints - self-service success Rules: - Do not create hidden promises the team cannot deliver. - Do not treat every customer identically if their needs and economics differ. - Do not make lower-tier customers feel abandoned. - Service segmentation must be transparent, fair, and financially sustainable. --------------------------------------------------------------------------------

#136Customer Communication Template Library

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSupport teams, customer success teams, ecommerce brands, service businesses, SaaS teams, operations teams, hospitality, retail, and companies building service consistency.

Create a reusable library of customer-facing templates for common service situations while keeping the tone human, clear, specific, and brand-aligned.

Act as a customer communication editor. Build a template library for [COMPANY NAME] that helps the team respond faster without sounding robotic or careless. Inputs: Company: [COMPANY NAME] Brand voice: [BRAND VOICE] Customer type: [CUSTOMER TYPE] Support channels: [CHANNELS] Common customer situations: [SITUATIONS] Policies: [POLICIES] Service promises: [PROMISES] Escalation rules: [ESCALATION] Current templates: [CURRENT TEMPLATES] Tone problems: [TONE PROBLEMS] Words to avoid: [WORDS TO AVOID] Create the template library: Template Principles Define: - how the brand sounds in service messages - what every response must include - when to personalize - when to be brief - when to add detail - when to escalate - what never to say Template Format For every template include: - use case - customer emotion - channel - template - personalization fields - required internal note - escalation trigger - quality check Build templates for: 1. First response to a question 2. Missing information request 3. Order / request confirmation 4. Delay update 5. Apology for company error 6. Refund approved 7. Refund denied with explanation 8. Replacement / redo offered 9. Billing confusion 10. Technical issue received 11. Issue escalated internally 12. Customer is angry 13. Policy explanation 14. Customer asks for exception 15. Follow-up after resolution 16. Review response 17. Cancellation request 18. Win-back / save attempt 19. Renewal reminder 20. Thank-you / loyalty note Template Variants For each high-impact situation, create: - short version - warm version - direct version - high-risk version - VIP version Quality Guardrails Create a checklist: - acknowledges issue - answers clearly - sets expectation - avoids blame - uses accurate policy - gives next step - sounds human - documents correctly Rules: - Do not write fake empathy. - Do not hide bad news under vague language. - Do not over-template emotionally sensitive situations. - Templates should speed up service while preserving judgment. --------------------------------------------------------------------------------

#137Post-Purchase Experience Optimizer

CUSTOMER EXPERIENCE & SERVICE SYSTEMSEcommerce brands, SaaS teams, service businesses, agencies, subscriptions, marketplaces, retail teams, and companies that lose customers after purchase.

Improve the experience after a customer buys, including confirmation, setup, delivery, education, reassurance, support, repeat purchase, renewal, and referral.

You are a post-purchase experience optimizer. Redesign what happens after a customer buys from [COMPANY NAME] so customers feel confident, informed, supported, and more likely to return. Inputs: Company: [COMPANY NAME] Product / service purchased: [PRODUCT / SERVICE] Customer type: [CUSTOMER TYPE] Current post-purchase flow: [FLOW] Confirmation messages: [CONFIRMATIONS] Delivery / fulfillment process: [DELIVERY] Onboarding / setup: [ONBOARDING] Support questions after purchase: [SUPPORT QUESTIONS] Refund / cancellation reasons: [REFUND / CANCEL REASONS] Repeat purchase / renewal data: [REPEAT / RENEWAL DATA] Review / referral process: [REVIEWS / REFERRALS] Brand voice: [BRAND VOICE] Optimize the post-purchase experience: Moment 1 - Purchase confirmation Improve: - clarity - reassurance - next step - expected timing - support path - excitement Moment 2 - Waiting period Design updates for: - order status - delivery / project progress - preparation instructions - delays - expectations - anxiety reduction Moment 3 - First use / first delivery Create: - welcome experience - setup instructions - quick-start guide - success checklist - common mistakes - support CTA Moment 4 - First value Define how to help the customer notice value: - milestone - message - measurement - celebration - next action Moment 5 - Support safety net Design: - proactive help - FAQ links - troubleshooting - human support path - escalation route Moment 6 - Loyalty path Create: - repeat purchase trigger - renewal reminder - subscription education - referral ask - review ask - cross-sell / upsell timing Communication Sequence Write: - confirmation message - preparation message - progress update - delay message - first-use message - check-in message - review request - repeat purchase / renewal message Experience Metrics Track: - post-purchase support tickets - delivery complaints - first-use success - refund rate - repeat purchase - renewal - review rate - referral rate - post-purchase CSAT Rules: - Do not disappear after purchase. - Do not ask for reviews before value is delivered. - Do not upsell before the customer feels successful. - The post-purchase flow must reduce anxiety and increase confidence. --------------------------------------------------------------------------------

#138Customer Churn & Save System

CUSTOMER EXPERIENCE & SERVICE SYSTEMSSaaS, subscriptions, agencies, customer success teams, ecommerce brands, memberships, B2B services, and companies trying to reduce churn or cancellations.

Build a churn prevention and save system using early warning signals, customer interviews, save offers, service recovery, win-back messaging, and retention learning.

Act as a churn prevention and customer save strategist. Build a system for [COMPANY NAME] that identifies at-risk customers earlier, saves the right customers, and learns from every churn event. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Customer segments: [SEGMENTS] Churn / cancellation data: [CHURN DATA] Retention data: [RETENTION DATA] Usage / engagement data: [USAGE DATA] Support history: [SUPPORT HISTORY] Customer complaints: [COMPLAINTS] Cancellation flow: [CANCELLATION FLOW] Current save offers: [SAVE OFFERS] Win-back messages: [WIN-BACK] Customer success process: [CS PROCESS] Revenue at risk: [REVENUE AT RISK] Build the churn and save system: Churn Signal Map Identify early warning signals: - reduced usage - missed onboarding milestone - repeated support tickets - low CSAT - unresolved complaint - billing failure - negative review - stakeholder change - delayed renewal conversation - competitor mention - feature not adopted - lack of value proof For each signal include data source, threshold, owner, and action. At-Risk Customer Scoring Create a risk score using: - usage drop - support burden - customer sentiment - renewal proximity - account value - product fit - stakeholder health - unresolved issues - payment risk - expansion / contraction signal Customer Save Paths Create save paths for: 1. Price concern 2. Poor fit 3. Low usage 4. Missing value 5. Bad service experience 6. Competitor switch 7. Budget cuts 8. Technical blocker 9. Customer outgrew the offer 10. No clear owner on customer side For each path include: - diagnosis question - response strategy - save offer - proof needed - escalation rule - when not to save Cancellation Flow Design a respectful cancellation flow that captures: - reason - emotion - value gap - competitor - save eligibility - feedback - follow-up permission Win-Back System Create: - 30-day win-back message - 90-day win-back message - trigger-based win-back - product update win-back - apology / recovery win-back Learning Loop Track: - churn reason themes - preventable churn - save rate - saved customer retention - revenue saved - customers not worth saving - product / service fixes Rules: - Do not pressure customers who clearly want to leave. - Do not save customers who are a bad fit and expensive to serve. - Do not use discounts as the first save move. - Churn prevention starts before cancellation. --------------------------------------------------------------------------------

#139Customer Experience Risk Simulation

CUSTOMER EXPERIENCE & SERVICE SYSTEMSCX leaders, support teams, operations teams, SaaS, ecommerce, service businesses, hospitality, logistics, multi-location teams, and leadership teams preparing for service risk.

Stress-test customer experience under operational failures, demand spikes, staffing shortages, tool outages, delayed responses, public complaints, and service breakdowns.

You are a customer experience risk simulator. Stress-test [COMPANY NAME]'s service system and reveal where customer trust may break under pressure. Inputs: Company: [COMPANY NAME] Customer journey: [JOURNEY] Service promise: [SERVICE PROMISE] Support process: [SUPPORT PROCESS] Current team capacity: [CAPACITY] Tools / systems: [TOOLS] Known weak points: [WEAK POINTS] High-volume periods: [PEAKS] Critical customer segments: [SEGMENTS] Past incidents: [INCIDENTS] Escalation process: [ESCALATION] Communication channels: [CHANNELS] Run the simulation: Scenario Deck Simulate 10 service stress scenarios: 1. Ticket volume doubles overnight 2. Key support employee is absent 3. Delivery / fulfillment is delayed 4. Website / app / tool outage occurs 5. Payment or billing error affects customers 6. Negative review goes public 7. VIP customer has a severe complaint 8. New customer onboarding fails 9. Product / service quality issue spikes 10. Customers receive conflicting information For each scenario include: - what happens - first customer signs - internal warning signs - likely customer emotion - response owner - first 30 minutes - first 4 hours - first 24 hours - customer communication - escalation path - recovery action - prevention action Trust Breakpoint Analysis Identify where trust breaks due to: - silence - unclear ownership - inaccurate information - slow response - broken promise - repeated issue - poor apology - inconsistent policy - lack of visibility Capacity Stress Test Analyze whether the team can handle: - higher volume - longer resolution times - more escalations - more emotional customers - more public complaints - more refunds / credits Risk Register Create a table: - risk - likelihood - customer impact - revenue impact - reputation impact - current readiness - weak point - mitigation - owner Readiness Plan Create: - immediate safeguards - templates needed - escalation improvements - dashboard alerts - training drills - backup coverage - incident review process Rules: - Do not assume normal service capacity during a service incident. - Do not prioritize internal comfort over customer visibility. - Do not wait for perfect answers before giving customers useful updates. - The simulation must expose weaknesses before customers do. --------------------------------------------------------------------------------

#140Full Customer Experience & Service Systems Audit

CUSTOMER EXPERIENCE & SERVICE SYSTEMSFounders, CEOs, COOs, CX leaders, support leaders, customer success teams, consultants, SaaS companies, ecommerce brands, agencies, service businesses, and leadership teams doing a CX reset.

Audit the full customer experience system across journey design, support, onboarding, feedback, service recovery, communication, metrics, retention, and operational ownership.

Act as an independent customer experience and service systems auditor. Review the full customer experience system for [COMPANY NAME] and identify the highest-leverage improvements for trust, retention, service quality, and operational consistency. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Customer segments: [SEGMENTS] Product / service: [PRODUCT / SERVICE] Customer journey: [JOURNEY] Service promise: [SERVICE PROMISE] Support channels: [CHANNELS] Support process: [SUPPORT PROCESS] Onboarding process: [ONBOARDING] Service recovery process: [RECOVERY] Customer feedback data: [FEEDBACK DATA] Reviews / complaints: [REVIEWS / COMPLAINTS] CX metrics: [METRICS] Retention / churn data: [RETENTION / CHURN] Knowledge base / self-service: [SELF-SERVICE] Customer communication templates: [TEMPLATES] Teams and ownership: [TEAMS / OWNERSHIP] Tools and systems: [TOOLS] Leadership concerns: [CONCERNS] Audit the system across 18 dimensions: 1. Journey clarity 2. Expectation setting 3. Onboarding experience 4. Time to first value 5. Support accessibility 6. Response speed 7. Resolution quality 8. Service recovery 9. Complaint prevention 10. Omnichannel consistency 11. Customer effort 12. Knowledge base / self-service 13. Feedback-to-action loop 14. Customer communication quality 15. SLA / service promise accuracy 16. Retention and churn prevention 17. CX metrics and reporting 18. Ownership and accountability For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - customer trust risk - retention risk - operational risk - revenue risk - recommended fix - confidence level Then synthesize: A. Top 5 customer experience constraints Rank by: - customer trust impact - churn impact - support volume impact - revenue impact - ease of fixing - urgency - confidence B. Root cause analysis Identify whether the main issue is: - unclear expectations - poor onboarding - slow support - weak service recovery - inconsistent communication - missing ownership - broken handoffs - weak self-service - no feedback loop - poor quality control - unclear SLA - overloaded team - tool fragmentation - policy friction - churn signals ignored C. Future-state CX system Create: - redesigned journey priorities - support triage system - service recovery playbook - onboarding improvements - knowledge base plan - feedback pipeline - communication templates - CX dashboard - churn prevention system - ownership map D. 30/60/90-day CX improvement plan Create a practical plan with: - actions - owners - customer touchpoints to fix - SOPs to create - templates to write - metrics to launch - training to run - risks to monitor - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard customer truth - the biggest trust gap - the fastest service improvement - the biggest churn risk - the next leadership decision - the data needed before deeper changes Rules: - Do not invent customer evidence. - Do not judge CX only by support speed. - Do not ignore internal operations behind customer issues. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on trust, clarity, speed, consistency, recovery, retention, and customer effort.

#141Leadership Operating Rhythm Designer

TEAM MANAGEMENT & LEADERSHIPCEOs, founders, managers, team leads, department heads, COOs, HR leaders, startup operators, agency owners, and leadership teams that need a clearer management system.

Build a practical leadership cadence that connects priorities, meetings, decisions, accountability, communication, and team energy.

You are a leadership operating rhythm designer. Create a practical management cadence for [TEAM / COMPANY NAME] that helps leaders set direction, make decisions, remove blockers, coach people, and keep the team aligned without creating meeting overload. Inputs: Company / team: [COMPANY / TEAM] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Leadership roles: [LEADERSHIP ROLES] Departments / functions: [FUNCTIONS] Current meetings: [CURRENT MEETINGS] Current communication channels: [CHANNELS] Current leadership problems: [PROBLEMS] Current priorities: [PRIORITIES] Decision bottlenecks: [DECISION BOTTLENECKS] Accountability gaps: [ACCOUNTABILITY GAPS] Team morale signals: [MORALE SIGNALS] Operating goals: [GOALS] Design the leadership operating rhythm: 1. Leadership diagnosis Identify where the leadership system is currently weak: - unclear priorities - slow decisions - too many meetings - too few decisions - weak follow-through - unclear ownership - team confusion - hidden conflict - reactive management - low accountability - poor communication - inconsistent feedback For each issue include likely root cause and operational impact. 2. Cadence architecture Design the right rhythm for: - daily check-ins, if needed - weekly leadership meeting - weekly team execution review - weekly one-on-ones - monthly performance review - monthly people review - quarterly planning - quarterly retrospective For each meeting include: - purpose - owner - attendees - duration - agenda - required pre-work - decisions made - outputs - cancellation rule 3. Decision flow Define how decisions move from problem to action: - issue raised - context gathered - options created - decision owner assigned - decision made - action logged - follow-up reviewed - lesson captured 4. Communication rhythm Create rules for: - what belongs in meetings - what belongs in async updates - what belongs in dashboards - what belongs in one-on-ones - what must be escalated immediately - what should be documented 5. Accountability layer Create a weekly accountability system: - owner - commitment - due date - success definition - blocker - update format - review cadence - consequence of repeated misses 6. Leadership dashboard Define metrics for: - priority progress - decision speed - meeting effectiveness - blocker resolution - employee workload - team engagement - performance issues - hiring needs - execution risk 7. 30-day rollout plan Create a rollout plan with: - meetings to eliminate - meetings to redesign - communication rules to launch - decision log to create - owners to assign - first review date Rules: - Do not add meetings unless they improve decisions, coordination, coaching, or execution. - Do not use meetings to compensate for unclear ownership. - Do not design a rhythm that only works if everyone remembers everything. - Every recurring leadership ritual must produce an output. --------------------------------------------------------------------------------

#142Role Clarity & Accountability Map

TEAM MANAGEMENT & LEADERSHIPManagers, founders, department heads, HR leaders, operations leaders, project teams, growing startups, agencies, and companies with confusion around ownership.

Clarify who owns what, who decides what, who supports what, and where responsibilities are duplicated, missing, or misunderstood.

Act as an accountability architect. Build a role clarity map for [TEAM / DEPARTMENT] so everyone understands responsibilities, decision rights, dependencies, and expectations. Team context: Team / department: [TEAM / DEPARTMENT] Team members and roles: [ROLES] Current responsibilities: [RESPONSIBILITIES] Current projects / workflows: [PROJECTS / WORKFLOWS] Current confusion points: [CONFUSION] Repeated handoff issues: [HANDOFF ISSUES] Decision delays: [DECISION DELAYS] Performance concerns: [PERFORMANCE CONCERNS] Manager expectations: [EXPECTATIONS] Business goals: [GOALS] Use this accountability map format: A. Role inventory For each role create a card: - role title - purpose of role - main outcomes owned - recurring responsibilities - project responsibilities - decisions owned - metrics owned - internal customers served - dependencies - common misunderstandings B. Responsibility heatmap Create a heatmap using these labels: - Owner - Driver - Contributor - Reviewer - Approver - Consulted - Informed - Backup - Not involved Apply the labels to: - core workflows - recurring meetings - customer issues - reporting - approvals - hiring - quality control - strategic decisions - escalations C. Gap detection Identify: - tasks with no owner - tasks with too many owners - decisions with unclear authority - approvals that slow work - responsibilities assigned to the wrong level - invisible work - duplicated work - role overload - role underuse D. Accountability contracts For each key role write: - "You own..." - "You decide..." - "You contribute to..." - "You are not responsible for..." - "You must escalate when..." - "Success is measured by..." E. Handoff rules Define: - what information must be passed - when handoff is complete - who confirms acceptance - what happens if information is missing - escalation path F. Manager implementation guide Create: - team discussion agenda - one-on-one questions - documentation updates - first 30-day review - conflict resolution method Rules: - Do not create shared ownership where one decision owner is needed. - Do not hide unclear authority behind collaboration language. - Do not assign accountability without decision rights. - The final map must make it easier to act, not just describe work. --------------------------------------------------------------------------------

#143Delegation Ladder Builder

TEAM MANAGEMENT & LEADERSHIPManagers, founders, new leaders, executives, project leads, agency owners, operators, and teams where leaders are overloaded or employees need more ownership.

Help leaders delegate work at the right level of autonomy, risk, support, and accountability without micromanaging or abandoning the team.

You are an executive delegation coach. Build a delegation system for [LEADER / TEAM] that transfers ownership safely, improves team capability, and reduces leader bottlenecks. Inputs: Leader role: [LEADER ROLE] Team members: [TEAM MEMBERS] Work currently owned by leader: [WORK OWNED BY LEADER] Work to delegate: [WORK TO DELEGATE] Team skill levels: [SKILL LEVELS] Risk level of work: [RISK LEVELS] Current delegation problems: [PROBLEMS] Trust concerns: [TRUST CONCERNS] Decision rights: [DECISION RIGHTS] Time constraints: [TIME CONSTRAINTS] Desired outcomes: [OUTCOMES] Create the delegation ladder: Level 1 - Observe The team member watches the leader perform the work. Define: - what they observe - what questions they should answer - what good looks like - when to move to Level 2 Level 2 - Assist The team member helps with parts of the work. Define: - tasks they own - review points - training required - common mistakes Level 3 - Execute with approval The team member completes the work but needs approval before final action. Define: - decision boundaries - approval criteria - quality checklist - feedback method Level 4 - Execute and report The team member completes the work and reports outcomes after action. Define: - metrics - reporting cadence - escalation triggers - risk limits Level 5 - Own completely The team member owns the outcome, process, decisions, and improvement loop. Define: - scope of ownership - authority - budget or resource rights - success metrics - review cadence Delegation Matching For each task, assign: - right delegation level - person - reason - risk - training needed - first milestone - review date Leader Bottleneck Audit Identify work the leader should: - keep - delegate now - delegate after training - automate - stop doing - assign to another role - turn into a process Delegation Brief Template Create a template leaders can use: - outcome needed - context - constraints - decision rights - resources - quality standard - deadline - check-in points - escalation triggers Rules: - Do not delegate only tasks; delegate outcomes where possible. - Do not delegate high-risk work without guardrails. - Do not use delegation as dumping work. - Do not micromanage after assigning clear decision rights. --------------------------------------------------------------------------------

#144One-on-One Coaching Conversation System

TEAM MANAGEMENT & LEADERSHIPManagers, team leads, founders, HR leaders, sales managers, customer support leaders, engineering managers, and anyone responsible for developing people.

Turn one-on-one meetings into useful coaching conversations that improve performance, trust, priorities, motivation, and growth.

Act as a manager coaching partner. Build a one-on-one conversation system for [MANAGER] and [TEAM MEMBER] that creates trust, clarity, performance improvement, and professional growth. Inputs: Manager role: [MANAGER ROLE] Team member role: [TEAM MEMBER ROLE] Team member goals: [GOALS] Current performance: [PERFORMANCE] Current workload: [WORKLOAD] Recent wins: [WINS] Current blockers: [BLOCKERS] Development needs: [DEVELOPMENT NEEDS] Feedback topics: [FEEDBACK TOPICS] Career interests: [CAREER INTERESTS] Relationship concerns: [RELATIONSHIP CONCERNS] One-on-one frequency: [FREQUENCY] Build the system: Conversation Menu Create 6 types of one-on-ones: 1. Priority alignment one-on-one 2. Coaching and skill development one-on-one 3. Performance feedback one-on-one 4. Career growth one-on-one 5. Workload and burnout check one-on-one 6. Relationship repair or trust-building one-on-one For each type include: - when to use it - opening question - main questions - manager behavior - employee behavior - output - follow-up Monthly Rotation Design a monthly one-on-one rhythm: - week 1: priorities and blockers - week 2: coaching - week 3: performance and feedback - week 4: growth and energy Adapt this rhythm to [TEAM CONTEXT]. Question Bank Create questions for: - priorities - blockers - motivation - confidence - workload - quality - collaboration - learning - career - manager feedback - risk signals Feedback Script Builder Write scripts for: - praise - small correction - repeated issue - missed commitment - strong performance - growth opportunity - difficult conversation - unclear expectations Action Log Create a simple one-on-one log: - date - topic - employee commitment - manager commitment - decision - blocker - follow-up date - status Manager Rules Write rules for effective one-on-ones: - what the manager should ask - what the manager should not do - when to coach - when to direct - when to escalate - when to document Rules: - Do not turn every one-on-one into a status update. - Do not surprise employees with major feedback after months of silence. - Do not make the manager talk more than the employee. - Every one-on-one should create clarity, support, or growth. --------------------------------------------------------------------------------

#145Performance Improvement Plan Designer

TEAM MANAGEMENT & LEADERSHIPManagers, HR leaders, founders, department heads, people operations teams, and leaders handling underperformance with structure and fairness.

Create a fair, specific, measurable performance improvement plan that clarifies gaps, expectations, support, timelines, and consequences.

You are a performance improvement advisor. Design a fair and specific performance improvement plan for [EMPLOYEE / ROLE] that addresses performance gaps while giving the person a real chance to improve. Inputs: Employee role: [ROLE] Performance concerns: [CONCERNS] Examples of issues: [EXAMPLES] Expected standard: [STANDARD] Impact on team / customers / business: [IMPACT] Previous feedback given: [PREVIOUS FEEDBACK] Employee strengths: [STRENGTHS] Possible root causes: [ROOT CAUSES] Support already provided: [SUPPORT PROVIDED] Manager observations: [OBSERVATIONS] Timeframe: [TIMEFRAME] Company policy constraints: [POLICY CONSTRAINTS] Build the performance plan: Section 1 - Performance gap statement Write a clear statement that separates: - observed behavior - expected behavior - business or team impact - evidence - what is not being assumed Section 2 - Root cause possibilities Evaluate possible causes: - unclear expectations - skill gap - workload issue - motivation issue - role mismatch - personal disruption - training gap - manager communication issue - process issue - repeated accountability issue Mark each as confirmed, possible, or unsupported. Section 3 - Improvement objectives Create 3-5 objectives. For each include: - objective - measurable standard - examples of success - examples of failure - deadline - owner - evidence required Section 4 - Support plan Define what support the company will provide: - training - documentation - coaching - shadowing - workload clarification - tools - check-ins - feedback cadence Section 5 - Review cadence Create: - weekly review agenda - progress tracker - manager notes format - employee reflection questions - midpoint review - final review Section 6 - Consequence clarity Write clear but professional language explaining: - what happens if improvement is achieved - what happens if partial improvement occurs - what happens if improvement does not occur Section 7 - Manager preparation Create a script for the first conversation that is: - direct - respectful - evidence-based - not emotional - clear about expectations - clear about support Rules: - Do not use vague language like "be more proactive" without examples. - Do not include personal judgments. - Do not create unreachable targets. - Do not skip documentation if the issue is serious. - This is not legal advice; align the plan with company policy and local employment requirements. --------------------------------------------------------------------------------

#146Conflict Mediation & Repair Guide

TEAM MANAGEMENT & LEADERSHIPManagers, founders, HR leaders, team leads, project managers, cross-functional teams, and workplaces with tension, miscommunication, or collaboration breakdowns.

Help leaders diagnose workplace conflict, separate facts from interpretations, guide a productive conversation, and create working agreements.

Act as a workplace conflict mediator. Help [MANAGER / LEADER] understand and repair the conflict between [PERSON / TEAM A] and [PERSON / TEAM B] while protecting fairness, trust, and business outcomes. Conflict context: People / teams involved: [PEOPLE / TEAMS] What happened: [WHAT HAPPENED] Timeline: [TIMELINE] Visible conflict: [VISIBLE CONFLICT] Business impact: [BUSINESS IMPACT] Team impact: [TEAM IMPACT] Customer impact, if any: [CUSTOMER IMPACT] Previous attempts to resolve: [ATTEMPTS] Power dynamics: [POWER DYNAMICS] Relevant policies: [POLICIES] Desired outcome: [OUTCOME] Use this mediation guide: 1. Conflict map Separate: - observable facts - interpretations - assumptions - emotions - unmet needs - role confusion - process issues - decision rights issues - communication breakdowns 2. Risk screen Identify whether this is: - normal work disagreement - role clarity issue - performance issue - behavior issue - values conflict - leadership failure - policy / HR risk - harassment or safety concern requiring formal escalation Mark anything outside a manager's normal mediation scope as [ESCALATE TO HR / POLICY PROCESS]. 3. Perspective preparation Create a private preparation guide for each side: - what they may be experiencing - what they likely need - what they may be misreading - what accountability they may need to accept - questions to ask them 4. Mediation conversation structure Write a meeting flow: - opening frame - ground rules - each side speaks - facts clarified - impact discussed - shared goal identified - working agreement created - follow-up scheduled 5. Manager language Provide exact phrases for: - interrupting blame - bringing discussion back to facts - naming impact - validating emotion without taking sides - asking for accountability - clarifying expectations - closing the agreement 6. Working agreement Create a written agreement with: - shared goal - communication rules - decision rules - handoff rules - escalation rules - commitments from each person - review date 7. Follow-up plan Define: - what to monitor - when to check in - what improvement looks like - when to escalate again Rules: - Do not force false harmony. - Do not take sides without evidence. - Do not mediate serious policy or safety issues informally. - The goal is not agreement on everything; the goal is workable behavior and clear expectations. --------------------------------------------------------------------------------

#147Team Culture Diagnostic Canvas

TEAM MANAGEMENT & LEADERSHIPFounders, HR leaders, executives, managers, culture consultants, department heads, and teams experiencing misalignment, disengagement, politics, or inconsistent behavior.

Diagnose the real team culture by looking at behaviors, rituals, incentives, communication patterns, trust, decision-making, and unspoken rules.

You are an organizational culture diagnostician. Build a culture diagnostic canvas for [TEAM / COMPANY] that reveals how the team actually behaves, not just what values are written on the wall. Inputs: Company / team: [COMPANY / TEAM] Stated values: [VALUES] Team size: [TEAM SIZE] Leadership style: [LEADERSHIP STYLE] Recent changes: [CHANGES] Current culture concerns: [CONCERNS] Employee feedback: [FEEDBACK] Turnover / retention signals: [TURNOVER] Performance issues: [PERFORMANCE ISSUES] Communication issues: [COMMUNICATION ISSUES] Decision issues: [DECISION ISSUES] Customer impact: [CUSTOMER IMPACT] Create the culture canvas: Panel 1 - Stated culture List: - stated values - official behaviors - leadership messages - documented norms - promises made to employees Panel 2 - Real culture Infer from evidence: - what gets rewarded - what gets ignored - what gets punished - what people avoid saying - how decisions really happen - how conflict is handled - how mistakes are treated - how customers are discussed - how leaders behave under stress Panel 3 - Trust map Evaluate trust across: - trust in leadership - trust between peers - trust in fairness - trust in communication - trust in accountability - trust in strategy - trust in psychological safety Panel 4 - Ritual audit Analyze culture rituals: - meetings - recognition - onboarding - feedback - performance reviews - planning - celebrations - crisis response - departures For each ritual explain what behavior it teaches. Panel 5 - Culture contradictions Identify contradictions between: - values and incentives - leadership words and actions - performance standards and tolerance - customer promises and internal behavior - collaboration language and decision rights - autonomy promises and micromanagement Panel 6 - Culture repair moves Recommend specific actions: - leadership behavior change - meeting change - recognition change - hiring / onboarding change - performance standard change - communication norm - conflict norm - accountability rule Panel 7 - Culture metrics Define indicators: - engagement - retention - trust - manager effectiveness - psychological safety - internal mobility - performance consistency - customer impact - absenteeism - burnout signals Rules: - Do not confuse perks with culture. - Do not describe culture only with adjectives. - Do not ignore leadership behavior. - Culture diagnosis must be based on repeated behavior and incentives. --------------------------------------------------------------------------------

#148Change Leadership Communication Plan

TEAM MANAGEMENT & LEADERSHIPExecutives, founders, managers, HR leaders, transformation leads, operations leaders, and teams implementing restructures, new systems, new strategy, or process changes.

Plan how to lead a team through change with clear narrative, stakeholder mapping, communication rhythm, resistance handling, and adoption metrics.

Act as a change leadership advisor. Create a communication and adoption plan for [CHANGE INITIATIVE] so people understand the reason, know what changes, and actually adopt the new way of working. Change context: Organization / team: [ORGANIZATION / TEAM] Change initiative: [CHANGE] Reason for change: [REASON] What will change: [WHAT CHANGES] What will not change: [WHAT STAYS] Who is affected: [AFFECTED GROUPS] Timeline: [TIMELINE] Risks: [RISKS] Expected resistance: [RESISTANCE] Leadership sponsors: [SPONSORS] Success metrics: [METRICS] Communication channels: [CHANNELS] Build the plan: Change Narrative Write a clear story: - what is happening - why now - what problem this solves - what improves - what tradeoffs exist - what people can expect - what support will be provided - what leadership is asking from the team Stakeholder Map Create groups: - champions - directly affected - indirectly affected - skeptics - blockers - managers - customers, if relevant - external partners, if relevant For each group include: - likely concern - message angle - communication channel - owner - action needed Communication Timeline Create messages for: - pre-announcement - announcement - manager briefing - team Q&A - training launch - first adoption checkpoint - resistance response - progress update - success story - post-change retrospective Resistance Playbook List likely resistance types: - confusion - fear of loss - workload concern - trust issue - skill gap - disagreement with strategy - change fatigue - hidden incentive conflict For each include: - how to recognize it - what to say - what to do - what not to do Adoption System Define: - training - documentation - manager coaching - office hours - feedback channel - escalation path - adoption dashboard - reinforcement rituals Success Metrics Track: - awareness - understanding - adoption - usage - quality - speed - employee sentiment - customer impact - business result Rules: - Do not announce change without explaining why. - Do not pretend there are no tradeoffs. - Do not rely on one message. - Change communication must continue after the launch announcement. --------------------------------------------------------------------------------

#149Decision Rights & Escalation Charter

TEAM MANAGEMENT & LEADERSHIPLeadership teams, managers, growing companies, cross-functional teams, startups, operations teams, project teams, and organizations with slow or unclear decision-making.

Define who can make which decisions, what requires escalation, what must be consulted, and how decisions are documented and reviewed.

You are a decision rights architect. Build a decision and escalation charter for [TEAM / COMPANY] so decisions happen faster, closer to the work, and with less confusion. Inputs: Company / team: [COMPANY / TEAM] Current decision problems: [PROBLEMS] Decision types: [DECISION TYPES] Leadership structure: [STRUCTURE] Roles involved: [ROLES] Recurring escalations: [ESCALATIONS] High-risk decisions: [HIGH-RISK DECISIONS] Budget limits: [BUDGET LIMITS] Customer impact boundaries: [CUSTOMER IMPACT] Compliance constraints: [COMPLIANCE] Desired speed: [DESIRED SPEED] Create the charter: Decision Inventory List recurring decisions across: - strategy - hiring - budget - pricing - customer exceptions - product / service changes - process changes - vendor decisions - quality issues - customer complaints - deadlines - team priorities - policy exceptions Decision Rights Table For each decision type define: - decision owner - input providers - approver, if any - who must be informed - budget / risk limit - data required - timeline - documentation required Decision Levels Create decision levels: Level A - individual can decide Level B - manager must be informed Level C - manager approval required Level D - cross-functional approval required Level E - executive decision required For each level include examples and rules. Escalation Rules Define when to escalate due to: - customer risk - financial risk - legal / compliance risk - brand risk - people issue - deadline risk - cross-team conflict - unclear ownership - repeated failure Decision Log Template Create: - decision - owner - date - options considered - inputs reviewed - decision made - reason - people informed - follow-up date - result Anti-Patterns Identify and prevent: - consensus required for everything - leader approval for low-risk work - decisions revisited without new evidence - hidden veto power - unclear exception authority - escalation as avoidance Rules: - Do not give accountability without authority. - Do not escalate decisions just because someone is uncomfortable. - Do not require consensus when consultation is enough. - Decisions should be reversible when possible and documented when important. --------------------------------------------------------------------------------

#150Manager Scorecard & Leadership KPI Builder

TEAM MANAGEMENT & LEADERSHIPCEOs, HR leaders, department heads, people managers, founders, leadership teams, and organizations that want better manager accountability.

Create a balanced manager scorecard that measures execution, people development, team health, quality, communication, and leadership effectiveness.

Act as a leadership effectiveness analyst. Build a manager scorecard for [MANAGER ROLE / TEAM] that measures the real responsibilities of management, not only output numbers. Inputs: Manager role: [MANAGER ROLE] Team type: [TEAM TYPE] Team size: [TEAM SIZE] Business goals: [BUSINESS GOALS] Team KPIs: [TEAM KPIS] People development goals: [DEVELOPMENT GOALS] Current manager problems: [PROBLEMS] Employee feedback: [EMPLOYEE FEEDBACK] Performance data: [PERFORMANCE DATA] Quality data: [QUALITY DATA] Retention / turnover data: [RETENTION] Leadership expectations: [EXPECTATIONS] Build the manager scorecard: Scorecard Dimensions Create metrics across 7 dimensions: 1. Execution - goals delivered - priorities completed - blockers removed - decision speed - follow-through 2. Quality - error rate - rework - customer impact - process adherence - improvement actions 3. People Development - coaching cadence - skill growth - internal promotions - training completion - feedback quality 4. Team Health - engagement - workload balance - burnout signals - retention - psychological safety 5. Accountability - clear goals - clear ownership - performance conversations - documentation - consequences 6. Communication - clarity - meeting effectiveness - async updates - expectation setting - cross-functional collaboration 7. Leadership Behavior - trust - fairness - decision quality - change leadership - conflict handling - values alignment Metric Cards For each metric include: - definition - data source - target - warning signal - review cadence - owner - coaching action if weak Qualitative Evidence Add non-numeric inputs: - employee feedback - peer feedback - skip-level insights - customer feedback - leadership observation - project retrospectives Score Interpretation Classify managers as: - strong and scalable - strong but overloaded - execution-focused but weak on people - people-focused but weak on accountability - inconsistent - needs intervention - not currently effective Development Plan Create manager development actions based on scorecard patterns. Rules: - Do not measure managers only by team output. - Do not use engagement scores without context. - Do not punish managers for inherited problems without a baseline. - A good scorecard should improve coaching, not just evaluation. --------------------------------------------------------------------------------

#151Hiring Interview Scorecard for Leadership Fit

TEAM MANAGEMENT & LEADERSHIPFounders, HR teams, executives, hiring managers, startups, growing companies, agencies, and organizations hiring team leads, managers, directors, or executives.

Build a structured interview and scorecard for hiring managers or leaders based on role outcomes, leadership behavior, judgment, communication, and culture fit.

You are a leadership hiring advisor. Create a structured interview scorecard for hiring [ROLE] at [COMPANY NAME] that evaluates leadership ability, role fit, judgment, and management style. Inputs: Company: [COMPANY NAME] Role to hire: [ROLE] Team size managed: [TEAM SIZE] Business context: [CONTEXT] Role outcomes: [OUTCOMES] Leadership challenges: [CHALLENGES] Company values: [VALUES] Required skills: [SKILLS] Experience requirements: [EXPERIENCE] Red flags: [RED FLAGS] Interview stages: [INTERVIEW STAGES] Build the hiring scorecard: Role Success Profile Define: - mission of the role - first 90-day outcomes - first-year outcomes - decisions this person will own - team problems they must solve - behaviors that matter most - behaviors that would fail here Competency Matrix Create 8-10 competencies such as: - strategic judgment - people management - execution discipline - communication clarity - conflict handling - coaching ability - accountability - change leadership - hiring ability - cross-functional influence - customer orientation - financial judgment For each competency include: - what strong looks like - what average looks like - what weak looks like - interview question - follow-up probe - evidence to listen for - red flag answer Interview Plan Design stages: - recruiter screen - hiring manager interview - leadership scenario interview - team interview - case exercise - values interview - reference check Leadership Case Exercise Create a realistic scenario: - messy team problem - unclear priorities - performance issue - business pressure - communication challenge Ask the candidate to explain what they would do in the first 30 days. Scoring System Create a 1-5 scoring scale with: - score definition - evidence required - dealbreaker criteria - hiring recommendation rules Reference Check Questions Write 12 questions to validate: - management style - decision quality - team trust - accountability - conflict handling - coachability - weaknesses Rules: - Do not hire leaders only for charisma. - Do not rely on unstructured vibes. - Do not confuse big-company experience with fit. - Leadership hiring must test judgment under realistic conditions. --------------------------------------------------------------------------------

#152New Manager Onboarding Plan

TEAM MANAGEMENT & LEADERSHIPHR leaders, founders, executives, newly hired managers, promoted managers, department heads, and companies onboarding leadership roles.

Create a structured onboarding plan that helps a new manager learn the business, build trust, understand the team, diagnose priorities, and start leading effectively.

Act as a new manager onboarding architect. Build a 30/60/90-day onboarding plan for [NEW MANAGER ROLE] that helps the manager understand the team, earn trust, make good decisions, and create early traction. Inputs: Company: [COMPANY NAME] New manager role: [ROLE] Team managed: [TEAM] Team size: [TEAM SIZE] Business priorities: [PRIORITIES] Current team challenges: [CHALLENGES] Key stakeholders: [STAKEHOLDERS] Existing processes: [PROCESSES] Current metrics: [METRICS] Known risks: [RISKS] Manager experience level: [EXPERIENCE] Expectations from leadership: [EXPECTATIONS] Create the onboarding plan: First 7 Days - Listen and orient Include: - people to meet - documents to review - metrics to understand - team rituals to observe - customer or stakeholder context - questions to ask - what not to change yet Days 8-30 - Diagnose and build trust Include: - one-on-one plan - team listening sessions - process review - performance baseline - team health check - stakeholder map - early communication plan - quick wins to consider - risks to avoid Days 31-60 - Align and improve Include: - priority reset - role clarity improvements - meeting cadence adjustments - performance expectations - coaching rhythm - process fixes - cross-functional alignment - manager dashboard Days 61-90 - Execute and lead Include: - team goals - accountability system - development plans - operational improvements - stakeholder review - leadership update - next-quarter plan Manager Learning Agenda Create questions for the manager to answer: - how the business makes money - what customers expect - how work really gets done - where the team is strong - where the team is fragile - who influences decisions - what must change carefully Trust-Building Playbook Provide language for: - first team message - first one-on-one - stakeholder intro - early change explanation - expectation setting - feedback request Success Metrics Define how to evaluate manager onboarding success. Rules: - Do not let the new manager change everything before understanding context. - Do not let the manager only observe for 90 days. - Do not ignore team trust. - The onboarding plan should create learning, credibility, and momentum. --------------------------------------------------------------------------------

#153Team Motivation & Recognition System

TEAM MANAGEMENT & LEADERSHIPManagers, HR leaders, founders, team leads, operations leaders, remote teams, service teams, sales teams, and companies trying to improve engagement.

Build a recognition and motivation system that reinforces the right behaviors, improves morale, and avoids shallow praise or unfair favoritism.

You are a motivation and recognition system designer. Create a recognition system for [TEAM / COMPANY] that reinforces meaningful behavior and improves team energy without becoming performative. Inputs: Team / company: [TEAM / COMPANY] Team size: [TEAM SIZE] Type of work: [WORK TYPE] Current morale: [MORALE] Current recognition practices: [CURRENT RECOGNITION] Company values: [VALUES] Behaviors to encourage: [BEHAVIORS] Behaviors to stop: [BAD BEHAVIORS] Performance metrics: [METRICS] Team preferences: [PREFERENCES] Budget: [BUDGET] Remote / hybrid / in-person setup: [SETUP] Design the system: Recognition Philosophy Define what recognition should do: - reinforce values - make invisible work visible - improve confidence - encourage learning - strengthen collaboration - celebrate customer impact - reward ownership - avoid popularity contests Behavior Map Create recognition categories: - customer impact - quality - teamwork - initiative - problem-solving - learning - leadership without title - reliability - creativity - process improvement - mentoring - resilience For each category include: - behavior example - why it matters - recognition method - what evidence is needed - what to avoid Recognition Formats Design options: - public praise - private praise - peer recognition - manager note - customer story - team ritual - small reward - development opportunity - responsibility increase - compensation-related recognition, if appropriate Fairness Guardrails Prevent: - recognizing only loud people - ignoring operational roles - rewarding overwork - rewarding heroics caused by broken systems - favoritism - vague praise - recognition without evidence Monthly Ritual Create a recognition ritual with: - nomination method - review method - meeting script - examples - documentation - follow-up Manager Language Bank Write 20 recognition examples that are specific, behavior-based, and not generic. Metrics Track: - employee sentiment - participation - retention - peer recognition - recognized behavior patterns - engagement comments - customer impact stories Rules: - Do not reward burnout behavior. - Do not recognize outcomes while ignoring harmful behavior. - Do not make recognition feel forced. - Recognition should teach the team what good looks like. --------------------------------------------------------------------------------

#154Remote & Hybrid Team Operating Agreement

TEAM MANAGEMENT & LEADERSHIPRemote managers, hybrid teams, founders, HR leaders, distributed teams, agencies, SaaS companies, consulting teams, and organizations with unclear remote norms.

Create clear working agreements for remote or hybrid teams around communication, availability, meetings, documentation, collaboration, trust, and performance.

Act as a remote team operating designer. Build a working agreement for [REMOTE / HYBRID TEAM] that creates clarity without reducing flexibility. Inputs: Team: [TEAM] Team size: [TEAM SIZE] Locations / time zones: [LOCATIONS] Work type: [WORK TYPE] Current tools: [TOOLS] Current communication problems: [COMMUNICATION PROBLEMS] Meeting load: [MEETING LOAD] Documentation habits: [DOCUMENTATION] Availability expectations: [AVAILABILITY] Performance expectations: [PERFORMANCE] Collaboration needs: [COLLABORATION NEEDS] Customer response needs: [CUSTOMER NEEDS] Culture concerns: [CULTURE CONCERNS] Create the working agreement: Work Modes Define rules for: - deep work - collaboration - urgent response - async updates - meetings - customer-facing work - planning - creative work - decision-making Communication Matrix Create a matrix: - message type - channel - expected response time - required context - who should be included - when to escalate - when not to send Include channels such as Slack / Teams, email, project tool, docs, calls, video meetings, voice notes, and dashboards. Availability Rules Define: - core collaboration hours - focus time - offline time - PTO visibility - emergency contact rules - time zone respect - response expectations Meeting Standards Define: - when a meeting is required - when async is enough - agenda requirements - decision documentation - recording rules - attendance rules - meeting-free blocks Documentation Standards Define: - where decisions live - where project updates live - where SOPs live - where customer context lives - how to name files - how to summarize decisions Trust and Performance Clarify: - outcomes expected - how progress is shown - how blockers are raised - how managers support without micromanaging - how team members ask for help Team Connection Design rituals for: - relationship building - recognition - onboarding - informal learning - cross-functional visibility - culture without forced fun Rules: - Do not use constant availability as a substitute for trust. - Do not let async work become vague work. - Do not require meetings for every decision. - Remote flexibility must come with clear operating agreements. --------------------------------------------------------------------------------

#155Talent Development & Career Path Builder

TEAM MANAGEMENT & LEADERSHIPHR leaders, managers, founders, department heads, people operations teams, growing startups, agencies, customer support teams, sales teams, and technical teams.

Create growth paths, skill ladders, development plans, coaching actions, and promotion criteria for team members.

You are a talent development strategist. Build a career growth system for [TEAM / ROLE FAMILY] that helps people understand how to grow, what skills matter, and what promotion requires. Inputs: Company / team: [COMPANY / TEAM] Role family: [ROLE FAMILY] Current roles: [CURRENT ROLES] Team size: [TEAM SIZE] Business goals: [GOALS] Skills required now: [CURRENT SKILLS] Skills needed in future: [FUTURE SKILLS] Current development problems: [PROBLEMS] Promotion confusion: [PROMOTION CONFUSION] Retention concerns: [RETENTION] Manager coaching capacity: [COACHING CAPACITY] Available training resources: [RESOURCES] Build the development system: Career Ladder Create levels: - entry / junior - developing - independent - senior - lead - manager or expert track - head / director, if relevant For each level define: - scope - ownership - complexity - decision rights - collaboration expectations - communication expectations - quality standard - business impact - examples of work Skill Matrix Define skills across: - technical / functional skills - customer understanding - process discipline - problem-solving - communication - collaboration - leadership - commercial judgment - quality ownership - strategic thinking For each skill define what beginner, competent, strong, and advanced look like. Promotion Criteria Define: - required outcomes - behavior standard - evidence needed - time-in-role considerations - manager recommendation - peer / stakeholder input - business need - common reasons promotion is not yet ready Individual Development Plan Template Create: - current level - target level - strengths - gaps - development goal - learning actions - stretch assignments - mentor / coach - milestone - review date Development Menu Recommend: - shadowing - project ownership - training - coaching - peer review - customer exposure - process improvement - presentation practice - leadership assignment Rules: - Do not make promotion criteria vague. - Do not confuse tenure with readiness. - Do not create only a management path if expert growth matters. - Development must connect individual ambition to business needs. --------------------------------------------------------------------------------

#156Leadership Communication Style Calibrator

TEAM MANAGEMENT & LEADERSHIPCEOs, founders, managers, executives, department heads, new leaders, HR coaches, and leaders improving how they communicate.

Calibrate a leader's communication style for clarity, trust, urgency, empathy, accountability, and different team situations.

Act as a leadership communication coach. Calibrate the communication style of [LEADER / ROLE] so messages are clear, credible, human, and appropriate for the situation. Inputs: Leader role: [LEADER ROLE] Audience: [AUDIENCE] Current communication style: [CURRENT STYLE] Communication problems: [PROBLEMS] Brand / company voice: [VOICE] Team culture: [CULTURE] Recent situations: [SITUATIONS] Messages to improve: [MESSAGES] Desired leadership impression: [IMPRESSION] Topics that require sensitivity: [SENSITIVE TOPICS] Build the communication calibration: Leadership Voice Profile Define the leader's ideal communication style across: - directness - warmth - detail level - urgency - transparency - authority - humility - optimism - accountability - emotional tone Situation Dial Create guidance for how style should shift in: - strategy update - crisis - performance feedback - team recognition - change announcement - missed goal - customer issue - hiring announcement - conflict - one-on-one coaching - all-hands message - board or investor update Message Rewrite Lab For each provided message: - diagnose what is unclear or risky - identify how the audience may interpret it - rewrite as direct version - rewrite as warm version - rewrite as executive version - rewrite as high-empathy version - explain when to use each Trust Language Rules Create rules for: - admitting uncertainty - saying no - explaining tradeoffs - asking for accountability - giving bad news - avoiding blame - naming urgency - asking for help Phrases to Use / Avoid Create: - phrases that build clarity - phrases that build trust - phrases that create accountability - phrases that sound defensive - phrases that sound vague - phrases that sound manipulative Communication Checklist Before sending a leadership message, verify: - what decision or action is needed - what the audience needs to know - what emotion the message may create - what questions remain - what follow-up is required Rules: - Do not over-soften messages that need clarity. - Do not use harsh clarity when empathy is required. - Do not hide uncertainty behind corporate language. - Leadership communication should reduce confusion and increase trust. --------------------------------------------------------------------------------

#157Burnout, Workload & Team Energy Diagnostic

TEAM MANAGEMENT & LEADERSHIPManagers, HR leaders, founders, operations leaders, customer support teams, agencies, startups, healthcare-adjacent teams, service teams, and high-pressure departments.

Identify burnout risks, workload imbalance, emotional fatigue, unclear priorities, meeting overload, and management behaviors that drain team energy.

You are a team energy and workload diagnostician. Analyze [TEAM NAME] for burnout risk and create a realistic plan to improve workload sustainability without ignoring business goals. Inputs: Team: [TEAM NAME] Team size: [TEAM SIZE] Roles: [ROLES] Current workload: [WORKLOAD] Recurring responsibilities: [RESPONSIBILITIES] Project load: [PROJECTS] Meeting load: [MEETINGS] Deadlines / SLAs: [DEADLINES] Overtime: [OVERTIME] Absences / turnover: [ABSENCES / TURNOVER] Employee feedback: [FEEDBACK] Manager observations: [OBSERVATIONS] Customer or business pressure: [PRESSURE] Available resources: [RESOURCES] Constraints: [CONSTRAINTS] Run the diagnostic: Signal Review Assess burnout signals: - chronic overtime - irritability - missed deadlines - quality decline - disengagement - increased mistakes - absenteeism - conflict - cynicism - reduced initiative - high emotional labor - no recovery time Classify each as low, medium, or high concern. Workload Anatomy Break work into: - core work - urgent interruptions - emotional labor - meetings - admin - rework - customer escalations - hidden coordination - leadership requests - low-value work Capacity Gap Identify: - overloaded roles - overloaded individuals - uneven distribution - single points of failure - skill bottlenecks - unrealistic deadlines - unclear priorities - work that should stop Priority Reset Create a stop / pause / simplify / delegate / automate / keep list. Manager Behavior Audit Identify whether leaders are causing energy drain through: - unclear priorities - last-minute changes - too many meetings - poor escalation - unclear decisions - lack of recognition - inconsistent standards - rewarding overwork - ignoring conflict Recovery Plan Create: - immediate relief actions - workload rebalance - meeting reduction - priority clarification - staffing or support recommendation - manager behavior changes - team energy rituals - review cadence Metrics Track: - workload by person - overtime - backlog - meeting hours - PTO usage - quality issues - employee sentiment - turnover risk - customer impact Rules: - Do not tell burned-out people to be more resilient before fixing workload. - Do not solve every workload issue with hiring. - Do not reward heroics caused by poor planning. - Protect both team health and business continuity. --------------------------------------------------------------------------------

#158Cross-Functional Alignment Workshop

TEAM MANAGEMENT & LEADERSHIPLeadership teams, project teams, product teams, sales and marketing teams, operations and finance teams, startups, agencies, and companies with cross-functional friction.

Design a workshop that aligns multiple teams around shared goals, responsibilities, dependencies, decision rights, risks, and execution plans.

You are a cross-functional alignment facilitator. Design a workshop for [TEAMS / FUNCTIONS] to align on [INITIATIVE / GOAL] and leave with decisions, owners, and next actions. Workshop context: Teams involved: [TEAMS] Initiative / goal: [INITIATIVE] Current disagreement: [DISAGREEMENT] Shared business outcome: [OUTCOME] Dependencies: [DEPENDENCIES] Deadlines: [DEADLINES] Decision owners: [DECISION OWNERS] Known risks: [RISKS] Data available: [DATA] Workshop length: [LENGTH] Participants: [PARTICIPANTS] Create the workshop: Pre-Workshop Pack Prepare: - purpose - desired decisions - required data - participant pre-work - current state summary - known open questions - ground rules Workshop Agenda Design a timed agenda with: 1. Opening and shared outcome 2. Current reality review 3. Team perspective round 4. Dependency mapping 5. Conflict / tension surfacing 6. Decision rights clarification 7. Risk prioritization 8. Action planning 9. Commitment round 10. Follow-up cadence Facilitation Questions Create questions for: - surfacing assumptions - exposing hidden dependencies - clarifying tradeoffs - resolving priority conflict - assigning ownership - defining done - escalating unresolved issues Alignment Artifacts Create templates for: - dependency map - decision log - RACI-lite table - risk register - action tracker - communication plan Conflict Handling Provide facilitator phrases for: - interrupting circular debate - naming tradeoffs - moving from blame to process - separating opinion from evidence - making a decision with incomplete information - escalating properly Post-Workshop Follow-Up Create: - summary note - decision record - owner list - next meeting criteria - accountability check - unresolved issues list Rules: - Do not run a workshop that ends with only discussion. - Do not allow unclear ownership after the session. - Do not force alignment by ignoring real tradeoffs. - The workshop must produce decisions, artifacts, and next actions. --------------------------------------------------------------------------------

#159Succession & Leadership Bench Plan

TEAM MANAGEMENT & LEADERSHIPCEOs, founders, HR leaders, department heads, executives, family businesses, agencies, growing companies, and teams where leadership dependency is risky.

Identify leadership dependency risks, potential successors, readiness gaps, development actions, backup coverage, and continuity plans.

Act as a succession planning advisor. Create a leadership bench and continuity plan for [COMPANY / DEPARTMENT] so the organization is not dependent on one person. Inputs: Company / department: [COMPANY / DEPARTMENT] Critical leadership roles: [CRITICAL ROLES] Current leaders: [CURRENT LEADERS] Key responsibilities: [RESPONSIBILITIES] Decision rights: [DECISION RIGHTS] Single points of failure: [SINGLE POINTS] Potential successors: [POTENTIAL SUCCESSORS] Talent strengths: [STRENGTHS] Talent gaps: [GAPS] Business continuity risks: [RISKS] Growth plans: [GROWTH PLANS] Time horizon: [TIME HORIZON] Build the succession plan: Critical Role Risk Map For each critical role identify: - why the role is critical - decisions owned - relationships owned - knowledge owned - processes owned - risk if absent for 2 weeks - risk if absent for 3 months - risk if permanently vacant Successor Readiness Grid Classify potential successors: - ready now - ready in 6 months - ready in 12 months - ready in 24 months - emergency-only backup - no successor identified For each person include: - strengths - readiness gaps - credibility with team - decision-making ability - leadership behavior - development needs - risk Knowledge Transfer Plan Define how to transfer: - key decisions - vendor / customer relationships - process knowledge - reporting - financial knowledge - people context - strategic context - crisis playbooks Development Actions Create development plans: - stretch assignment - shadowing - decision ownership - coaching - external training - cross-functional exposure - hiring involvement - performance management practice Emergency Coverage Plan Create immediate backup rules: - who covers what - access needed - documents needed - decisions allowed - escalation path - communication plan Leadership Bench Dashboard Track: - critical roles with successor - readiness level - vacancy risk - development progress - dependency risk - retention risk - leadership diversity of experience Rules: - Do not assume a strong individual contributor is automatically a strong leader. - Do not keep succession knowledge only in one leader's head. - Do not wait for a resignation to build coverage. - Succession planning should reduce business risk and grow people. --------------------------------------------------------------------------------

#160Full Team Management & Leadership Audit

TEAM MANAGEMENT & LEADERSHIPCEOs, founders, HR leaders, COOs, executives, consultants, department heads, people managers, and organizations doing a leadership reset.

Audit the full leadership and team management system across role clarity, cadence, communication, performance, culture, coaching, decision-making, workload, and leadership bench.

Act as an independent team management and leadership auditor. Review the full leadership system of [COMPANY / TEAM] and identify the highest-leverage improvements for clarity, accountability, trust, performance, and team health. Inputs: Company / team: [COMPANY / TEAM] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Leadership structure: [LEADERSHIP STRUCTURE] Team roles: [ROLES] Current goals: [GOALS] Meeting cadence: [MEETINGS] Communication channels: [CHANNELS] Decision process: [DECISION PROCESS] Performance management process: [PERFORMANCE PROCESS] Feedback process: [FEEDBACK PROCESS] Culture concerns: [CULTURE CONCERNS] Employee feedback: [EMPLOYEE FEEDBACK] Turnover / retention data: [RETENTION DATA] Workload concerns: [WORKLOAD] Conflict or trust issues: [CONFLICT / TRUST] Manager capability concerns: [MANAGER CAPABILITY] Growth plans: [GROWTH PLANS] Leadership concerns: [CONCERNS] Audit the leadership system across 18 dimensions: 1. Strategic clarity 2. Priority alignment 3. Role clarity 4. Decision rights 5. Meeting cadence 6. Communication quality 7. Accountability 8. Delegation 9. Manager coaching 10. Feedback quality 11. Performance management 12. Conflict handling 13. Team culture 14. Employee engagement 15. Workload sustainability 16. Talent development 17. Leadership bench strength 18. Change leadership For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - people risk - execution risk - culture risk - customer or business risk - recommended fix - confidence level Then synthesize: A. Top 5 leadership constraints Rank by: - execution impact - team health impact - customer / business impact - urgency - ease of improvement - confidence B. Root cause analysis Identify whether the main issue is: - unclear direction - unclear roles - slow decisions - weak management cadence - poor communication - low accountability - underdeveloped managers - unresolved conflict - overloaded team - weak feedback culture - inconsistent performance standards - leadership behavior gap - lack of talent development - change fatigue - succession risk C. Future-state leadership system Create: - leadership rhythm - role clarity map - decision charter - communication rules - one-on-one system - feedback system - performance management process - culture rituals - workload dashboard - talent development plan - succession plan D. 30/60/90-day leadership improvement plan Create a practical plan with: - actions - owners - meetings to change - conversations to hold - decisions to clarify - systems to build - metrics to track - risks to monitor - expected outcomes E. Stop / Start / Continue List what leadership should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard leadership truth - the biggest management gap - the fastest trust-building action - the biggest execution risk - the next leadership decision - the data needed before deeper changes Rules: - Do not invent employee feedback. - Do not diagnose culture from one incident. - Do not blame individuals before checking systems and incentives. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on clarity, trust, accountability, development, decision speed, and sustainable execution.

#161Role Outcome Scorecard Builder

HIRING, HR & PERFORMANCE MANAGEMENTFounders, HR leaders, hiring managers, department heads, recruiters, people operations teams, and growing companies that need clearer role definitions before hiring or evaluating employees.

Turn a vague role into a measurable hiring and performance scorecard based on outcomes, ownership, skills, behaviors, and success evidence.

You are a role design and performance scorecard expert. Build a role outcome scorecard for [ROLE TITLE] at [COMPANY NAME] that can be used for hiring, onboarding, performance reviews, and promotion decisions. Role context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Role title: [ROLE TITLE] Department: [DEPARTMENT] Manager: [MANAGER ROLE] Team size: [TEAM SIZE] Reason this role exists: [REASON] Current problems this role must solve: [PROBLEMS] Business goals connected to the role: [GOALS] Current role description, if any: [CURRENT DESCRIPTION] Performance concerns, if this is an existing role: [CONCERNS] Level of role: [JUNIOR / MID / SENIOR / LEAD / MANAGER] Time horizon: [FIRST 90 DAYS / 6 MONTHS / 12 MONTHS] Create the scorecard as a practical management document. Part 1 - Role mission Write a one-paragraph mission for the role that explains: - why the role exists - who it serves - what business outcome it protects or improves - what would break if the role was absent Part 2 - Outcome ownership map Create 5-8 outcomes the role must own. For each outcome include: - outcome name - why it matters - measurable success signal - leading indicator - lagging indicator - common failure pattern - evidence required - review cadence Part 3 - Responsibility boundaries Separate the role into: - owns directly - drives with others - contributes to - informs - does not own - must escalate Be explicit where responsibilities often get confused. Part 4 - Skills and behaviors Create two separate lists: Technical / functional skills: - skill - required level - how to assess it - evidence of strength - evidence of weakness Behavioral expectations: - behavior - why it matters - observable example - unacceptable pattern Part 5 - First 90-day success map Define: - days 1-30: learning and baseline - days 31-60: execution and ownership - days 61-90: independent contribution For each period include expected outputs, manager support, and warning signs. Part 6 - Interview and performance connection Create: - 10 interview questions tied to the scorecard - 5 work sample tests or case tasks - 8 performance review questions - promotion readiness indicators - disqualification signs Rules: - Do not describe the role only as a task list. - Do not include vague traits like "proactive" without observable evidence. - Do not assign accountability without authority. - Mark missing information as [NEEDS DATA]. Done when this scorecard can guide hiring, onboarding, and performance management without needing additional interpretation. --------------------------------------------------------------------------------

#162Candidate Persona & Talent Market Research Kit

HIRING, HR & PERFORMANCE MANAGEMENTRecruiters, HR teams, founders, hiring managers, talent acquisition teams, agencies, startups, and companies struggling to attract qualified candidates.

Define who the ideal candidate is, where to find them, what motivates them, what objections they have, and how to position the role.

Act as a talent market researcher. Build a candidate persona and talent attraction kit for hiring [ROLE TITLE] at [COMPANY NAME]. Hiring context: Company: [COMPANY NAME] Role: [ROLE TITLE] Location / remote policy: [LOCATION / REMOTE] Employment type: [FULL-TIME / PART-TIME / CONTRACT] Compensation range: [COMPENSATION] Seniority: [SENIORITY] Industry: [INDUSTRY] Team context: [TEAM CONTEXT] Why the role is open: [WHY OPEN] Must-have skills: [MUST-HAVES] Nice-to-have skills: [NICE-TO-HAVES] Company strengths: [STRENGTHS] Company weaknesses or tradeoffs: [TRADEOFFS] Competitors for talent: [TALENT COMPETITORS] Build the kit using this research sequence: 1. Candidate archetype gallery Create 4 candidate archetypes: - experienced operator - ambitious builder - specialist expert - career switcher or adjacent profile For each archetype include: - background - current job title - likely current employer type - motivations - fears - career trigger - compensation expectation - objections to the role - what would attract them - what would repel them - best sourcing channel 2. Candidate motivation map Map motivations across: - money - title - autonomy - learning - mission - stability - flexibility - manager quality - career acceleration - team quality - technical challenge - customer impact Rank which motivations matter most for this role. 3. Role positioning Write role positioning in three versions: - practical career-growth version - mission and impact version - high-performance challenge version Explain which candidate type each version attracts. 4. Talent competitor comparison Compare [COMPANY NAME] against likely employers competing for the same candidates. Include: - where the company wins - where the company loses - how to frame the tradeoff honestly - what not to overpromise 5. Sourcing channel plan Recommend channels: - LinkedIn search - referrals - industry communities - niche job boards - direct outreach - universities or bootcamps - past applicants - internal promotion - agencies - events For each channel include target candidate type, message angle, and success metric. 6. Candidate objection bank List likely objections and write honest responses for each. Rules: - Do not define the ideal candidate only by years of experience. - Do not overpromise culture, growth, or compensation. - Do not ignore why strong candidates would say no. - Separate facts from assumptions. --------------------------------------------------------------------------------

#163Job Description Conversion Rewrite Lab

HIRING, HR & PERFORMANCE MANAGEMENTRecruiters, HR leaders, founders, hiring managers, startups, agencies, and companies whose job posts attract too many irrelevant applicants or too few strong ones.

Rewrite a job description so it attracts the right candidates, filters out poor-fit applicants, and clearly explains outcomes, expectations, tradeoffs, and hiring process.

You are a job description conversion editor. Rewrite the job description for [ROLE TITLE] so it is clear, specific, appealing, honest, and aligned with the real work. Inputs: Company: [COMPANY NAME] Role title: [ROLE TITLE] Original job description: [PASTE JOB DESCRIPTION] Role scorecard or responsibilities: [ROLE DETAILS] Must-have requirements: [MUST-HAVES] Nice-to-have requirements: [NICE-TO-HAVES] Compensation / benefits: [COMPENSATION / BENEFITS] Location / schedule: [LOCATION / SCHEDULE] Hiring process: [HIRING PROCESS] Company culture: [CULTURE] Reasons candidates should join: [REASONS TO JOIN] Tradeoffs candidates should know: [TRADEOFFS] Legal or compliance requirements: [REQUIREMENTS] Rewrite the job description in this lab format: Step A - Diagnose the current post Identify: - vague sections - inflated requirements - unclear role outcomes - generic culture language - missing compensation clarity - missing candidate benefits - unrealistic expectations - jargon - biased or exclusionary language - weak application CTA Step B - Build the message spine Define: - role promise - core mission - first-year outcomes - ideal candidate profile - reasons to join - reasons not to join - hiring process promise Step C - Write the improved job post Use this structure: 1. Short role hook 2. Why this role matters 3. What you will own 4. What success looks like in the first 90 days 5. What success looks like in the first year 6. What we are looking for 7. What is useful but not required 8. How we work 9. Compensation and benefits 10. Hiring process 11. Equal opportunity / inclusion statement, if applicable 12. Clear application CTA Step D - Candidate filter questions Write 5 application questions that reveal fit without creating unnecessary friction. Step E - Quality check Score the new job post on: - clarity - specificity - appeal - honesty - inclusiveness - filtering power - candidate trust Rules: - Do not use exaggerated phrases like "rockstar" or "ninja." - Do not require credentials unless they are truly necessary. - Do not hide major tradeoffs. - Do not make the role sound bigger or smaller than it is. --------------------------------------------------------------------------------

#164Structured Interview Architecture Studio

HIRING, HR & PERFORMANCE MANAGEMENTHiring managers, HR teams, recruiters, founders, interview panels, talent teams, and companies that want fairer and more consistent hiring decisions.

Create a structured interview process with stages, competencies, questions, scorecards, work samples, calibration rules, and decision criteria.

Act as a structured hiring architect. Design a complete interview process for [ROLE TITLE] at [COMPANY NAME] that evaluates job-relevant evidence instead of interview vibes. Role inputs: Company: [COMPANY NAME] Role: [ROLE TITLE] Seniority: [SENIORITY] Department: [DEPARTMENT] Role scorecard: [ROLE SCORECARD] Must-have competencies: [COMPETENCIES] Dealbreakers: [DEALBREAKERS] Hiring team: [HIRING TEAM] Number of interview stages: [STAGES] Work sample options: [WORK SAMPLE OPTIONS] Candidate experience requirements: [CANDIDATE EXPERIENCE] Timeline: [TIMELINE] Design the interview architecture: Module 1 - Hiring criteria Create 6-10 evaluation criteria. For each criterion include: - definition - why it matters - evidence to collect - strong signal - weak signal - red flag - interviewer owner Module 2 - Interview stages Design the process: - recruiter screen - hiring manager interview - technical / functional interview - behavioral interview - work sample or case task - cross-functional interview - final decision conversation - reference check For each stage include: - purpose - duration - interviewer - questions - what must be scored - what must not be evaluated - pass / fail standard Module 3 - Question bank Create structured questions for: - past performance - judgment - problem-solving - collaboration - ownership - communication - learning ability - role-specific expertise - values alignment - conflict handling Include follow-up probes for each question. Module 4 - Work sample design Create a realistic work sample with: - prompt - context - time limit - expected output - scoring rubric - what good looks like - what weak looks like - candidate instructions Module 5 - Interview scorecard Create a 1-5 scoring system with evidence requirements. Module 6 - Decision meeting Write a decision meeting agenda: - evidence review - score comparison - concerns - tradeoffs - bias check - final recommendation - follow-up actions Rules: - Do not ask illegal, irrelevant, or personal questions. - Do not let each interviewer evaluate the same thing unless intentionally calibrated. - Do not use culture fit as a vague rejection reason. - Every hiring decision must connect to job-relevant evidence. --------------------------------------------------------------------------------

#165Interview Calibration & Bias Control Board

HIRING, HR & PERFORMANCE MANAGEMENTHR leaders, recruiters, hiring managers, interview panels, DEI teams, founders, and companies scaling hiring across multiple managers.

Help interview panels align on standards, reduce inconsistent scoring, catch bias, and make hiring decisions based on evidence.

You are an interview calibration facilitator. Create a calibration system for the hiring panel evaluating [ROLE TITLE] so interviewers apply the same standards and reduce bias. Context: Company: [COMPANY NAME] Role: [ROLE TITLE] Interview panel: [PANEL] Role scorecard: [SCORECARD] Competencies: [COMPETENCIES] Candidate pool: [CANDIDATE POOL] Past hiring issues: [ISSUES] Scoring system: [SCORING SYSTEM] Company values: [VALUES] Decision timeline: [TIMELINE] Create the calibration board: Board Section 1 - Shared standard For each competency, define: - what a 5 looks like - what a 3 looks like - what a 1 looks like - minimum acceptable evidence - disqualifying evidence - what does not count as evidence Board Section 2 - Bias traps Identify likely bias risks: - halo effect - similarity bias - pedigree bias - confidence bias - communication style bias - recency bias - accent or language bias - overvaluing charisma - undervaluing quiet competence - "culture fit" misuse - over-indexing on one weak answer For each include how to prevent it. Board Section 3 - Interviewer assignments Assign each interviewer: - competencies to evaluate - questions to ask - evidence to collect - topics to avoid - scoring responsibility Board Section 4 - Candidate evidence grid Create a grid format: - candidate - competency - evidence observed - score - confidence level - concern - follow-up needed Board Section 5 - Debrief rules Define decision meeting rules: - scores submitted before discussion - evidence before opinion - no vague labels - separate trainable gaps from role-critical gaps - discuss tradeoffs - document reason Board Section 6 - Final decision logic Create decision categories: - strong hire - hire with support plan - mixed evidence, follow-up needed - no hire - future pipeline Rules: - Do not let the loudest interviewer decide. - Do not accept "I just liked them" as evidence. - Do not penalize candidates for style differences unrelated to job success. - Do not lower the bar without naming the tradeoff. --------------------------------------------------------------------------------

#166Hiring Funnel Diagnostic & Repair System

HIRING, HR & PERFORMANCE MANAGEMENTRecruiters, HR leaders, founders, talent acquisition teams, agencies, scaling startups, and companies with slow hiring or poor candidate conversion.

Diagnose and improve a hiring funnel across sourcing, applications, screening, interviews, offers, acceptance, and candidate experience.

Act as a hiring funnel diagnostician. Audit the hiring funnel for [ROLE TITLE / TEAM] and identify the biggest leaks, delays, quality problems, and candidate experience risks. Inputs: Company: [COMPANY NAME] Role or role family: [ROLE / ROLE FAMILY] Hiring goal: [HIRING GOAL] Open roles: [OPEN ROLES] Sourcing channels: [CHANNELS] Application numbers: [APPLICATION DATA] Screening numbers: [SCREENING DATA] Interview conversion: [INTERVIEW DATA] Offer data: [OFFER DATA] Acceptance rate: [ACCEPTANCE RATE] Time to fill: [TIME TO FILL] Time in stage: [TIME IN STAGE] Candidate feedback: [FEEDBACK] Hiring manager feedback: [MANAGER FEEDBACK] Recruiter capacity: [CAPACITY] Current process: [PROCESS] Run the diagnostic: Funnel Stage Review Analyze: 1. Sourcing to application 2. Application to screen 3. Screen to hiring manager interview 4. Interview to work sample 5. Work sample to final 6. Final to offer 7. Offer to acceptance 8. Acceptance to start date For each stage identify: - volume - conversion rate - quality signal - delay - candidate drop-off - manager bottleneck - process friction - likely root cause - recommended fix Candidate Quality Lens Assess whether the funnel has: - enough qualified candidates - too many unqualified applicants - too narrow sourcing - unclear job description - weak employer positioning - slow response time - unrealistic requirements - compensation mismatch Candidate Experience Lens Identify moments where candidates may feel: - ignored - confused - over-tested - under-informed - misled - rushed - disrespected - uncertain about timeline Bottleneck Ranking Rank bottlenecks by: - hiring impact - candidate quality impact - speed impact - candidate trust impact - ease of fixing Repair Plan Create: - quick fixes this week - process fixes this month - sourcing experiments - JD changes - interview changes - manager SLA - candidate communication improvements - metrics dashboard Rules: - Do not assume the problem is sourcing before checking conversion. - Do not speed up hiring by weakening evaluation quality. - Do not ignore candidate trust. - Mark missing funnel data as [NEEDS DATA]. --------------------------------------------------------------------------------

#167Reference Check Intelligence Script

HIRING, HR & PERFORMANCE MANAGEMENTHiring managers, recruiters, HR teams, executives, founders, and anyone making final-stage hiring decisions.

Create a reference check system that validates strengths, risks, management needs, performance patterns, and role fit without relying on generic praise.

You are a reference check strategist. Build a reference check script for [CANDIDATE NAME] for the role of [ROLE TITLE] that collects useful evidence for the hiring decision. Inputs: Candidate: [CANDIDATE NAME] Role: [ROLE TITLE] Company: [COMPANY NAME] Role scorecard: [SCORECARD] Interview strengths: [STRENGTHS] Interview concerns: [CONCERNS] Work sample results: [WORK SAMPLE] Reference relationship: [REFERENCE RELATIONSHIP] Seniority of role: [SENIORITY] Key risks to validate: [RISKS] Legal / policy constraints: [CONSTRAINTS] Create the reference check system: Opening script Write a professional opening that: - confirms the reference's relationship to the candidate - explains the purpose - sets confidentiality expectations where appropriate - asks for candid, job-relevant feedback Validation Map For each hiring criterion, create: - what we need to validate - question to ask - follow-up probe - strong signal - weak signal - concerning signal Question Sequence Create questions in this order: 1. Relationship and context 2. Scope of candidate's role 3. Strengths in real work 4. Examples of outcomes delivered 5. Collaboration style 6. Communication style 7. Ownership and reliability 8. Judgment under pressure 9. Feedback and coachability 10. Weaknesses or development areas 11. Management style needed 12. Role-specific skill validation 13. Would you rehire them? 14. What should we know to help them succeed? Concern Testing Write tactful questions to validate specific concerns: - [CONCERN 1] - [CONCERN 2] - [CONCERN 3] Signal Interpretation Guide Classify answers as: - clear positive evidence - neutral evidence - unclear evidence - risk signal - disqualifying concern Reference Summary Template Create a summary format: - reference credibility - confirmed strengths - confirmed risks - management needs - role fit - confidence level - hiring recommendation impact Rules: - Do not ask inappropriate personal questions. - Do not accept vague praise without examples. - Do not use reference checks only as a formality. - Respect applicable employment law and company policy. --------------------------------------------------------------------------------

#168Compensation Band & Offer Strategy Builder

HIRING, HR & PERFORMANCE MANAGEMENTHR leaders, founders, finance teams, recruiters, hiring managers, compensation analysts, and companies building offer packages.

Create a compensation and offer strategy that balances market competitiveness, internal equity, budget, candidate motivation, and retention risk.

Act as a compensation strategy advisor. Build a compensation band and offer strategy for [ROLE TITLE] at [COMPANY NAME] that is competitive, fair, and financially responsible. Inputs: Company: [COMPANY NAME] Role: [ROLE TITLE] Level: [LEVEL] Location / remote policy: [LOCATION] Employment type: [EMPLOYMENT TYPE] Budget range: [BUDGET] Current internal salaries for similar roles: [INTERNAL DATA] Market data available: [MARKET DATA] Candidate expectations: [CANDIDATE EXPECTATIONS] Benefits: [BENEFITS] Bonus / commission / equity: [VARIABLE COMP] Business constraints: [CONSTRAINTS] Retention risks: [RETENTION RISKS] Pay philosophy: [PAY PHILOSOPHY] Legal / compliance constraints: [CONSTRAINTS] Build the strategy: 1. Compensation philosophy for this role Define whether the company should lead, match, or lag the market and why. 2. Band architecture Create: - minimum - midpoint - maximum - entry criteria - midpoint criteria - top-of-band criteria - growth path - review cadence 3. Internal equity check Analyze: - salary compression risk - fairness across current employees - manager pay relationships - promotion implications - retention concerns - communication sensitivity 4. Candidate offer strategy Create offer packages for: - budget-conscious offer - target offer - stretch offer - high-priority candidate offer For each include: - base salary - variable compensation - benefits - flexibility - title - growth opportunity - start-date strategy - negotiation room 5. Total rewards positioning Write how to explain the offer honestly, including: - cash compensation - benefits - learning - flexibility - mission - team - career growth - stability - tradeoffs 6. Negotiation guide Create responses for: - candidate asks above range - candidate has competing offer - candidate values flexibility over cash - candidate asks for title increase - candidate asks for equity - candidate questions fairness Rules: - Do not create compensation that breaks internal equity. - Do not hide major compensation constraints. - Do not compete only on salary if the company cannot win there. - This is not legal advice; align with local pay transparency and employment requirements. --------------------------------------------------------------------------------

#169New Hire Onboarding Ramp Map

HIRING, HR & PERFORMANCE MANAGEMENTHR teams, managers, founders, department heads, people operations teams, startups, agencies, and companies with inconsistent onboarding.

Design a role-specific onboarding plan that helps a new hire learn context, build relationships, deliver early wins, and become productive faster.

You are an onboarding experience architect. Create a role-specific onboarding ramp map for [NEW HIRE ROLE] at [COMPANY NAME]. Inputs: Company: [COMPANY NAME] New hire role: [ROLE] Department: [DEPARTMENT] Manager: [MANAGER] Start date: [START DATE] Work setup: [REMOTE / HYBRID / IN-PERSON] Role scorecard: [SCORECARD] Key systems: [TOOLS / SYSTEMS] Key stakeholders: [STAKEHOLDERS] Training materials: [TRAINING MATERIALS] First projects: [FIRST PROJECTS] Known onboarding problems: [PROBLEMS] Compliance requirements: [COMPLIANCE] Success expectations: [EXPECTATIONS] Design the ramp map: Pre-boarding Create actions for: - offer accepted to start date - equipment / access - welcome communication - documents - schedule - manager preparation - team announcement Day 1 Experience Create: - agenda - welcome message - first manager conversation - systems access checklist - cultural orientation - first low-risk task - end-of-day check-in Week 1 Learning Path Define: - company context - team context - customer context - role expectations - tools training - process training - stakeholder introductions - first deliverable 30-Day Ramp Define: - knowledge to learn - relationships to build - tasks to complete - questions to answer - manager support - success signals - risk signals 60-Day Ramp Define: - ownership increase - quality expectations - independent work - feedback loops - process improvement opportunity 90-Day Ramp Define: - full role ownership - performance baseline - development plan - future goals - retention check Onboarding Artifacts Create: - new hire checklist - manager checklist - buddy checklist - first 30 questions to answer - role-specific resource list - 30/60/90 review template Rules: - Do not make onboarding only HR paperwork. - Do not overload the new hire on day one. - Do not assume the manager knows how to onboard. - Onboarding must connect learning to early role outcomes. --------------------------------------------------------------------------------

#170Probation & First 90-Day Success Tracker

HIRING, HR & PERFORMANCE MANAGEMENTManagers, HR teams, founders, people operations, department heads, and organizations with probation periods or structured early performance reviews.

Create a fair first-90-day evaluation system that tracks ramp progress, role fit, feedback, support needs, and probation decisions.

Act as a first-90-day performance advisor. Build a probation and early success tracker for [EMPLOYEE / ROLE] that helps the manager evaluate progress fairly and support the employee properly. Inputs: Employee role: [ROLE] Start date: [START DATE] Probation period: [PERIOD] Role expectations: [EXPECTATIONS] Onboarding plan: [ONBOARDING PLAN] Manager: [MANAGER] Key responsibilities: [RESPONSIBILITIES] Training completed: [TRAINING] Early deliverables: [DELIVERABLES] Observed strengths: [STRENGTHS] Observed concerns: [CONCERNS] Feedback already given: [FEEDBACK] Support provided: [SUPPORT] Company policy: [POLICY] Build the tracker: Success Milestones Create milestones for: - first week - 30 days - 60 days - 90 days For each milestone include: - expected knowledge - expected behavior - expected output - collaboration expectation - quality standard - evidence required - manager check-in questions Progress Categories Classify progress as: - ahead of ramp - on track - mixed progress - at risk but recoverable - serious concern - poor fit Define evidence for each category. Early Warning Signs Identify warning signs across: - skill - reliability - communication - quality - attitude - learning speed - role fit - values alignment - judgment - teamwork Manager Support Plan Create support options: - extra training - clearer expectations - shadowing - more frequent check-ins - workload adjustment - documented feedback - mentor / buddy - process clarification Probation Review Template Create: - summary of progress - evidence of success - evidence of concern - employee self-reflection - manager assessment - support provided - decision options - next steps Decision Paths Write guidance for: - confirm employment - extend probation, if policy allows - change role scope - create improvement plan - end employment, if appropriate and policy-aligned Rules: - Do not surprise the employee at the final review. - Do not confuse onboarding gaps with performance failure. - Do not ignore serious early warning signs. - This is not legal advice; follow company policy and local employment law. --------------------------------------------------------------------------------

#171Performance Review Evidence Synthesizer

HIRING, HR & PERFORMANCE MANAGEMENTManagers, HR teams, employees preparing self-reviews, founders, department heads, and organizations improving review quality.

Convert messy notes, goals, feedback, metrics, and examples into a fair, balanced, evidence-based performance review.

You are a performance review synthesis expert. Create an evidence-based performance review for [EMPLOYEE / ROLE] using the information provided. Review context: Employee: [EMPLOYEE] Role: [ROLE] Review period: [PERIOD] Goals: [GOALS] KPIs / metrics: [METRICS] Projects completed: [PROJECTS] Examples of strong performance: [STRONG EXAMPLES] Examples of missed expectations: [MISSED EXPECTATIONS] Peer feedback: [PEER FEEDBACK] Customer feedback: [CUSTOMER FEEDBACK] Manager notes: [MANAGER NOTES] Employee self-review: [SELF-REVIEW] Role expectations: [EXPECTATIONS] Rating scale, if any: [RATING SCALE] Synthesize the review: Evidence Inventory Separate evidence into: - outcomes delivered - behaviors observed - collaboration examples - customer impact - quality examples - leadership examples - missed commitments - repeated patterns - one-off incidents - unsupported opinions Performance Themes Identify 3-5 major themes. For each theme include: - summary - supporting evidence - business or team impact - strength or development area - confidence level Balanced Review Draft Write: 1. Overall performance summary 2. Key achievements 3. Strengths demonstrated 4. Areas for improvement 5. Examples and evidence 6. Growth opportunities 7. Goals for next period 8. Support the manager will provide 9. Suggested rating, if applicable Bias and Fairness Check Check for: - recency bias - vague criticism - personality judgments - inconsistent standards - missing evidence - overemphasis on one incident - ignoring context - inflated praise without evidence Conversation Guide Create a manager script for discussing: - positive feedback - constructive feedback - disagreement - next goals - development support Rules: - Do not invent evidence. - Do not include personal judgments unrelated to work. - Do not soften serious performance issues so much that expectations become unclear. - Do not let one recent event dominate the entire review unless it was highly significant. --------------------------------------------------------------------------------

#172Feedback Conversation Script Studio

HIRING, HR & PERFORMANCE MANAGEMENTManagers, team leads, HR partners, founders, executives, and anyone preparing for a difficult feedback conversation.

Create clear, respectful scripts for giving feedback about behavior, performance, quality, communication, collaboration, or leadership issues.

Act as a management communication coach. Prepare a feedback conversation script for [MANAGER] to discuss [FEEDBACK TOPIC] with [EMPLOYEE / ROLE]. Conversation inputs: Manager: [MANAGER] Employee / role: [EMPLOYEE / ROLE] Feedback topic: [TOPIC] Observed behavior: [OBSERVED BEHAVIOR] Specific examples: [EXAMPLES] Impact: [IMPACT] Expected behavior: [EXPECTED BEHAVIOR] Previous conversations: [PREVIOUS CONVERSATIONS] Employee strengths: [STRENGTHS] Possible context: [POSSIBLE CONTEXT] Desired outcome: [OUTCOME] Conversation sensitivity: [LOW / MEDIUM / HIGH] Company policy considerations: [POLICY] Build the script studio output: 1. Conversation objective State what the conversation must accomplish in one sentence. 2. Manager mindset Write 5 reminders for the manager to stay fair, calm, direct, and curious. 3. Opening script Write a concise opening that: - names the topic - explains why it matters - avoids blame - sets a constructive tone 4. Evidence statement Write the feedback using this pattern: "When [specific behavior] happened in [specific context], the impact was [impact]. The expectation is [standard]." 5. Curiosity questions Create questions to understand context without backing away from the standard. 6. Employee response paths Prepare manager responses if the employee: - agrees - disagrees - becomes defensive - blames others - gets emotional - is silent - says expectations were unclear - asks what to do differently 7. Agreement and next steps Write language for: - behavior change - support offered - follow-up date - success evidence - documentation, if needed 8. Follow-up message Draft a short written recap after the conversation. Rules: - Do not use vague feedback. - Do not diagnose motives. - Do not avoid the impact. - Do not make the conversation sound like a legal notice unless the situation requires formal action. - Keep the tone direct, respectful, and evidence-based. --------------------------------------------------------------------------------

#173Career Ladder & Promotion Packet Builder

HIRING, HR & PERFORMANCE MANAGEMENTHR leaders, managers, department heads, founders, people operations, growing companies, and teams where promotions feel unclear or inconsistent.

Create clear career levels, promotion criteria, evidence requirements, development actions, and promotion packet templates.

You are a career architecture specialist. Build a career ladder and promotion packet system for [ROLE FAMILY] at [COMPANY NAME]. Inputs: Company: [COMPANY NAME] Role family: [ROLE FAMILY] Current roles and levels: [CURRENT LEVELS] Team size: [TEAM SIZE] Business needs: [BUSINESS NEEDS] Current promotion problems: [PROMOTION PROBLEMS] Skills required: [SKILLS] Behavior expectations: [BEHAVIORS] Performance metrics: [METRICS] Compensation bands, if available: [BANDS] Manager feedback: [MANAGER FEEDBACK] Employee questions: [EMPLOYEE QUESTIONS] Build the career system: Ladder Structure Create levels such as: - Level 1: Associate / Junior - Level 2: Specialist / Intermediate - Level 3: Independent Owner - Level 4: Senior - Level 5: Lead / Principal - Level 6: Manager or Head, if relevant For each level define: - scope - autonomy - complexity - decision rights - quality standard - collaboration expectations - communication expectations - business impact - examples of work - what is not expected yet Skill Progression Matrix Create a matrix across: - functional expertise - problem-solving - execution - communication - collaboration - customer or stakeholder judgment - leadership - process improvement - commercial awareness Promotion Readiness Criteria For each level transition define: - required outcomes - required behaviors - evidence required - minimum consistency period - common gaps - manager responsibilities - employee responsibilities Promotion Packet Template Create a template with: - employee summary - current level - proposed level - evidence by criterion - business impact - peer / stakeholder input - manager recommendation - risk or development gaps - compensation implication - final decision Promotion Governance Define: - review cadence - decision makers - calibration process - fairness checks - communication to employee Rules: - Do not make promotion only about tenure. - Do not create criteria that reward politics over impact. - Do not require management responsibilities for every growth path. - Make promotion decisions evidence-based and explainable. --------------------------------------------------------------------------------

#174Performance Improvement Support Path

HIRING, HR & PERFORMANCE MANAGEMENTManagers, HR business partners, founders, people operations, department heads, and organizations handling performance issues carefully.

Create a supportive, measurable improvement path for an employee who is underperforming, with clear expectations, support, timelines, and decision points.

You are an HR performance improvement advisor. Build a performance improvement support path for [EMPLOYEE / ROLE] that is clear, humane, measurable, and policy-aligned. Inputs: Employee role: [ROLE] Performance concern: [CONCERN] Specific examples: [EXAMPLES] Expected standard: [STANDARD] Impact on team / customer / business: [IMPACT] Previous feedback: [PREVIOUS FEEDBACK] Employee explanation or context: [EMPLOYEE CONTEXT] Support already given: [SUPPORT GIVEN] Possible root causes: [ROOT CAUSES] Manager notes: [MANAGER NOTES] Company policy: [POLICY] Timeline: [TIMELINE] Severity: [SEVERITY] Create the support path: 1. Situation summary Write a factual summary separating: - facts observed - expectations missed - impact - context known - assumptions not confirmed 2. Improvement goals Create 3-5 goals. For each goal include: - expected behavior or output - measurable standard - examples of success - examples of failure - deadline - evidence source 3. Support commitments Define what the manager / company will provide: - training - documentation - coaching - examples - tools - workload clarity - feedback cadence - access to resources 4. Employee commitments Define what the employee must do: - behaviors - deliverables - communication - documentation - escalation - learning actions - deadlines 5. Check-in plan Create a weekly check-in format: - progress review - evidence review - blockers - support needed - next commitment - manager note 6. Decision points Define outcomes: - improvement achieved - partial improvement - no improvement - role mismatch - escalation to formal process - exit decision, if applicable and policy-aligned 7. Conversation scripts Write: - first conversation script - midpoint review script - final review script - written recap template Rules: - Do not create vague goals. - Do not use the plan as a surprise punishment. - Do not ignore whether the manager or system contributed to the problem. - This is not legal advice; align with HR policy and employment law. --------------------------------------------------------------------------------

#175HR Policy Communication Translator

HIRING, HR & PERFORMANCE MANAGEMENTHR teams, people operations, founders, managers, internal communications, legal-adjacent HR work, and companies rolling out policy changes.

Translate HR policies into clear, human, employee-friendly communication without losing accuracy, boundaries, or compliance intent.

Act as an HR policy communication translator. Rewrite or explain [POLICY NAME] so employees understand what it means, why it exists, what they must do, and where to ask questions. Inputs: Policy name: [POLICY NAME] Original policy text: [PASTE POLICY] Audience: [AUDIENCE] Reason for policy: [REASON] What changed, if anything: [WHAT CHANGED] Employee concerns: [CONCERNS] Required compliance language: [REQUIRED LANGUAGE] Tone: [TONE] Channels: [EMAIL / HANDBOOK / SLACK / ALL-HANDS / FAQ] Legal review needed: [YES / NO] Translate the policy: Plain-English Summary Explain in simple language: - what the policy is - who it applies to - why it exists - what employees need to do - what managers need to do - what happens if there are questions or exceptions Employee FAQ Create questions employees are likely to ask: - what does this mean for me? - when does it start? - what changed? - what is allowed? - what is not allowed? - how do I request an exception? - who approves? - where is this documented? - what happens if there is a mistake? Manager Guidance Write manager-specific guidance: - how to explain the policy - what not to say - when to escalate to HR - how to handle exceptions - how to document issues Communication Versions Create: - short Slack / Teams announcement - email announcement - handbook summary - all-hands talking points - manager briefing note Risk Review Flag: - language that may sound punitive - ambiguous terms - missing examples - possible employee concerns - sections needing legal review Rules: - Do not change the meaning of the policy. - Do not remove required compliance language. - Do not make promises the company has not approved. - Mark anything that requires legal review as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#176Employee Engagement Pulse Interpreter

HIRING, HR & PERFORMANCE MANAGEMENTHR leaders, founders, executives, managers, people operations, culture teams, and organizations running engagement surveys.

Turn employee survey or pulse data into clear themes, root causes, risks, leadership actions, and communication plans.

You are an employee engagement analyst. Analyze the employee pulse data below and convert it into practical leadership actions. Data inputs: Company / team: [COMPANY / TEAM] Survey period: [PERIOD] Survey questions: [QUESTIONS] Survey scores: [SCORES] Open-text comments: [COMMENTS] Participation rate: [PARTICIPATION] Employee segments: [SEGMENTS] Previous survey data: [PREVIOUS DATA] Recent company changes: [CHANGES] Known leadership concerns: [CONCERNS] Business context: [CONTEXT] Interpret the pulse: Signal Summary Create a concise summary of: - strongest positive signals - strongest negative signals - biggest movement since last survey - biggest disagreement between segments - highest-risk theme - most actionable theme Theme Clustering Cluster comments into themes: - leadership trust - communication clarity - workload - manager quality - recognition - growth opportunities - compensation - collaboration - psychological safety - tools and process - mission alignment - performance fairness For each theme include: - score / sentiment - representative employee language - frequency - severity - affected segments - likely root cause - confidence level Risk Matrix Rank risks by: - retention risk - engagement impact - performance impact - culture impact - speed of action needed Action Planning Create action cards: - issue - what leadership should do - what managers should do - what HR should do - what not to do - owner - timeline - success metric Communication Plan Write: - leadership acknowledgement message - what we heard - what we will do - what we cannot change yet - when employees will hear next update Rules: - Do not overreact to one comment unless it signals serious risk. - Do not hide negative themes. - Do not promise action where leadership has not committed. - Do not ask for feedback repeatedly without closing the loop. --------------------------------------------------------------------------------

#177Retention Risk & Stay Interview System

HIRING, HR & PERFORMANCE MANAGEMENTHR leaders, managers, founders, people operations, executives, and teams trying to retain high performers or critical employees.

Identify why valuable employees may leave, what keeps them engaged, what risks must be addressed, and what managers should do next.

Act as a retention strategist. Build a retention risk and stay interview system for [TEAM / EMPLOYEE GROUP] so leaders can understand what keeps people and what may push them out. Inputs: Company / team: [COMPANY / TEAM] Employee group: [EMPLOYEE GROUP] Critical roles: [CRITICAL ROLES] Recent turnover: [TURNOVER] Exit interview themes: [EXIT THEMES] Engagement feedback: [ENGAGEMENT FEEDBACK] Compensation concerns: [COMPENSATION] Manager concerns: [MANAGER CONCERNS] Career growth concerns: [CAREER CONCERNS] Workload concerns: [WORKLOAD] High performers: [HIGH PERFORMERS] Retention goals: [GOALS] Build the retention system: Retention Risk Signals Identify signs of risk: - reduced engagement - missed growth expectations - compensation dissatisfaction - manager relationship strain - workload fatigue - lack of recognition - unclear career path - external market pull - role stagnation - conflict - low trust in leadership - repeated frustration Stay Interview Guide Create questions across: - what keeps you here? - what might cause you to leave? - what work energizes you? - what work drains you? - where do you want to grow? - what support do you need? - how is your manager relationship? - what should leadership understand? - what would make the next year worthwhile? Manager Listening Guide For each type of answer, explain: - what it may mean - follow-up question - action category - escalation need - what not to say Retention Action Menu Create actions across: - compensation review - career path - role redesign - workload adjustment - recognition - flexibility - manager coaching - project opportunity - learning support - conflict repair - leadership communication Risk Scoring Create a retention risk score: Risk = dissatisfaction + external market pull + criticality + low growth + manager friction + workload strain - engagement anchors Retention Plan Template Create: - employee / group - risk level - key motivators - key risks - actions - owner - deadline - follow-up date - confidence level Rules: - Do not ask stay interview questions if leadership will ignore the answers. - Do not promise raises or promotions without approval. - Do not assume high performers are satisfied. - Retention actions must be specific, owned, and followed up. --------------------------------------------------------------------------------

#178Workforce Planning Scenario Model

HIRING, HR & PERFORMANCE MANAGEMENTCEOs, COOs, HR leaders, finance teams, department heads, founders, operations teams, and companies planning hiring budgets or headcount.

Plan staffing needs under different business scenarios using workload, capacity, budget, role gaps, hiring timing, productivity, and risk.

You are a workforce planning analyst. Build a scenario model for [COMPANY / DEPARTMENT] that shows what roles are needed, when they are needed, and what tradeoffs leadership must decide. Inputs: Company / department: [COMPANY / DEPARTMENT] Current headcount: [HEADCOUNT] Current roles: [ROLES] Business goals: [GOALS] Revenue / volume forecast: [FORECAST] Current workload: [WORKLOAD] Productivity assumptions: [PRODUCTIVITY] Budget constraints: [BUDGET] Known capacity gaps: [GAPS] Planned projects: [PROJECTS] Attrition risk: [ATTRITION] Hiring lead times: [LEAD TIMES] Outsourcing options: [OUTSOURCING] Automation options: [AUTOMATION] Build the scenario model: Current Capacity Baseline Estimate: - work demand by function - current capacity - overload areas - underused capacity - single points of failure - critical skill gaps - manager span of control Scenario A - Conservative Assume slower growth or tighter budget. Define: - roles to hire - roles to delay - work to stop or simplify - outsourcing opportunities - risk accepted Scenario B - Base Case Assume expected business plan. Define: - required roles - hiring sequence - timing - budget impact - productivity ramp - dependencies Scenario C - Growth Case Assume faster growth or higher demand. Define: - accelerated hiring needs - leadership layer needs - recruiting capacity - onboarding capacity - culture risk - quality risk Role Priority Matrix Rank potential hires by: - business impact - urgency - workload relief - revenue impact - customer impact - risk reduction - difficulty to hire - budget fit Build / Buy / Borrow Decision For each gap recommend: - hire full-time - hire contractor - outsource - train internal person - automate - stop the work Leadership Decision Memo Write a memo with: - recommended headcount plan - budget implications - roles to approve now - roles to defer - risks if not hired - assumptions to validate - metrics to monitor Rules: - Do not plan headcount only by wish list. - Do not ignore onboarding and manager capacity. - Do not solve every capacity issue with hiring. - Mark weak assumptions as [ASSUMPTION]. --------------------------------------------------------------------------------

#179Hiring Decision Memo Generator

HIRING, HR & PERFORMANCE MANAGEMENTHiring managers, recruiters, HR teams, founders, executives, interview panels, and companies that need documented hiring decisions.

Turn interview evidence, scorecards, references, work samples, compensation fit, risks, and tradeoffs into a clear hire / no-hire recommendation.

You are a hiring decision memo writer. Create a decision-ready memo for [CANDIDATE NAME] for [ROLE TITLE] at [COMPANY NAME]. Inputs: Candidate: [CANDIDATE NAME] Role: [ROLE TITLE] Role scorecard: [SCORECARD] Interview notes: [INTERVIEW NOTES] Scorecard ratings: [RATINGS] Work sample results: [WORK SAMPLE] Reference check notes: [REFERENCES] Strengths: [STRENGTHS] Concerns: [CONCERNS] Compensation expectations: [COMPENSATION] Availability / start date: [AVAILABILITY] Team feedback: [TEAM FEEDBACK] Hiring manager recommendation: [MANAGER RECOMMENDATION] Alternative candidates: [ALTERNATIVES] Decision deadline: [DEADLINE] Write the hiring decision memo: Executive Recommendation Choose one: - strong hire - hire - hire with support plan - hold for more evidence - no hire - future pipeline Explain the recommendation in 3-5 sentences. Evidence Summary Create a table: - criterion - evidence for - evidence against - score - confidence level - decision impact Role Fit Analysis Assess: - skill fit - experience fit - motivation fit - culture contribution - manager fit - team fit - ramp risk - retention risk Risk and Mitigation For each concern include: - concern - evidence - severity - likelihood - mitigation plan - who owns mitigation - whether it is acceptable Offer Strategy, if hire Recommend: - offer positioning - compensation approach - start date - onboarding focus - first 30-day support - manager expectations No-Hire Rationale, if no hire Write a respectful internal rationale that is: - evidence-based - job-relevant - specific - not personality-based - not discriminatory Decision Questions List unresolved questions that must be answered before final decision. Rules: - Do not use vague phrases like "not a culture fit" without evidence. - Do not ignore serious concerns because the candidate is likable. - Do not reject based on non-job-related style differences. - The memo must help leadership make a fair, documented decision. --------------------------------------------------------------------------------

#180Full Hiring, HR & Performance Management Audit

HIRING, HR & PERFORMANCE MANAGEMENTCEOs, founders, HR leaders, people operations, COOs, department heads, consultants, agencies, startups, and companies doing an HR or talent system reset.

Audit the full people system across hiring, onboarding, role clarity, compensation, feedback, performance reviews, development, retention, and workforce planning.

Act as an independent HR and performance management auditor. Review the full hiring, HR, and performance system of [COMPANY NAME] and identify the highest-leverage improvements for talent quality, fairness, clarity, retention, and execution. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Headcount: [HEADCOUNT] Org structure: [ORG STRUCTURE] Current open roles: [OPEN ROLES] Hiring process: [HIRING PROCESS] Job descriptions: [JOB DESCRIPTIONS] Interview scorecards: [SCORECARDS] Candidate funnel data: [FUNNEL DATA] Compensation philosophy: [COMPENSATION] Onboarding process: [ONBOARDING] Role clarity documents: [ROLE CLARITY] Performance review process: [PERFORMANCE PROCESS] Feedback culture: [FEEDBACK CULTURE] Promotion process: [PROMOTION PROCESS] Training and development: [DEVELOPMENT] Engagement data: [ENGAGEMENT] Retention / turnover data: [RETENTION] HR policies: [POLICIES] Workforce plan: [WORKFORCE PLAN] Leadership concerns: [CONCERNS] Audit the people system across 20 dimensions: 1. Workforce planning 2. Role clarity 3. Job description quality 4. Talent attraction 5. Candidate sourcing 6. Hiring funnel performance 7. Structured interviewing 8. Bias control and calibration 9. Hiring decision documentation 10. Compensation and internal equity 11. Offer strategy 12. Onboarding 13. First 90-day ramp 14. Performance expectations 15. Feedback quality 16. Performance reviews 17. Performance improvement process 18. Career ladders and promotion 19. Retention and engagement 20. HR policy communication For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - people risk - legal / compliance risk, if relevant - business risk - fairness risk - recommended fix - confidence level Then synthesize: A. Top 5 people-system constraints Rank by: - business impact - retention impact - fairness impact - hiring impact - urgency - ease of improvement - confidence B. Root cause analysis Identify whether the main issue is: - unclear roles - weak hiring criteria - unstructured interviews - poor candidate experience - compensation mismatch - weak onboarding - vague performance expectations - inconsistent feedback - weak manager capability - unclear promotion path - engagement issues - retention risk - no workforce plan - policy confusion C. Future-state people system Create: - role scorecard system - structured hiring process - interview calibration process - compensation band approach - onboarding ramp - performance review cycle - feedback system - career ladder - retention process - workforce planning cadence D. 30/60/90-day HR improvement plan Create a practical plan with: - actions - owners - templates to create - processes to change - manager training needed - metrics to track - policy reviews - communication plan - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard talent truth - the biggest hiring risk - the biggest performance management gap - the fastest improvement opportunity - the next leadership decision - the data needed before scaling people operations Rules: - Do not invent employee or hiring data. - Do not give legal advice; flag areas requiring HR/legal review. - Do not blame employees before checking role clarity, management, and systems. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on fairness, clarity, job-relevant evidence, retention, and business execution.

#181Partnership Opportunity Thesis Builder

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTFounders, CEOs, partnership leads, business development teams, growth teams, SaaS companies, agencies, marketplaces, service businesses, and companies exploring strategic alliances.

Turn vague partnership ideas into a clear strategic thesis with partner types, value exchange, customer benefit, business impact, and go/no-go criteria.

You are a strategic partnerships advisor. Build a partnership opportunity thesis for [COMPANY NAME] so the team can decide what types of partnerships are worth pursuing and which ones should be ignored. Context packet: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Product / service: [PRODUCT OR SERVICE] Target customers: [CUSTOMERS] Current growth goals: [GROWTH GOALS] Current constraints: [CONSTRAINTS] Existing partners, if any: [EXISTING PARTNERS] Potential partner ideas: [PARTNER IDEAS] Customer journey: [CUSTOMER JOURNEY] Revenue goals: [REVENUE GOALS] Brand positioning: [POSITIONING] Internal resources available: [RESOURCES] Build the partnership thesis: 1. Strategic reason for partnerships Explain why partnerships should exist for this company. Choose the main strategic purpose: - distribution - credibility - product completeness - customer acquisition - customer retention - ecosystem access - operational capacity - cost reduction - market entry - data / insight access - co-branding - revenue expansion Explain why this purpose is stronger than alternatives. 2. Partner category map Identify 6-10 partner categories. For each category include: - partner type - customer overlap - value they bring - value the company brings - likely business model - trust requirement - operational complexity - risk level - example partner profiles 3. Value exchange logic For each partner category define: - what the company gives - what the partner gives - what the customer receives - what each side gains financially - what each side gains strategically - what would make the exchange unfair or unsustainable 4. Partnership fit criteria Create a fit score from 1 to 5 across: - customer overlap - strategic alignment - revenue potential - ease of execution - brand trust - operational fit - data / integration requirements - legal / compliance risk - partner motivation - internal capacity 5. Partnership thesis statement Write: - one-sentence partnership thesis - what partners we want - what partners we avoid - what outcomes partnerships must create - what tradeoffs we accept 6. First partnership bets Recommend the top 5 partnership opportunities to test. For each include: - partner type - why now - first offer - first outreach angle - success metric - risk - next step Rules: - Do not recommend partnerships only because they sound impressive. - Do not ignore whether the partner has a real incentive to participate. - Do not create partnership ideas that require more operational capacity than the company has. - Mark weak assumptions as [ASSUMPTION]. Done when leadership can clearly say what partnerships are for, who to pursue, and why. --------------------------------------------------------------------------------

#182Strategic Partner Landscape Map

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTPartnership teams, business development leaders, founders, market expansion teams, SaaS companies, B2B services, ecommerce brands, marketplaces, and consultants building partner pipelines.

Map the partner ecosystem around a market and identify the highest-potential companies, communities, platforms, influencers, vendors, channels, and ecosystem players.

Act as an ecosystem cartographer. Create a strategic partner landscape map for [COMPANY NAME] in [MARKET / CATEGORY] that reveals where valuable partnerships could come from. Research context: Company: [COMPANY NAME] Market / category: [MARKET] Target customer: [CUSTOMER] Geography: [GEOGRAPHY] Product / service: [PRODUCT / SERVICE] Growth objective: [OBJECTIVE] Known competitors: [COMPETITORS] Known ecosystem players: [KNOWN PLAYERS] Channels already used: [CHANNELS] Partnership goal: [GOAL] Partnership constraints: [CONSTRAINTS] Create the landscape map in these zones: Zone A - Customer access partners Find partner types that already reach the target customer. Include: - communities - newsletters - media companies - influencers - associations - agencies - consultants - platforms - marketplaces - events For each, explain the access mechanism. Zone B - Complementary product partners Identify products or services customers use before, during, or after using [PRODUCT / SERVICE]. For each, explain: - workflow adjacency - integration potential - bundle potential - referral potential - customer value Zone C - Trust and credibility partners Identify institutions or brands that can increase trust. Examples: - certification bodies - expert communities - established vendors - industry leaders - review platforms - education providers Zone D - Distribution partners Identify partners that can sell, refer, resell, implement, or introduce. Separate: - referral partners - affiliates - resellers - implementation partners - agencies - consultants - channel partners - enterprise alliances Zone E - Operational or vendor partners Identify partners that can improve delivery, cost, speed, quality, capacity, or reliability. Zone F - Competitive partnership patterns Analyze how competitors appear to use partnerships. Look for: - integrations - marketplaces - co-marketing - affiliate programs - agency networks - certifications - ecosystem pages - sponsorships - reseller models Output format: Create a table with: - partner category - example profile - why they matter - partnership motion - likely incentive - difficulty - expected impact - first test idea - priority Then create: 1. Top 20 target partner profiles 2. 10 partnership angles to test 3. 5 partner categories to avoid 4. Recommended first 30-day research plan Rules: - Do not list famous companies unless they are realistic targets. - Do not confuse customers with partners. - Do not recommend a partnership type without explaining the incentive. - If real company names are unknown, use partner profiles instead of inventing names. --------------------------------------------------------------------------------

#183Partner Fit Scoring Matrix

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTPartnership managers, founders, business development teams, investor-backed startups, channel teams, agencies, consultants, and companies choosing between partnership opportunities.

Score and prioritize potential partners using strategic alignment, customer overlap, economics, execution complexity, risk, trust, and long-term value.

You are a partnership evaluation analyst. Build a partner fit scoring matrix for the potential partners below and recommend which ones to pursue first. Potential partners: [PASTE PARTNER LIST] Company context: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customer: [TARGET CUSTOMER] Partnership objective: [OBJECTIVE] Current capacity: [CAPACITY] Required outcome: [OUTCOME] Brand constraints: [BRAND CONSTRAINTS] Revenue model: [REVENUE MODEL] Risk concerns: [RISKS] Use this scoring system: Score each partner from 1 to 5 across these dimensions: A. Strategic alignment Does the partner help achieve a core business objective? B. Customer overlap Does the partner already serve the same or adjacent customer? C. Partner motivation Does the partner have a clear reason to collaborate? D. Value exchange balance Does each side receive meaningful value? E. Revenue potential Can the partnership create measurable revenue or pipeline? F. Customer value Will customers clearly benefit? G. Execution simplicity Can the partnership be tested without heavy complexity? H. Brand trust Does the partner improve or protect trust? I. Operational fit Can the company actually deliver on the partnership? J. Risk level Does the partner create legal, brand, delivery, dependency, or customer risk? Calculate: Total Fit Score = A + B + C + D + E + F + G + H + I - Risk Penalty Risk Penalty: - low risk = 0 - moderate risk = 2 - high risk = 5 - severe risk = 10 For each partner provide: - fit score - strongest reason to pursue - strongest reason not to pursue - likely partnership model - best first offer - required internal owner - minimum viable test - success metric - decision recommendation Decision categories: - pursue now - research more - keep warm - reject - avoid After scoring, create: 1. Top 5 priority partners 2. Best low-risk quick win 3. Highest-upside but complex partner 4. Partner with hidden risk 5. Recommended outreach sequence 6. What data is missing before final decision Rules: - Do not rank partners only by brand name. - Do not ignore execution difficulty. - Do not assume the partner cares unless the incentive is clear. - Use [NEEDS DATA] when partner information is missing. --------------------------------------------------------------------------------

#184Co-Marketing Collaboration Blueprint

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTB2B brands, SaaS teams, agencies, creators, newsletters, communities, event teams, partnership marketers, and companies planning webinars, reports, guides, campaigns, or launches with partners.

Design a co-marketing partnership with audience fit, campaign concept, asset plan, promotion responsibilities, lead sharing, metrics, and follow-up.

Act as a co-marketing campaign architect. Build a complete co-marketing blueprint between [COMPANY NAME] and [PARTNER NAME]. Collaboration brief: Company: [COMPANY NAME] Partner: [PARTNER NAME] Company audience: [COMPANY AUDIENCE] Partner audience: [PARTNER AUDIENCE] Shared audience: [SHARED AUDIENCE] Campaign goal: [GOAL] Offer / topic: [OFFER OR TOPIC] Channels available: [CHANNELS] Budget: [BUDGET] Timeline: [TIMELINE] Lead sharing rules: [LEAD RULES] Brand constraints: [BRAND CONSTRAINTS] Compliance constraints: [COMPLIANCE] Existing assets: [ASSETS] Build the blueprint: Campaign concept Create 3 campaign concepts. For each concept include: - name - central idea - audience problem - why both brands should own it - format - lead magnet or CTA - partner value - customer value - risk Choose the strongest concept and explain why. Audience fit Compare: - audience overlap - audience differences - buying stage - trust relationship - likely objections - message angle for each audience Asset plan Create the campaign asset stack: - landing page - registration page - email invites - social posts - newsletter mentions - paid support, if any - webinar / event deck - report or guide - follow-up emails - sales handoff notes - recap content - repurposed clips or posts For each asset assign: - owner - due date - required input - approval owner - success metric Promotion split Define what each partner must do: - email list promotion - social promotion - founder / executive promotion - community promotion - website placement - sales team sharing - retargeting - partner newsletter - post-event follow-up Lead and data rules Define: - what data is collected - who owns leads - who can follow up - consent language needed - data sharing boundaries - reporting access - privacy review needs Campaign timeline Create a timeline across: - planning - asset creation - approval - promotion - launch - live event or campaign peak - follow-up - reporting - retrospective Measurement Track: - registrations - attendance - downloads - qualified leads - pipeline - engagement - partner-sourced revenue - list growth - content reuse - brand lift signals Rules: - Do not create a co-marketing campaign where one side does all the work. - Do not share lead data without clear consent and rules. - Do not let the campaign become generic because two brands are involved. - Make the value for both audiences obvious. --------------------------------------------------------------------------------

#185Channel Partner Program Designer

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTSaaS companies, B2B services, ecommerce brands, agencies, marketplaces, software vendors, consultants, and companies scaling distribution through partners.

Build a channel, reseller, referral, affiliate, or implementation partner program with incentives, tiers, enablement, qualification, governance, and performance metrics.

You are a channel program strategist. Design a partner program for [COMPANY NAME] that allows the company to grow through qualified partners without losing control of customer experience. Program context: Company: [COMPANY NAME] Product / service: [PRODUCT / SERVICE] Target customers: [CUSTOMERS] Partner type: [REFERRAL / RESELLER / AFFILIATE / AGENCY / IMPLEMENTATION / INTEGRATION / OTHER] Current partner motion: [CURRENT MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Customer success requirements: [SUCCESS REQUIREMENTS] Support capacity: [SUPPORT CAPACITY] Margin / commission constraints: [MARGIN] Brand standards: [BRAND STANDARDS] Legal / compliance constraints: [CONSTRAINTS] Design the program: 1. Program model Choose the best model: - referral partner - affiliate - reseller - value-added reseller - implementation partner - integration partner - strategic alliance - certified expert network Explain why this model fits the economics and customer journey. 2. Partner qualification Define qualification criteria: - audience access - customer trust - domain expertise - sales capability - implementation capability - brand fit - support quality - ethical standards - geographic fit - technical ability - financial reliability 3. Partner tiers Create 3-4 tiers. For each tier include: - requirements - benefits - commission / margin - enablement access - support level - certification requirement - co-marketing rights - performance expectations - review cadence 4. Incentive structure Design: - referral fees - recurring commission - one-time commission - revenue share - implementation margin - bonuses - co-marketing funds - non-cash incentives - clawback rules 5. Enablement system Create: - partner onboarding - training modules - sales scripts - demo assets - objection handling - pricing rules - case studies - implementation checklist - customer handoff process - partner portal structure 6. Governance Define: - deal registration - customer ownership - discount authority - brand usage rules - customer support boundaries - conflict rules - termination criteria 7. Metrics Track: - active partners - partner-sourced pipeline - partner-sourced revenue - conversion rate - average deal size - customer retention - partner activation - enablement completion - support issues - channel conflict Rules: - Do not overpay partners for deals they did not influence. - Do not allow partners to misrepresent the offer. - Do not launch a channel program without enablement. - Customer experience must remain protected. --------------------------------------------------------------------------------

#186Vendor Selection RFP Builder

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTOperations teams, procurement, finance, IT, HR, marketing teams, restaurant groups, retail operators, agencies, SaaS buyers, and companies choosing vendors.

Create a clear request for proposal that defines business needs, requirements, evaluation criteria, timelines, vendor questions, pricing format, and decision process.

Act as a procurement and vendor selection specialist. Build an RFP for selecting a vendor for [VENDOR CATEGORY / SERVICE]. Business need: Company: [COMPANY NAME] Vendor category: [CATEGORY] Problem to solve: [PROBLEM] Current vendor or process: [CURRENT STATE] Scope needed: [SCOPE] Locations / departments affected: [LOCATIONS / DEPARTMENTS] Volume / usage: [VOLUME] Budget range: [BUDGET] Timeline: [TIMELINE] Must-have requirements: [MUST-HAVES] Nice-to-have requirements: [NICE-TO-HAVES] Integration needs: [INTEGRATIONS] Compliance / legal needs: [COMPLIANCE] Service expectations: [SERVICE EXPECTATIONS] Decision makers: [DECISION MAKERS] Create the RFP document: Section 1 - Company and project overview Write a concise overview of: - who the company is - why the vendor is needed - what outcome the company expects - what success looks like Section 2 - Scope of work Define: - included services - excluded services - deliverables - locations / users / departments - expected volume - required timeline - support needs - reporting needs Section 3 - Vendor requirements Separate: - mandatory requirements - preferred requirements - technical requirements - operational requirements - compliance requirements - service-level requirements - documentation requirements Section 4 - Vendor response format Ask vendors to provide: - company overview - relevant experience - proposed solution - implementation plan - staffing / account team - service model - pricing - assumptions - risks - references - contract terms - differentiators Section 5 - Pricing template Create a pricing table that makes proposals comparable. Include: - one-time fees - recurring fees - usage-based fees - implementation costs - support costs - training costs - add-ons - minimum commitments - cancellation costs - hidden fees to disclose Section 6 - Evaluation scorecard Create scoring criteria with weights: - fit to requirements - total cost - service reliability - implementation plan - vendor experience - support model - risk - contract flexibility - references - strategic fit Section 7 - Timeline and process Define: - RFP release date - vendor questions deadline - proposal due date - demo dates - finalist selection - reference checks - decision date - implementation target Rules: - Do not write vague requirements that vendors can interpret however they want. - Do not let pricing be submitted in incomparable formats. - Do not ask for unnecessary information that slows evaluation. - Mark anything requiring legal review as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#187Vendor Due Diligence Risk Screen

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTProcurement teams, operations leaders, finance teams, IT, HR, legal-adjacent teams, vendor managers, and companies making high-risk vendor decisions.

Evaluate a vendor before signing by checking operational reliability, financial risk, references, security, compliance, service capacity, reputation, and dependency exposure.

You are a vendor due diligence analyst. Create a due diligence screen for [VENDOR NAME] before [COMPANY NAME] signs or renews an agreement. Vendor context: Vendor: [VENDOR NAME] Vendor category: [CATEGORY] Service / product provided: [SERVICE] Business-criticality: [LOW / MEDIUM / HIGH / MISSION-CRITICAL] Spend level: [SPEND] Contract length: [CONTRACT LENGTH] Data access level: [DATA ACCESS] Customer impact if vendor fails: [CUSTOMER IMPACT] Operational dependency: [DEPENDENCY] Current concerns: [CONCERNS] Available vendor materials: [MATERIALS] References: [REFERENCES] Compliance requirements: [COMPLIANCE] Run the due diligence screen: Risk Area 1 - Operational capability Evaluate: - ability to deliver scope - staffing capacity - implementation process - support model - escalation process - business continuity - quality control - reporting Risk Area 2 - Financial and commercial stability Evaluate: - pricing clarity - hidden cost risk - payment terms - dependency on one contract - financial stability signals - insurance - long-term viability Risk Area 3 - Security and data Evaluate: - data access - data storage - access controls - security certifications - incident response - subcontractors - privacy obligations - data deletion process Risk Area 4 - Compliance and legal Evaluate: - required licenses - certifications - regulatory fit - contract terms - audit rights - indemnity - liability limits - service obligations Risk Area 5 - Reputation and references Evaluate: - customer references - review patterns - case studies - public issues - litigation or controversy signals - responsiveness during sales process Risk Area 6 - Dependency and exit risk Evaluate: - switching difficulty - migration needs - proprietary lock-in - knowledge concentration - termination support - replacement options Create output: A. Vendor risk score Score each area from 1 to 5 and provide total risk level. B. Required questions for vendor Write 25 due diligence questions. C. Required documents List documents to request. D. Reference check script Create 12 questions to ask references. E. Risk mitigation plan For each major risk include: - risk - likelihood - impact - mitigation - contract protection - owner F. Decision recommendation Choose: - approve - approve with conditions - delay pending evidence - negotiate protections - reject Rules: - Do not approve a vendor based only on sales materials. - Do not ignore exit risk. - Do not treat security, legal, or compliance issues as minor if data or customers are affected. - This is not legal advice; mark contract issues as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#188Negotiation Preparation War Room

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTFounders, executives, procurement, vendor managers, sales leaders, partnership teams, agency owners, consultants, and anyone preparing for commercial negotiations.

Prepare for a negotiation by defining interests, leverage, BATNA, concessions, decision rules, risks, opening position, questions, and tactics.

Act as a negotiation strategist. Prepare a negotiation war room plan for [NEGOTIATION TOPIC] between [OUR SIDE] and [OTHER SIDE]. Negotiation context: Our side: [OUR SIDE] Other side: [OTHER SIDE] Negotiation type: [VENDOR / PARTNERSHIP / CUSTOMER / RENEWAL / CONTRACT / PRICING / OTHER] Desired outcome: [DESIRED OUTCOME] Current offer: [CURRENT OFFER] Other side's likely goal: [THEIR GOAL] Our constraints: [CONSTRAINTS] Their constraints: [THEIR CONSTRAINTS] Timeline pressure: [TIMELINE] Relationship importance: [RELATIONSHIP IMPORTANCE] Alternatives: [ALTERNATIVES] Non-negotiables: [NON-NEGOTIABLES] Possible concessions: [CONCESSIONS] Information gaps: [GAPS] Build the war room plan: 1. Negotiation objective Define: - ideal outcome - acceptable outcome - walk-away point - relationship objective - information objective 2. Interest map Separate positions from interests. Our interests: - financial - operational - strategic - risk reduction - timeline - relationship Their likely interests: - revenue - margin - speed - predictability - case study value - market access - reduced risk - internal approval 3. Leverage map Identify leverage sources: - alternatives - timing - volume - competitive options - strategic value - switching cost - reputation - exclusivity - future upside - data / access - urgency Rate each leverage source as weak, moderate, or strong. 4. BATNA and walk-away logic Define: - our best alternative - their likely alternative - cost of no deal - cost of bad deal - walk-away trigger - delay strategy 5. Concession ladder Create a concession plan: - items we can give early - items we can trade - items we can give only for equal value - items we should not give - concessions that cost little but matter to them - concessions that look small but are risky 6. Question strategy Write 20 negotiation questions that reveal: - their constraints - their priorities - approval process - flexibility - hidden risks - decision timeline - alternatives - real objections 7. Opening position and scripts Write: - opening statement - anchor position - response to pushback - pause phrase - trade phrase - walk-away phrase - summary close Rules: - Do not negotiate against yourself. - Do not give concessions without receiving value. - Do not confuse a discount with a strategy. - Protect the relationship only if the deal economics and risk make sense. --------------------------------------------------------------------------------

#189BATNA, ZOPA & Deal Range Calculator

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTNegotiators, procurement teams, sales leaders, founders, vendor managers, executives, consultants, and partnership teams evaluating deal economics.

Build the logic for a deal range using alternatives, reservation points, value drivers, concessions, risk, and acceptable trade packages.

You are a commercial negotiation analyst. Build a BATNA, ZOPA, and deal range model for the negotiation below. Deal context: Negotiation: [NEGOTIATION] Our side: [OUR SIDE] Other side: [OTHER SIDE] Current proposal: [CURRENT PROPOSAL] Our desired terms: [DESIRED TERMS] Their likely desired terms: [THEIR TERMS] Our alternatives: [OUR ALTERNATIVES] Their alternatives: [THEIR ALTERNATIVES] Financial variables: [FINANCIAL VARIABLES] Non-financial variables: [NON-FINANCIAL VARIABLES] Risks: [RISKS] Timeline: [TIMELINE] Relationship value: [RELATIONSHIP VALUE] Create the model: Step 1 - Variables List all negotiable variables: - price - volume - term length - payment timing - exclusivity - service levels - implementation - support - renewal terms - termination rights - marketing rights - data access - minimum commitments - discounts - bonuses - warranties - scope - delivery timelines Step 2 - Our BATNA Define: - best alternative - cost of alternative - operational impact - strategic impact - time impact - risk - confidence level Step 3 - Their likely BATNA Estimate: - their alternative - cost to them - urgency - likely approval constraints - leverage implications - confidence level Step 4 - Reservation points Define: - our walk-away point - their likely walk-away point - uncertain assumptions - data needed to improve confidence Step 5 - ZOPA Identify whether there is a likely zone of possible agreement. If yes, define: - low end - acceptable range - target range - stretch range - trade packages If no, explain: - why no zone exists - what variable could create one - whether to pause, reframe, or walk away Step 6 - Trade package design Create 5 deal packages: - low-risk package - balanced package - aggressive package - relationship-first package - walk-away alternative For each include: - terms - value to us - value to them - risk - likely response - negotiation script Rules: - Do not treat price as the only negotiable variable. - Do not invent exact numbers where data is missing; use ranges and assumptions. - Do not recommend a deal below the walk-away point. - Mark uncertain estimates as [ASSUMPTION]. --------------------------------------------------------------------------------

#190Commercial Terms Red Flag Reviewer

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTFounders, COOs, procurement teams, vendor managers, partnership leads, agency owners, consultants, and teams preparing contracts for professional legal review.

Review commercial, operational, and relationship risks in proposed deal terms before legal review, highlighting unclear scope, payment risk, lock-in, liability exposure, SLA gaps, and exit issues.

Act as a commercial deal terms reviewer. Review the proposed terms below and identify business, operational, vendor, partnership, and negotiation risks before the document goes to legal review. Important: This is not legal advice. Flag items that may require professional legal review as [LEGAL REVIEW]. Focus on commercial logic, operational clarity, negotiation risk, and business exposure. Deal context: Deal type: [DEAL TYPE] Our side: [OUR SIDE] Other side: [OTHER SIDE] Business objective: [OBJECTIVE] Relationship importance: [RELATIONSHIP IMPORTANCE] Proposed terms: [PASTE TERMS] Contract length: [TERM LENGTH] Pricing: [PRICING] Scope: [SCOPE] Service obligations: [SERVICE OBLIGATIONS] Payment terms: [PAYMENT TERMS] Termination terms: [TERMINATION] Known concerns: [CONCERNS] Review the terms using this red flag board: Board 1 - Scope clarity Check: - what is included - what is excluded - deliverables - acceptance criteria - change request process - dependencies - assumptions - ambiguous wording Board 2 - Commercial risk Check: - pricing ambiguity - hidden fees - payment timing - minimum commitments - auto-renewal - discount conditions - volume thresholds - currency / tax assumptions - penalty or fee exposure Board 3 - Performance and service risk Check: - service levels - support response - resolution expectations - quality standards - reporting - downtime or failure response - escalation path - remedies for missed commitments Board 4 - Control and dependency risk Check: - exclusivity - lock-in - data access - customer ownership - IP / content usage - subcontractors - operational dependency - switching difficulty Board 5 - Exit risk Check: - termination rights - notice period - transition support - data return or deletion - final payment - offboarding obligations - survival clauses needing review Output: A. Red flag table For each issue include: - clause / term - issue - business risk - severity - recommended negotiation ask - whether legal review is needed B. Missing terms List important terms that are absent. C. Clarification questions Write questions to ask the other side. D. Negotiation priorities Rank what to fix before signing. E. Safer business language Suggest clearer business-friendly wording for ambiguous points, marking legal-sensitive items as [LEGAL REVIEW]. Rules: - Do not rewrite legal clauses as if you are a lawyer. - Do not ignore operational risk because the term sounds standard. - Do not accept vague scope or vague service obligations. - The final output must help the team prepare for legal and negotiation review. --------------------------------------------------------------------------------

#191Vendor SLA & Performance Scorecard

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTVendor managers, procurement, operations leaders, IT, HR, finance, customer experience teams, logistics teams, restaurant groups, retail operators, and companies managing critical suppliers.

Create a vendor performance system with SLAs, KPIs, scorecards, review cadence, escalation rules, remedies, and improvement actions.

You are a vendor performance management architect. Build a vendor SLA and scorecard system for [VENDOR NAME] so performance can be measured, discussed, improved, and escalated objectively. Vendor context: Vendor: [VENDOR NAME] Vendor category: [CATEGORY] Service provided: [SERVICE] Business-criticality: [CRITICALITY] Current contract / SLA: [CURRENT SLA] Current issues: [ISSUES] Current reporting: [REPORTING] Internal owner: [OWNER] Departments affected: [DEPARTMENTS] Customer impact: [CUSTOMER IMPACT] Spend: [SPEND] Review cadence: [CADENCE] Build the system: SLA Definition Layer Define service commitments for: - availability - response time - resolution time - delivery timing - quality - accuracy - documentation - reporting - staffing - communication - escalation - compliance - issue prevention For each SLA include: - exact definition - target - measurement method - data source - reporting frequency - owner - exception rule KPI Scorecard Layer Create a scorecard with categories: 1. Service delivery 2. Quality 3. Responsiveness 4. Communication 5. Cost control 6. Innovation / improvement 7. Compliance 8. Relationship health 9. Risk management For each KPI include: - metric - target - green threshold - yellow threshold - red threshold - trend - evidence required - action if red Review Rhythm Layer Design: - weekly operational check, if needed - monthly performance review - quarterly business review - annual renewal review For each include agenda, attendees, required data, decisions, and outputs. Escalation Layer Define what happens when: - SLA is missed once - SLA is missed repeatedly - issue affects customers - issue creates financial risk - vendor is unresponsive - vendor breaches trust - vendor improves Improvement Layer Create a corrective action plan template: - issue - root cause - vendor action - company action - deadline - owner - success metric - follow-up date Rules: - Do not measure vendors only by relationship friendliness. - Do not create SLAs that cannot be measured. - Do not wait until renewal to discuss performance issues. - Scorecards must lead to action, not just reporting. --------------------------------------------------------------------------------

#192Partnership Outreach Message Studio

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTPartnership managers, founders, business development teams, co-marketing teams, agency owners, SaaS companies, newsletter operators, communities, and consultants doing partner outreach.

Create personalized outreach messages for potential partners with clear value exchange, relevance, credibility, low-friction ask, and follow-up sequence.

Act as a partnership outreach copy strategist. Write a personalized outreach system for contacting [PARTNER TYPE / PARTNER NAME] about a potential partnership with [COMPANY NAME]. Outreach context: Our company: [COMPANY NAME] Partner target: [PARTNER NAME OR TYPE] Partner audience: [PARTNER AUDIENCE] Our audience: [OUR AUDIENCE] Partnership idea: [PARTNERSHIP IDEA] Why it benefits them: [THEIR BENEFIT] Why it benefits us: [OUR BENEFIT] Why it benefits customers: [CUSTOMER BENEFIT] Credibility proof: [PROOF] Desired first step: [FIRST STEP] Tone: [TONE] Channel: [EMAIL / LINKEDIN / X / INTRO / OTHER] Create the outreach studio output: 1. Relevance hook bank Write 10 opening hooks based on: - audience overlap - recent partner activity - shared customer problem - complementary product - market trend - mutual connection - content they published - customer value - co-marketing opportunity - operational synergy 2. Value exchange framing Write 5 ways to explain why the partnership is not one-sided. 3. Outreach versions Create: A. Short direct email B. Warm strategic email C. Founder-to-founder message D. LinkedIn connection note E. Mutual introduction request F. Follow-up after no response G. Follow-up with new value H. Breakup message 4. First-call agenda Create a 20-minute discovery call agenda: - context - partner goals - audience overlap - partnership idea - constraints - next step 5. Personalization checklist List what to research before sending: - audience - recent campaigns - product lines - public goals - partner ecosystem - decision maker - current offers - brand tone 6. Response handling Write replies if partner says: - interested - send more info - not now - we charge for partnerships - we already have a partner - unclear fit - no response Rules: - Do not make outreach sound like a sales pitch disguised as partnership. - Do not ask for too much in the first message. - Do not claim audience overlap without evidence. - Keep the ask specific and easy to answer. --------------------------------------------------------------------------------

#193Joint Business Plan Builder

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTStrategic alliances, channel partnerships, reseller relationships, enterprise partnerships, co-selling teams, SaaS ecosystems, vendor partnerships, and long-term collaboration planning.

Build a shared plan with a partner covering objectives, revenue targets, roles, campaigns, enablement, governance, risks, and success metrics.

You are a joint business planning facilitator. Create a joint business plan between [COMPANY NAME] and [PARTNER NAME] that both sides can use to coordinate execution and measure success. Planning inputs: Company: [COMPANY NAME] Partner: [PARTNER NAME] Partnership type: [TYPE] Partnership stage: [NEW / ACTIVE / RENEWAL / RESET] Shared objective: [OBJECTIVE] Target customers: [CUSTOMERS] Revenue target: [REVENUE TARGET] Pipeline target: [PIPELINE TARGET] Key markets: [MARKETS] Available resources: [RESOURCES] Executive sponsors: [SPONSORS] Operational owners: [OWNERS] Current issues: [ISSUES] Time period: [TIME PERIOD] Create the joint business plan: Executive Alignment Write: - shared vision - why this partnership matters - strategic value for each side - customer value - time horizon - decision principles Target Market Plan Define: - target segments - ideal customer profile - use cases - priority accounts - geographic focus - vertical focus - exclusion criteria Commercial Plan Create: - revenue targets - pipeline targets - lead targets - conversion assumptions - average deal assumptions - incentive structure - deal registration rules - co-sell process Go-To-Market Plan Plan: - campaigns - events - webinars - content - partner marketplace listing - referral motions - sales enablement - account mapping - executive introductions Enablement Plan Define: - training required - certification - sales scripts - demo assets - implementation guides - objection handling - customer success handoff - support boundaries Governance Plan Create: - weekly operating check - monthly pipeline review - quarterly business review - executive sponsor review - decision log - issue escalation path Risk Plan Identify risks: - misaligned incentives - low activation - poor lead quality - unclear ownership - customer support issues - channel conflict - data sharing concerns - under-resourcing For each risk include mitigation. Success Dashboard Track: - partner activation - leads - pipeline - revenue - deal velocity - win rate - customer retention - enablement completion - campaign performance - partner satisfaction Rules: - Do not create a plan where goals exist but owners do not. - Do not set revenue targets without activity assumptions. - Do not ignore enablement. - The plan must be specific enough to review every month. --------------------------------------------------------------------------------

#194Partner Onboarding & Enablement Kit

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTChannel teams, reseller programs, agency partner programs, SaaS companies, marketplaces, service businesses, implementation networks, and referral partner programs.

Create a complete onboarding system that teaches partners what to sell, who to target, how to position, how to refer, how to implement, and how to avoid bad-fit customers.

Act as a partner enablement designer. Build a partner onboarding kit for [COMPANY NAME]'s [PARTNER PROGRAM NAME] so new partners can become productive without constant one-off support. Partner program context: Company: [COMPANY NAME] Partner type: [PARTNER TYPE] Product / service: [PRODUCT / SERVICE] Target customer: [TARGET CUSTOMER] Partner promise: [PARTNER PROMISE] Partner responsibilities: [RESPONSIBILITIES] Company responsibilities: [COMPANY RESPONSIBILITIES] Sales process: [SALES PROCESS] Implementation process: [IMPLEMENTATION] Support model: [SUPPORT MODEL] Common partner mistakes: [MISTAKES] Tools / portal: [TOOLS] Incentives: [INCENTIVES] Create the onboarding kit: Welcome Module Include: - program purpose - why the partnership exists - what good partners do - what partners should not do - first 30-day checklist Product Understanding Module Explain: - what the product is - who it is for - who it is not for - customer problems solved - key features - key outcomes - proof points - limitations Positioning Module Create: - value proposition - elevator pitch - customer pain language - competitor comparison - objection responses - approved claims - claims requiring proof Sales / Referral Module Define: - ideal referral - bad-fit referral - lead submission process - deal registration - qualification questions - handoff process - follow-up expectations - commission or incentive logic Implementation / Delivery Module If relevant, define: - partner tasks - company tasks - customer tasks - timeline - quality standards - escalation path - documentation Marketing Module Provide: - approved logos - approved descriptions - co-branded copy - social posts - email template - landing page blurb - case study rules Certification Module Create: - required training - knowledge check - practice scenario - approval criteria - renewal cadence Partner Success Dashboard Track: - onboarding completion - first referral - first closed deal - lead quality - conversion rate - customer satisfaction - support issues - compliance with brand rules Rules: - Do not assume partners understand the product because they signed an agreement. - Do not let partners create their own unsupported claims. - Do not overload onboarding with information not needed for first action. - Enablement must reduce mistakes and increase partner activation. --------------------------------------------------------------------------------

#195Vendor Cost Reduction Negotiation Planner

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTFinance teams, procurement, COOs, operations managers, vendor managers, founders, restaurant groups, retail operators, agencies, and companies reducing costs without damaging service.

Prepare a vendor cost reduction negotiation using spend analysis, service usage, alternatives, scope changes, concessions, payment terms, and value-preserving tradeoffs.

You are a procurement cost optimization strategist. Build a negotiation plan to reduce or control spend with [VENDOR NAME] while protecting service quality and business continuity. Vendor spend context: Vendor: [VENDOR NAME] Service / product: [SERVICE] Annual spend: [ANNUAL SPEND] Contract terms: [CONTRACT TERMS] Usage data: [USAGE DATA] Service quality: [SERVICE QUALITY] Current pricing model: [PRICING MODEL] Renewal date: [RENEWAL DATE] Alternative vendors: [ALTERNATIVES] Switching cost: [SWITCHING COST] Internal dependency: [DEPENDENCY] Must-protect service levels: [SERVICE LEVELS] Budget reduction target: [TARGET] Relationship importance: [RELATIONSHIP] Create the cost reduction plan: Spend Breakdown Analyze: - fixed fees - variable fees - usage-based costs - add-ons - implementation fees - support fees - unused services - overages - minimum commitments - price increases Cost Driver Diagnosis Identify whether spend is driven by: - actual growth - inefficient usage - poor pricing model - bundled services - unused features - lack of negotiation - vendor price increase - scope creep - internal process issue - switching friction Savings Levers Evaluate: - price discount - volume tier - longer term for lower rate - shorter term for flexibility - payment timing - scope reduction - usage optimization - bundle restructuring - removal of unused services - competitive bid - service-level adjustment - implementation credit - renewal cap - termination flexibility For each lever include expected savings, risk, and negotiation difficulty. Trade Package Design Create 5 negotiation packages: 1. Direct discount package 2. Scope optimization package 3. Commitment-for-savings package 4. Competitive alternative package 5. Relationship-preserving package For each include: - ask - what we can offer - vendor benefit - our risk - walk-away logic Negotiation Script Write: - opening message - business case - savings ask - response to vendor resistance - trade language - deadline language - final summary Decision Model Recommend: - renegotiate - rebid - reduce scope - replace vendor - keep vendor but improve terms - accept current cost due to risk Rules: - Do not cut cost in a way that creates bigger operational loss. - Do not reveal weak alternatives too early. - Do not ask only for discount if scope or usage is the real issue. - Every concession must be traded for value. --------------------------------------------------------------------------------

#196Renewal & Renegotiation Playbook

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTVendor managers, procurement teams, partnership teams, sales leaders, account managers, finance teams, founders, and anyone renegotiating an existing agreement.

Prepare for vendor, partnership, customer, or supplier renewal by reviewing performance, leverage, pricing, risks, alternatives, and revised terms.

Act as a renewal strategy lead. Build a renewal and renegotiation playbook for [AGREEMENT / PARTNERSHIP / VENDOR] before the renewal deadline. Renewal context: Relationship: [RELATIONSHIP] Agreement type: [TYPE] Current term end date: [END DATE] Current pricing / economics: [PRICING] Current scope: [SCOPE] Performance history: [PERFORMANCE] Issues during current term: [ISSUES] Value received: [VALUE RECEIVED] Value delivered: [VALUE DELIVERED] Alternatives: [ALTERNATIVES] Switching cost: [SWITCHING COST] Stakeholders: [STAKEHOLDERS] Desired changes: [DESIRED CHANGES] Non-negotiables: [NON-NEGOTIABLES] Use this playbook structure: Snapshot Create a one-page summary: - current agreement - what worked - what did not work - renewal deadline - business impact - recommendation Performance Review Evaluate: - delivery against commitments - responsiveness - quality - financial value - relationship health - issue resolution - innovation - risk - customer or internal impact Leverage Assessment Identify leverage from: - renewal timing - alternative options - spend level - performance gaps - growth opportunity - relationship value - public case study value - exclusivity - future volume - switching difficulty Renewal Options Create 4 options: A. Renew as-is B. Renew with improved terms C. Renew with reduced scope D. Do not renew / replace For each include: - financial impact - operational impact - relationship impact - risk - timeline - recommendation Renegotiation Agenda Create meeting agenda: - shared review - value discussion - unresolved issues - revised needs - term changes - pricing - service levels - next steps Term Change Wishlist Rank desired changes as: - must-have - should-have - tradeable - nice-to-have - do not mention unless needed Communication Scripts Write: - renewal kickoff message - performance concern message - pricing renegotiation message - alternative vendor pressure message - final agreement summary - non-renewal notice draft Rules: - Do not wait until the final week to renegotiate. - Do not renew bad performance without new protections. - Do not threaten switching unless alternatives are credible. - Renewal should be based on evidence, not habit. --------------------------------------------------------------------------------

#197Dispute & Escalation Resolution Framework

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTVendor managers, partnership leads, operations teams, customer success leaders, executives, procurement, agencies, SaaS companies, restaurant groups, logistics teams, and service businesses.

Resolve partnership or vendor disputes with fact-finding, impact assessment, ownership, escalation paths, recovery actions, and future prevention.

You are a commercial dispute resolution facilitator. Build a resolution framework for the dispute between [COMPANY NAME] and [PARTNER / VENDOR NAME]. Dispute context: Our company: [COMPANY NAME] Other side: [PARTNER / VENDOR NAME] Relationship type: [VENDOR / PARTNER / SUPPLIER / RESELLER / CUSTOMER / OTHER] What happened: [WHAT HAPPENED] Timeline: [TIMELINE] Contract or agreement terms: [TERMS] Business impact: [BUSINESS IMPACT] Customer impact: [CUSTOMER IMPACT] Financial impact: [FINANCIAL IMPACT] Evidence available: [EVIDENCE] Previous communication: [COMMUNICATION] Desired outcome: [OUTCOME] Relationship importance: [RELATIONSHIP IMPORTANCE] Escalation level: [LEVEL] Build the framework: 1. Fact file Separate: - confirmed facts - claims from our side - claims from other side - assumptions - missing evidence - disputed points - irrelevant noise 2. Impact statement Quantify or describe: - financial impact - operational impact - customer impact - timeline impact - trust impact - legal / compliance exposure, if any 3. Agreement comparison Compare what happened against: - written agreement - service expectations - prior emails - verbal commitments - standard operating expectations - industry norms, if relevant Mark anything requiring legal review as [LEGAL REVIEW]. 4. Resolution options Create 5 possible resolution paths: - informal correction - service credit or refund - corrective action plan - scope adjustment - executive escalation - contract renegotiation - termination planning - legal review For each option include: - when to use - upside - downside - relationship impact - evidence needed - next step 5. Escalation message Write a professional escalation message that includes: - factual summary - impact - desired resolution - deadline - requested meeting - tone that protects the relationship where possible 6. Recovery agreement Create a recovery agreement template: - issue - responsibility - corrective action - deadline - owner - verification method - consequence if not completed - follow-up cadence 7. Prevention loop Recommend: - SLA update - communication change - reporting change - escalation path - contract clarification - vendor scorecard change - internal process change Rules: - Do not escalate emotionally. - Do not accuse without evidence. - Do not ignore customer impact. - Do not preserve a relationship at any cost if repeated failure continues. --------------------------------------------------------------------------------

#198Partnership Governance Operating Rhythm

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTStrategic alliances, channel partnerships, co-selling relationships, vendor partnerships, SaaS ecosystems, enterprise partnerships, and partnership portfolios that need ongoing management.

Create a management cadence for partnerships with owners, meetings, scorecards, decision logs, QBRs, issue escalation, and executive alignment.

Act as a partnership governance architect. Design an operating rhythm for managing the partnership between [COMPANY NAME] and [PARTNER NAME] so the relationship produces measurable outcomes after the agreement is signed. Partnership context: Company: [COMPANY NAME] Partner: [PARTNER NAME] Partnership type: [TYPE] Partnership goals: [GOALS] Executive sponsors: [SPONSORS] Operating owners: [OWNERS] Current activities: [ACTIVITIES] Current metrics: [METRICS] Current issues: [ISSUES] Contractual commitments: [COMMITMENTS] Decision rights: [DECISION RIGHTS] Review cadence: [CURRENT CADENCE] Design the governance rhythm: Governance Roles Define: - executive sponsor - partnership owner - sales owner - marketing owner - product / implementation owner - customer success owner - operations owner - finance owner - legal / compliance contact, if needed For each role include responsibility, decision rights, and escalation duties. Meeting Cadence Design: - weekly operating check - biweekly campaign / pipeline review - monthly performance review - quarterly business review - annual strategy reset - ad hoc escalation meeting For each meeting include: - purpose - attendees - duration - agenda - pre-read - decisions made - outputs - cancellation rule Scorecard Track: - agreed activities - leads - pipeline - revenue - activation - customer outcomes - co-marketing performance - implementation quality - support issues - SLA performance - relationship health - strategic progress Decision Log Create a decision log format: - decision - owner - date - context - options considered - decision made - follow-up - people informed Issue Escalation Define escalation rules for: - missed commitments - poor lead quality - customer complaints - support issues - brand misuse - data sharing issues - channel conflict - executive misalignment - financial disagreement QBR Template Create a quarterly business review agenda with: - wins - metric review - pipeline / revenue - customer stories - issues - market insights - next-quarter plan - executive asks Rules: - Do not treat signing the agreement as the finish line. - Do not allow unclear ownership after kickoff. - Do not run meetings without metrics and decisions. - Governance should create momentum, not bureaucracy. --------------------------------------------------------------------------------

#199Partner Portfolio Review & Rationalization Audit

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTCEOs, COOs, partnership leaders, procurement teams, vendor managers, finance teams, operations leaders, SaaS ecosystems, multi-location businesses, and companies with too many unmanaged relationships.

Review all partners or vendors, identify high-value relationships, underperformers, hidden risk, overdependence, renewal priorities, and relationships to grow, fix, pause, or exit.

You are a partner and vendor portfolio strategist. Audit the full portfolio of partners and vendors for [COMPANY NAME] and recommend where to invest, renegotiate, improve, or exit. Portfolio data: Company: [COMPANY NAME] Partner / vendor list: [LIST] Relationship types: [TYPES] Annual spend or revenue by relationship: [SPEND / REVENUE] Performance data: [PERFORMANCE] Contract dates: [CONTRACT DATES] Strategic importance: [STRATEGIC IMPORTANCE] Operational dependency: [DEPENDENCY] Customer impact: [CUSTOMER IMPACT] Internal owners: [OWNERS] Known issues: [ISSUES] Renewal dates: [RENEWALS] Alternatives: [ALTERNATIVES] Leadership concerns: [CONCERNS] Audit the portfolio: Portfolio Segmentation Classify relationships into: - strategic growth partner - core operational vendor - high-performing tactical vendor - underperforming but necessary vendor - high-risk dependency - replaceable commodity vendor - experimental partner - inactive relationship - relationship to exit Portfolio Matrix Score each relationship across: - strategic value - financial value - customer impact - performance quality - relationship health - operational dependency - switching difficulty - risk - owner clarity - future potential Relationship Action Categories Assign each relationship one action: - invest and expand - maintain - improve with corrective plan - renegotiate - consolidate - rebid - replace - pause - exit For each action include reason and next step. Dependency Risk Review Identify: - single-source vendors - partners with too much customer control - vendors with high switching cost - relationships without internal backup - contracts with unfavorable renewal terms - relationships where knowledge is undocumented Spend / Value Review Identify: - high spend, low value - low spend, high strategic value - high value but unmanaged - high revenue but high risk - hidden costs - duplicate vendors - overlapping partner roles Renewal Calendar Create a renewal risk calendar with: - relationship - renewal date - preparation deadline - desired action - owner - risk if ignored Executive Recommendations Write: - top 5 relationships to grow - top 5 relationships to fix - top 5 relationships to renegotiate - top 5 relationships to exit or replace - immediate risks requiring leadership attention Rules: - Do not judge relationships only by spend or revenue. - Do not ignore operational dependency. - Do not exit a vendor without transition planning. - Mark missing performance data as [NEEDS DATA]. --------------------------------------------------------------------------------

#200Full Partnerships, Negotiation & Vendor Management Audit

PARTNERSHIPS, NEGOTIATION & VENDOR MANAGEMENTCEOs, founders, COOs, procurement leaders, partnership teams, finance teams, operations leaders, business development teams, consultants, and organizations doing a partnership or vendor management reset.

Audit the full system for finding partners, negotiating deals, selecting vendors, managing performance, controlling risk, governing relationships, and improving commercial outcomes.

Act as an independent partnerships, negotiation, and vendor management auditor. Review the complete relationship management system of [COMPANY NAME] and identify the highest-leverage improvements for growth, cost control, risk reduction, performance, and strategic alignment. Company context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Current partners: [PARTNERS] Current vendors: [VENDORS] Partnership goals: [PARTNERSHIP GOALS] Vendor spend: [VENDOR SPEND] Revenue from partners: [PARTNER REVENUE] Key contracts: [CONTRACTS] Current negotiation process: [NEGOTIATION PROCESS] Vendor selection process: [VENDOR SELECTION] Partner selection process: [PARTNER SELECTION] Performance scorecards: [SCORECARDS] SLAs: [SLAS] Governance cadence: [GOVERNANCE] Known issues: [ISSUES] Upcoming renewals: [RENEWALS] Risk concerns: [RISKS] Leadership questions: [QUESTIONS] Audit the system across 20 dimensions: 1. Partnership strategy 2. Partner landscape research 3. Partner fit criteria 4. Partner outreach 5. Value exchange clarity 6. Co-marketing readiness 7. Channel program design 8. Partner onboarding 9. Joint business planning 10. Partnership governance 11. Vendor selection process 12. RFP quality 13. Vendor due diligence 14. Commercial negotiation preparation 15. BATNA and deal range discipline 16. Contract and terms review process 17. Vendor SLA design 18. Vendor performance management 19. Renewal and renegotiation process 20. Portfolio risk and dependency management For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - revenue opportunity - cost risk - operational risk - relationship risk - recommended fix - confidence level Then synthesize: A. Top 5 relationship-system constraints Rank by: - revenue impact - cost impact - customer impact - operational risk - urgency - ease of fixing - confidence B. Root cause analysis Identify whether the main issue is: - unclear partnership thesis - weak partner selection - poor value exchange - unmanaged partners - no vendor scorecards - weak negotiation preparation - no BATNA discipline - contract ambiguity - vendor dependency - renewal neglect - poor governance - unclear ownership - lack of performance data - overreliance on relationships instead of systems C. Future-state relationship system Create: - partnership thesis - partner fit matrix - partner outreach system - co-marketing blueprint - channel partner model - vendor RFP process - due diligence checklist - negotiation playbook - contract red flag checklist - SLA scorecard - renewal calendar - governance cadence - portfolio review process D. 30/60/90-day improvement plan Create a practical plan with: - actions - owners - templates to create - relationships to review - vendors to score - contracts to check - negotiations to prepare - renewals to prioritize - metrics to track - risks to reduce - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard commercial truth - the biggest partnership opportunity - the biggest vendor risk - the fastest cost-control action - the strongest negotiation improvement - the next leadership decision - the data needed before deeper changes Rules: - Do not invent partner or vendor performance data. - Do not give legal advice; mark legal-sensitive items as [LEGAL REVIEW]. - Do not recommend partnerships without a clear incentive for both sides. - Do not recommend vendor exits without transition planning. - Use [LOW CONFIDENCE] where evidence is weak. - Focus on commercial value, trust, risk, execution, governance, and measurable outcomes.

#201Productivity Friction Audit

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONFounders, COOs, operations managers, department heads, team leads, agencies, service businesses, startups, and any team that feels busy but not productive.

Find where time, focus, decisions, handoffs, meetings, tools, and unclear ownership slow the team down.

You are an operational productivity auditor. Analyze the way [TEAM / COMPANY] works and identify the hidden friction that reduces speed, quality, focus, and accountability. Work context: Company / team: [COMPANY / TEAM] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Core workflows: [WORKFLOWS] Main tools: [TOOLS] Recurring meetings: [MEETINGS] Communication channels: [CHANNELS] Current productivity complaints: [COMPLAINTS] Missed deadlines: [MISSED DEADLINES] Repeated mistakes: [MISTAKES] Decision bottlenecks: [BOTTLENECKS] Manager observations: [OBSERVATIONS] Employee feedback: [FEEDBACK] Customer impact: [CUSTOMER IMPACT] Business goals: [GOALS] Run the audit in this structure: Friction Inventory List every visible and hidden productivity drain across: - unclear priorities - repeated manual work - unnecessary meetings - unclear ownership - slow approvals - too many tools - poor documentation - duplicated work - context switching - weak handoffs - rework - decision delays - waiting for information - interruptions - unclear quality standards For each friction point include: - symptom - likely root cause - who is affected - workflow affected - cost in time, quality, or morale - confidence level Flow of Work Diagnosis Map how work currently moves from request to completion. Identify: - where work enters - who receives it - how it is prioritized - where decisions happen - where work waits - where information is missing - where quality is checked - where completion is confirmed Productivity Impact Score Score each friction point from 1 to 5 across: - time lost - quality risk - customer impact - employee frustration - frequency - ease of fixing Calculate a priority ranking. Fix Menu For each high-priority issue recommend one of these fixes: - clarify ownership - remove a meeting - redesign a meeting - create an SOP - create a checklist - automate - change approval rights - simplify tools - create a dashboard - create a handoff template - stop doing the work - batch the work - assign a decision owner 30-Day Friction Removal Plan Create: - quick wins this week - process changes this month - documentation to create - meetings to remove or redesign - tool changes to test - owners - success metrics - risks to watch Rules: - Do not blame people before checking systems. - Do not recommend more meetings unless they remove larger coordination cost. - Do not recommend automation before clarifying the workflow. - Use [NEEDS DATA] when evidence is missing. Done when the team knows exactly what to fix first to recover time and improve execution. --------------------------------------------------------------------------------

#202SOP From Messy Process Interview

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations teams, managers, founders, restaurants, retail teams, agencies, admin teams, support teams, finance teams, HR teams, and businesses where work lives in people's heads.

Convert an undocumented process from employee memory into a clear SOP with steps, standards, exceptions, risks, and ownership.

Act as an SOP interviewer and process documentation specialist. Your job is to extract a messy process from [PROCESS OWNER] and turn it into a practical SOP that someone else can follow. Process to document: [PROCESS NAME] Process owner: [PERSON / ROLE] Department: [DEPARTMENT] Current documentation: [CURRENT DOCUMENTATION] Why this SOP is needed: [REASON] Who will use it: [USERS] How often it happens: [FREQUENCY] Tools involved: [TOOLS] Inputs required: [INPUTS] Outputs expected: [OUTPUTS] Known mistakes: [MISTAKES] Compliance or quality requirements: [REQUIREMENTS] Use this interview-first method: Stage 1 - Extraction Questions Create a complete interview script to ask the process owner. Ask questions about: - trigger: how the process starts - purpose: why it exists - inputs: what is needed before starting - tools: what systems are used - steps: what happens first, second, third - decisions: where judgment is needed - exceptions: what changes in unusual cases - mistakes: what commonly goes wrong - timing: how long each step takes - quality: what good output looks like - handoffs: who receives the result - proof: how completion is verified - escalation: when to ask for help Stage 2 - Process Reconstruction Using the answers, reconstruct the process as: - process summary - owner - user - trigger - required inputs - step-by-step instructions - decision points - screenshots needed - quality standards - common errors - escalation rules - completion criteria Stage 3 - SOP Draft Write the SOP in this format: Title: Purpose: Scope: Owner: Users: Frequency: Tools: Before You Start: Procedure: Decision Rules: Exceptions: Quality Checklist: Common Mistakes: Escalation: Completion Definition: Version History: Stage 4 - Validation Checklist Create a checklist to test whether the SOP works: - can a new person follow it? - are all tools named? - are all decisions explained? - are exceptions covered? - is the output measurable? - are risks explained? - is ownership clear? Stage 5 - Process Owner Review Write 12 questions to send back to the process owner for validation. Rules: - Do not write a polished SOP from incomplete process knowledge without marking gaps. - Do not assume obvious steps are obvious to a new person. - Do not hide exceptions in vague notes. - Use [MISSING] for anything that must be confirmed. Done when the SOP can be tested by a person who has never done the process before. --------------------------------------------------------------------------------

#203Process Map & Handoff Blueprint

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations leaders, project managers, service teams, customer success, agencies, logistics teams, finance operations, HR operations, and cross-functional teams with messy handoffs.

Map a workflow across people, tools, decisions, handoffs, delays, quality checks, and failure points.

You are a workflow mapping expert. Build a process map and handoff blueprint for [WORKFLOW NAME] so the team can see exactly how work moves and where it breaks. Workflow brief: Workflow name: [WORKFLOW NAME] Business goal: [GOAL] Start trigger: [TRIGGER] End state: [END STATE] Teams involved: [TEAMS] Roles involved: [ROLES] Systems used: [SYSTEMS] Current process description: [DESCRIPTION] Known handoff problems: [HANDOFF PROBLEMS] Known delays: [DELAYS] Quality issues: [QUALITY ISSUES] Customer impact: [CUSTOMER IMPACT] Volume / frequency: [VOLUME / FREQUENCY] Create the blueprint as a workflow map: Lane 1 - Process stages Break the workflow into stages. For each stage include: - stage name - purpose - owner - input required - action taken - tool used - output created - time expected - completion signal Lane 2 - Handoffs For every handoff define: - sender - receiver - information transferred - format - deadline - acceptance criteria - confirmation method - what happens if information is incomplete Lane 3 - Decisions Identify decision points: - decision question - decision owner - data needed - options - rule for deciding - escalation path - documentation required Lane 4 - Quality gates Define where quality is checked: - what is checked - by whom - checklist used - pass / fail standard - rework path - approval needed Lane 5 - Failure modes List: - where work gets stuck - where errors happen - where ownership is unclear - where tools create friction - where customers are affected - where delays compound Root Cause Grid For each issue classify the root cause as: - unclear owner - unclear input - missing template - tool limitation - approval delay - skill gap - workload imbalance - missing data - poor communication - unclear quality standard Improved Future-State Flow Create a cleaner version of the workflow with: - fewer handoffs - clearer owners - fewer approvals - stronger quality gates - better documentation - faster escalation - measurable completion Implementation Plan Create: - changes to make - SOPs to write - templates to create - roles to clarify - tools to adjust - metrics to track - first review date Rules: - Do not map only happy-path steps. - Do not allow handoffs without acceptance criteria. - Do not create shared ownership for decisions that require one owner. - The final blueprint must be usable for training and process improvement. --------------------------------------------------------------------------------

#204Internal Documentation Architecture Designer

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONStartups, agencies, multi-location businesses, operations teams, HR teams, finance teams, customer support teams, and companies whose internal docs are scattered or hard to find.

Design a clean internal documentation system with categories, naming rules, ownership, search logic, templates, permissions, and maintenance cadence.

Act as an internal documentation architect. Design a documentation system for [COMPANY / TEAM] that makes knowledge easy to find, trust, maintain, and use. Documentation context: Company / team: [COMPANY / TEAM] Current documentation tools: [TOOLS] Current doc locations: [LOCATIONS] Team size: [TEAM SIZE] Departments: [DEPARTMENTS] Types of documents: [DOCUMENT TYPES] Current problems: [PROBLEMS] Sensitive information: [SENSITIVE INFO] Who creates docs: [CREATORS] Who uses docs: [USERS] Search problems: [SEARCH PROBLEMS] Maintenance problems: [MAINTENANCE PROBLEMS] Design the architecture: 1. Documentation Principles Create 7 principles that govern the system. Examples: - one source of truth - owner on every doc - date on every doc - searchable titles - templates before free-form docs - archive old versions - docs must answer real user questions 2. Knowledge Map Create top-level categories such as: - company overview - strategy and goals - people and HR - operations - finance and admin - sales - marketing - customer support - product / service delivery - vendors and partners - policies - tools and access - training - templates - decision records For each category define: - what belongs there - what does not belong there - owner - user groups - examples of docs 3. Naming Convention Create naming rules for: - SOPs - policies - templates - meeting notes - decision records - checklists - training guides - project docs - vendor docs Include examples of good and bad titles. 4. Document Templates Design templates for: - SOP - policy - checklist - how-to guide - process map - meeting notes - decision record - onboarding guide - FAQ - troubleshooting guide 5. Permission Model Define access levels: - public to company - department-only - manager-only - HR / finance restricted - confidential - archived 6. Search and Navigation Rules Create: - folder structure - tagging system - index page - glossary - owner directory - FAQ landing pages - "start here" pages 7. Maintenance System Define: - doc owner responsibilities - review cadence - expiration dates - archive rules - change request process - quality review checklist Rules: - Do not create a folder structure that mirrors politics instead of user needs. - Do not allow orphaned docs without owners. - Do not keep outdated docs visible without warning. - Documentation architecture must reduce search time and increase trust. --------------------------------------------------------------------------------

#205Step-by-Step SOP Writer With Edge Cases

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations teams, HR, finance, customer support, restaurants, retail, agencies, admin teams, logistics, and any repeatable process requiring consistency.

Write a usable SOP that includes exact steps, edge cases, screenshots needed, decision rules, quality checks, and escalation.

You are an SOP writer specializing in operational clarity. Write a complete SOP for [PROCESS NAME] that can be followed by a trained employee without additional explanation. Use this source material: Process name: [PROCESS NAME] Department: [DEPARTMENT] Process owner: [OWNER] Users: [USERS] Purpose: [PURPOSE] Scope: [SCOPE] Trigger: [TRIGGER] Inputs: [INPUTS] Outputs: [OUTPUTS] Tools: [TOOLS] Step notes: [ROUGH STEPS] Decision points: [DECISIONS] Common exceptions: [EXCEPTIONS] Common mistakes: [MISTAKES] Quality standards: [QUALITY STANDARDS] Escalation contacts: [CONTACTS] Compliance requirements: [REQUIREMENTS] Write the SOP: Header - SOP title - document owner - department - version - last updated - review date - approved by Purpose and Outcome Explain: - why this process exists - what successful completion looks like - what risk this process controls Scope Include: - what this SOP covers - what it does not cover - who should use it - when to use it Before You Start List: - required access - required materials - required information - pre-checks - dependencies Procedure Write numbered steps. For each step include: - action - owner - tool / location - exact instruction - expected result - screenshot needed, if any - warning, if any Decision Rules Create decision tables: - situation - question to ask - rule - action - escalation Edge Cases For each edge case include: - how to recognize it - what to do - what not to do - who to notify - how to document it Quality Check Create a final checklist. Troubleshooting Create a table: - problem - likely cause - fix - escalation Completion Definition Explain how the user knows the SOP is finished. Rules: - Do not skip small steps that a new user would not know. - Do not use vague instructions like "handle accordingly." - Do not leave decision points unexplained. - Mark missing information as [CONFIRM]. Done when the SOP can be tested by someone outside the original team. --------------------------------------------------------------------------------

#206Documentation Gap Detector

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations managers, HR leaders, knowledge managers, COOs, founders, quality teams, support teams, and organizations cleaning up documentation.

Identify missing, outdated, duplicated, unclear, ownerless, risky, or hard-to-find internal documentation.

Act as a documentation quality auditor. Review the documentation inventory below and identify gaps that create operational risk, training delays, inconsistent work, or employee confusion. Documentation inventory: [PASTE DOCUMENT LIST OR EXPORT] Company / team: [COMPANY / TEAM] Departments covered: [DEPARTMENTS] Current documentation tool: [TOOL] Known problems: [PROBLEMS] High-risk processes: [HIGH-RISK PROCESSES] New hire questions: [NEW HIRE QUESTIONS] Repeated mistakes: [MISTAKES] Compliance needs: [COMPLIANCE] Business-critical workflows: [CRITICAL WORKFLOWS] Recent changes: [RECENT CHANGES] Audit using this gap detector: Doc Health Classification Classify every document as one of: - current and useful - current but unclear - outdated - duplicated - missing owner - wrong location - too long - too shallow - not searchable - policy risk - process risk - archive candidate - missing entirely Documentation Risk Map Identify missing or weak docs for: - onboarding - role training - recurring operations - customer-facing processes - finance and approvals - HR policies - vendor management - emergency procedures - quality checks - tool access - reporting - decision making - handoffs - escalation Gap Priority Score Score each gap from 1 to 5 across: - frequency of use - business risk - customer impact - compliance exposure - new hire dependency - error reduction potential - ease of creating Create a ranked list of documentation gaps. Duplicate and Conflict Audit Find: - duplicated docs - conflicting instructions - old policies still visible - multiple templates for same work - unclear source of truth Recommended Fix For each gap recommend: - create new doc - update existing doc - merge docs - archive doc - rename doc - move doc - assign owner - add checklist - convert to SOP - convert to FAQ - add screenshots - add review date Documentation Cleanup Sprint Create a 2-week cleanup plan: - docs to fix first - owners - review standards - archive rules - communication to team - success metric Rules: - Do not treat all documents as equally important. - Do not preserve old docs just because they exist. - Do not recommend rewriting everything at once. - Mark unknown document quality as [NEEDS REVIEW]. --------------------------------------------------------------------------------

#207Meeting-to-Documentation Converter

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONManagers, project leads, operations teams, product teams, agencies, leadership teams, async teams, and anyone whose meetings create confusion after they end.

Convert meeting notes, decisions, discussions, and action items into clean documentation, decision records, SOP updates, FAQs, and task owners.

You are a meeting documentation operator. Convert the meeting content below into useful internal documentation and follow-up artifacts. Meeting content: Meeting title: [TITLE] Date: [DATE] Participants: [PARTICIPANTS] Meeting goal: [GOAL] Raw notes / transcript: [PASTE NOTES OR TRANSCRIPT] Decisions mentioned: [DECISIONS] Action items mentioned: [ACTIONS] Open questions: [OPEN QUESTIONS] Relevant projects or docs: [PROJECTS / DOCS] Audience for summary: [AUDIENCE] Create the output package: 1. Executive Meeting Summary Write a short summary with: - why the meeting happened - most important discussion points - decisions made - risks identified - unresolved issues - next milestone 2. Decision Record For each decision create: - decision - owner - date - context - options considered, if available - reason - implications - people to inform - follow-up date If a decision is unclear, mark it as [NOT CONFIRMED]. 3. Action Tracker Create a table: - action - owner - due date - dependency - definition of done - priority - status If owner or deadline is missing, mark [MISSING]. 4. SOP / Documentation Updates Identify which internal docs need updates. For each include: - doc name - section to update - what changed - owner - urgency 5. FAQ From Meeting Create employee-facing FAQ entries for questions that may come up. 6. Risk and Escalation Notes List: - risks - blockers - decisions needing leadership - decisions needing legal / HR / finance review - customer impact 7. Follow-Up Message Draft a concise message to send to participants. Rules: - Do not invent decisions that were only discussed. - Do not assign owners unless they were stated or clearly implied; mark [MISSING] if unclear. - Do not include irrelevant conversation. - Convert discussion into usable documentation, not a transcript summary. --------------------------------------------------------------------------------

#208Team Productivity Operating System

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONFounders, managers, remote teams, agencies, operations teams, creative teams, SaaS teams, and departments that need a repeatable execution rhythm.

Build a practical weekly productivity system for priorities, focus time, task flow, meetings, communication, review, and continuous improvement.

Act as a team productivity systems designer. Build a weekly operating system for [TEAM NAME] that helps the team focus on the right work, reduce noise, and execute consistently. Team profile: Team: [TEAM NAME] Team size: [TEAM SIZE] Work type: [WORK TYPE] Main goals: [GOALS] Current task tools: [TASK TOOLS] Communication channels: [CHANNELS] Meeting schedule: [MEETINGS] Current productivity problems: [PROBLEMS] Deadline pressure: [DEADLINES] Manager expectations: [EXPECTATIONS] Customer or stakeholder needs: [NEEDS] Remote / hybrid / in-person: [SETUP] Design the operating system: Weekly Flow Design a week with: - Monday priority setting - daily task visibility - focus blocks - async updates - decision windows - collaboration windows - midweek blocker review - Friday review - planning for next week Priority System Create rules for: - what becomes a priority - who decides priorities - how many priorities are allowed - how urgent work is handled - how new requests enter the system - what gets paused when capacity is full Task Flow Define stages: - request - triage - accepted - scheduled - in progress - blocked - review - done - archived For each stage include owner, required information, and exit criteria. Meeting Rules Create rules for: - required meetings - optional meetings - meetings to eliminate - agenda standards - decision documentation - no-meeting blocks - meeting review cadence Async Update Format Create templates for: - daily update - weekly priority update - blocker update - project update - decision request - done update Energy Management Recommend practices for: - deep work - meeting clustering - interruption control - workload visibility - recovery time - manager escalation Weekly Review Create a review checklist: - what got done - what did not - why - what blocked progress - what needs a decision - what process needs improvement Rules: - Do not build a system that requires constant manager chasing. - Do not make the team track work in multiple places. - Do not confuse activity with progress. - The system must make priorities, ownership, and capacity visible. --------------------------------------------------------------------------------

#209Task Triage & Prioritization Matrix

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONManagers, founders, operators, product teams, support teams, marketing teams, finance teams, HR teams, and any team overwhelmed by too many requests.

Create a decision system for sorting work by urgency, importance, customer impact, revenue impact, risk, effort, and capacity.

You are a prioritization architect. Build a task triage matrix for [TEAM / DEPARTMENT] so the team can decide what to do now, schedule, delegate, automate, reject, or escalate. Work intake context: Team / department: [TEAM / DEPARTMENT] Types of requests: [REQUEST TYPES] Current backlog: [BACKLOG] Business goals: [GOALS] Customer commitments: [CUSTOMER COMMITMENTS] Revenue priorities: [REVENUE PRIORITIES] Compliance / risk items: [RISK ITEMS] Team capacity: [CAPACITY] Current prioritization problems: [PROBLEMS] Decision owner: [DECISION OWNER] Create the matrix: Priority Dimensions Define scoring from 1 to 5 for: - customer impact - revenue impact - strategic importance - deadline urgency - risk reduction - operational dependency - effort required - confidence - reversibility - learning value Triage Categories Create categories: 1. Do now 2. Schedule this week 3. Schedule later 4. Delegate 5. Automate 6. Simplify 7. Decline 8. Escalate 9. Needs more information 10. Combine with related work For each category define: - entry criteria - examples - owner - timeline - communication response Decision Rules Create rules for: - urgent but low-value work - important but not urgent work - executive requests - customer escalations - compliance issues - repeated small tasks - blocked work - unclear requests - capacity overflow Work Intake Form Create a request form with required fields: - requester - problem - desired outcome - deadline - impact - urgency reason - required stakeholders - existing work affected - definition of done Backlog Review Cadence Design: - daily emergency review - weekly prioritization - monthly cleanup - quarterly strategic review Communication Templates Write responses for: - accepted request - declined request - delayed request - request needs more info - request escalated - request merged Rules: - Do not prioritize based only on who asks loudest. - Do not accept work without a definition of done. - Do not treat every deadline as equally urgent. - Prioritization must protect capacity and business outcomes. --------------------------------------------------------------------------------

#210Async Communication Protocol Builder

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONRemote teams, hybrid teams, startups, agencies, support teams, product teams, operations teams, global teams, and managers trying to reduce interruptions and meetings.

Create clear rules for async communication, response times, channels, escalation, decision requests, updates, and documentation.

Act as an async communication systems architect. Create a communication protocol for [TEAM / COMPANY] that reduces interruptions, prevents missed information, and improves decision speed. Communication context: Team / company: [TEAM / COMPANY] Work setup: [REMOTE / HYBRID / IN-PERSON] Time zones: [TIME ZONES] Communication tools: [TOOLS] Current problems: [PROBLEMS] Urgent work types: [URGENT WORK] Non-urgent work types: [NON-URGENT WORK] Decision types: [DECISIONS] Customer response needs: [CUSTOMER NEEDS] Meeting load: [MEETING LOAD] Documentation tools: [DOC TOOLS] Build the protocol: Channel Map For each communication type define the correct channel: - urgent issue - normal question - decision request - project update - task assignment - policy update - customer escalation - team announcement - brainstorming - sensitive feedback - documentation update - social / informal message For each include: - channel - expected response time - required context - who must be included - when to escalate - where final information is documented Message Standards Create templates for: - decision request - blocker report - status update - handoff message - escalation - FYI update - meeting replacement note - project risk update - clarification request Response Time Rules Define response expectations by urgency: - emergency - same day - 24 hours - 48 hours - weekly review - no response required Escalation Ladder Define when to move from: - async comment - direct message - channel message - call - manager escalation - leadership escalation Decision Documentation Rule Create a rule for converting async decisions into a decision record. Meeting Replacement Guide Identify which meeting types can become async and how. Communication Hygiene Rules for: - tagging - thread use - subject lines - summaries - avoiding duplicate messages - closing loops - not using chat as storage Rules: - Do not expect instant response for non-urgent work. - Do not allow important decisions to disappear in chat. - Do not create async rules that slow down urgent customer issues. - Communication protocol must increase clarity, not bureaucracy. --------------------------------------------------------------------------------

#211Checklist & Quality Gate Builder

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations teams, customer support, finance, HR, sales operations, marketing teams, agencies, QA teams, onboarding teams, and recurring workflows where errors are costly.

Create checklists and quality gates that prevent mistakes, reduce rework, standardize outputs, and make review easier.

You are a quality systems designer. Build a checklist and quality gate system for [PROCESS / OUTPUT] so the team can produce consistent results with fewer mistakes. Quality context: Process / output: [PROCESS / OUTPUT] Team using it: [TEAM] Current errors: [ERRORS] Rework patterns: [REWORK] Customer or stakeholder impact: [IMPACT] Required standards: [STANDARDS] Compliance needs: [COMPLIANCE] Tools used: [TOOLS] Who creates the work: [CREATORS] Who reviews the work: [REVIEWERS] Deadline pressure: [DEADLINES] Design the quality system: Checklist Type Selection Choose the right checklist format: - do-confirm checklist - read-do checklist - pre-flight checklist - review checklist - launch checklist - handoff checklist - exception checklist - troubleshooting checklist Explain why this format fits. Pre-Work Checklist Create checks for: - required inputs - access - materials - stakeholder information - deadlines - assumptions - dependencies Execution Checklist Create step checks that prevent common mistakes. Each item must be: - observable - binary where possible - short - in the order of work - tied to a known risk Quality Gate Define: - gate name - when it happens - reviewer - pass criteria - fail criteria - evidence required - rework path - escalation rule Final Review Checklist Create final checks for: - completeness - accuracy - formatting - compliance - customer impact - internal consistency - approval - documentation Failure Pattern Library List common failures and add prevention checks. Checklist Adoption Plan Define: - where checklist lives - when it must be used - how completion is recorded - who owns updates - review cadence - training needed Rules: - Do not create checklist items that are vague opinions. - Do not make checklists so long that people skip them. - Do not use a checklist to compensate for unclear ownership. - Every item should prevent a real error or confirm a real standard. --------------------------------------------------------------------------------

#212Tool Stack & Workflow Simplification Audit

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONCOOs, operations teams, IT, startups, agencies, remote teams, support teams, sales operations, marketing operations, and companies with tool sprawl.

Audit internal tools, duplicated systems, manual steps, unnecessary notifications, and workflow complexity to simplify work.

Act as a tool stack simplification consultant. Audit the tools and workflows used by [TEAM / COMPANY] and recommend how to reduce complexity without losing important functionality. Tool stack context: Company / team: [COMPANY / TEAM] Tools used: [TOOLS] What each tool is used for: [TOOL USE] Team size: [TEAM SIZE] Departments: [DEPARTMENTS] Main workflows: [WORKFLOWS] Integrations: [INTEGRATIONS] Current problems: [PROBLEMS] Duplicate data entry: [DUPLICATION] Notifications: [NOTIFICATIONS] Monthly tool costs: [COSTS] Security / access concerns: [SECURITY] Required tools: [REQUIRED TOOLS] Run the audit: Tool Purpose Table For each tool identify: - primary purpose - actual usage - owner - users - data stored - workflows affected - integrations - cost - risk if removed Overlap Detection Find overlaps in: - project management - chat - documentation - file storage - CRM - task tracking - reporting - approvals - forms - automation - analytics - customer communication Workflow Complexity Map Identify: - duplicate entry - manual transfer - too many status fields - unclear source of truth - unnecessary notifications - tool switching - missing integration - workarounds - shadow systems Simplification Options For each issue recommend: - keep - consolidate - remove - replace - integrate - automate - rename / restructure - restrict access - improve training - create usage rules Decision Matrix Score each tool by: - business value - user adoption - workflow dependency - cost - data importance - replaceability - security risk - complexity added Future-State Tool Rules Create rules for: - where tasks live - where docs live - where decisions live - where customer data lives - where reports live - what cannot be duplicated - who approves new tools Migration Plan Create: - quick cleanup - consolidation candidates - data migration needs - training plan - communication plan - risks - success metrics Rules: - Do not remove a tool without identifying what workflow it supports. - Do not recommend new tools before simplifying current ones. - Do not ignore data ownership and access risk. - The goal is fewer sources of truth and less context switching. --------------------------------------------------------------------------------

#213Delegated Task Brief Standard

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONManagers, founders, agencies, creative teams, operations teams, assistants, project managers, remote teams, and anyone whose delegated work often comes back incomplete.

Create a standard brief for assigning work with context, outcome, authority, constraints, examples, deadline, review points, and definition of done.

You are a delegation systems expert. Create a task brief standard for [TEAM / MANAGER] so delegated work is clear, complete, and easier to execute correctly. Delegation context: Team / manager: [TEAM / MANAGER] Type of work delegated: [WORK TYPES] People receiving tasks: [RECIPIENTS] Current delegation problems: [PROBLEMS] Common misunderstandings: [MISUNDERSTANDINGS] Review process: [REVIEW PROCESS] Deadline issues: [DEADLINE ISSUES] Quality issues: [QUALITY ISSUES] Tools used: [TOOLS] Build the standard: Task Brief Template Create a template with these fields: - task title - background - why this matters - desired outcome - owner - decision authority - deadline - priority - required inputs - constraints - examples - non-examples - quality standard - definition of done - review points - escalation triggers - dependencies - final delivery format Field Guide For each field explain: - why it matters - how to fill it - good example - bad example Delegation Levels Define levels: - follow exact instruction - execute with review before sending - choose method but confirm direction - own outcome and report progress - fully own outcome and improve process For each level include when to use it. Task Acceptance Rule Create rules for how the assignee confirms: - understanding - timeline - risks - missing information - first next step Review System Design: - first check-in - draft review - final review - feedback format - revision rules Manager Scripts Write examples for: - assigning a task clearly - correcting unclear output - changing deadline - expanding ownership - declining poor-quality work - praising strong ownership Rules: - Do not delegate without a definition of done. - Do not give responsibility without authority. - Do not assume urgency is obvious. - The standard must reduce rework and manager follow-up. --------------------------------------------------------------------------------

#214Internal Training Module Builder

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONHR teams, operations managers, trainers, customer support teams, sales teams, restaurants, retail teams, agencies, and companies onboarding employees into repeatable work.

Convert an SOP or internal process into a training module with learning objectives, practice tasks, examples, checks, and manager validation.

Act as an internal training designer. Convert [SOP / PROCESS / ROLE TASK] into a training module that teaches someone how to perform the work correctly. Training source: Topic: [TOPIC] Audience: [NEW HIRES / EXISTING TEAM / MANAGERS / ROLE] Existing SOP or process notes: [PASTE SOP / NOTES] Skill level of learners: [SKILL LEVEL] Training format: [LIVE / ASYNC / VIDEO / DOC / WORKSHOP] Time available: [TIME] Tools required: [TOOLS] Quality standard: [STANDARD] Common mistakes: [MISTAKES] Manager validation method: [VALIDATION] Design the module: Learning Objectives Write 3-6 objectives using observable actions. Example: - learner can identify... - learner can complete... - learner can explain... - learner can troubleshoot... Concept Map Explain: - why the process matters - where it fits in the business - what happens before it - what happens after it - who depends on it Training Sequence Create the lesson flow: 1. Context 2. Demonstration 3. Guided practice 4. Independent practice 5. Error review 6. Quality check 7. Manager validation For each section include: - teaching points - learner activity - materials needed - estimated time Practice Tasks Create: - beginner practice - realistic practice - edge-case practice - timed practice - quality review practice Knowledge Check Create: - multiple-choice questions - scenario questions - error-spotting questions - short answer questions - pass criteria Manager Validation Create a validation checklist: - learner completed task - learner followed SOP - learner handled exception - learner met quality standard - learner knows when to escalate Training Assets Recommend: - slides - screenshots - screen recording - checklist - quick reference guide - FAQ - practice dataset Rules: - Do not make training only informational. - Do not skip practice. - Do not certify someone based only on watching. - Training must connect directly to the real work output. --------------------------------------------------------------------------------

#215Decision Record & Internal Policy System

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONLeadership teams, operations teams, HR, finance, compliance-sensitive teams, startups, growing companies, and organizations where decisions disappear in chat.

Create a system for documenting decisions and policies so teams understand what changed, why, who approved it, and how to apply it.

You are an internal governance documentation specialist. Build a decision record and policy documentation system for [COMPANY / TEAM]. Governance context: Company / team: [COMPANY / TEAM] Current decision process: [DECISION PROCESS] Current policy process: [POLICY PROCESS] Where decisions are discussed: [CHANNELS] Where policies live: [POLICY LOCATION] Recurring confusion: [CONFUSION] Approval roles: [APPROVAL ROLES] Sensitive policy areas: [SENSITIVE AREAS] Compliance concerns: [COMPLIANCE] Who needs access: [AUDIENCE] Create the system: Decision Record Template Create a template with: - decision title - decision date - owner - approver - context - problem - options considered - decision made - reason - tradeoffs - people affected - implementation steps - review date - related documents Decision Classification Define decision types: - strategic - operational - financial - people / HR - customer exception - vendor - policy - process - tool - urgent incident For each type define documentation requirement. Policy Template Create a policy template: - policy title - purpose - who it applies to - policy statement - definitions - responsibilities - procedure - exceptions - enforcement / consequences - related documents - owner - review date - approval history Approval Path Define: - who drafts - who reviews - who approves - who communicates - who maintains - when legal / HR / finance review is needed Communication Rule Create message formats for: - new decision - changed policy - urgent policy update - decision reversal - clarification - reminder Decision Search System Define how decisions and policies should be named, tagged, stored, and linked. Review Cadence Create a quarterly review process: - expired decisions - outdated policies - unclear exceptions - repeated questions - needed updates Rules: - Do not let major decisions live only in Slack, email, or memory. - Do not write policies so vague that managers interpret them differently. - Do not hide tradeoffs. - Mark legal-sensitive areas as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#216Automation Opportunity Backlog

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations teams, AI automation teams, COOs, founders, agencies, admin teams, marketing operations, HR operations, finance operations, and teams exploring AI workflows.

Identify repetitive internal work that can be automated, templated, delegated, eliminated, or improved before automation.

Act as an automation opportunity analyst. Build an automation backlog for [TEAM / COMPANY] by reviewing repetitive work and separating true automation opportunities from process problems. Work inventory: Team / company: [TEAM / COMPANY] Recurring tasks: [TASKS] Task frequency: [FREQUENCY] Time spent: [TIME SPENT] Tools used: [TOOLS] Manual data entry: [MANUAL ENTRY] Repeated copy / messages: [REPEATED COPY] Approval steps: [APPROVALS] Current errors: [ERRORS] Current templates: [TEMPLATES] Data sensitivity: [DATA SENSITIVITY] Available automation tools: [AUTOMATION TOOLS] Team skill level: [SKILL LEVEL] Budget: [BUDGET] Classify each task: Category 1 - Eliminate Work that should not exist. Category 2 - Simplify Work that is too complex because the process is unclear. Category 3 - Template Work that can be standardized without automation. Category 4 - Checklist Work that needs consistency before automation. Category 5 - Delegate Work that belongs to another role. Category 6 - Automate Work that is stable, repetitive, rule-based, and low-risk enough to automate. Category 7 - AI-Assisted Work that requires judgment but can be accelerated with AI. Automation Readiness Score Score each task from 1 to 5 across: - repetition - rule clarity - data availability - error risk - time savings - business impact - tool compatibility - sensitivity risk - process stability - human review need Opportunity Cards For each top opportunity include: - task - current process - proposed improvement - automation type - tools needed - data needed - human review gate - risk - estimated time saved - owner - first test Pilot Plan Create a 30-day pilot: - first automation to test - process documentation needed - success metric - failure metric - QA check - rollback plan - training needed Rules: - Do not automate a broken process before simplifying it. - Do not automate high-risk decisions without human approval. - Do not ignore data privacy or access control. - Prioritize boring, frequent, stable work first. --------------------------------------------------------------------------------

#217Runbook & Incident Response Document Builder

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations teams, IT, customer support, logistics, restaurants, retail, SaaS teams, facilities teams, vendor management, and any business needing repeatable emergency response.

Build a practical runbook for recurring incidents, operational failures, urgent issues, outages, customer escalations, and emergency procedures.

You are an incident runbook writer. Create a runbook for [INCIDENT / EMERGENCY / OPERATIONAL ISSUE] so the team knows exactly what to do under pressure. Incident context: Incident type: [INCIDENT TYPE] Business area: [AREA] Who detects it: [DETECTOR] Who owns response: [OWNER] Severity levels: [SEVERITY LEVELS] Customer impact: [CUSTOMER IMPACT] Operational impact: [OPERATIONAL IMPACT] Tools / systems: [TOOLS] Contacts: [CONTACTS] Vendor involvement: [VENDORS] Compliance or safety requirements: [REQUIREMENTS] Previous incidents: [HISTORY] Current response process: [CURRENT PROCESS] Build the runbook: 1. Incident Definition Explain what qualifies as this incident and what does not. 2. Severity Levels Create severity levels: - low - medium - high - critical For each define: - symptoms - customer impact - response time - owner - escalation requirement - communication requirement 3. Detection Checklist List how the issue is detected: - alerts - customer reports - employee observation - dashboard signals - vendor notice - system failure - physical inspection 4. Immediate Response Create exact first actions: - confirm issue - protect safety or customer impact - notify owner - gather facts - stop further damage - start incident log 5. Response Workflow Write steps for: - triage - containment - communication - resolution - verification - customer / stakeholder update - documentation - post-incident review 6. Communication Templates Create: - internal alert - manager update - customer-facing message - vendor escalation - leadership update - resolved notice 7. Escalation Matrix Define: - who to contact - when to escalate - what information to include - backup contacts - after-hours rules 8. Post-Incident Review Create template: - what happened - timeline - root cause - impact - response quality - prevention actions - owners - deadlines Rules: - Do not rely on memory during incidents. - Do not make the runbook too vague to use under pressure. - Do not skip communication ownership. - Mark safety, legal, HR, or compliance issues as [SPECIAL REVIEW]. --------------------------------------------------------------------------------

#218Documentation Governance Cadence

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONOperations leaders, HR teams, knowledge managers, compliance teams, customer support, SaaS teams, agencies, and growing companies with outdated docs.

Create a maintenance system so internal documentation stays accurate, owned, reviewed, archived, and improved over time.

Act as a documentation governance lead. Design a governance cadence for [COMPANY / TEAM] that keeps internal documentation useful, current, and trusted. Governance context: Company / team: [COMPANY / TEAM] Documentation platform: [PLATFORM] Number of docs: [DOC COUNT] Departments: [DEPARTMENTS] Current owners: [OWNERS] Current review process: [REVIEW PROCESS] Pain points: [PAIN POINTS] High-risk documents: [HIGH-RISK DOCS] Compliance requirements: [COMPLIANCE] New hire dependency: [ONBOARDING DEPENDENCY] Process change frequency: [CHANGE FREQUENCY] Create the governance cadence: Ownership Model Define: - document owner - subject matter expert - reviewer - approver - documentation admin - user feedback owner For each role include responsibilities. Document Lifecycle Create lifecycle stages: - draft - under review - approved - active - needs update - deprecated - archived For each stage define rules and labels. Review Cadence Assign review frequency: - monthly - quarterly - twice per year - annually - event-based review - after incident review - after policy change review Define which doc types belong in each frequency. Change Management Define how updates happen: - change request submitted - owner reviews - SME updates - approver approves - change log updated - users notified - old version archived Doc Health Dashboard Track: - docs without owner - docs past review date - high-use docs - docs with low trust - repeated search failures - duplicate docs - archived docs - recent updates - user feedback Governance Meetings Design: - monthly documentation cleanup - quarterly high-risk review - annual archive review For each include purpose, agenda, owners, outputs. User Feedback Loop Create ways users can report: - outdated doc - unclear instruction - missing SOP - broken link - duplicate doc - wrong owner Rules: - Do not create documentation governance that depends on one person remembering everything. - Do not let old docs stay active without warning. - Do not review low-risk docs as often as high-risk docs. - Governance must protect trust in the documentation system. --------------------------------------------------------------------------------

#219Searchable Wiki Cleanup Sprint

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONTeams using Notion, Confluence, Google Drive, Slab, ClickUp Docs, SharePoint, Guru, Coda, or any internal knowledge base that has become cluttered.

Clean up a messy internal wiki by reorganizing pages, renaming documents, removing duplicates, archiving old content, and creating better navigation.

You are an internal wiki cleanup specialist. Plan a focused cleanup sprint for [WIKI / KNOWLEDGE BASE] so employees can find accurate information faster. Wiki context: Platform: [PLATFORM] Current structure: [CURRENT STRUCTURE] Page / folder list: [PASTE LIST] Known search issues: [SEARCH ISSUES] Most-used docs: [MOST USED DOCS] Outdated docs: [OUTDATED DOCS] Duplicate docs: [DUPLICATES] Departments using it: [DEPARTMENTS] Important user questions: [QUESTIONS] Sensitive docs: [SENSITIVE DOCS] Sprint length: [SPRINT LENGTH] People available: [PEOPLE] Plan the sprint: Sprint Goal Write a clear goal and success definition. Example success signals: - employees can find key docs in under 60 seconds - no active doc lacks an owner - duplicated SOPs are merged - outdated docs are archived - top-level navigation is clear Wiki Triage Labels Create labels: - keep - update - merge - split - rename - move - archive - delete after approval - restrict access - convert to template - convert to SOP - needs owner Cleanup Board Create a table: - page / doc - current location - problem - action - owner - priority - approval needed - due date Navigation Redesign Recommend: - top-level categories - landing pages - department hubs - role-based start pages - popular docs section - new hire path - search tags - glossary - owner directory Renaming Rules Create clear title formulas for: - SOPs - policies - templates - guides - checklists - meeting notes - project docs - decision records Archive Policy Define: - when to archive - who approves archive - how to label archived docs - how to preserve history - how to prevent old docs from appearing as current Team Communication Write: - sprint announcement - owner request message - doc update request - cleanup completion note Rules: - Do not delete sensitive or historical information without approval. - Do not reorganize only by department if users search by task. - Do not create clever titles that hurt search. - The sprint must improve findability and trust. --------------------------------------------------------------------------------

#220Full Productivity, SOPs & Internal Documentation Audit

PRODUCTIVITY, SOPS & INTERNAL DOCUMENTATIONCEOs, COOs, founders, operations leaders, consultants, HR leaders, department heads, knowledge managers, agencies, startups, and companies doing an operations reset.

Audit the full internal productivity and documentation system across workflows, SOPs, meetings, task flow, tools, knowledge base, automation, checklists, and governance.

Act as an independent productivity, SOP, and internal documentation auditor. Review the full working system of [COMPANY / TEAM] and identify the highest-leverage improvements for speed, clarity, quality, training, and operational consistency. Company context: Company / team: [COMPANY / TEAM] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Departments: [DEPARTMENTS] Core workflows: [WORKFLOWS] Current SOPs: [SOPS] Current documentation platform: [DOC PLATFORM] Task management tools: [TASK TOOLS] Communication channels: [CHANNELS] Meeting cadence: [MEETINGS] Automation tools: [AUTOMATION TOOLS] Known productivity problems: [PRODUCTIVITY PROBLEMS] Known documentation problems: [DOCUMENTATION PROBLEMS] Training issues: [TRAINING ISSUES] Repeated mistakes: [MISTAKES] Customer or stakeholder impact: [IMPACT] Leadership concerns: [CONCERNS] Audit the system across 20 dimensions: 1. Priority clarity 2. Task intake 3. Task triage 4. Workflow design 5. Handoffs 6. Decision documentation 7. Meeting effectiveness 8. Async communication 9. Tool stack simplicity 10. SOP coverage 11. SOP quality 12. Checklist and QA gates 13. Internal knowledge architecture 14. Search and navigation 15. Documentation ownership 16. Documentation maintenance 17. Training from documentation 18. Automation readiness 19. Incident runbooks 20. Governance cadence For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - time loss risk - quality risk - training risk - customer / business risk - recommended fix - confidence level Then synthesize: A. Top 5 operational constraints Rank by: - time recovered - quality improvement - training impact - customer impact - ease of fixing - urgency - confidence B. Root cause analysis Identify whether the main issue is: - unclear priorities - weak task intake - too many meetings - tool sprawl - undocumented processes - outdated docs - no doc owners - poor handoffs - unclear decision rights - lack of checklists - no training system - automation before process clarity - no governance cadence - low documentation trust C. Future-state operating system Create: - weekly productivity rhythm - task triage system - meeting rules - async communication protocol - SOP library structure - process map standards - checklist system - decision record system - wiki architecture - automation backlog - documentation governance cadence D. 30/60/90-day improvement plan Create a practical plan with: - actions - owners - SOPs to create - docs to update - meetings to remove - workflows to map - tools to simplify - checklists to launch - automations to pilot - metrics to track - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard productivity truth - the biggest documentation risk - the fastest time-saving action - the highest-value SOP to create - the biggest tool or meeting issue - the next leadership decision - the data needed before deeper changes Rules: - Do not invent process data. - Do not recommend automation before process cleanup. - Do not blame employees before checking workflow design. - Use [LOW CONFIDENCE] where evidence is missing. - Focus on clarity, speed, consistency, knowledge access, and repeatable execution.

#221Strategic Risk Register Architect

RISK, COMPLIANCE & DECISION MAKINGCEOs, COOs, founders, risk managers, compliance teams, finance leaders, operations leaders, department heads, consultants, and companies that need clearer visibility into business risk.

Build a practical risk register that turns vague business threats into categorized risks, owners, probability, impact, controls, thresholds, and response actions.

You are a strategic risk management advisor. Build a complete risk register for [COMPANY NAME] that leadership can use to identify, prioritize, monitor, and respond to business risks. Company context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Industry: [INDUSTRY] Company size: [SIZE] Geography: [GEOGRAPHY] Main revenue streams: [REVENUE STREAMS] Critical operations: [CRITICAL OPERATIONS] Current goals: [GOALS] Known risks: [KNOWN RISKS] Recent incidents: [INCIDENTS] Regulatory environment: [REGULATIONS] Leadership concerns: [CONCERNS] Available risk data: [DATA] Create the risk register in this structure: 1. Risk universe Identify risks across these categories: - strategic risk - financial risk - operational risk - compliance risk - legal risk - customer risk - reputational risk - technology risk - cybersecurity risk - data privacy risk - people risk - vendor / third-party risk - market risk - supply chain risk - business continuity risk - decision-making risk 2. Risk cards For each risk create a card with: - risk name - risk statement - category - root cause - trigger event - possible consequences - affected teams - probability - impact - velocity - current controls - control weakness - risk owner - early warning indicators - response plan - review cadence - confidence level 3. Probability and impact scoring Use a 1-5 scoring system. Define: - probability score - impact score - velocity score - detectability score - residual risk score 4. Heatmap Create a risk heatmap: - critical risks - high risks - medium risks - low risks - watchlist risks 5. Response strategy For each high-priority risk choose: - avoid - reduce - transfer - accept - monitor - escalate Explain why. 6. Governance plan Define: - who owns the register - who updates it - how often it is reviewed - when leadership is notified - when board review is needed - what evidence must be collected 7. First 30-day risk actions Create a practical action plan with owners, deadlines, and expected outputs. Rules: - Do not create generic risks that could apply to any company. - Do not treat risk scoring as precise if evidence is weak. - Do not assign a risk without an owner. - Use [NEEDS DATA] where information is missing. Done when leadership can see the highest risks and the next action for each one. --------------------------------------------------------------------------------

#222Compliance Obligation Map

RISK, COMPLIANCE & DECISION MAKINGCompliance officers, founders, operations leaders, finance teams, HR teams, legal-adjacent teams, regulated businesses, healthcare-adjacent teams, food service groups, fintech, SaaS, and companies preparing for audits.

Convert laws, regulations, standards, contracts, policies, and internal requirements into a clear compliance obligation map with owners, evidence, controls, and review cadence.

Act as a compliance obligation mapper. Translate the requirements affecting [COMPANY NAME] into a working compliance map that teams can actually follow. Important: This is not legal advice. Flag legal-sensitive items as [LEGAL REVIEW]. If a rule is uncertain, mark it as [VERIFY]. Inputs: Company: [COMPANY NAME] Industry: [INDUSTRY] Jurisdictions: [JURISDICTIONS] Products / services: [PRODUCTS / SERVICES] Customer types: [CUSTOMERS] Employee count: [EMPLOYEE COUNT] Data handled: [DATA TYPES] Facilities / locations: [LOCATIONS] Vendors / processors: [VENDORS] Contracts with obligations: [CONTRACTS] Known regulations / standards: [REGULATIONS / STANDARDS] Internal policies: [POLICIES] Upcoming audits or inspections: [AUDITS] Known compliance issues: [ISSUES] Build the obligation map: Layer 1 - Source inventory List all possible sources of obligations: - law / regulation - industry standard - customer contract - vendor contract - license / permit - insurance requirement - internal policy - certification - audit requirement - reporting requirement Layer 2 - Obligation extraction For each obligation identify: - obligation statement - source - jurisdiction - applicable business area - responsible team - required action - frequency - deadline - evidence required - penalty or risk if missed - confidence level Layer 3 - Control mapping For each obligation define: - preventive control - detective control - corrective control - control owner - evidence owner - review cadence - system or document used - current weakness Layer 4 - Responsibility matrix Create a responsibility matrix: - accountable owner - process owner - evidence collector - reviewer - approver - escalation contact Layer 5 - Compliance calendar Create a calendar of: - recurring filings - license renewals - policy reviews - employee training - audit dates - inspection preparation - reporting deadlines - vendor reviews Layer 6 - Gap list Identify: - missing policies - missing evidence - unclear ownership - outdated controls - training gaps - documentation gaps - high-risk obligations needing legal review Final output: - executive summary - obligation table - top 10 compliance risks - 30/60/90-day remediation plan Rules: - Do not invent specific legal requirements where the source is missing. - Do not bury deadlines in paragraphs. - Do not assign compliance to "everyone." - Separate legal interpretation from operational execution. --------------------------------------------------------------------------------

#223High-Stakes Decision Memo Builder

RISK, COMPLIANCE & DECISION MAKINGCEOs, founders, executives, managers, product leaders, finance teams, operations leaders, boards, consultants, and teams making important strategic or operational decisions.

Create a decision memo that turns complex options into clear tradeoffs, evidence, risks, assumptions, decision criteria, and a final recommendation.

You are an executive decision memo writer. Create a decision-ready memo for [DECISION TOPIC] so leadership can choose a direction with clarity. Decision context: Decision to make: [DECISION] Company / team: [COMPANY / TEAM] Why now: [WHY NOW] Options being considered: [OPTIONS] Business goal: [GOAL] Constraints: [CONSTRAINTS] Available data: [DATA] Stakeholders affected: [STAKEHOLDERS] Risks: [RISKS] Budget / resources: [BUDGET / RESOURCES] Timeline: [TIMELINE] Decision owner: [OWNER] Known disagreements: [DISAGREEMENTS] Write the memo using this format: 1. Decision request State exactly what decision is needed. Use this sentence: "We need to decide whether to [DECISION] by [DATE] so that [BUSINESS OUTCOME]." 2. Recommendation upfront Choose one recommendation: - proceed - proceed with conditions - delay - run a test first - choose option A - choose option B - do not proceed - escalate for more input Explain the recommendation in 5 sentences or less. 3. Options table For each option include: - option - what it means - upside - downside - cost - timeline - operational impact - people impact - customer impact - reversibility - risk level - confidence level 4. Decision criteria Define weighted criteria such as: - revenue impact - cost impact - speed - risk - customer experience - strategic fit - execution complexity - compliance exposure - team capacity - reversibility Score each option. 5. Assumptions and evidence Separate: - confirmed facts - strong assumptions - weak assumptions - unknowns - data needed - opinions 6. Risk section For the recommended option include: - top risks - likelihood - impact - mitigation - owner - trigger for reconsideration 7. Implementation implications If approved, define: - first step - owner - timeline - budget - dependencies - communication needed - success metric 8. Decision log entry Create a short decision record that can be saved internally. Rules: - Do not hide the recommendation at the end. - Do not pretend weak assumptions are facts. - Do not include more options than leadership can reasonably compare. - Do not optimize only for speed if risk is material. --------------------------------------------------------------------------------

#224Risk Appetite & Escalation Threshold Charter

RISK, COMPLIANCE & DECISION MAKINGCEOs, boards, founders, COOs, risk teams, finance leaders, operations leaders, compliance teams, and companies that need clearer decision boundaries.

Define what level of risk the company is willing to accept, where risk must be reduced, and when decisions must be escalated to leadership.

Act as a risk governance designer. Create a risk appetite and escalation threshold charter for [COMPANY NAME] so teams know what they can decide independently and what must be escalated. Inputs: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Industry: [INDUSTRY] Stage of company: [STAGE] Strategic goals: [GOALS] Regulatory exposure: [REGULATORY EXPOSURE] Financial constraints: [FINANCIAL CONSTRAINTS] Customer trust requirements: [CUSTOMER TRUST] Operational risks: [OPERATIONAL RISKS] Leadership concerns: [CONCERNS] Current decision rights: [DECISION RIGHTS] Past risk incidents: [INCIDENTS] Build the charter: A. Risk appetite statements Create appetite statements for: - financial risk - legal / compliance risk - customer trust risk - brand / reputation risk - safety risk - data privacy risk - cybersecurity risk - operational risk - vendor dependency risk - people risk - innovation / experimentation risk For each category define: - low appetite - moderate appetite - high appetite - no appetite B. Risk tolerance thresholds Define measurable thresholds for escalation: - financial loss amount - customer count affected - data sensitivity level - regulatory exposure - SLA breach severity - negative publicity risk - vendor dependency - employee impact - strategic impact - reversibility C. Decision zones Create three zones: Green zone: - teams can decide independently - documentation required - review cadence Yellow zone: - manager approval required - mitigation plan required - monitoring required Red zone: - executive approval required - legal / compliance review may be needed - board notification may be needed D. Escalation rules Define when to escalate: - before acting - immediately after detection - during incident response - before customer communication - before signing - before spending - before changing policy E. Examples Create 20 realistic examples of decisions and classify each as green, yellow, or red. F. Governance Define: - owner of the charter - review frequency - communication plan - training needs - exception process Rules: - Do not create thresholds so vague that teams still need permission for everything. - Do not allow high-risk decisions to stay informal. - Do not confuse risk appetite with risk ignorance. - The charter must increase decision speed and reduce unmanaged exposure. --------------------------------------------------------------------------------

#225Internal Control Design Canvas

RISK, COMPLIANCE & DECISION MAKINGFinance teams, operations leaders, compliance teams, COOs, founders, controllers, internal auditors, department heads, and businesses needing stronger process control.

Design internal controls that prevent, detect, and correct errors, fraud, compliance failures, quality issues, and operational breakdowns.

You are an internal control designer. Build a control canvas for [PROCESS NAME] at [COMPANY NAME] that reduces risk without creating unnecessary bureaucracy. Process context: Company: [COMPANY NAME] Process: [PROCESS NAME] Process owner: [OWNER] Process steps: [STEPS] Systems used: [SYSTEMS] People involved: [PEOPLE] Approvals required: [APPROVALS] Known errors: [ERRORS] Known fraud or abuse risks: [FRAUD RISKS] Compliance requirements: [COMPLIANCE] Financial exposure: [FINANCIAL EXPOSURE] Customer impact: [CUSTOMER IMPACT] Current controls: [CURRENT CONTROLS] Use this control canvas: Canvas Block 1 - Process objective Define what the process is supposed to achieve and what must be protected. Canvas Block 2 - Failure modes List how the process can fail: - wrong data - unauthorized action - missing approval - duplicate payment - missed deadline - policy violation - quality issue - fraud - customer harm - compliance failure - system error - handoff failure Canvas Block 3 - Risk points Map the process step where each risk appears. For each risk point include: - risk - process step - cause - impact - likelihood - current detection method - weakness Canvas Block 4 - Control design Design controls across: Preventive controls: - approval - access restriction - checklist - segregation of duties - system validation - required fields - policy limit Detective controls: - reconciliation - exception report - manager review - audit sample - dashboard alert - variance analysis Corrective controls: - rework process - escalation - refund / adjustment - incident log - root cause review - training update Canvas Block 5 - Control quality For each control define: - owner - frequency - evidence - system - exception rule - testing method - failure response Canvas Block 6 - Lean control check Identify controls that are: - essential - useful but too manual - duplicative - outdated - missing - too weak - too burdensome Final output: - control matrix - top control gaps - recommended redesign - testing plan - 30-day implementation plan Rules: - Do not add controls that nobody will perform. - Do not rely only on trust where money, data, safety, or compliance is involved. - Do not create approvals without decision criteria. - Good controls should reduce risk and preserve workflow speed. --------------------------------------------------------------------------------

#226Compliance Training Scenario Lab

RISK, COMPLIANCE & DECISION MAKINGHR teams, compliance teams, operations leaders, managers, regulated businesses, food service groups, finance teams, data-handling teams, and companies building employee training.

Create realistic compliance training scenarios that teach employees how to recognize risk, make the right choice, escalate issues, and document actions.

Act as a compliance training designer. Create scenario-based training for [COMPLIANCE TOPIC] at [COMPANY NAME] that helps employees apply the rules in real situations. Training context: Company: [COMPANY NAME] Compliance topic: [TOPIC] Audience: [AUDIENCE] Employee roles: [ROLES] Regulatory or policy source: [SOURCE] Common mistakes: [MISTAKES] High-risk situations: [HIGH-RISK SITUATIONS] Reporting / escalation path: [ESCALATION] Required documentation: [DOCUMENTATION] Tone: [TONE] Training length: [LENGTH] Assessment requirement: [ASSESSMENT] Build the training lab: 1. Learning outcomes Write 5-7 outcomes employees must achieve. Each outcome must start with: "After this training, employees can..." 2. Plain-language rule summary Explain the rule without legal or policy jargon. Include: - what is required - what is prohibited - what is allowed with approval - what must be documented - when to escalate 3. Scenario set Create 10 realistic scenarios. For each scenario include: - situation - role involved - pressure or ambiguity - possible choices - best answer - why it is correct - what could go wrong - escalation required - documentation required 4. Red flag recognition List red flags employees should notice. Organize them into: - words customers / vendors may say - documents that look wrong - process shortcuts - unusual requests - missing information - conflicts of interest - pressure tactics - safety / privacy / legal warning signs 5. Micro-assessment Create: - 10 multiple choice questions - 5 true / false questions - 3 short answer questions - answer key - passing criteria 6. Manager reinforcement guide Create a 15-minute team discussion guide. Include: - opening - 3 discussion questions - examples to ask for - what managers should clarify - where to send questions Rules: - Do not make training only about memorizing policy text. - Do not use unrealistic perfect-world examples. - Do not shame employees for asking questions. - Mark legal-sensitive content as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#227Incident Response Decision Tree

RISK, COMPLIANCE & DECISION MAKINGOperations teams, compliance teams, IT teams, cybersecurity teams, customer support, HR, finance, risk managers, executives, and companies preparing for service, safety, data, vendor, or customer incidents.

Create a decision tree for handling incidents from detection to triage, escalation, communication, containment, documentation, recovery, and postmortem.

You are an incident response architect. Build a decision tree for handling [INCIDENT TYPE] at [COMPANY NAME]. Incident context: Company: [COMPANY NAME] Incident type: [INCIDENT TYPE] Examples of incidents: [EXAMPLES] Critical systems or processes: [SYSTEMS / PROCESSES] Customers affected: [CUSTOMERS] Data involved: [DATA] Legal / compliance exposure: [EXPOSURE] Internal teams: [TEAMS] External parties: [EXTERNAL PARTIES] Current response process: [CURRENT PROCESS] Communication channels: [CHANNELS] Escalation contacts: [CONTACTS] Service obligations: [OBLIGATIONS] Create the decision tree: Start condition Define what counts as a suspected incident. Decision Node 1 - Is there immediate harm or active risk? Branches: - yes: contain immediately - no: proceed to classification - unknown: treat as potentially active and investigate Decision Node 2 - What type of incident is it? Classify: - customer service failure - data privacy event - cybersecurity event - financial error - safety issue - vendor failure - compliance breach - employee conduct issue - operational outage - reputational issue Decision Node 3 - Severity level Create severity levels: S1 - critical S2 - high S3 - moderate S4 - low S5 - informational For each define: - customer impact - business impact - legal / compliance impact - response time - owner - escalation requirement Decision Node 4 - Who must be notified? Define notification rules for: - incident owner - leadership - legal / compliance - customer support - affected customers - vendors - regulators, if applicable - insurance, if applicable - board, if applicable Mark legal/regulatory notification items as [LEGAL REVIEW]. Decision Node 5 - What action happens first? Create first-action rules: - contain - investigate - communicate - preserve evidence - stop process - disable access - issue customer update - escalate to specialist - activate backup plan Decision Node 6 - What must be documented? Create incident log fields: - time detected - reporter - description - systems affected - people affected - actions taken - decisions made - evidence - communications - owner - next update time Recovery phase Define: - resolution criteria - customer recovery - operational recovery - control restoration - leadership update - post-incident review Postmortem Create a postmortem template: - what happened - why it happened - impact - response quality - root cause - corrective actions - owners - deadlines Rules: - Do not wait for perfect information before containing active risk. - Do not communicate externally without approved facts in high-risk incidents. - Do not skip evidence preservation. - Do not close incidents without prevention actions. --------------------------------------------------------------------------------

#228Policy Gap Audit

RISK, COMPLIANCE & DECISION MAKINGHR teams, compliance teams, operations leaders, founders, managers, legal-adjacent teams, multi-location businesses, regulated industries, and companies preparing for audits or growth.

Audit company policies to find missing, outdated, vague, unenforced, risky, contradictory, or poorly communicated rules.

Act as a policy auditor. Review the policy set for [COMPANY NAME] and identify gaps, contradictions, unclear ownership, and operational risks. Policy inputs: Company: [COMPANY NAME] Industry: [INDUSTRY] Locations / jurisdictions: [LOCATIONS] Employee count: [EMPLOYEE COUNT] Customer types: [CUSTOMERS] Current policies: [PASTE POLICY LIST OR TEXT] Known incidents or violations: [INCIDENTS] Audit or inspection concerns: [AUDIT CONCERNS] Regulatory requirements known: [REQUIREMENTS] Manager confusion: [MANAGER CONFUSION] Employee questions: [EMPLOYEE QUESTIONS] Business changes since last update: [CHANGES] Run the audit: Audit Lens A - Coverage Identify whether policies exist for: - code of conduct - conflicts of interest - anti-bribery / gifts - data privacy - information security - access control - expense reimbursement - procurement - vendor management - customer complaints - refunds / credits - HR and attendance - health and safety - incident reporting - document retention - compliance training - approvals and authority - remote work, if relevant Audit Lens B - Clarity For each policy evaluate: - who it applies to - what is required - what is prohibited - what needs approval - who approves - what evidence is needed - what happens if not followed - where questions go Audit Lens C - Operational usability Check whether the policy is: - written in plain language - easy to find - easy to follow - connected to a process - supported by templates - trained to employees - reviewed regularly - enforced consistently Audit Lens D - Risk Classify policy gaps as: - critical - high - medium - low - watchlist Include: - risk created - likely scenario - affected team - owner - recommended fix - legal review needed Audit Lens E - Contradictions Find contradictions between: - policy and practice - different policies - policy and customer promise - policy and manager behavior - policy and system settings - policy and contract terms Final deliverables: - policy gap register - top 10 urgent policy fixes - policies to rewrite - policies to create - policies to retire - communication plan - review calendar Rules: - Do not assume a policy exists because a process exists. - Do not rewrite legal language without flagging [LEGAL REVIEW]. - Do not create policies nobody can enforce. - Policies must be clear enough for managers and employees to use. --------------------------------------------------------------------------------

#229Third-Party Risk Classification Grid

RISK, COMPLIANCE & DECISION MAKINGProcurement, compliance teams, operations leaders, IT, finance, vendor managers, startups, SaaS companies, agencies, retail groups, restaurant groups, and companies with growing vendor portfolios.

Classify vendors, partners, contractors, platforms, and service providers by risk level based on data access, business dependency, customer impact, compliance exposure, and switching difficulty.

You are a third-party risk analyst. Classify the third parties used by [COMPANY NAME] and design the right level of review, controls, monitoring, and escalation for each one. Third-party data: Company: [COMPANY NAME] Third-party list: [LIST] Services provided: [SERVICES] Annual spend: [SPEND] Contract terms: [CONTRACTS] Data access: [DATA ACCESS] System access: [SYSTEM ACCESS] Customer impact: [CUSTOMER IMPACT] Operational dependency: [DEPENDENCY] Compliance obligations: [COMPLIANCE] Known issues: [ISSUES] Renewal dates: [RENEWALS] Internal owners: [OWNERS] Create the classification grid: Risk dimensions Score each third party from 1 to 5 across: - data sensitivity - system access - financial exposure - customer impact - operational dependency - regulatory / compliance exposure - brand / reputation exposure - subcontractor complexity - geographic / jurisdiction risk - switching difficulty - incident history - contract weakness Risk tiers Classify each third party as: Tier 1 - critical Tier 2 - high risk Tier 3 - moderate risk Tier 4 - low risk Tier 5 - minimal risk For each tier define: - due diligence required - contract review level - security review level - insurance / certification requirements - performance monitoring - review cadence - approval authority - exit plan requirement Third-party profile card For each significant third party include: - name - service - owner - tier - key risks - current controls - missing evidence - renewal risk - required action - deadline Monitoring plan Define ongoing monitoring for: - SLA performance - incident history - certificate renewals - data access changes - financial exposure - contract renewal - user access review - customer complaints - dependency concentration Escalation rules Define when to escalate: - vendor incident - missed SLA - contract breach - data exposure - price increase - critical service instability - owner missing - renewal approaching with unresolved risk Rules: - Do not review every vendor with the same intensity. - Do not ignore low-spend vendors if they have high data or operational risk. - Do not classify risk without an internal owner. - Mark missing vendor evidence as [NEEDS DATA]. --------------------------------------------------------------------------------

#230Data Privacy Impact Assessment Workshop

RISK, COMPLIANCE & DECISION MAKINGSaaS teams, ecommerce brands, marketing teams, product teams, operations teams, compliance teams, privacy managers, founders, and businesses handling personal data.

Assess privacy risk for a product, process, campaign, vendor, or workflow by mapping data collected, purpose, consent, retention, access, sharing, controls, and customer impact.

Act as a privacy impact assessment facilitator. Run a structured privacy review for [PROJECT / PROCESS / TOOL] at [COMPANY NAME]. Important: This is not legal advice. Mark regulatory interpretation as [LEGAL REVIEW]. Use [VERIFY] where the facts are uncertain. Assessment context: Company: [COMPANY NAME] Project / process / tool: [PROJECT] Business purpose: [PURPOSE] Data subjects: [CUSTOMERS / EMPLOYEES / USERS / VENDORS] Data collected: [DATA] Sensitive data involved: [SENSITIVE DATA] Data sources: [SOURCES] Data storage: [STORAGE] Data sharing: [SHARING] Vendors / processors: [VENDORS] Jurisdictions: [JURISDICTIONS] Retention period: [RETENTION] Security controls: [CONTROLS] Customer-facing notices: [NOTICES] Consent mechanism: [CONSENT] Known concerns: [CONCERNS] Run the workshop: Round 1 - Data flow map Map: - what data is collected - where it comes from - why it is collected - where it is stored - who can access it - who it is shared with - how long it is kept - how it is deleted - where customers are informed Round 2 - Purpose and necessity check For each data element ask: - why do we need it? - what decision or process uses it? - can we collect less? - can we anonymize or aggregate? - what happens if we do not collect it? - is the purpose clear to the person? Round 3 - Rights and transparency check Review: - notice clarity - consent / lawful basis, if applicable - opt-out process - access request process - deletion request process - correction process - complaint process Round 4 - Risk assessment Identify risks: - overcollection - unclear purpose - weak consent - excessive retention - unnecessary sharing - weak access control - vendor exposure - cross-border transfer issue - sensitive data exposure - customer surprise - security weakness For each risk include likelihood, impact, mitigation, owner, and legal review need. Round 5 - Decision Recommend: - approve - approve with controls - redesign - delay pending legal review - reject Output: - privacy impact summary - data map - risk register - required controls - customer notice changes - open legal questions - approval record Rules: - Do not collect data just because it may be useful later. - Do not assume consent is valid without checking the actual customer experience. - Do not ignore vendors and subprocessors. - Privacy risk includes customer trust, not only legal exposure. --------------------------------------------------------------------------------

#231Ethics & Conflict-of-Interest Review Board

RISK, COMPLIANCE & DECISION MAKINGLeadership teams, HR, compliance, procurement, sales teams, finance, managers, founders, boards, and organizations that need better judgment in gray-area situations.

Review ethical dilemmas, conflicts of interest, incentives, gifts, side deals, biased decisions, insider access, or situations that may damage trust.

You are an ethics review board facilitator. Evaluate the situation below and help [COMPANY NAME] make a fair, transparent, and trust-protecting decision. Situation: Company: [COMPANY NAME] People involved: [PEOPLE] Situation summary: [SUMMARY] Decision needed: [DECISION] Relevant policies: [POLICIES] Financial interests: [FINANCIAL INTERESTS] Personal relationships: [RELATIONSHIPS] Gifts / benefits / incentives: [GIFTS OR BENEFITS] Customer or vendor involvement: [CUSTOMER / VENDOR] Power dynamics: [POWER DYNAMICS] Public perception risk: [PUBLIC RISK] Known facts: [FACTS] Unknowns: [UNKNOWNS] Run the ethics board review: Seat 1 - Facts chair List: - confirmed facts - missing facts - conflicting accounts - documents needed - people to interview Seat 2 - Policy chair Assess: - which policies apply - what the policy clearly says - where policy is ambiguous - what requires HR or legal review Seat 3 - Stakeholder chair Identify affected parties: - employees - customers - vendors - shareholders / owners - managers - public / community - regulators, if relevant For each party explain the trust impact. Seat 4 - Incentives chair Analyze: - who benefits - who may be disadvantaged - hidden incentives - pressure to decide too quickly - conflicts of interest - appearance of unfairness Seat 5 - Options chair Create decision options: - allow - allow with disclosure - allow with restrictions - require recusal - reject - investigate further - escalate to formal review - update policy For each option include upside, downside, fairness risk, trust risk, and implementation steps. Seat 6 - Reputation chair Ask: "If this decision were explained publicly with all facts known, would it still feel fair and defensible?" Seat 7 - Final recommendation Provide: - recommended decision - rationale - required documentation - communication plan - prevention action - policy update, if needed Rules: - Do not decide only based on whether something is technically allowed. - Do not ignore appearance of conflict. - Do not punish without facts. - Mark legal or HR-sensitive issues as [LEGAL / HR REVIEW]. --------------------------------------------------------------------------------

#232Fraud, Abuse & Anomaly Signal Map

RISK, COMPLIANCE & DECISION MAKINGFinance teams, operations leaders, compliance teams, marketplaces, ecommerce brands, SaaS teams, HR, procurement, internal audit, and companies with fraud or abuse exposure.

Identify signals of fraud, abuse, misuse, manipulation, leakage, policy violations, or suspicious activity in operational, financial, customer, or employee processes.

Act as a fraud and abuse risk analyst. Build a signal map for detecting suspicious activity in [PROCESS / SYSTEM] at [COMPANY NAME]. Process context: Company: [COMPANY NAME] Process / system: [PROCESS / SYSTEM] Users involved: [USERS] Transactions or actions: [TRANSACTIONS] Financial exposure: [FINANCIAL EXPOSURE] Data available: [DATA] Known fraud / abuse cases: [KNOWN CASES] Current controls: [CONTROLS] Approval rules: [APPROVALS] Tools used: [TOOLS] Investigation team: [TEAM] Policy constraints: [POLICIES] Create the signal map: Signal Families Identify suspicious signals across: - unusual volume - unusual timing - repeated small transactions - duplicate records - abnormal refunds / credits - approval bypass - mismatched vendor / customer data - repeated policy exceptions - account sharing - excessive permissions - sudden behavior change - suspicious location / device - unusual discounting - inventory mismatch - payroll or expense irregularity - fake accounts or reviews - collusion patterns Signal Cards For each signal include: - signal name - what it may indicate - data needed - threshold - false positive risk - severity - detection method - owner - immediate action - investigation step - documentation needed Anomaly Rules Create rules: - if signal A happens once, then... - if signal A repeats, then... - if signal A combines with signal B, then... - if high-value account is involved, then... - if employee access is involved, then... - if customer harm is possible, then... Investigation Workflow Create a safe workflow: 1. detect 2. preserve evidence 3. restrict access, if needed 4. review data 5. interview relevant parties, if appropriate 6. classify finding 7. remediate 8. document 9. update controls Response Categories Classify outcomes as: - false positive - process error - training issue - policy violation - suspicious activity - confirmed fraud / abuse - requires HR/legal review - requires customer remediation Dashboard Define metrics: - signal count - confirmed cases - false positive rate - loss prevented - investigation time - repeat offender patterns - control failures - unresolved cases Rules: - Do not accuse people without evidence. - Do not create surveillance beyond legitimate business need. - Do not ignore false positives. - Mark HR/legal-sensitive actions as [HR / LEGAL REVIEW]. --------------------------------------------------------------------------------

#233Business Continuity Stress Test

RISK, COMPLIANCE & DECISION MAKINGCOOs, operations leaders, risk managers, IT teams, finance teams, founders, facility managers, service businesses, retail groups, restaurant groups, logistics, and leadership teams.

Stress-test how the business responds to disruptions such as outages, staff shortages, supplier failure, cyber incidents, location closures, cash constraints, or demand spikes.

You are a business continuity stress-test facilitator. Test [COMPANY NAME]'s ability to continue operating during realistic disruption scenarios. Business context: Company: [COMPANY NAME] Critical products / services: [CRITICAL SERVICES] Critical locations: [LOCATIONS] Critical systems: [SYSTEMS] Critical vendors: [VENDORS] Critical roles: [ROLES] Customer commitments: [COMMITMENTS] Current continuity plan: [PLAN] Past disruptions: [PAST DISRUPTIONS] Recovery time requirements: [RTO] Data recovery requirements: [RPO] Known weak points: [WEAK POINTS] Available backup resources: [BACKUPS] Run the stress test: Scenario Set Simulate 8 disruption scenarios: 1. Key system goes down for 24 hours 2. Main vendor fails to deliver 3. Key employee or manager is unavailable 4. Location or facility is inaccessible 5. Cybersecurity incident limits access 6. Payment or finance system fails 7. Demand spikes beyond capacity 8. Negative public incident affects customer trust For each scenario produce: - scenario description - first warning signs - immediate impact - customer impact - financial impact - operational impact - people impact - legal / compliance exposure - first 2-hour response - first 24-hour response - first 7-day response - recovery requirement - failure point - mitigation Continuity Dependency Map Map dependencies: - systems - people - vendors - data - facilities - approvals - cash - communications - customer channels - logistics Readiness Score Score readiness from 1 to 5 across: - detection - escalation - backup process - communication - recovery speed - documentation - owner clarity - customer protection - compliance handling Gap Register Create: - gap - scenario exposed - risk - owner - required fix - deadline - cost / effort - priority Continuity Playbook Create: - emergency contacts - command structure - customer communication rules - backup process - vendor backup plan - manual workaround - recovery checklist - post-incident review Rules: - Do not assume normal staffing during disruption. - Do not rely on one person knowing the workaround. - Do not skip customer communication planning. - Continuity planning must protect critical operations first. --------------------------------------------------------------------------------

#234Board-Level Risk Report Generator

RISK, COMPLIANCE & DECISION MAKINGCEOs, CFOs, COOs, risk officers, compliance leaders, founders, board members, investors, and executive teams needing concise risk reporting.

Convert messy risk information into a clear board or leadership report with material risks, trends, decisions needed, mitigations, accountability, and confidence levels.

Act as a board risk reporting advisor. Create a board-level risk report for [COMPANY NAME] covering [REPORTING PERIOD]. Reporting inputs: Company: [COMPANY NAME] Reporting period: [PERIOD] Risk register: [RISK REGISTER] Incidents this period: [INCIDENTS] Compliance updates: [COMPLIANCE UPDATES] Audit findings: [AUDIT FINDINGS] Financial risk indicators: [FINANCIAL RISKS] Operational risk indicators: [OPERATIONAL RISKS] Cyber / data risk indicators: [CYBER / DATA RISKS] Legal or regulatory developments: [LEGAL / REGULATORY] Vendor risks: [VENDOR RISKS] People risks: [PEOPLE RISKS] Customer / reputational risks: [CUSTOMER / REPUTATION] Leadership concerns: [CONCERNS] Decisions needed: [DECISIONS] Write the report: Page 1 - Executive risk snapshot Include: - overall risk posture - top 5 material risks - risks increasing - risks decreasing - new risks - incidents requiring attention - decisions needed from board / leadership Page 2 - Top material risks For each material risk include: - risk statement - current status - trend - impact - probability - owner - mitigation progress - remaining exposure - decision or support needed Page 3 - Incident and compliance summary Summarize: - incidents opened - incidents closed - severe incidents - overdue remediation - regulatory / audit updates - compliance gaps - legal review items Page 4 - Risk indicators dashboard Create a simple dashboard with: - red indicators - amber indicators - green indicators - missing data - threshold breached - next update Page 5 - Decisions and asks Clearly state: - decisions needed - resources needed - risk acceptance requests - policy approvals - investment needs - escalation items Appendix - Detail table Create a detailed table for optional review. Rules: - Do not bury critical risks in a long list. - Do not hide weak data quality. - Do not report activity instead of risk posture. - Do not make the board guess what decision is needed. - Use [LOW CONFIDENCE] where evidence is weak. --------------------------------------------------------------------------------

#235Decision Quality Retrospective

RISK, COMPLIANCE & DECISION MAKINGLeadership teams, founders, managers, product teams, investment committees, operations leaders, finance teams, strategy teams, and organizations improving decision quality.

Review a past decision to understand whether it was good, lucky, flawed, rushed, biased, poorly executed, or missing critical evidence.

You are a decision quality facilitator. Run a retrospective on the decision: [PAST DECISION]. Decision history: Decision made: [DECISION] Date made: [DATE] Decision owner: [OWNER] People involved: [PEOPLE] Options considered: [OPTIONS] Evidence available at the time: [EVIDENCE THEN] Assumptions made: [ASSUMPTIONS] Expected outcome: [EXPECTED OUTCOME] Actual outcome: [ACTUAL OUTCOME] Timeline of execution: [TIMELINE] Unexpected events: [UNEXPECTED EVENTS] Current opinions about the decision: [OPINIONS] Run the retrospective: Stage 1 - Reconstruct the decision Create a timeline: - problem identified - options created - evidence gathered - debate held - decision made - implementation started - first results - final outcome Stage 2 - Separate decision quality from outcome quality Classify the decision as: - good decision, good outcome - good decision, bad outcome - bad decision, good outcome - bad decision, bad outcome - unclear due to missing evidence Explain the difference. Stage 3 - Decision criteria review Evaluate whether the team had clear criteria for: - strategic fit - financial impact - customer impact - execution feasibility - risk - reversibility - compliance exposure - timing - opportunity cost Stage 4 - Bias and failure mode scan Check for: - confirmation bias - sunk cost bias - authority bias - groupthink - urgency pressure - optimism bias - loss aversion - data cherry-picking - avoiding conflict - unclear decision owner - poor documentation Stage 5 - Execution review Analyze whether the outcome was affected by: - weak implementation - unclear ownership - insufficient resources - poor communication - wrong assumptions - external shock - delayed action - lack of monitoring Stage 6 - Lessons Create: - what we would do again - what we would change - what evidence we needed earlier - what decision rule should be created - what early warning signal was missed - how future decisions should improve Stage 7 - Decision learning record Write a concise record for future leaders. Rules: - Do not judge the decision only by the outcome. - Do not blame people before examining process. - Do not rewrite history with facts that were not available then. - The goal is better future decisions, not punishment. --------------------------------------------------------------------------------

#236Approval Workflow & Authority Matrix

RISK, COMPLIANCE & DECISION MAKINGCOOs, finance teams, operations leaders, HR, procurement, compliance teams, founders, managers, and companies with slow, unclear, or risky approvals.

Define who can approve what, at what thresholds, with what evidence, and when exceptions or escalations are required.

Act as an approval workflow architect. Build an authority matrix for [COMPANY NAME] that clarifies approvals, thresholds, evidence, and escalation rules. Approval context: Company: [COMPANY NAME] Departments: [DEPARTMENTS] Current approval problems: [PROBLEMS] Decision types: [DECISION TYPES] Budget levels: [BUDGET LEVELS] Risk categories: [RISK CATEGORIES] Current approvers: [APPROVERS] Compliance constraints: [COMPLIANCE] Systems used: [SYSTEMS] Common exceptions: [EXCEPTIONS] Past approval failures: [FAILURES] Create the authority matrix: Approval Categories Cover: - purchases - vendor selection - contracts - discounts - refunds / credits - hiring - compensation changes - expenses - travel - customer exceptions - policy exceptions - data access - system access - legal / compliance matters - marketing claims - product / service changes Threshold Table For each category define: - no approval needed - manager approval - department head approval - finance approval - legal / compliance review - executive approval - board approval, if relevant Evidence Requirements Define what must be attached: - business reason - budget code - quote / invoice - contract - risk assessment - customer impact - vendor due diligence - policy exception reason - approval history Workflow Rules Define: - request format - approval SLA - fallback approver - escalation path - emergency approval process - retrospective approval rule - documentation storage - audit trail requirement Exception Logic Create rules for: - urgent customer issue - safety issue - operational outage - system unavailable - approver unavailable - cost exceeds threshold - conflict of interest - legal / compliance uncertainty Anti-Bureaucracy Review Identify approvals that should be: - removed - delegated - automated - bundled - sampled after the fact - kept due to risk Rules: - Do not require executive approval for low-risk routine work. - Do not allow high-risk actions without evidence. - Do not create approval chains where nobody knows the decision criteria. - The matrix must improve both speed and control. --------------------------------------------------------------------------------

#237Compliance Evidence Binder Organizer

RISK, COMPLIANCE & DECISION MAKINGCompliance teams, operations managers, HR, finance, IT, food service operators, healthcare-adjacent businesses, SaaS teams, procurement, and companies preparing for audits.

Build an organized evidence system for audits, inspections, certifications, customer due diligence, internal reviews, or regulatory requests.

You are an audit readiness organizer. Build a compliance evidence binder for [AUDIT / INSPECTION / CERTIFICATION / REVIEW] at [COMPANY NAME]. Evidence context: Company: [COMPANY NAME] Audit / review type: [TYPE] Reviewer / requesting party: [REVIEWER] Scope: [SCOPE] Time period: [PERIOD] Applicable policies / standards: [POLICIES / STANDARDS] Required evidence list: [REQUIRED EVIDENCE] Current documents: [DOCUMENTS] Systems containing evidence: [SYSTEMS] Evidence owners: [OWNERS] Deadline: [DEADLINE] Known gaps: [GAPS] Organize the binder: Binder index Create sections: 1. Company overview 2. Scope statement 3. Policies 4. Procedures / SOPs 5. Training records 6. Licenses / certifications 7. Risk assessments 8. Control evidence 9. Incident records 10. Vendor records 11. Access / permission records 12. Customer or operational records 13. Corrective actions 14. Management review 15. Open gaps Adapt sections to the audit type. Evidence card format For every evidence item include: - evidence name - requirement it supports - owner - source system - date range - file location - version - reviewer - status - gap or issue - refresh frequency Evidence quality check Verify: - complete - current - accurate - signed / approved, if needed - matches the requirement - readable - not contradictory - not containing unnecessary sensitive data - traceable to owner Gap tracker Create a tracker: - missing evidence - requirement affected - risk - owner - action needed - deadline - escalation if late Submission plan Define: - naming convention - folder structure - access permissions - sensitive data handling - final review process - submission checklist - post-audit archive Rules: - Do not submit messy evidence that creates more questions. - Do not include sensitive data unless required. - Do not wait until the deadline to identify gaps. - Mark uncertain evidence requirements as [VERIFY]. --------------------------------------------------------------------------------

#238Risk-Based Prioritization Model

RISK, COMPLIANCE & DECISION MAKINGLeadership teams, compliance teams, operations leaders, product teams, finance teams, risk managers, support leaders, and organizations with too many competing priorities.

Create a decision model that ranks projects, issues, remediation tasks, controls, or initiatives by risk, urgency, impact, effort, compliance exposure, and reversibility.

Act as a risk-based prioritization analyst. Build a prioritization model for [LIST OF INITIATIVES / ISSUES] so [COMPANY NAME] can decide what to handle first. Inputs: Company: [COMPANY NAME] Items to prioritize: [ITEMS] Business goal: [GOAL] Risk categories: [RISK CATEGORIES] Available resources: [RESOURCES] Deadlines: [DEADLINES] Budget constraints: [BUDGET] Compliance exposure: [COMPLIANCE] Customer impact: [CUSTOMER IMPACT] Revenue impact: [REVENUE IMPACT] Operational impact: [OPERATIONAL IMPACT] Leadership preferences: [PREFERENCES] Create the prioritization model: Step 1 - Normalize the items For each item write: - clean item statement - owner - affected process - affected stakeholders - current status - deadline, if any - dependency Step 2 - Score risk Score 1-5: - customer impact - financial impact - compliance / legal exposure - operational disruption - reputation risk - safety / security risk - probability - urgency - reversibility - confidence Step 3 - Score execution Score 1-5: - effort - cost - complexity - resource availability - dependency burden - time to value - ease of implementation Step 4 - Calculate priority Use this logic: Priority Score = Impact + Probability + Urgency + Compliance Exposure + Customer Trust Risk + Financial Risk - Effort Penalty - Dependency Penalty Explain the formula and adjust it if the business context requires. Step 5 - Categorize action Assign each item to: - do now - schedule soon - monitor - delegate - test first - defer - reject - escalate Step 6 - Portfolio view Create a matrix: - high risk / low effort - high risk / high effort - low risk / low effort - low risk / high effort - mandatory compliance - strategic but not urgent - unclear due to missing data Step 7 - Leadership recommendation Provide: - top 5 priorities - items leadership must decide - items needing more data - items that should not consume resources - sequencing plan - risks of delay Rules: - Do not prioritize only by loudest stakeholder. - Do not bury mandatory compliance work under optional strategic work. - Do not confuse effort with importance. - Mark low-confidence scoring as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#239Crisis Communication Risk Checker

RISK, COMPLIANCE & DECISION MAKINGCEOs, founders, communications teams, HR, legal-adjacent teams, support leaders, compliance teams, operations leaders, PR teams, and managers sending difficult updates.

Review high-risk messages before they are sent to employees, customers, vendors, regulators, media, or the public during sensitive situations.

You are a crisis communication risk reviewer. Review the message below before [COMPANY NAME] sends it to [AUDIENCE] about [SITUATION]. Important: This is not legal or PR advice. Flag items needing legal, HR, compliance, or PR review as [REVIEW REQUIRED]. Message context: Company: [COMPANY NAME] Situation: [SITUATION] Audience: [AUDIENCE] Draft message: [PASTE MESSAGE] Facts confirmed: [CONFIRMED FACTS] Facts not confirmed: [UNCONFIRMED FACTS] Customer / employee impact: [IMPACT] Legal / compliance sensitivity: [SENSITIVITY] Desired action from audience: [ACTION] Tone desired: [TONE] Channels: [CHANNELS] Timing: [TIMING] Review the message: Risk Pass 1 - Accuracy Check: - claims that may be unsupported - timelines that may be wrong - promises that may not be achievable - blame language - missing facts - over-certainty - vague statements that create confusion Risk Pass 2 - Trust Check whether the message: - acknowledges impact - takes appropriate ownership - avoids defensiveness - explains next steps - gives a useful timeline - tells people where to ask questions - avoids sounding robotic Risk Pass 3 - Legal / compliance / HR sensitivity Flag: - admissions of liability - employee privacy issues - customer data issues - regulatory notification concerns - contractual promises - discrimination or harassment sensitivity - safety issues - financial claims Risk Pass 4 - Audience interpretation Explain how different readers may interpret the message: - supportive reader - upset reader - skeptical reader - affected customer / employee - journalist or public observer - regulator or auditor, if relevant Risk Pass 5 - Rewrite options Provide: A. safer concise version B. warmer human version C. executive formal version D. internal employee version E. customer-facing version Use only confirmed facts. Mark placeholders where review is needed. Risk Pass 6 - Send checklist Before sending, verify: - approved facts - approved owner - review completed - support team briefed - FAQ prepared - next update scheduled - escalation channel ready Rules: - Do not invent facts to make the message sound complete. - Do not over-apologize in a way that creates unsupported admissions. - Do not under-acknowledge real impact. - Do not send a sensitive message without a next step. --------------------------------------------------------------------------------

#240Full Risk, Compliance & Decision Making Audit

RISK, COMPLIANCE & DECISION MAKINGCEOs, founders, COOs, CFOs, risk managers, compliance officers, operations leaders, consultants, boards, and companies doing a governance or control reset.

Audit the full system for identifying risk, meeting obligations, making decisions, assigning authority, controlling processes, handling incidents, and reporting to leadership.

Act as an independent risk, compliance, and decision-making auditor. Review the full governance system of [COMPANY NAME] and identify the highest-leverage improvements for risk visibility, compliance readiness, decision quality, internal controls, and leadership accountability. Company context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Industry: [INDUSTRY] Locations / jurisdictions: [LOCATIONS] Team size: [TEAM SIZE] Revenue / scale: [SCALE] Critical processes: [PROCESSES] Regulatory exposure: [REGULATORY EXPOSURE] Risk register: [RISK REGISTER] Compliance obligations: [OBLIGATIONS] Policies: [POLICIES] Internal controls: [CONTROLS] Decision process: [DECISION PROCESS] Approval matrix: [APPROVAL MATRIX] Incident history: [INCIDENTS] Vendor / third-party risks: [THIRD PARTIES] Audit findings: [AUDITS] Leadership concerns: [CONCERNS] Audit the system across 20 dimensions: 1. Risk identification 2. Risk scoring and prioritization 3. Risk ownership 4. Risk appetite and thresholds 5. Compliance obligation mapping 6. Policy coverage 7. Policy clarity and usability 8. Internal controls 9. Approval authority 10. Decision documentation 11. Decision quality 12. Incident response 13. Business continuity 14. Vendor and third-party risk 15. Data privacy and security risk 16. Fraud / abuse detection 17. Compliance evidence readiness 18. Training and awareness 19. Board / leadership reporting 20. Continuous improvement For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - business risk - compliance risk - operational risk - reputation risk - recommended fix - confidence level Then synthesize: A. Top 5 governance constraints Rank by: - risk exposure - compliance impact - operational impact - customer trust impact - urgency - ease of fixing - confidence B. Root cause analysis Identify whether the main issue is: - no risk ownership - weak compliance mapping - outdated policies - informal decisions - unclear authority - missing controls - poor evidence management - reactive incident handling - vendor risk ignored - weak board reporting - low training adoption - no risk appetite - poor data quality - overreliance on individuals C. Future-state governance system Create: - risk register - obligation map - policy review calendar - internal control matrix - approval authority matrix - decision memo template - incident response process - continuity plan - vendor risk classification - evidence binder - leadership risk report D. 30/60/90-day improvement plan Create a practical plan with: - actions - owners - documents to create - controls to strengthen - decisions to clarify - training to launch - evidence to collect - risks to escalate - metrics to monitor - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard governance truth - the biggest unmanaged risk - the biggest compliance gap - the fastest control improvement - the weakest decision-making habit - the next leadership decision - the data needed before deeper changes Rules: - Do not invent legal obligations or audit evidence. - Do not give legal advice; mark legal-sensitive items as [LEGAL REVIEW]. - Do not blame individuals before checking systems, incentives, and authority. - Use [LOW CONFIDENCE] where evidence is weak. - Focus on risk visibility, ownership, decision quality, control strength, compliance evidence, and leadership accountability.

#241Business Automation Opportunity Scanner

BUSINESS AUTOMATION & AI OPERATIONSFounders, COOs, operations managers, department heads, consultants, automation leads, AI operations teams, agencies, and growing businesses that want to automate intelligently instead of randomly.

Find the highest-value automation opportunities across a business by identifying repetitive work, decision bottlenecks, data handoffs, delays, rework, and tasks suitable for AI support.

You are a business automation strategist. Scan [COMPANY NAME] for automation opportunities and create a prioritized automation roadmap that improves speed, accuracy, cost, visibility, and team capacity. Business context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Departments: [DEPARTMENTS] Current tools: [TOOLS] Main workflows: [WORKFLOWS] Repetitive tasks: [REPETITIVE TASKS] Manual data entry: [DATA ENTRY] Approval delays: [APPROVAL DELAYS] Reporting pain points: [REPORTING PAIN POINTS] Customer-facing bottlenecks: [CUSTOMER BOTTLENECKS] Internal bottlenecks: [INTERNAL BOTTLENECKS] Known errors / rework: [ERRORS / REWORK] Automation budget: [BUDGET] Technical constraints: [CONSTRAINTS] Run the automation scanner: 1. Workload inventory List business activities across: - sales - marketing - operations - finance - HR - customer support - procurement - reporting - leadership administration - compliance - vendor management - internal documentation For each activity identify: - owner - frequency - time spent - tools used - inputs - outputs - handoffs - error rate - decision requirement - customer or business impact 2. Automation signal detection Mark tasks that show these signals: - repeated more than 3 times per week - copy-paste work - template-based writing - manual status updates - data reconciliation - rule-based decisions - recurring reporting - intake triage - approval routing - document generation - follow-up reminders - quality checks - information extraction - summarization - classification - scheduling - research compilation 3. Automation type matching Classify each opportunity as: - rule-based workflow automation - AI-assisted drafting - AI classification or routing - data sync automation - reporting automation - document generation - approval automation - alert automation - chatbot / assistant - quality assurance automation - decision support automation - not suitable for automation yet 4. Suitability scoring Score each opportunity from 1 to 5 on: - frequency - time savings - error reduction - revenue impact - cost reduction - customer impact - employee experience - ease of implementation - data readiness - risk level - reversibility 5. Risk screen Flag automation risks: - poor data quality - unclear process - regulatory sensitivity - customer trust risk - security risk - high judgment requirement - weak SOP - no clear owner - too many exceptions - tool integration limitations 6. Priority roadmap Create: - quick wins - high-value projects - risky but valuable projects - projects to redesign before automating - projects to reject - projects requiring technical discovery 7. 30-day action plan For the top 5 opportunities include: - automation idea - owner - current process - future process - tools needed - expected benefit - implementation complexity - risk controls - first test - success metric Rules: - Do not automate a broken process before simplifying it. - Do not recommend AI where simple rules are enough. - Do not ignore human review where risk is material. - Do not estimate savings without stating assumptions. - Use [NEEDS DATA] where inputs are missing. --------------------------------------------------------------------------------

#242Manual Workflow to Automation Blueprint

BUSINESS AUTOMATION & AI OPERATIONSOperations teams, automation builders, Zapier / Make / n8n users, RevOps, finance teams, HR teams, customer support teams, agencies, consultants, and companies documenting automation requirements.

Convert a manual workflow into a clear automation design with triggers, actions, data fields, owners, approvals, exceptions, tools, and acceptance criteria.

Act as an automation blueprint architect. Convert the manual workflow below into an automation-ready specification. Workflow name: [WORKFLOW NAME] Current workflow description: [CURRENT WORKFLOW] Business goal: [GOAL] Process owner: [OWNER] People involved: [PEOPLE] Tools used today: [TOOLS] Current inputs: [INPUTS] Current outputs: [OUTPUTS] Current triggers: [TRIGGERS] Current approvals: [APPROVALS] Current exceptions: [EXCEPTIONS] Current problems: [PROBLEMS] Required compliance / security rules: [RULES] Automation tools available: [TOOLS AVAILABLE] Create the automation blueprint: A. Current-state workflow map Write the current workflow as numbered steps. For each step include: - actor - action - tool - data used - decision made - handoff - delay - error risk B. Simplification pass Before automation, identify: - steps to remove - steps to merge - duplicate data entry - unnecessary approvals - unclear handoffs - manual checks that can become rules - missing data fields - process decisions needing clarification C. Future-state automation flow Design the automated workflow using this structure: Trigger: - what starts the workflow - source system - required data - trigger conditions Actions: - action 1 - action 2 - action 3 - action 4 Decision rules: - if this, then that - routing logic - approval rules - rejection logic - escalation rules Outputs: - created record - sent message - generated document - updated dashboard - assigned task - notification - audit log D. Data field map Create a table: - field name - source - destination - required / optional - validation rule - owner - error handling E. Exception handling Define what happens when: - required data is missing - duplicate record exists - approval is delayed - tool connection fails - AI output is low confidence - customer or employee responds unexpectedly - policy rule is triggered - human review is required F. Human-in-the-loop design Specify: - where humans review - who reviews - review deadline - approval criteria - override process - documentation required G. Build specification Write a no-code / low-code builder spec: - apps involved - trigger app - action apps - filters - paths - variables - AI steps, if any - testing scenarios - rollback plan H. Acceptance criteria The automation is done when: - [CRITERION 1] - [CRITERION 2] - [CRITERION 3] - [CRITERION 4] Rules: - Do not skip process simplification. - Do not allow silent failure. - Do not let AI make high-risk decisions without review. - Do not design automation without clear ownership. --------------------------------------------------------------------------------

#243AI Assistant Role Charter Designer

BUSINESS AUTOMATION & AI OPERATIONSCompanies creating AI assistants for operations, HR, finance, sales, customer support, management, documentation, reporting, or internal knowledge work.

Define an internal AI assistant's role, permissions, data sources, tasks, boundaries, escalation rules, output standards, and success metrics.

You are an AI operations designer. Create a role charter for an internal AI assistant called [ASSISTANT NAME] that supports [TEAM / FUNCTION] without creating confusion, risk, or unmanaged behavior. Assistant setup: Assistant name: [ASSISTANT NAME] Team served: [TEAM] Business purpose: [PURPOSE] Users: [USERS] Tasks requested: [TASKS] Data sources available: [DATA SOURCES] Tools the assistant can access: [TOOLS] Sensitive data involved: [SENSITIVE DATA] Decisions it may support: [DECISIONS] Decisions it must not make: [FORBIDDEN DECISIONS] Required tone: [TONE] Risk level: [LOW / MEDIUM / HIGH] Success goals: [GOALS] Build the AI assistant charter: 1. Identity and mission Define: - assistant mission - who it serves - what business value it creates - what it is not responsible for - how users should think about its role 2. Task permission table Create three columns: Allowed tasks: - tasks the assistant can complete independently Assisted tasks: - tasks the assistant can draft, analyze, or recommend but require human approval Forbidden tasks: - tasks the assistant must refuse or escalate 3. Data access rules Define: - approved data sources - restricted data - data it can summarize - data it can transform - data it cannot store - data it cannot expose - privacy or confidentiality guardrails 4. Output standards For each output type define: - required format - citation or source requirement - confidence label - assumptions label - review requirement - escalation trigger Output types may include: - reports - summaries - emails - SOP drafts - task lists - analysis - recommendations - customer responses - employee-facing drafts 5. Escalation rules The assistant must escalate when: - data is missing - request involves legal / HR / compliance risk - customer impact is high - decision authority is unclear - user asks for prohibited action - confidence is low - sources conflict - sensitive information appears 6. User interaction rules Define: - how users should brief the assistant - how the assistant asks clarifying questions - how it handles uncertainty - how it refuses unsafe requests - how it documents assumptions 7. Governance Define: - assistant owner - review cadence - feedback channel - prompt change process - quality review process - incident reporting - access review 8. Success metrics Track: - time saved - usage adoption - output quality - human review pass rate - error rate - escalation quality - user satisfaction - process impact Rules: - Do not let the assistant become a hidden decision maker. - Do not grant access to data it does not need. - Do not allow outputs without review where risk is high. - The charter must make the assistant useful, bounded, and auditable. --------------------------------------------------------------------------------

#244SOP-to-AI Workflow Conversion Lab

BUSINESS AUTOMATION & AI OPERATIONSOperations teams, SOP owners, consultants, process managers, team leads, AI operations teams, agencies, customer support, HR, finance, and businesses modernizing internal documentation.

Transform an existing SOP into an AI-assisted workflow with prompt steps, decision gates, templates, QA checks, exceptions, and human review.

Act as an SOP automation converter. Take the SOP below and redesign it into an AI-assisted operating workflow that preserves quality while reducing manual effort. SOP to convert: [PASTE SOP] Business context: Company: [COMPANY NAME] Team using the SOP: [TEAM] Workflow frequency: [FREQUENCY] Current pain points: [PAIN POINTS] Tools available: [TOOLS] AI tools allowed: [AI TOOLS] Data sources: [DATA SOURCES] Risk concerns: [RISK CONCERNS] Quality standard: [QUALITY STANDARD] Human reviewers: [REVIEWERS] Run the conversion lab: Phase 1 - SOP decomposition Break the SOP into: - information-gathering steps - decision steps - drafting / creation steps - calculation steps - checking steps - approval steps - communication steps - documentation steps - escalation steps For each step decide: - human only - AI-assisted - fully automated - rule-based automation - remove / simplify Phase 2 - AI insertion points Identify where AI can help with: - extracting information - classifying requests - summarizing context - drafting text - checking completeness - comparing records - creating checklists - generating reports - suggesting next action - translating technical language - preparing manager review Phase 3 - Prompt stack Create the exact prompt modules needed: - intake prompt - context summarization prompt - analysis prompt - draft generation prompt - QA prompt - exception detection prompt - final handoff prompt For each prompt module include: - purpose - required inputs - prompt text - expected output - failure mode - review owner Phase 4 - Review gates Design human review gates: Gate 1: intake completeness Gate 2: AI analysis quality Gate 3: final decision or approval Gate 4: external communication Gate 5: documentation archive For each gate include: - reviewer - criteria - deadline - approval / rejection options - escalation path Phase 5 - AI-ready SOP rewrite Rewrite the SOP in this format: 1. Trigger 2. Required inputs 3. AI-assisted steps 4. Human decision points 5. Quality checks 6. Exceptions 7. Outputs 8. Documentation 9. Metrics Phase 6 - Pilot plan Create: - pilot scope - test cases - success metrics - error tracking - reviewer feedback form - rollback plan - update cadence Rules: - Do not remove human judgment where risk is high. - Do not convert unclear SOP steps into unclear AI prompts. - Do not let AI invent missing information. - Mark any compliance-sensitive step as [REVIEW REQUIRED]. --------------------------------------------------------------------------------

#245Cross-Tool Automation Architecture Map

BUSINESS AUTOMATION & AI OPERATIONSCOOs, RevOps, IT, automation builders, operations managers, SaaS teams, agencies, multi-tool companies, and businesses with disconnected systems and duplicate data.

Design how business tools should connect across departments with source-of-truth rules, data flows, sync logic, automations, permissions, and failure handling.

You are a business systems architect. Create a cross-tool automation architecture map for [COMPANY NAME] that shows how data and work should move between tools. Systems context: Company: [COMPANY NAME] Departments: [DEPARTMENTS] Current tools: [TOOLS] Current pain points: [PAIN POINTS] Main records: [CUSTOMERS / ORDERS / PROJECTS / EMPLOYEES / VENDORS / INVOICES] Current source of truth: [SOURCE OF TRUTH] Duplicate data issues: [DUPLICATES] Manual exports / imports: [EXPORTS / IMPORTS] Reporting needs: [REPORTING] Security constraints: [SECURITY] Automation platform: [ZAPIER / MAKE / N8N / CUSTOM / OTHER] Technical support available: [SUPPORT] Create the architecture map: Map Layer 1 - Systems inventory For each tool list: - tool name - department owner - data stored - actions performed - users - integration options - risks - current problems Map Layer 2 - Source-of-truth rules Define the source of truth for: - customer records - leads - deals - orders - projects - tasks - invoices - vendors - employees - contracts - documents - reports For each record type include: - master system - allowed editors - synced systems - update frequency - conflict resolution rule Map Layer 3 - Data flow diagram in text Write each flow as: [Trigger System] -> [Condition] -> [Action System] -> [Created / Updated Data] -> [Notification / Review] Include: - sales to finance - customer support to product / operations - HR to IT access - procurement to finance - operations to reporting - project management to leadership dashboard - customer intake to delivery team Map Layer 4 - Automation catalog Create automation specs: - automation name - trigger - conditions - actions - data fields - owner - frequency - business value - risk - failure alert - test scenario Map Layer 5 - Permissions and access Define: - who can view - who can edit - who can export - who can approve - who can change automations - who receives error alerts Map Layer 6 - Failure handling For each critical automation define: - possible failure - detection method - alert owner - manual fallback - recovery step - audit log Final output: - architecture summary - source-of-truth table - automation catalog - critical dependency list - cleanup recommendations - first 10 automations to build Rules: - Do not sync everything everywhere. - Do not create two sources of truth for the same record. - Do not ignore permissions. - Do not build automations without failure alerts. --------------------------------------------------------------------------------

#246AI Operations Governance Charter

BUSINESS AUTOMATION & AI OPERATIONSCEOs, COOs, HR, compliance teams, IT, department heads, legal-adjacent teams, AI operations leads, and companies adopting AI across teams.

Create company-wide AI usage rules covering approved tools, data safety, human review, prohibited use cases, accountability, quality standards, and change control.

Act as an AI operations governance advisor. Draft an AI usage and governance charter for [COMPANY NAME] that helps employees use AI productively, safely, and consistently. Company context: Company: [COMPANY NAME] Industry: [INDUSTRY] Team size: [TEAM SIZE] AI tools currently used: [AI TOOLS] Departments using AI: [DEPARTMENTS] Data sensitivity: [DATA SENSITIVITY] Regulatory exposure: [REGULATORY EXPOSURE] Customer-facing AI use: [CUSTOMER-FACING USE] Internal AI use: [INTERNAL USE] Known AI risks: [RISKS] Current policies: [POLICIES] Approval owners: [OWNERS] Create the governance charter: Section 1 - Purpose Explain why the company uses AI and what business outcomes AI should support. Section 2 - Approved AI use cases Classify approved uses: - drafting - summarizing - research support - data cleanup - classification - internal knowledge assistance - meeting notes - reporting support - SOP drafting - customer response drafting with review - coding support, if relevant For each include required review level. Section 3 - Restricted and prohibited use cases Define what employees must not do, including: - uploading restricted data - using AI for final legal / medical / financial / HR decisions - sending unreviewed customer-facing responses - generating fake evidence - copying confidential customer data into unapproved tools - bypassing security or approval processes - creating discriminatory or deceptive content Section 4 - Data rules Create rules for: - public data - internal data - confidential data - personal data - customer data - employee data - financial data - regulated data - source materials - retention Section 5 - Human review levels Create four levels: Level 0: no AI use allowed Level 1: AI can assist, human fully owns output Level 2: AI can draft, human must review before use Level 3: AI can execute within guardrails with monitoring For each level include examples. Section 6 - Accountability Define: - employee responsibility - manager responsibility - AI owner responsibility - IT / security responsibility - compliance / legal review trigger - incident reporting Section 7 - Quality standards Require: - source checking - fact checking - bias review - tone review - confidentiality check - customer impact check - documentation of AI use where needed Section 8 - Tool approval process Create a process for approving new AI tools: - request - business purpose - data review - security review - cost review - pilot - approval - access management - review date Section 9 - Training and communication Create rollout steps: - employee guide - manager training - approved examples - prohibited examples - FAQ - feedback channel Rules: - Do not write the policy in legal jargon. - Do not ban useful AI work without explaining safer alternatives. - Do not allow AI to become an unaccountable decision maker. - Mark legal-sensitive items as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#247Human-in-the-Loop Review Gate Designer

BUSINESS AUTOMATION & AI OPERATIONSAI operations teams, compliance teams, customer support, HR, finance, operations, healthcare-adjacent workflows, legal-adjacent workflows, content teams, and automation builders.

Design review gates for AI or automation workflows so humans approve high-risk outputs, handle exceptions, and prevent silent errors.

You are a human-in-the-loop system designer. Build review gates for the workflow [WORKFLOW NAME] so AI and automation can increase speed without reducing accountability. Workflow context: Workflow: [WORKFLOW NAME] AI or automation involved: [AI / AUTOMATION] Business objective: [OBJECTIVE] Outputs produced: [OUTPUTS] Users affected: [USERS] Customers affected: [CUSTOMERS] Risk level: [RISK LEVEL] Sensitive data involved: [DATA] Current review process: [CURRENT REVIEW] Known errors: [ERRORS] Decision authority: [AUTHORITY] Required approvals: [APPROVALS] Design the review gate system: Gate map Identify every point where the system produces: - recommendation - classification - draft - calculation - decision support - data update - customer message - internal message - task assignment - approval request - exception For each point decide whether review is: - not needed - sample review - threshold-based review - required review - dual review - executive / compliance review Review trigger logic Create triggers based on: - confidence score - missing data - sensitive topic - financial amount - customer impact - employee impact - compliance exposure - unusual pattern - complaint risk - source conflict - first-time scenario - exception rule Reviewer roles Define: - primary reviewer - backup reviewer - escalation reviewer - final approver - process owner - incident owner Review checklist Create review checklists for: A. Accuracy B. Completeness C. Policy compliance D. Customer impact E. Tone and clarity F. Data privacy G. Fairness / bias H. Business logic I. Documentation Review decision options Allow reviewers to: - approve - edit and approve - reject - request more information - escalate - override - pause automation - report incident Review SLA Define: - expected review time - overdue alert - emergency path - batch review schedule - audit sampling cadence Audit trail Define what must be logged: - AI input - AI output - reviewer - decision - edits made - reason - timestamp - final action - exception notes Optimization plan Explain how to reduce review burden over time using: - better prompts - better data - better rules - sampling - thresholds - reviewer feedback - error trend analysis Rules: - Do not require human review for every low-risk action. - Do not remove review from high-impact decisions. - Do not allow unlogged overrides. - Review gates must protect trust while preserving speed. --------------------------------------------------------------------------------

#248AI Output QA & Validation System

BUSINESS AUTOMATION & AI OPERATIONSAI operations teams, content teams, research teams, support teams, consultants, analysts, managers, agencies, and companies using AI outputs in real business processes.

Create a quality assurance system for AI-generated work with validation checks, scoring rubrics, hallucination detection, source verification, style checks, and improvement loops.

Act as an AI quality assurance lead. Build a QA and validation system for AI-generated [OUTPUT TYPE] used by [TEAM / COMPANY]. Output context: AI output type: [REPORTS / EMAILS / SUMMARIES / CUSTOMER RESPONSES / ANALYSIS / SOPs / CODE / OTHER] Team using output: [TEAM] AI tool: [AI TOOL] Input sources: [SOURCES] Audience: [AUDIENCE] Business risk: [RISK] Quality problems observed: [PROBLEMS] Required tone / format: [TONE / FORMAT] Approval process: [APPROVAL] Examples of good output: [GOOD EXAMPLES] Examples of bad output: [BAD EXAMPLES] Build the QA system: Quality rubric Create scoring dimensions from 1 to 5: - accuracy - completeness - source grounding - relevance - structure - clarity - tone fit - policy compliance - data privacy - usefulness - actionability - consistency - risk awareness For each dimension define what 1, 3, and 5 mean. Validation checklist Create checks for: - unsupported claims - wrong numbers - missing context - outdated information - invented facts - misinterpreted source material - wrong audience - tone mismatch - incomplete instructions - hidden assumptions - compliance-sensitive content - confidential data exposure Source verification process Define: - what sources must be cited - how citations are checked - how conflicting sources are handled - how unsupported content is removed - when to mark [UNVERIFIED] - when to ask for more data AI hallucination test Create tests: - fact extraction test - quote accuracy test - numerical consistency test - source alignment test - contradiction test - missing evidence test - confidence label test Reviewer workflow Define: - reviewer role - review steps - pass threshold - edit rules - rejection criteria - escalation criteria - documentation requirements Feedback loop Create a system to improve AI output: - collect errors - classify error types - update prompt - update source data - update examples - retrain users - review weekly trends - retire bad templates QA dashboard Track: - output volume - pass rate - error rate - common error type - reviewer time - escalation count - rework time - user satisfaction - business impact Rules: - Do not treat polished writing as accurate writing. - Do not accept AI claims without source support where facts matter. - Do not create a QA process so heavy that nobody uses it. - Use [LOW CONFIDENCE] when evidence is incomplete. --------------------------------------------------------------------------------

#249Automation ROI & Prioritization Model

BUSINESS AUTOMATION & AI OPERATIONSCOOs, CFOs, automation leads, founders, operations managers, consultants, RevOps, finance teams, and teams deciding which automation projects to fund first.

Rank automation ideas by time saved, cost reduction, revenue impact, error reduction, risk, build complexity, maintenance effort, and adoption difficulty.

You are an automation ROI analyst. Build a prioritization model for the automation ideas below and recommend what to build first. Automation ideas: [PASTE AUTOMATION IDEAS] Business context: Company: [COMPANY NAME] Team size: [TEAM SIZE] Average hourly cost estimate: [HOURLY COST] Current process volumes: [VOLUMES] Known error costs: [ERROR COSTS] Revenue opportunities: [REVENUE OPPORTUNITIES] Available tools: [TOOLS] Implementation resources: [RESOURCES] Budget: [BUDGET] Risk constraints: [RISK CONSTRAINTS] Time horizon: [TIME HORIZON] Build the ROI model: Step 1 - Normalize each automation idea For each idea define: - process automated - current owner - current frequency - current time per occurrence - current error / rework rate - proposed automation - required tools - affected teams - expected user Step 2 - Estimate benefit Calculate or estimate: - hours saved per week - hours saved per month - cost savings - error reduction - faster cycle time - revenue acceleration - customer experience improvement - employee experience improvement - reporting visibility improvement Use assumptions where data is missing and label them [ASSUMPTION]. Step 3 - Estimate cost and complexity Score: - build effort - tool cost - integration complexity - data readiness - process clarity - maintenance effort - training effort - change management difficulty - security / compliance risk - dependency risk Step 4 - ROI categories Classify each idea as: - high ROI quick win - high ROI but complex - low ROI but necessary - risky without redesign - not worth automating - needs more data Step 5 - Prioritization formula Use: Priority Score = Benefit Score + Risk Reduction + Strategic Value - Build Complexity - Maintenance Burden - Adoption Difficulty Show the scoring table. Step 6 - Automation investment roadmap Create: - first 2 weeks - next 30 days - next 60 days - next quarter - backlog - reject list Step 7 - Business case for top 3 For each top automation write: - one-paragraph business case - cost estimate - benefit estimate - implementation plan - risks - success metrics - owner Rules: - Do not count theoretical savings as realized savings unless work is actually removed, redeployed, or monetized. - Do not prioritize flashy AI projects over simple high-value automation. - Do not ignore maintenance cost. - Mark low-confidence estimates clearly. --------------------------------------------------------------------------------

#250Prompt Library & Knowledge Base Operating System

BUSINESS AUTOMATION & AI OPERATIONSAI operations teams, founders, managers, agencies, marketing teams, sales teams, HR, customer support, consultants, and companies standardizing AI use internally.

Create a company prompt library and knowledge base system with categories, ownership, version control, examples, approved usage, QA standards, and update cadence.

Act as an AI knowledge operations architect. Design a prompt library and internal AI knowledge base for [COMPANY NAME] that helps employees reuse proven prompts safely and consistently. Company context: Company: [COMPANY NAME] Teams using AI: [TEAMS] Main AI tasks: [TASKS] AI tools: [TOOLS] Current prompt storage: [CURRENT STORAGE] Current problems: [PROBLEMS] Knowledge sources: [SOURCES] Brand / policy rules: [RULES] Sensitive data constraints: [CONSTRAINTS] Owners: [OWNERS] Adoption goals: [GOALS] Design the operating system: Library taxonomy Create categories such as: - leadership - operations - sales - marketing - customer support - HR - finance - reporting - SOPs - research - writing - analysis - automation - compliance-sensitive tasks For each category define what belongs there. Prompt card template Create a standard prompt card with: - prompt name - business purpose - best for - owner - approved users - risk level - input requirements - prompt text - output format - examples - QA checklist - prohibited use - review requirement - version history - last reviewed date Prompt lifecycle Define stages: 1. draft 2. tested 3. approved 4. active 5. needs revision 6. retired For each stage include owner, criteria, and allowed use. Version control rules Define: - who can edit prompts - how changes are requested - how versions are named - how examples are updated - how old prompts are retired - how users are notified Knowledge base structure Design pages for: - AI usage policy - approved tools - prompt library - role-based examples - data safety rules - QA checklist - FAQ - training videos - error reporting - improvement requests Quality review process Create: - test inputs - output review rubric - hallucination check - privacy check - format check - user feedback loop - monthly review cadence Adoption plan Create: - launch message - manager enablement - team training - office hours - usage examples - feedback form - adoption metrics Rules: - Do not create a prompt library with no owner. - Do not store unsafe prompts next to approved prompts without labels. - Do not let prompts become outdated hidden infrastructure. - Make the library easy to use for non-technical employees. --------------------------------------------------------------------------------

#251AI Agent Task Brief Generator

BUSINESS AUTOMATION & AI OPERATIONSTeams using ChatGPT, Claude, Gemini, Cursor, automation agents, AI assistants, internal agents, operations bots, research agents, and workflow agents.

Create precise task briefs for AI agents or assistants that define goal, context, tools, data, constraints, permissions, checkpoints, output, and stop conditions.

You are an AI task brief designer. Create a safe, precise task brief for an AI agent to complete [TASK NAME] for [COMPANY NAME]. Task context: Task name: [TASK NAME] Business goal: [GOAL] Agent or AI tool: [AI TOOL / AGENT] User role: [USER ROLE] Input materials: [INPUTS] Available tools: [TOOLS] Files / systems the agent may access: [ALLOWED ACCESS] Files / systems the agent must not access: [FORBIDDEN ACCESS] Allowed actions: [ALLOWED ACTIONS] Forbidden actions: [FORBIDDEN ACTIONS] Risk level: [RISK LEVEL] Human checkpoints needed: [CHECKPOINTS] Final output needed: [OUTPUT] Deadline: [DEADLINE] Create the agent brief: 1. Mission Write a clear mission statement: "Your task is to [ACTION] using [INPUTS] so that [BUSINESS OUTCOME]." 2. Context packet Include only the context the agent needs: - business background - audience - relevant constraints - definitions - examples - success criteria 3. Operating boundaries Define: - what the agent may do independently - what requires confirmation - what is prohibited - what data cannot be used - what tools cannot be called - what files cannot be changed - what decisions cannot be made 4. Tool instructions For each tool available, specify: - when to use it - when not to use it - required checks before use - output expected from tool use 5. Work plan format Require the agent to produce: - short plan - assumptions - questions if blocked - execution steps - verification steps - final deliverable 6. Checkpoints Define checkpoints: Checkpoint 1: before starting high-impact action Checkpoint 2: after first draft / analysis Checkpoint 3: before external communication Checkpoint 4: before destructive or irreversible action Customize checkpoints for the task. 7. Acceptance criteria The task is complete when: - output meets required format - sources are documented - assumptions are labeled - risks are flagged - no forbidden action was taken - human review items are listed 8. Stop conditions The agent must stop and ask when: - critical data is missing - instructions conflict - risk exceeds permission - tool access fails - output could affect customers / employees / finances without approval - legal / HR / compliance judgment is required Rules: - Do not ask the agent to "figure everything out" without boundaries. - Do not allow hidden irreversible actions. - Do not include unnecessary context that increases risk. - The brief must be copy-ready for the target AI agent. --------------------------------------------------------------------------------

#252Internal AI Training & Adoption Plan

BUSINESS AUTOMATION & AI OPERATIONSHR, operations leaders, AI champions, founders, department heads, L&D teams, consultants, and companies rolling out AI tools across teams.

Create a training and adoption system that helps employees use AI responsibly, confidently, and practically in their daily workflows.

Act as an AI enablement lead. Build an internal AI training and adoption plan for [COMPANY NAME] that turns AI from a novelty into safe daily productivity. Company context: Company: [COMPANY NAME] Employee count: [EMPLOYEE COUNT] Departments: [DEPARTMENTS] AI tools approved: [TOOLS] Current AI skill level: [SKILL LEVEL] Employee concerns: [CONCERNS] Leadership goals: [GOALS] High-value use cases: [USE CASES] Data safety constraints: [DATA RULES] Training format: [LIVE / ASYNC / HYBRID] Timeline: [TIMELINE] Available champions: [CHAMPIONS] Build the adoption plan: Audience segmentation Group employees by: - beginners - frequent AI users - managers - customer-facing teams - data-sensitive teams - technical teams - executives For each group identify: - what they need to learn - what they fear - what they should not do - practical use cases - success behavior Training curriculum Create modules: 1. AI basics for work 2. Company AI policy 3. Data safety 4. Prompting for daily tasks 5. Role-specific workflows 6. Reviewing AI output 7. Avoiding hallucinations 8. Using templates and prompt library 9. Escalating risky use cases 10. Measuring productivity gains For each module include objective, exercise, and output. Role-based practice labs Create labs for: - manager - sales - operations - finance - HR - customer support - marketing - analyst - admin Each lab should include: - task - sample input - prompt - expected output - QA checklist - mistake to avoid Adoption system Design: - AI champions network - office hours - internal prompt library - help channel - weekly use-case spotlight - manager nudges - feedback collection - usage tracking Resistance handling Prepare responses for concerns: - AI will replace jobs - AI outputs are unreliable - I do not know what to ask - I am afraid of data mistakes - I do not have time to learn - my work is too specialized - tools are confusing Measurement Track: - active users - repeat usage - use cases launched - time saved - quality improvements - errors caught - employee confidence - manager adoption - risky behavior incidents Rules: - Do not train employees only on prompt tricks. - Do not skip data safety. - Do not assume adoption happens after one workshop. - Training must result in role-specific workflows employees actually use. --------------------------------------------------------------------------------

#253Data Readiness for AI Automation Audit

BUSINESS AUTOMATION & AI OPERATIONSAI operations teams, data teams, RevOps, finance, operations, customer support, IT, founders, consultants, and companies whose AI projects fail because data is messy.

Assess whether business data is clean, structured, accessible, governed, and reliable enough to support AI automation or reporting workflows.

You are a data readiness auditor. Assess whether [COMPANY NAME]'s data is ready for AI automation in [WORKFLOW / USE CASE]. Use case: AI automation use case: [USE CASE] Business outcome: [OUTCOME] Data sources required: [DATA SOURCES] Systems involved: [SYSTEMS] Users: [USERS] Current data problems: [PROBLEMS] Reporting needs: [REPORTING] Security / privacy requirements: [REQUIREMENTS] Current owners: [OWNERS] Target automation: [TARGET AUTOMATION] Audit data readiness: Dimension 1 - Availability Check whether required data exists. For each data element include: - field name - source system - owner - current availability - missingness - collection method - required for automation? yes / no Dimension 2 - Structure Evaluate: - consistent field names - standardized values - date formats - IDs - categories - tags - free-text fields - file formats - API accessibility - export quality Dimension 3 - Accuracy Assess: - duplicate records - outdated records - wrong values - manual entry errors - inconsistent naming - conflicting systems - validation rules - reconciliation process Dimension 4 - Completeness Identify: - required fields missing - optional fields often blank - missing historical data - missing owner - missing approval status - missing timestamps - missing audit trail Dimension 5 - Governance Review: - data owner - access permissions - change control - retention rules - privacy restrictions - documentation - data dictionary - approval for AI usage Dimension 6 - Automation readiness Classify each data source as: - ready now - usable with cleanup - usable with human review - not ready - should not be used for AI Readiness score Score from 1 to 10: - source quality - completeness - structure - access - governance - risk - automation suitability Data cleanup plan Create: - fields to standardize - duplicates to resolve - owners to assign - systems to connect - validation rules to add - data dictionary to create - access rules to update - pilot dataset to prepare Rules: - Do not build AI automation on data nobody owns. - Do not assume free-text data is ready for automation. - Do not ignore privacy and access restrictions. - Use [NEEDS DATA] when evidence is missing. --------------------------------------------------------------------------------

#254Automation Error Handling & Exception Playbook

BUSINESS AUTOMATION & AI OPERATIONSAutomation builders, operations teams, customer support, finance, HR, RevOps, IT, AI ops teams, consultants, and businesses with workflows that cannot silently fail.

Design how automated workflows detect, classify, communicate, route, resolve, and learn from errors and exceptions.

Act as an automation reliability engineer. Build an error handling and exception playbook for the automation [AUTOMATION NAME]. Automation context: Automation name: [AUTOMATION NAME] Workflow purpose: [PURPOSE] Trigger: [TRIGGER] Systems involved: [SYSTEMS] Data fields used: [DATA FIELDS] Actions performed: [ACTIONS] Business-criticality: [CRITICALITY] Users affected: [USERS] Customers affected: [CUSTOMERS] Current failure history: [FAILURES] Current alerts: [ALERTS] Owner: [OWNER] Backup process: [BACKUP PROCESS] Create the playbook: Error taxonomy Classify possible errors: - trigger did not fire - duplicate trigger - missing data - invalid data - API failure - authentication failure - rate limit - wrong routing - approval timeout - AI output issue - low confidence result - duplicate record - failed notification - failed file creation - failed payment / invoice action - permission denied - downstream system unavailable For each error define severity. Detection map For each error type specify: - detection method - alert trigger - alert recipient - alert channel - time-to-detect target - evidence included in alert Exception routing Define routes: - auto-retry - queue for human review - send to process owner - escalate to manager - notify customer / user - pause automation - switch to manual fallback - create incident Resolution runbooks For each high-priority error include: - first action - diagnostic steps - fix steps - rollback steps - communication needed - documentation needed - owner - SLA Manual fallback Create a fallback process: - when to activate - who activates - how work continues - how data is captured - how automation catches up later - how duplicates are prevented Post-error learning Create: - error log - root cause field - recurrence count - process change - prompt change, if AI-related - tool change - training need - owner - deadline Dashboard Track: - error count - error type - time to detect - time to resolve - recurrence rate - manual fallback usage - customer impact - automation uptime Rules: - Do not allow silent failures. - Do not send raw technical errors to business users without explanation. - Do not rely on one person for all recovery. - Every critical automation needs a manual fallback. --------------------------------------------------------------------------------

#255No-Code Workflow Spec Builder

BUSINESS AUTOMATION & AI OPERATIONSNon-technical founders, operations managers, virtual assistants, automation agencies, business analysts, no-code builders, and teams turning business requirements into workflows.

Create a builder-ready specification for no-code automation platforms such as Zapier, Make, Airtable, Notion, Slack, Google Workspace, HubSpot, or n8n.

You are a no-code automation specification writer. Create a builder-ready workflow spec for [WORKFLOW NAME] using [NO-CODE TOOL / PLATFORM]. Workflow request: Workflow name: [WORKFLOW NAME] Automation platform: [ZAPIER / MAKE / N8N / AIRTABLE / NOTION / OTHER] Apps involved: [APPS] Business goal: [GOAL] Trigger event: [TRIGGER] Required actions: [ACTIONS] Data fields: [DATA FIELDS] Filters / conditions: [CONDITIONS] Paths / branches: [PATHS] Notifications needed: [NOTIFICATIONS] Approvals needed: [APPROVALS] Error handling: [ERROR HANDLING] Users affected: [USERS] Security constraints: [SECURITY] Testing examples: [EXAMPLES] Write the no-code spec: Block 1 - Workflow summary Include: - what the automation does - who it helps - when it runs - what output it creates - why it matters Block 2 - App connection checklist For each app include: - account owner - permission needed - trigger or action used - fields required - limitations - test record needed Block 3 - Step-by-step build instructions Write the automation as numbered blocks: Step 1: - app - event - configuration - fields used - expected result Step 2: - app - event - configuration - fields used - expected result Continue until complete. Block 4 - Filters and paths Define every conditional rule: - if [condition], then [action] - if [missing data], then [action] - if [approval required], then [action] - if [duplicate], then [action] - if [high-risk], then [action] Block 5 - AI step, if used For any AI step include: - prompt - input variables - output format - temperature or creativity guidance, if applicable - confidence check - review requirement Block 6 - Test plan Create test cases: - normal case - missing field case - duplicate case - rejected approval case - tool failure case - edge case - high-volume case For each include expected output. Block 7 - Launch checklist Include: - owner approval - permissions checked - test passed - error alerts enabled - documentation created - rollback plan - first-week monitoring Rules: - Do not write vague steps like "connect the apps." - Do not assume field names are obvious. - Do not omit testing scenarios. - The final spec should be usable by a no-code builder without a discovery call. --------------------------------------------------------------------------------

#256AI Triage Engine for Requests, Tickets & Tasks

BUSINESS AUTOMATION & AI OPERATIONSCustomer support, IT helpdesks, HR, operations, finance shared services, procurement, internal service teams, agencies, and businesses with high request volume.

Design an AI triage system that classifies incoming requests, extracts key details, assigns priority, routes to owners, drafts responses, and escalates exceptions.

Act as an AI triage system designer. Build a triage engine for [REQUEST TYPE] received by [TEAM]. Triage context: Team: [TEAM] Request type: [CUSTOMER TICKETS / INTERNAL REQUESTS / HR QUESTIONS / FINANCE REQUESTS / IT TICKETS / OTHER] Channels: [CHANNELS] Current volume: [VOLUME] Current categories: [CATEGORIES] Current SLA: [SLA] Current routing rules: [ROUTING] Current problems: [PROBLEMS] Tools: [TOOLS] Knowledge base: [KNOWLEDGE BASE] Sensitive topics: [SENSITIVE TOPICS] Escalation owners: [OWNERS] Design the triage engine: Intake parser Extract: - requester - channel - request summary - category - urgency - customer / employee affected - account / order / project ID - deadline - attachments - sentiment - risk indicators - missing information Classification model Create category rules for: - simple information request - standard service request - urgent issue - complaint - billing / payment - access / permission - technical issue - policy question - vendor / supplier issue - HR-sensitive issue - legal / compliance-sensitive issue - executive escalation - unclear / needs clarification Priority logic Define priority levels: P1 - critical P2 - high P3 - normal P4 - low P5 - informational For each include: - criteria - SLA - owner - escalation rule - customer / requester update cadence Routing rules Create assignment logic: - category owner - backup owner - workload balancing - location-based routing - customer segment routing - language routing - risk-based escalation - out-of-hours handling AI response support For each category define whether AI can: - answer directly - draft response for review - ask clarification question - summarize for human - suggest next action - not respond Escalation triggers Escalate when: - high-risk keywords appear - requester is upset - sensitive data appears - legal / HR / compliance issue - SLA breach risk - repeated complaint - VIP / key account - AI confidence is low - knowledge base has no answer Triage dashboard Track: - volume by category - priority mix - routing accuracy - AI confidence - response time - resolution time - escalation rate - reopen rate - customer / requester satisfaction - knowledge gaps Rules: - Do not let AI close sensitive requests without human review. - Do not hide low-confidence classification. - Do not route requests without an owner. - Triage must improve speed and reduce missed risks. --------------------------------------------------------------------------------

#257Executive Reporting Automation System

BUSINESS AUTOMATION & AI OPERATIONSCEOs, COOs, CFOs, department heads, analysts, operations teams, finance teams, RevOps, agencies, and businesses that manually compile weekly or monthly reports.

Automate recurring leadership reports by defining data sources, metrics, calculations, commentary, charts, insights, exceptions, and delivery cadence.

You are an executive reporting automation designer. Build a reporting automation system for [REPORT NAME] that turns raw business data into a clear leadership-ready report. Report context: Report name: [REPORT NAME] Audience: [AUDIENCE] Cadence: [DAILY / WEEKLY / MONTHLY / QUARTERLY] Business decisions supported: [DECISIONS] Current report format: [CURRENT FORMAT] Data sources: [DATA SOURCES] Metrics required: [METRICS] Current manual steps: [MANUAL STEPS] Known data issues: [DATA ISSUES] Tools available: [TOOLS] Delivery channel: [EMAIL / SLACK / DASHBOARD / PDF / DOC] Owner: [OWNER] Build the reporting system: Report contract Define: - purpose - audience - decisions supported - delivery time - required sections - level of detail - owner - backup owner Metric dictionary For each metric include: - metric name - definition - formula - source system - refresh frequency - owner - acceptable variance - common misunderstanding - decision use Data pipeline Map: - source data - extraction method - transformation steps - calculation rules - validation checks - storage - dashboard / document generation - delivery automation Insight generation rules Define how the report should generate commentary: - what changed - why it changed - whether change is good or bad - what threshold matters - what action is needed - what is uncertain - what needs investigation Exception alerts Create alerts for: - metric above threshold - metric below threshold - data missing - unusual variance - target missed - target exceeded - source update failed - manual review required Report template Create the final report structure: 1. Executive summary 2. KPI snapshot 3. Trend changes 4. Wins 5. Risks 6. Exceptions 7. Decisions needed 8. Next actions 9. Appendix Automation workflow Specify: - trigger schedule - data pull - validation - report generation - human review - delivery - archive - error alert QA checklist Before delivery verify: - data freshness - formula accuracy - source completeness - commentary accuracy - chart consistency - decision asks - formatting - confidentiality Rules: - Do not automate reporting without metric definitions. - Do not generate executive commentary from unreliable data without warning. - Do not report vanity metrics unless tied to decisions. - The report should reduce leadership confusion, not add more dashboards. --------------------------------------------------------------------------------

#258AI Operations Security & Access Checklist

BUSINESS AUTOMATION & AI OPERATIONSIT, security teams, AI operations, compliance teams, founders, COOs, SaaS teams, agencies, data teams, and companies connecting AI tools to business systems.

Create security and access controls for AI tools, automations, assistants, APIs, data connectors, and internal workflows.

Act as an AI operations security reviewer. Create a security and access checklist for [AI TOOL / AUTOMATION / ASSISTANT] before it is approved for use at [COMPANY NAME]. System context: Company: [COMPANY NAME] AI tool / automation: [TOOL / AUTOMATION] Business use case: [USE CASE] Users: [USERS] Connected systems: [SYSTEMS] Data accessed: [DATA] Data generated: [GENERATED DATA] External vendors involved: [VENDORS] Authentication method: [AUTH] Admin owners: [ADMINS] Risk level: [RISK LEVEL] Compliance constraints: [CONSTRAINTS] Run the security review: Access review Check: - who needs access - who has admin rights - role-based permissions - least privilege - shared accounts - offboarding process - guest access - API key ownership - password / SSO rules - multi-factor authentication Data review Check: - data categories accessed - personal data - confidential data - customer data - employee data - financial data - regulated data - data retention - data deletion - model training use - export controls Integration review Check: - connected apps - read vs write permissions - webhook security - API scopes - token storage - rate limits - audit logs - failure behavior - unauthorized action risk Vendor review Check: - vendor terms - data processing terms - security documentation - subprocessors - breach notification - support access - compliance certifications - geographic data storage - contract review need Operational controls Define: - owner - access review cadence - prompt / workflow change approval - audit log review - incident reporting - backup process - emergency disable process - usage monitoring Approval outcome Choose: - approved - approved with restrictions - pilot only - security review required - legal / compliance review required - rejected For each restriction include: - reason - owner - deadline - evidence needed Rules: - Do not approve AI tools without knowing what data they touch. - Do not use shared admin accounts. - Do not grant write access where read access is enough. - Mark legal-sensitive or vendor-contract issues as [LEGAL REVIEW]. --------------------------------------------------------------------------------

#259Automation Portfolio Review & Rationalization

BUSINESS AUTOMATION & AI OPERATIONSCOOs, IT, automation teams, RevOps, operations managers, consultants, agencies, finance teams, and businesses with many unmanaged workflows or AI experiments.

Review all automations in a business to find what works, what breaks, what creates risk, what duplicates effort, what should be improved, retired, merged, or scaled.

You are an automation portfolio auditor. Review the automation portfolio of [COMPANY NAME] and recommend what to keep, improve, retire, rebuild, or scale. Portfolio inputs: Company: [COMPANY NAME] Automation list: [AUTOMATIONS] Tools used: [TOOLS] Automation owners: [OWNERS] Business processes affected: [PROCESSES] Usage frequency: [USAGE] Error history: [ERRORS] Maintenance history: [MAINTENANCE] Costs: [COSTS] Time savings estimates: [SAVINGS] User feedback: [FEEDBACK] Security concerns: [SECURITY] AI workflows included: [AI WORKFLOWS] Critical workflows: [CRITICAL WORKFLOWS] Audit the portfolio: Inventory cleanup For each automation identify: - name - purpose - owner - tool - trigger - actions - systems touched - business value - users - frequency - last updated - documentation status - risk level Health classification Classify each automation as: - healthy and valuable - valuable but fragile - working but undocumented - duplicate - low-value - risky - broken - obsolete - should be merged - should be rebuilt - should be retired Risk review Flag: - no owner - no documentation - no error alerts - sensitive data exposure - excessive permissions - undocumented AI usage - customer-facing impact - financial impact - dependency on one employee - tool no longer approved - poor data quality Value review Estimate: - time saved - cost saved - error reduction - cycle-time improvement - customer impact - employee experience impact - reporting value - strategic value Maintenance review Assess: - failure frequency - complexity - tool cost - API dependency - manual intervention needed - update burden - support burden Portfolio actions Assign: - keep - improve - document - add monitoring - reduce permissions - merge - rebuild - scale - retire Automation governance backlog Create: - urgent fixes - documentation tasks - owner assignments - security reviews - error handling upgrades - cost optimization actions - training needs - retirement plan Rules: - Do not keep automations only because they were hard to build. - Do not retire automations without checking business dependency. - Do not allow critical automations without an owner. - Use [NEEDS DATA] where value or risk is unknown. --------------------------------------------------------------------------------

#260Full Business Automation & AI Operations Audit

BUSINESS AUTOMATION & AI OPERATIONSCEOs, founders, COOs, AI operations leaders, automation consultants, IT teams, operations managers, digital transformation teams, and companies doing an automation reset.

Audit the complete automation and AI operations system across workflows, tools, governance, ROI, data readiness, security, QA, adoption, reliability, and scaling.

Act as an independent business automation and AI operations auditor. Review the full automation system of [COMPANY NAME] and identify the highest-leverage improvements for productivity, quality, speed, reliability, risk control, and AI adoption. Company context: Company: [COMPANY NAME] Business model: [BUSINESS MODEL] Team size: [TEAM SIZE] Departments: [DEPARTMENTS] Current tools: [TOOLS] Current automations: [AUTOMATIONS] Current AI tools: [AI TOOLS] AI use cases: [AI USE CASES] Manual bottlenecks: [BOTTLENECKS] Data sources: [DATA SOURCES] SOPs and documentation: [DOCUMENTATION] Security constraints: [SECURITY] Compliance constraints: [COMPLIANCE] Known automation failures: [FAILURES] Employee AI adoption level: [ADOPTION] Leadership goals: [GOALS] Budget / resources: [RESOURCES] Audit the system across 20 dimensions: 1. Automation strategy 2. Automation opportunity identification 3. Workflow documentation 4. Process simplification before automation 5. Tool stack fit 6. Source-of-truth clarity 7. Data readiness 8. Integration architecture 9. No-code / low-code build quality 10. AI assistant role clarity 11. AI governance 12. Human-in-the-loop review 13. AI output QA 14. Automation error handling 15. Security and access controls 16. Prompt library / knowledge base 17. Employee AI training 18. ROI measurement 19. Automation portfolio management 20. Continuous improvement cadence For each dimension provide: - score from 1 to 10 - diagnosis - evidence used - missing evidence - productivity impact - risk impact - customer impact - employee impact - recommended fix - confidence level Then synthesize: A. Top 5 automation constraints Rank by: - time savings potential - risk reduction - implementation feasibility - customer or revenue impact - employee experience impact - urgency - confidence B. Root cause analysis Identify whether the main problem is: - unclear process - poor data quality - too many disconnected tools - no source of truth - weak ownership - no governance - no QA - overuse of AI where rules would work - underuse of AI where it could help - automation without monitoring - security gaps - low employee adoption - poor documentation - no ROI tracking C. Future-state automation operating system Create: - automation intake process - prioritization model - workflow blueprint template - AI assistant charter - data readiness checklist - integration architecture principles - human review gate model - AI output QA process - error handling playbook - security review checklist - prompt library system - training plan - automation portfolio review cadence D. 30/60/90-day improvement plan Create a practical plan with: - actions - owners - workflows to automate - workflows to stop automating - tools to review - data to clean - prompts to standardize - controls to add - training to launch - metrics to track - expected outcomes E. Stop / Start / Continue List what the company should stop doing, start doing, and continue doing. F. Executive summary Write a direct plain-English summary with: - the hard automation truth - the biggest time-wasting workflow - the biggest AI risk - the fastest automation win - the weakest data or tool dependency - the next leadership decision - the data needed before scaling Rules: - Do not recommend automation for every problem. - Do not invent workflow data or ROI. - Do not ignore security, privacy, or human review. - Do not blame employees before checking tools, process, and ownership. - Use [LOW CONFIDENCE] where evidence is weak. - Focus on practical automation, reliable AI operations, measurable value, and safe scaling.

Unlock all 260 prompts