Useful prompts for work that needs doing.

Create a concise competitor positioning 1-pager for a sales enablement document or strategy memo. Compare our messaging with {{competitor_name}} for {{target_customer_segment}} using our value proposition, differentiator, and the competitor source at {{competitor_homepage_url}}.

Use only information supported by the supplied competitor source. If the URL is inaccessible or does not substantiate a claim, write "Not verifiable from the supplied source" rather than inferring features, customers, results, or weaknesses. Do not invent quotes, capabilities, testimonials, or competitive claims. Distinguish direct quotes from summaries.

Our value proposition: {{our_value_proposition}}
Our key differentiator: {{key_differentiator}}

Return only this fixed format:
Competitor Main Message: [One direct quote with source context, or an accurate summary if no reliable quote is available]
Key Differences:
- [Specific difference in message, audience, approach, or stated benefit]
- [Specific difference in message, audience, approach, or stated benefit]
- [Specific difference in message, audience, approach, or stated benefit]
Competitor Gaps (Not Saying):
- [A meaningful omission supported by the source comparison, or "Not verifiable from the supplied source"]
- [A meaningful omission supported by the source comparison, or "Not verifiable from the supplied source"]
Our Counter-Positioning: [One clear statement explaining how our value proposition and differentiator position us against the competitor for the target segment]

Keep the result factual, specific, concise, and usable after one light edit. Do not add an introduction, conclusion, methodology, disclaimers beyond necessary source limitations, or follow-up questions.

Convert the supplied prospect criteria into one LinkedIn-compatible Boolean search query string. Use only these field labels: title, industry, companySize, geo, yearsExperience, connectionDegree. Format each populated criterion as field:"value" and join criteria with AND. Omit any optional criterion that is blank or set to Any. Do not invent information, broaden the criteria, ask questions, or include explanations, labels, markdown, or a trailing period. Return the plain text query string only.

Target job title or function: {{target_role}}
Target industry: {{target_industry}}
Target company size: {{company_size}}
Target location: {{target_location}}
Years of experience: {{years_experience}}
Connection degree preference: {{connection_degree}}

Create a concise 5-point company research snapshot for sales outreach using the inputs below.

Company: {{company_name}}
Our solution/product: {{solution_product}}
Target pain point: {{target_pain_point}}

Use this exact structure:
1. What they do: Summarize the company, its market, customers, and primary offering.
2. Recent news: Identify relevant recent developments only when supported by reliable information available in your context. If you cannot verify a development or do not have current information, state that clearly instead of guessing.
3. Their positioning: Explain how the company appears to differentiate itself and compete.
4. Key challenges: Identify plausible business or operational challenges, distinguishing evidence-based observations from reasonable inferences.
5. Why they may need our solution: Connect the likely challenges to {{solution_product}} and {{target_pain_point}} without overstating fit.

Keep the response to exactly five numbered points. Use specific, useful language suitable for a salesperson preparing a cold call or email. Do not use hype openers, politeness padding, generic marketing claims, fabricated facts, invented news, or unsupported certainty. Do not ask follow-up questions; proceed with the available information. Flag important unknowns briefly. Do not recommend contacting anyone or write outreach copy.

Condense the email draft below into a clear, direct message of fewer than 50 words. Preserve the primary goal, essential facts, and any call to action. Use the recipient context to make the wording appropriate. Do not add details, assumptions, filler, or unnecessary politeness. If useful, include a concise subject line. Output exactly this format:
Subject: concise subject or None
Message: condensed email

Email draft:
{{original_email}}

Primary goal or key point:
{{primary_goal}}

Recipient role or relationship:
{{recipient_context}}

Summarize the meeting using only the information in the transcript and attendee lists. Do not invent names, dates, commitments, decisions, or details. Use the objective only to understand context.

Transcript:
{{meeting_transcript}}

Internal attendees:
{{internal_attendees}}

External attendees:
{{external_attendees}}

Meeting objective or agenda:
{{meeting_objective}}

Return exactly 3 plain-text bullets in this fixed order:
- Decision: State the clearest decision made. If none was made, write "No decision stated."
- Our team action: State the clearest action assigned to the internal team. Include an owner only when explicitly stated. If none was assigned, write "No internal action stated."
- Client or counterpart next step: State the clearest next step assigned to the external party or counterpart. Include an owner only when explicitly stated. If none was assigned, write "No external next step stated."

Keep each bullet concise and usable after one light edit. Do not add headings, explanations, questions, dates, or extra bullets.

Prepare a concise meeting brief for the next 60 seconds using the details below.

Meeting type: {{meeting_type}}
Attendees: {{attendee_list}}
Meeting goal: {{meeting_goal}}
Current project context: {{current_project_context}}

Return only these sections:
1. Top 3 things to accomplish — make each specific to the goal, attendees, and context.
2. 2 key questions — make them useful for moving the meeting forward.
3. One surprise element to discuss — a non-obvious risk, opportunity, trade-off, or insight grounded in the context.

Keep the entire response under 150 words. Do not ask follow-up questions, add greetings or filler, or invent facts. Make reasonable assumptions when needed.

Generate exactly 5 email subject lines for the topic {{topic}}, intended for {{audience}}, using the key angle {{key_angle}} and fitting this campaign context: {{campaign_context}}.

Make each subject line concise, clear, and compelling for quick opens without fake urgency, false deadlines, scarcity claims, ALL CAPS, or excessive punctuation. Reflect the topic and angle accurately. Return only the 5 subject lines, one per line, with no numbering, bullets, commentary, or follow-up questions.

Draft a warm, direct professional email opener using the details below.

Recipient: {{recipient_name}}
Email topic or purpose: {{email_topic}}
Relationship context: {{relationship_context}}

Return exactly 2 sentences and nothing else. Address the recipient naturally, state the reason for writing clearly, and make the draft usable after one light edit. Avoid fluff, jargon, hype, excessive politeness, and phrases such as "touch base" or "synergy". Do not ask clarifying questions.

Draft a concise meeting-decline message based on the details below. Output only the message body, with no subject line, labels, commentary, quotation marks, or follow-up questions.

Meeting topic: {{meeting_topic}}
Their intended outcome: {{meeting_outcome}}
Reason for declining: {{decline_reason}}
Specific async alternative: {{async_alternative}}
Requested response time or deadline: {{response_deadline}}

Acknowledge their intended outcome in the opening sentence. State the decline plainly without over-explaining or over-apologizing. Propose the specific async alternative exactly and include the response time or deadline when relevant. Close with one clear next step. Do not invent details, testimonials, social proof, or a future meeting invitation.

Create a documented data dictionary from the CRM field names and context below.

Inputs:
- Raw CRM field names: {{raw_field_names}}
- Sales and marketing workflow context: {{workflow_context}}
- Existing notes or purpose guesses: {{existing_notes}}
- Teams responsible for data entry: {{data_entry_teams}}

For every field, preserve the exact field name and provide:
1. Definition
2. Owning team
3. Workflow stage where it is created or updated
4. Good value example
5. Bad value example
6. Notes, including assumptions or unresolved ambiguity

Return only a standard Markdown table with this exact header:
| Field | Definition | Owner | Stage | Good value example | Bad value example | Notes |

Include every supplied field exactly once. Use plain language and concrete examples relevant to the stated workflow. Do not invent system behavior, policies, or field meanings as facts. When information is uncertain, state a concise assumption in Notes. Do not request files, tools, or follow-up information.

Convert the provided customer feedback and context into one neutral, factual engineering issue report. Remove emotional, accusatory, and speculative language. Preserve concrete actions, exact error text, timestamps, environment details, identifiers, and reproduction information. Do not invent, infer, or normalize missing facts. If information is absent, write "Not provided" or list it under Unknowns. Return only this format:

Title: [Feature/Module] - [Brief Issue Summary]

Summary: [One concise factual description]

Steps to Reproduce:
1. [Factual step]
2. [Factual step]

Expected Behavior: [What should have happened]

Actual Behavior: [What happened, including exact errors or observable effects]

Environment: [OS, browser, device, product version, deployment environment, or Not provided]

References: [Relevant account/order ID, incident timestamp, logs, screenshots, or Not provided]

Unknowns:
- [Missing debugging information]

Customer message:
{{customer_message}}

Attached evidence or error details:
{{diagnostic_evidence}}

Account or order context:
{{account_context}}

Incident timing and environment:
{{incident_details}}

Reproduction steps described by the customer:
{{reproduction_steps}}

Write a voicemail for a prospect who has not replied to two emails. Return exactly 3 lines and no other text. Keep it under 55 words, or about 25 seconds when spoken. Be direct and natural, with no apology or filler. Use all details, briefly compressing the value proposition if needed:
Hi {{prospect_name}} at {{prospect_company}}, this is a follow-up to my {{last_email_date}} email.
I'm calling because {{value_prop}}.
I'll send a calendar invite for {{next_step}}.

Write one plain, honest LinkedIn answer post based only on the information provided.

Customer question:
{{customer_question}}

Fact-based answer and technical context:
{{answer_details}}

Target reader or industry context:
{{target_reader}}

Product or service context:
{{product_context}}

Desired length:
{{length_constraint}}

Start directly with the question or relevant context. Answer clearly, explain what the answer means for the target reader, and keep the wording useful and specific. Do not invent facts, testimonials, social proof, examples, results, or technical details. Do not use hype openers, engagement bait, unnecessary politeness, step-by-step theatre, hashtags, or a call to action asking people to comment, share, or message. Return only the finished LinkedIn post as plain text.

Create a practical, evidence-based close plan for the late-stage opportunity using only the information provided below.

Deal status and timeline:
{{deal_status_timeline}}

Identified stakeholders and roles:
{{stakeholders}}

Known objections, risks, and blockers:
{{risks_objections_blockers}}

Prospect's decision criteria or evaluation checklist:
{{decision_criteria}}

Committed next steps and follow-up agreements:
{{commitments}}

Use this exact output structure:

## 1. Close Assessment
State the current stage, decision readiness, timeline pressure, and the most important gap to resolve. Base every point on the provided information. Identify unknowns rather than filling them in.

## 2. Decision Criteria
For each criterion, include: criterion, evidence of status, remaining gap, and action required. Clearly label criteria with insufficient evidence.

## 3. Stakeholders
For each stakeholder, include: name or role, influence in the decision, current position if known, concern or need, and engagement action. Do not infer personal motivations without evidence.

## 4. Dependencies
List internal or prospect-side dependencies that could delay or prevent a decision. For each, include the dependency, responsible party if known, required outcome, and target date if provided.

## 5. Risks and Blockers
For each risk or blocker, include: issue, evidence, likely impact on the deal, mitigation, owner, and deadline where available. Separate confirmed issues from unresolved possibilities.

## 6. Commitments
List every existing commitment, including the agreed action, owner, due date, completion status, and evidence or missing confirmation.

## 7. Action Plan
List the specific actions required to reach a decision, prioritized as Critical, High, or Medium. For each action, include the owner, deadline, intended outcome, and dependency. Use only owners and dates supplied in the inputs; otherwise write "Not specified".

## 8. Recommended Close Path
Give a concise sequence of the next three to five actions, ordered by dependency and urgency. Include the decision milestone that each action supports.

Keep the tone professional, direct, and free of hype. Do not provide generic sales advice. Do not fabricate facts, dates, owners, statistics, testimonials, external research, or stakeholder opinions. Do not assume access to tools or information outside the provided inputs. Make the plan usable after one light edit.

Rewrite the message below so it professionally pushes back on the request, deadline, or decision while remaining constructive.

Original message or request:
{{original_message}}

Specific constraint or limitation:
{{constraint}}

Proposed alternative or compromise:
{{alternative}}

Recipient relationship:
{{recipient_context}}

Write only the revised message. Clearly state the constraint, briefly explain its impact, and offer the proposed alternative. Preserve the facts provided and do not invent details, statistics, commitments, or excuses. Use a direct, professional, non-aggressive tone; avoid excessive apologizing, blame, hype, and filler. Keep it concise and ready to send after one light edit. Format it as one to three short paragraphs with no heading, commentary, or bullet points.

Draft a ready-to-send client message about the issue below. Return exactly two parts: a concise subject line or opening, followed by the message body.

Client: {{client_name_or_title}}
What went wrong: {{mistake_description}}
Impact on the client: {{client_impact}}
Immediate fix: {{immediate_fix}}
Next step or timeline: {{next_step_or_timeline}}

Acknowledge the mistake directly without excuses, external blame, or defensiveness. Explain the impact from the client's perspective, state the concrete corrective action, and make the next step or timeline unmistakable. Keep the language professional, direct, calm, and accountable. Avoid hype, excessive apology, vague assurances, and invented details. Write for one light edit and do not ask follow-up questions.

Extract a precise, actionable meeting log from the source material below. Separate confirmed outcomes from discussion, speculation, and unresolved matters. Do not summarize the meeting or include greetings, filler, an introduction, or a conclusion.

Meeting context or goal: {{meeting_context}}
Attendees: {{attendees}}
Current date: {{current_date}}
Raw transcript or notes:
{{meeting_text}}

Return exactly these sections in this order:

CONFIRMED DECISIONS
| Description | Owner | Deadline | Status | Evidence/Notes |
|---|---|---|---|---|

ACTION ITEMS AND COMMITMENTS
| Description | Owner | Deadline | Status | Evidence/Notes |
|---|---|---|---|---|

UNRESOLVED QUESTIONS
| Question or issue | Owner | Deadline | Status | Evidence/Notes |
|---|---|---|---|---|

DEPENDENCIES AND RISKS
| Dependency or risk | Owner | Deadline | Status | Evidence/Notes |
|---|---|---|---|---|

Extraction rules:
- Include decisions, unresolved questions, commitments, actions, owners, deadlines, dependencies, and risks only when supported by the source.
- Put an item in CONFIRMED DECISIONS only when the notes clearly show agreement, approval, or a final choice. Keep proposals and general discussion out of that section.
- Capture owners and deadlines when explicitly stated or clearly implied. If unavailable, write “Unassigned” or “Not specified”; never invent details.
- Resolve relative deadlines such as “next Friday” using the current date. Preserve uncertainty when the date cannot be resolved.
- Use concise, specific descriptions. Normalize status to one of: Confirmed, Open, In progress, Blocked, or Not specified.
- If a section has no supported items, write “None identified” in its first row.
- Preserve important qualifiers and distinguish commitments from suggestions. Use short source wording in Evidence/Notes when it clarifies why an item was extracted.

Create a concise sales call brief using only the information provided below. Do not request more information, invent facts, add hype, or include introductions or closing remarks.

Company and industry: {{company_name_industry}}
Contact person and role: {{contact_name_role}}
Previous conversation summary: {{conversation_summary}}
Primary call objective: {{call_objective}}
Relevant solution details, pain points, and objections: {{solution_and_pain_points}}

Use exactly these three sections and no others:

What You Should Know
- Summarize the most relevant company, contact, conversation, solution, pain-point, and objection context.
- Identify any important unknowns without guessing.

What You Should Ask
- Provide 4 to 6 specific questions tailored to the context and objective.

What You Should Accomplish
- Provide 3 to 5 clear, measurable goals for the call tied to the stated objective.

Keep the brief practical, concise, and usable after one light edit.

Convert the meeting material below into a concise, factual JSON action record.

Meeting transcript or notes:
{{meeting_text}}

Attendees:
{{attendees}}

Meeting agenda or objective:
{{meeting_objective}}

Known project deadlines:
{{project_deadlines}}

Stakeholder roles:
{{stakeholder_roles}}

Return only valid JSON with exactly these top-level keys:
{
  "confirmed_decisions": ["..."],
  "unresolved_questions": ["..."],
  "action_items": [
    {"owner": "...", "deadline": "...", "task": "..."}
  ],
  "dependencies": ["..."],
  "commitments": ["..."]
}

Rules:
- Include only decisions explicitly confirmed in the transcript or notes; do not treat suggestions, possibilities, or discussion as decisions.
- Capture every clearly stated action, with the named owner and deadline when available.
- Use "Unassigned" for a missing owner and "Not specified" for a missing deadline; do not invent facts.
- Include only dependencies and commitments explicitly stated or directly supported by the material.
- Preserve dates and names as provided.
- Use empty arrays when a section has no supported entries.
- Do not add commentary, explanations, markdown, or extra keys.

Produce a structured, evidence-based close plan for the sales opportunity described below. Use only the supplied information. Do not invent facts, statistics, testimonials, stakeholder motivations, deadlines, dependencies, or decision criteria. Where information is missing, write "Not provided" and identify the specific gap. Distinguish explicit evidence from reasonable inferences.

Opportunity context:
{{opportunity_context}}

Stakeholders and roles:
{{stakeholders}}

Decision criteria or evaluation metrics:
{{decision_criteria}}

Active risks or blockers:
{{risks_blockers}}

Committed next steps and required actions:
{{committed_actions}}

Use exactly these section headers and keep the content concise and actionable:

## Opportunity Snapshot
Summarize the opportunity name, current stage, stated objective, and close status based only on the input.

## Decision Criteria
List each known evaluation metric or approval criterion. For each, state the evidence, current status, and any gap.

## Stakeholders
For each stakeholder, list name, role, stated or evidenced influence, position if known, and the next engagement needed. Mark unknown information as "Not provided."

## Dependencies
List internal or external prerequisites for approval or execution. Identify the source input and whether each dependency is confirmed, inferred, or unresolved.

## Risks
List each active risk or blocker, its likely impact on close, evidence, mitigation action, owner if known, and target date if known. Do not assign owners or dates that are not provided.

## Commitments and Actions
Convert the supplied commitments into a table with columns: Action, Owner, Deadline, Success Signal, and Status. Preserve stated owners and deadlines; use "Not provided" when absent.

## Close Recommendation
State the recommended immediate close motion, the strongest evidence supporting it, the unresolved approval gap, and the next decision checkpoint. Do not use hype or unsupported probability claims.

Audit the account and territory assignment data below against the stated rules. Use only the supplied information. Do not use external lookups or invent missing values. Infer what can be determined without asking follow-up questions, and label any undeterminable item as "Not determinable from supplied data" with the missing basis stated.

SOURCE DATA
Current account ownership dataset:
{{account_ownership_dataset}}

Territory assignment rules:
{{territory_assignment_rules}}

Sales team capacity limits and coverage maps:
{{capacity_and_coverage_maps}}

Historical assignment change log:
{{assignment_change_log}}

Apply all stated region, industry, revenue, capacity, coverage, effective-date, and ownership rules. Check each account for valid ownership, uncovered territory or account coverage, multiple active owners, capacity breaches, and inconsistent application of the rules. Use the change log to identify recent or recurring assignment logic issues. Calculate percentages from the supplied records only; state the denominator used. Suggested resolutions must be evidence-based and must not create owners, territories, or assignments that are absent from the supplied data.

Return exactly the following structure and headings. Keep tables compact and use "None identified" when a section has no findings.

# Account and Territory Assignment Audit

## 1. Audit summary
- Audit scope:
- Total accounts audited:
- Accounts with valid ownership:
- Uncovered accounts:
- Coverage percentage:
- Accounts with ownership conflicts:
- Accounts with duplicate coverage:
- Rule violations or logic inconsistencies:
- Capacity breaches:
- Key data limitations:

## 2. Ownership conflicts and recommended resolution
| Account | Current owner(s) | Conflict type | Rule or evidence | Recommended resolution | Confidence |
|---|---|---|---|---|---|

## 3. Uncovered accounts and recommended owner
| Account | Region | Industry | Revenue | Coverage gap | Eligible owner or territory | Recommendation | Confidence |
|---|---|---|---:|---|---|---|---|

## 4. Duplicate coverage report
| Account | Affected owner(s) or territories | Duplicate condition | Likely cause | Recommended resolution |
|---|---|---|---|---|

## 5. Rule violations and logic inconsistencies
| Account, segment, or rule | Finding | Expected logic | Observed logic | Evidence | Recommended correction |
|---|---|---|---|---|---|

## 6. Capacity and coverage risks
| Owner or territory | Assigned accounts | Capacity limit | Variance | Coverage-map issue | Recommended action |
|---|---:|---:|---:|---|---|

## 7. Assignment change-log observations
| Date or change reference | Account or territory | Observed change | Related audit finding | Risk or implication |
|---|---|---|---|---|

## 8. Prioritized actions
1. [High] Action — rationale and affected records.
2. [Medium] Action — rationale and affected records.
3. [Low] Action — rationale and affected records.

Do not add sections, omit required sections, include external facts, or present assumptions as confirmed data.

Prepare one client-facing pricing negotiation package for the stalled deal described below. Use only the supplied facts. Do not invent statistics, benchmarks, testimonials, customer results, competitor claims, or unsupported estimates. Label assumptions, estimates, and missing information clearly.

Client and audience:
{{client_audience}}

Current offer:
{{current_offer}}

Client alternative or target:
{{client_alternative}}

Evidence of business value:
{{value_evidence}}

Negotiation flexibility and preferred next step:
{{negotiation_flexibility}}

Use this fixed format and section order:

Deal Diagnosis
- Identify the client's pricing concern and the seller's commercial position without conceding value prematurely.
- Add a brief Information Gaps note listing every missing fact that materially affects the recommendation.

Offer Comparison
- Compare the current offer and the alternative across headline price, scope, outcomes, implementation, delivery, quality, risk, support, and commercial terms.
- Separate confirmed differences from unknowns. Do not treat the options as like-for-like unless the evidence supports that conclusion.

Value Case
- Explain the value in concrete business terms using only the supplied evidence.
- Quantify value only when the inputs support it; otherwise provide a clearly labeled reasoned case and identify what would be needed to quantify it.

Negotiation Plan
- Recommend one negotiation strategy with a target position, acceptable boundary, and specific concessions if appropriate.
- Make every concession conditional on a reciprocal client commitment, such as scope confirmation, term agreement, timing, payment, access, or approval authority.
- Define what must not be conceded and avoid unconditional discounts.

Client Message
- Write a concise, ready-to-send message addressed to the stated client or audience.
- Acknowledge the pricing concern, explain the meaningful differences, connect them to business value, present practical commercial options, and request the preferred next step or decision by the stated deadline.
- Use a professional, direct, credible style without hype, pressure, deception, or unsupported claims.

Objection Responses
- List the most likely client objections and provide concise, evidence-based responses tailored to this deal.

Next Step
- State one specific action, owner, and timing that would move the deal forward.

Return only the completed negotiation package with the seven headings above.

Analyze the lifecycle-stage conversion data below to identify where qualified demand is being lost, distinguish likely process failures from data-quality problems, and prioritize the most actionable findings.

Lifecycle-stage definitions and sequence:
{{stage_definitions}}

Stage-level volume data for the analysis period:
{{stage_volume_data}}

Segmented conversion, aging, or time-in-stage data:
{{segment_data}}

Known CRM issues, process rules, handoff expectations, exclusions, and caveats:
{{data_quality_and_caveats}}

Instructions:
- Analyze the full supplied lifecycle path and calculate or report conversion and loss at every available transition. Show denominators and state the time period and stage definitions used.
- Account for re-entry, recycling, withdrawals, skipped stages, aging, incompatible cohorts, and mixed lead/opportunity populations when the supplied data indicates they matter.
- Separate observed facts, calculated metrics, hypotheses, and assumptions. Do not invent values, benchmarks, causes, sample-size thresholds, financial impact, or unsupported causal claims.
- Distinguish process failure, data-quality problem, and mixed or unclear findings using only supplied evidence such as timing, ownership, handoff completion, stage-history consistency, duplicate records, missing fields, stale records, or conflicting definitions.
- Report segment differences only where the supplied data supports a valid comparison, and flag insufficient volume or missing data.
- Rank findings by business impact and confidence.

Return exactly these sections in this order:
1. Executive finding: a concise statement identifying the largest qualified-demand loss points and the most important qualification or data caveat.
2. Lifecycle conversion table: use exactly these columns: Stage transition | Starting volume | Next-stage volume | Conversion rate | Loss rate or volume | Key segment differences | Likely issue type | Evidence | Confidence | Priority. Use N/A where a field cannot be calculated.
3. Finding classification: classify each material finding as Process failure, Data-quality problem, or Mixed or unclear, with a short rationale and supporting evidence.
4. Prioritized interventions: list the three to five most actionable interventions in priority order. For each, state the observed loss point, recommended process or data change, expected decision benefit, and confidence. Do not claim an expected uplift unless the inputs support it.
5. Missing data and validation checks: list the checks required before making high-confidence decisions.
6. Assumptions and limitations: state cohort, period, denominator, stage-definition, data-quality, and causality limitations that affect interpretation.

Use concise business language. Keep conclusions traceable to the supplied data or transparent calculations.

Act as a marketing content strategist. Analyze the published content library, target audience, business context, and optional evidence below to diagnose existing coverage and prioritize evidence-based content gaps. Perform only this job: do not draft content, create a full editorial calendar, or recommend generic SEO topics.

Inputs:
Published content library:
{{published_content_library}}

Target audience:
{{target_audience}}

Business context:
{{business_context}}

Optional demand or customer evidence:
{{demand_evidence}}

Use only the supplied information. Do not invent statistics, search volume, customer feedback, performance results, testimonials, business facts, or market conditions. Clearly label reasonable inferences. Treat a topic as a genuine gap only when the existing content does not adequately address the audience need, buyer question, search intent, or decision stage. Reject cosmetic variations, synonyms, repackaging, new formats, or minor angle changes when the underlying topic is already adequately covered.

Return exactly these sections in this order:

Coverage summary
Give a concise overview of what the library covers, including recurring audience problems, search intents, buyer stages, formats, and commercially relevant themes. Reference specific supplied content by title, URL, identifier, or other available marker.

Repeated or heavily covered themes
List the themes that appear repeatedly or are strongly covered. For each, cite the supporting content and briefly explain the coverage pattern.

Gap analysis
Distinguish genuine gaps, weakly covered topics, and apparent gaps that overlap with existing content. For each meaningful finding, explain the unmet need, the relevant audience or buyer question, the decision stage or intent, the supporting evidence, and the overlap judgment.

Prioritized content gaps
Use a table with exactly these columns: Rank | Gap | Audience or buyer question | Decision stage or search intent | Evidence | Existing-content overlap check | Recommended format or angle | Priority rationale. Include only gaps supported by the supplied inputs. Rank them by audience importance, commercial relevance, evidence of demand, decision-stage value, and the extent to which existing content fails to answer the need. State when evidence is limited.

Limitations and evidence notes
Identify missing, ambiguous, outdated, inconsistent, or insufficient source information that affects confidence. Separate supplied evidence from inference.

Be professional, clear, practical, direct, and evidence-aware. Make every major coverage finding and recommendation traceable to the supplied inputs.