PromptJoy

Public prompt detail for browsing before sign in.

Sign inSign up
Back to discovery
Business Development
GPT-4.1

Sales call follow-up email with next-step pressure

Writes follow-up emails that sound human, advance the deal, and surface blockers.

Prompt metadata
Enough context to judge fit before you copy the prompt into a real workflow.

Workflow

Business Development

Model fit

GPT-4.1

Author

PromptJoy Community

Author role

Community contributor

Origin

PromptJoy community submission

Published

Apr 7, 2026

Copy, save, and vote
Copy works on this curated prompt now. Its visible copy count updates on this device, and signed-in users can also save or vote here while the shared library fills in.

Copies the full prompt body so you can use it immediately in your model of choice.

Visible copy count on this device: 318

Current vote signal: +111

Sign in to save or vote on this curated prompt. Your state will stay on this device for your signed-in account while the shared library fills in.

What happens here

Copy keeps the prompt body exact and updates the visible count on this device. Save and vote also work on this curated prompt for signed-in users until the shared public library is live.

Live trust breakdown

Task clarity

78

+18 names the role the model should play

Input contract

22

+12 uses bullets to separate input fields or context

Output contract

52

+18 defines what the model should return

Guardrails

20

+12 sets quality constraints for the response

Safety

100

+12 does not request secrets or sensitive identifiers

Reusability

44

+12 separates context, output, and rules into readable blocks

Community signal

57

+24 strong positive vote ratio

Remix into your draft

Trust score

54

Vote signal

+111

Saves

93

Copies

318

Trust score breakdown
A rubric-based quality score with visible evidence and improvement opportunities. No LLM API is used to produce these numbers.

Task clarity

Checks whether the prompt clearly names the role, task, and workflow it is meant to support.

78

Evidence

  • +18 names the role the model should play
  • +18 states the job the prompt is meant to do
  • +14 title describes the use case rather than a generic label
  • +10 has task-oriented tags

Improve

  • No obvious improvement flagged.

Input contract

Checks whether the prompt tells the user what context, data, or materials to provide.

22

Evidence

  • +12 uses bullets to separate input fields or context

Improve

  • List the inputs the user should provide before running the prompt.
  • Ask for the goal, audience, or situation behind the request.
Prompt body
Written by PromptJoy Community for business development work on GPT-4.1, with attribution preserved on the detail page.
sales
email
follow-up
You are helping me write a strong post-call follow-up email after a discovery or demo call.

I will give you:
- who the buyer is
- what matters to them
- the pain they described
- objections or hesitation that came up
- the next step I want

Write:
1. a concise follow-up email
2. a shorter version for a busy buyer
3. one alternate CTA if the buyer went quiet
Public detail stays open, but save and vote still require sign-in
This page stays public for browsing and copying. When you sign in, the save and vote controls on this curated prompt stay available on this device without moving the public prompt library behind auth.
Create account to saveLog in to saveSign up to remixLog in to remix

Output contract

Rewards prompts that define the shape, order, and priority of the answer.

52

Evidence

  • +18 defines what the model should return
  • +22 uses a multi-part output format

Improve

  • Say how the answer should be organized or prioritized.

Guardrails

Looks for constraints that reduce generic answers, unsupported assumptions, and avoidable cleanup.

20

Evidence

  • +12 sets quality constraints for the response

Improve

  • Add rules that prevent generic or unwanted output.
  • Tell the model how to handle missing evidence or uncertainty.

Safety

Checks for sensitive-data exposure, harmful misuse language, and whether the prompt sets safe-use boundaries.

100

Evidence

  • +12 does not request secrets or sensitive identifiers
  • +10 avoids obvious harmful misuse instructions
  • +8 avoids jailbreak or policy-bypass wording

Improve

  • Add a short safety boundary for sensitive data, authorization, or privacy.

Reusability

Checks whether the prompt is portable, readable, and discoverable enough to reuse.

44

Evidence

  • +12 separates context, output, and rules into readable blocks
  • +10 has enough metadata for discovery and reuse
  • +8 does not depend on private one-off context

Improve

  • Aim for a reusable prompt between roughly 80 and 260 words.

Community signal

Uses copy, save, and vote behavior cautiously, with low confidence until enough activity exists.

57

Evidence

  • +24 strong positive vote ratio
  • +11 saved 93 times
  • +12 copied 318 times
  • +10 based on 536 total interactions

Improve

  • No obvious improvement flagged.