🚨 BREAKING: Claude can now read every threat in your business like the CIA reads enemy intelligence (for free).
Here are 6 insane Claude prompts that tell you exactly what to act on and
what to ignore in business.
(Save for later)
1/ WILL YOUR CLIENT CHURN
Prompt:
1. Ask for the specific client behavior I'm concerned about, the history of our relationship, and the last 3 interactions before starting
2. Map every signal the client has sent — response time changes, tone shifts, feedback quality, and engagement level
3. Classify each signal as a churn indicator or normal friction using the threat credibility framework
4. Deliver a churn probability assessment — real threat or recoverable friction
5. Prescribe the exact recovery move if the threat is real and the exact do-nothing move if it isn't
- Every signal must be classified explicitly — never leave ambiguity about what it means
- Churn indicators must be distinguished from normal friction — not every silence is a resignation
- Recovery move must be specific — not "reach out and check in"
- Do-nothing move must also be specific — knowing when not to act is as valuable as acting
- Test: if I made the recovery move right now would it help or make the situation worse
2/ WILL THEY UNDERCUT YOU
Prompt:
1. Ask for my competitor's recent moves, my current positioning, and the specific threat I'm worried about before starting
2. Map every signal the competitor has sent — pricing changes, content shifts, new hires, product updates, and audience targeting
3. Apply the credibility test — do they have the resources, incentive, and capability to follow through
4. Deliver a threat credibility score — real competitive threat or empty market noise
5. Prescribe the exact defensive move if the threat is real and the exact ignore move if it isn't
- Every competitor signal must be assessed for credibility — not just noted
- Credibility test must include resources, incentive, and capability — all three must be present for a real threat
- Defensive move must be specific and proportional — never overreact to a threat that isn't credible
- Ignore move must be explicit — knowing what to dismiss is as valuable as knowing what to fight
- Test: if this competitor followed through tomorrow would it actually damage my business
3/ WILL THEY NEGOTIATE YOU DOWN
Prompt:
1. Ask for the specific prospect behavior I'm reading, the conversation history, and the price I'm planning to present before starting
2. Map every signal the prospect has sent — budget questions, competitor comparisons, hesitation language, and urgency signals
3. Classify each signal as a genuine price objection or a buying signal disguised as hesitation
4. Deliver a negotiation probability assessment — real price pushback or pre-sale anxiety I'm misreading
5. Prescribe the exact hold-firm move if pushback is coming and the exact present-with-confidence move if it isn't
- Every prospect signal must be classified — never assume hesitation means price resistance
- Buying signals disguised as hesitation must be identified explicitly — these are the most dangerous misreads
- Hold-firm move must include specific language — not just "don't discount"
- Present-with-confidence move must eliminate pre-emptive discounting before it happens
- Test: if I presented my full price right now with zero apology would this prospect pay it
4/ WILL YOUR SPONSOR PULL OUT
Prompt:
1. Ask for the specific sponsor behavior I'm concerned about, the deal history, and the last 3 interactions before starting
2. Map every signal the sponsor has sent — payment timing, communication frequency, brief quality, and campaign enthusiasm
3. Classify each signal as a cancellation indicator or normal brand procurement friction
4. Deliver a deal risk assessment — real cancellation threat or recoverable friction
5. Prescribe the exact re-engagement move if the threat is real and the exact patience move if it isn't
- Every sponsor signal must be classified explicitly — delayed payment means different things in different contexts
- Normal brand procurement friction must be distinguished from genuine disengagement
- Re-engagement move must be specific — not "follow up and check in"
- Patience move must include a specific timeline — how long to wait before escalating
- Test: if I sent the re-engagement move right now would it help or signal desperation
5/ IS THE ALGORITHM SUPPRESSING YOU
Prompt:
1. Ask for my recent platform metrics, content type, posting frequency, and any recent changes I made before starting
2. Map every performance signal — reach drops, engagement rate changes, follower growth stalls, and impression patterns
3. Apply the suppression test — is the pattern consistent with algorithmic restriction or normal content variance
4. Deliver a suppression probability assessment — real algorithmic threat or variance I'm misreading
5. Prescribe the exact recovery protocol if suppression is real and the exact stay-the-course move if it isn't
- Every performance signal must be assessed against baseline — never evaluate in isolation
- Algorithmic restriction patterns must be distinguished from normal variance — they look similar but require opposite responses
- Recovery protocol must be specific — exact content changes, posting adjustments, or engagement moves
- Stay-the-course move must include a specific reassessment timeline — when to check again
- Test: if I implemented the recovery protocol right now would it help or signal panic to the algorithm
6/ BUILD YOUR THREAT DETECTION SYSTEM
Prompt:
1. Ask for every critical relationship and revenue source in my business before starting
2. Map the key signals to monitor for each relationship — what a real threat looks like vs what normal friction looks like
3. Build the threat credibility framework — the specific test every signal must pass before I take action
4. Design the weekly threat audit — a 15-minute review that keeps me ahead of every real threat
5. Deliver the complete signal library — the specific behaviors that mean act now and the specific behaviors that mean ignore completely
- Every critical relationship must have its own signal map — threats look different in different contexts
- Threat credibility framework must be simple enough to apply in under 5 minutes per signal
- Weekly audit must take under 15 minutes — never elaborate enough to skip
- Signal library must be binary — act or ignore, never "it depends"
- Test: if I ran this system every week for 90 days would I ever be surprised by a threat again
This site literally has thousands of prompts for Claude, ChatGPT, Gemini, & Nano Banana.
Explore for free 👇
godofprompt.ai/prompt-library
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.
