Skip to main content
BusinessPRDsintermediate

Jobs-to-be-Done (JTBD) Customer Problem Discovery Protocol

Optimized for Claude, Chatgpt, Gemini • Verified Prompt Template

Uncover hidden functional, emotional, and social customer jobs, habit inertia, and anxieties preventing switching.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables4 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[product_context]Product Context / DomaintextRequiredThe software, service, or workflow being investigatedDefault: Team documentation and engineering runbook search tool that links Slack, GitHub, and Google Docs.
[target_user]Target User PersonatextRequiredThe primary practitioner or decision-makerDefault: On-call software engineers and tech leads at fast-growing scaleups (50-200 engineers).
[current_workarounds]Current Workarounds & IncumbentstextareaRequiredHow users currently solve or tolerate this painDefault: Pinging teammates on Slack ('Hey who knows how to restart the staging pipeline?'), searching fragmented Confluence pages that haven't been updated in 9 months, or grep-searching repo history.
[trigger_event]Primary Trigger EventtextRequiredThe specific moment friction becomes urgent or unbearableDefault: A high-severity PagerDuty incident occurs during off-hours, and the on-call engineer spends 40 minutes hunting for an updated runbook while latency spirals.

Example Output & Parameters Breakdown

Inspect verified benchmark AI responses and review how parameters, system constraints, and input variables calibrate generation.

Parameters & Variable Breakdown

4 Inputs
[product_context]
Team documentation and engineering runbook search tool that links Slack, GitHub, and Google Docs.
[target_user]
On-call software engineers and tech leads at fast-growing scaleups (50-200 engineers).
[current_workarounds]
Pinging teammates on Slack ('Hey who knows how to restart the staging pipeline?'), searching fragmented Confluence pages that haven't been updated in 9 months, or grep-searching repo history.
[trigger_event]
A high-severity PagerDuty incident occurs during off-hours, and the on-call engineer spends 40 minutes hunting for an updated runbook while latency spirals.

Verified AI Benchmark Response

Grounded Output
### 1. The Core Jobs-to-be-Done Hierarchy - **Functional Job:** Resolve production incidents accurately under time pressure without relying on synchronous tribal knowledge. - **Emotional Job:** Feel confident, calm, and self-sufficient when waking up to an alarm at 3:00 AM. - **Social Job:** Be viewed by leadership and peers as a reliable, competent on-call engineer who resolves incidents swiftly without causing customer escalations. ### 2. The Four Forces of Progress - **Push of the Present:** The humiliation and stress of escalating to the VP of Engineering at 3 AM because the deployment documentation is broken and out-of-date. - **Pull of the New Solution:** The promise of a single search command in Slack that surfaces the verified, tested terminal command within 5 seconds. - **Anxiety of the New:** Fear that installing another tool will just create a *third* out-of-date documentation silo that requires manual maintenance. - **Habit Inertia:** The subconscious reflex to just type '@here does anyone know where the Redis cluster keys are?' in Slack because it requires zero cognitive effort. ### 3. High-Leverage JTBD Discovery Questions 1. *'Think back to the last time an incident went over SLA. At what exact minute did you realize you didn't have the info you needed, and what was the very next tab you opened?'* 2. *'When you realized the doc was outdated, who did you message, and how long did you wait before guessing the command yourself?'*

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Product managers conducting customer discovery interviews for roadmap prioritization
Founders positioning new tools against entrenched habits and spreadsheets
User researchers synthesizing qualitative interview recordings into executive frameworks

Tips for Best Results

Techniques to elevate response fidelity

  • •Explicitly define your Ideal Customer Profile (ICP), their acute pain points, and current legacy alternatives.
  • •Provide strict negative constraints: list corporate clichés, overused jargon, or vague promises the model must avoid.
  • •Ask the model to critique its own copy from the perspective of a cynical, time-pressed prospect before finalizing.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Failing to define a singular, clear Call-to-Action (CTA), resulting in unfocused and diluted messaging.
  • •Accepting high-level marketing buzzwords that sound impressive but say nothing concrete to users.
  • •Not fact-checking competitive claims, legal guarantees, or pricing specifications generated by the model.

Frequently Asked Questions About This Prompt

Technical guidance on model compatibility, parameter substitution, iteration techniques, and commercial usage.

Q1.Which AI models work best with the "Jobs-to-be-Done (JTBD) Customer Problem Discovery Protocol" prompt?

This prompt is thoroughly tested and compatible with Claude, Chatgpt, Gemini. For multi-step reasoning, architectural planning, and code refactoring, Claude 3.7/3.5 Sonnet and ChatGPT-4o provide the highest constraint adherence. For large-document synthesis, Google Gemini 2.5 Pro is also recommended.

Q2.How do I customize the parameters in this prompt template?

This template features 4 customizable parameter(s): [product_context], [target_user], [current_workarounds], [trigger_event]. Replace each bracketed placeholder with your project's specific details, constraints, or code before submitting to your AI model. You can also use our interactive workbench on this page to populate and copy the completed prompt in one click.

Q3.Can I use this prompt and its outputs for commercial projects?

Yes. All prompts published on Beautiful AI Prompt are 100% free for both personal and commercial use. You hold full ownership of all code, copy, strategies, or imagery generated by your selected AI model when running this prompt.

Q4.How does this prompt prevent AI hallucinations and ensure output accuracy?

This template enforces explicit negative constraints, few-shot parameter boundaries, and schema requirements (such as tabular comparisons or step-by-step logic). This suppresses speculative drift and forces the AI model to ground its response in your provided inputs.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Business

View all Business prompts
Businessadvanced

SaaS Pricing Tier & Value-Metric Packaging Architect

Structure pricing tiers (Free, Pro, Team, Enterprise) anchored against high-expansion value metrics rather than arbitrary gates.

[Copy & Paste Template]3 parameters

›You are a Principal B2B SaaS Monetization Director and Pricing Strategist. I need to design or restructure the packaging and pricing model for our software product. Product Category & Target Customer: [product_category] Core Value Metric & Usage Driver: [usage_driver] Current or Proposed Pricing Thoughts: [current_pricing] Deliver the comprehensive Monetization & Packaging Blueprint: 1. Value Metric Selection: Analyze the pros and cons of 3 potential value metrics (e.g. per-seat vs. consumption-based vs. hybrid tiering) and select the optimal driver that naturally scales as the customer grows. 2. Tiered Packaging Matrix (Free/Starter, Pro, Growth/Team, Enterprise): For each tier, define: (A) Dollar Price Point, (B) Target Persona, (C) Hard Feature Gates (SSO, Audit Logs, SLA), (D) Soft Usage Quotas. 3. Freemium to Paid Conversion Mechanics: Exact psychological trigger points that compel a free user to pull out a credit card without feeling bait-and-switched. 4. Enterprise Expansion Playbook: How sales can renegotiate accounts when usage surges beyond self-serve thresholds.

claudechatgpt
#saas-pricing#monetization#packaging
Businessadvanced

Early-Stage Business Idea Feasibility & Risk Pre-Mortem

Conduct a rigorous pre-mortem analysis to identify fatal assumptions, distribution bottlenecks, and market risks before writing code.

[Copy & Paste Template]4 parameters

›You are a seasoned venture builder and startup risk analyst known for rigorous, unsentimental feasibility reviews. I want to conduct a comprehensive Pre-Mortem and Feasibility Teardown on a new business idea. Business Concept Overview: [business_concept] Target Customer & Problem: [target_customer_problem] Proposed Monetization Model: [monetization_model] Primary Growth / Distribution Hypothesis: [distribution_channel] Analyze this business concept with the following rigorous breakdown: 1. The 18-Month Pre-Mortem: Fast-forward 18 months assuming this company shut down. Detail the top 3 most likely root causes of failure (focus on distribution failure, low willingness-to-pay, retention cliff, or unit economic leakage). 2. Critical Assumption Inventory: List the 5 make-or-break hypotheses that must be true for this business to reach $1M ARR, ranked by uncertainty and impact. 3. Defensibility & Moat Evaluation: Analyze how vulnerable this is to platform risk, fast-following incumbents, and AI commoditization. 4. Day-Zero De-risking Experiments: Propose 3 low-cost, non-technical validation experiments I can run in the next 14 days to validate customer pull before building any product.

claudechatgptgemini
#business-validation#startup#pre-mortem
Marketingintermediate

Negative Buyer Persona & Anti-ICP Definition Framework

Identify high-churn, unprofitable customer profiles to eliminate wasted marketing ad spend and sales rep distraction.

[Copy & Paste Template]3 parameters

›You are a VP of Product Marketing and Revenue Efficiency expert. I need to formulate an explicit Anti-ICP (Negative Buyer Persona) guide to stop our sales and marketing teams from chasing bad-fit prospects that drive high churn and team burnout. Our Ideal Customer Profile (ICP): [ideal_customer_profile] Our Product's Non-Negotiable Requirements / Constraints: [product_constraints] Past Painful Customer Experiences / High-Churn Profiles: [past_bad_fits] Construct our definitive Anti-ICP Dossier: 1. The 3 Primary Anti-Personas: Give each negative profile a descriptive name, job role, and their deceptive initial appeal (why sales reps are tempted to chase them). 2. Early Warning Red Flags: Detail 5 disqualifying questions or statements prospects make on discovery calls that should trigger an immediate, polite disqualification. 3. Toxic Feature Expectations: Identify features these prospects routinely demand that violate our product roadmap and cause severe custom-engineering drag. 4. Graceful Disqualification Script: Provide an empathetic, professional email/call script to reject or refer these leads to competitors without creating resentment.

claudechatgptgemini
#buyer-persona#anti-icp#positioning

Related Engineering Guides

Deep-dive playbooks and system prompt methodologies for Business

View all guides