Request a prompt · Member roadmap

You’re closing the deals.
You should shape the library.

Tell us the sales scenario you wish a tested prompt existed for. We read every request, surface the most-asked, and ship them — with your name on the credit line.

I asked for a prompt that handles “we’re already evaluating Salesforce.” Three weeks later it shipped — with my name on it. Now it’s the second-most-run objection prompt in the library.
Rohan MehtaAE · Brightpath
request → ship · Mar 2026

Submit a prompt request.

Five fields. Three minutes. The more specific the scenario, the more likely it ships.

Auto-saved11:47 · just now
01Name the scenarioRequired

A short, plain-English title — like you’d Slack it to a teammate. Skip jargon.

e.g. Re-engaging a champion who’s gone silent for 3+ weeks
Be specific. “Cold email” is too broad — “Cold email to a CFO at a company that just IPO’d” is right.0 / 90
02Where in the deal does this hit?Required

Pick the stage. Multiple is fine if it spans phases.

Prospecting· 74Outreach· 98Discovery· 62Demo prep· 31Objection handling· 45Proposal· 22Negotiation· 18Closing· 14Post-sale / renewal· 29
03Describe the exact scenarioRequired

What’s the situation, who’s involved, and what outcome do you need? The more real detail, the better.

e.g. My champion just left the account. The new contact is unknown to me, procurement is suddenly involved, and we have a verbal from 6 weeks ago that’s going cold. I need a re-engagement prompt that acknowledges the change without sounding desperate.
Include deal specifics: who, what, why it’s hard, what “good” looks like.0 / 600
What makes a request ship faster
  • Name the specific persona you’re selling to
  • Explain why existing prompts don’t cover it
  • Describe what the AI output should look like
04How often would you run this?

Helps us prioritize high-frequency scenarios. No wrong answer.

Daily
Multiple times a week or more
Weekly
A few times a month
Situational
When the scenario comes up
05Credit line (optional)

If it ships, your name and role go on the prompt. Leave blank to stay anonymous.

Your name
Role · Company
Ready to submit? We review every request within 48 hours.
Save draft
Submit request →

How it works

1
Submit the scenario
Five fields, three minutes. Be specific — it triples your shipping odds.
You are here
2
We read every request
The team reviews weekly. Dupes get merged and votes combined.
Usually within 48 hrs
3
High-voted ones go to drafting
14+ votes and a clear scenario = drafted. You get a notif when it moves.
No timeline guarantee
4
Field test → ship
10 reps run it live before it goes into the library. Median: 19 days.
Your name goes on it

Recent requests

View all →
Objection·Community2 days ago
“Build vs buy” rebuttal that doesn’t sound defensive
CFO is always asking why we shouldn’t just hire an engineer to build this internally…
31
In drafting
Outreach·Pro member5 days ago
CFO cold outreach after a missed earnings call
Company just missed Q1 by 12%. CFO is under pressure. How do you open?
14
In queue
Renewal·Pro member1 week ago
Champion reactivation after 90-day silence
They went cold. CRM shows last touch in January. Nothing since.
8
Under review

Top contributors

RM
Rohan Mehta
AE · Brightpath
7
SK
Sarah Kim
SDR · Northwind
5
JT
Javier Torres
CSM · Acmecloud
4
LP
Layla Patel
Enterprise AE
3
Shipped from requests

Your requests.
In the library.

These three prompts started as submissions from members. They’re now among the most-run in the library.

Objection · Shipped Apr 17

“Already evaluated Salesforce” rebuttal

Four-step reframe for the most-cited objection in enterprise SaaS. Outputs a 90-second talk track built around the specific competitor named.

Requested by Rohan Mehta · AE, Brightpath
Mar 29 → Apr 17 · 19 days request to ship
2,104 runs · Score 4.5Open prompt →
Renewal · Shipped Apr 28

The silent reactivation play

Three-touch sequence for accounts that stopped engaging without churning. Pulls last six months of CRM activity to find the warmest re-entry angle.

Requested by Javier Torres · CSM, Acmecloud
Apr 6 → Apr 28 · 22 days request to ship
318 runs · Score 4.3Open workflow →
Discovery · Shipped Apr 03

Pre-call brief for an unknown account

For when an inbound lead lands on your calendar with 12 hours’ notice. Pulls the company, the prospect, and three plausible pain points before the call.

Requested by Sarah Kim · SDR, Northwind
Mar 14 → Apr 03 · 20 days request to ship
1,204 runs · Score 4.7Open workflow →
The roadmap, in public

Where every request actually is.

No black box. Every request you submit moves through these four columns.

In queue

38
CFO outreach after a missed earnings call
Outreach · 14 votes
Multi-year prepay vs Q4 budget freeze
Closing · 4 votes
Voicemail script for a procurement gatekeeper
Outreach · 6 votes
Cold email to a stealth-mode startup
Outreach · 3 votes

Drafting

9
“Build vs buy” rebuttal that doesn’t sound defensive
Objection · 31 votes
Discovery question chain for a champion turnover
Discovery · 12 votes
Re-engage after a 90-day “not now”
Outreach · 8 votes

Field test

11
Multi-thread plan when champion is junior
Discovery · day 4 of 10
PG&A push when buyer wants procurement
Negotiation · day 7 of 10
Renewal expansion against flat budget
Renewal · day 2 of 10

Shipped this month

9
“Already evaluated Salesforce” rebuttal
Objection · 4.5 score
Silent reactivation play (CSM)
Renewal · 4.3 score
Pre-call brief for unknown account
Discovery · 4.7 score
Procurement-gatekeeper bypass email
Outreach · 4.1 score
Common questions

About requests.

The most-asked questions from the first 400 submissions. If yours isn’t covered, drop us a line on the contact page.

Will every request get built?

No. About one in three ships. The rest either get folded into an existing workflow, fail field test, or aren’t a fit for the library (e.g. coaching scripts, marketing copy). You’ll get an email either way.

How long does it take?

Median is 19 days from submission to live. The fastest was 6 days (a heavily-duped objection rebuttal that jumped the queue). The slowest in our books is still in field test on day 41.

What if I don’t want my name on it?

Leave the submitter fields blank. The credit line will read “Requested by a Promptifi member.” We’ll still email you when it ships if you toggled that on.

Can I request a prompt that’s already in the library but better?

Yes — and we love these. Tag the existing workflow in your description and tell us what’s missing. Half of our v2 prompts started this way.

Submit a request

Tell us what you need.

Five fields. The more specific the scenario, the more likely it ships.

Short, plain-English title. Be specific — not just "cold email" but "cold email to a CFO at a company that just IPO'd".

The more real detail, the better. Vague requests rarely ship.

Credit line (optional)

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.