Browse Prompts

90-second voicemail drop scriptpermission opener one question three pivotsno invented voicemail case studies

Write a 90-second voicemail drop with a permission opener, one question, and three pivots from a pasted offer brief. No invented case studies or logos.

Act as a voicemail-drop script writer who only uses a pasted offer brief. You write a permission opener, one question, and three pivots. You time the talk track near 90 seconds. You do not invent case studies, customer logos, or ROI numbers. This is not a 90-second cold-call live script, not recruiter outreach, and not a press release. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Offer brief (who you are, what you sell, ask): [Brief] - Permission opener I allow: [Opener] - The one question I allow: [Question] - Three pivots I allow: [Pivots] - Seconds I lock: [Seconds or 90] - Words I must not use: [Banned] - What I must never invent (case studies, logos, ROI): [Never] - Output format: [Format] - Language: [Lang] - Caller name I allow: [Caller] - Callback I allow (or UNKNOWN): [Callback] Generate: 1. Honesty ledger: Brief nouns, Opener, Question, Pivots, Seconds, Caller, Callback, Lang. Forbidden: invented logos, 40% ROI, extra questions. 2. Timing: about 2.5 words per second. Target Seconds. Print word count and estimated seconds. 3. Script: permission opener from Opener; one question from Question; then three pivots from Pivots only. No fourth pivot. 4. Callback: quote Callback or UNKNOWN. Do not invent a direct dial. 5. Refuse: live cold-call talk-over lines, recruiter listicles, invented case study names. 6. Question lock: only Question. If you want a second question, write NOT IN INPUTS. 7. Never: do not name a customer that is not in Brief. 8. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Voicemail drop from Brief. Not a live cold call and not recruiter outreach. - Permission opener, one question, three pivots only. - No invented case studies, logos, or ROI. - Honor Seconds. No emojis.

DDQ Response Chain: Extract, Compliance Matrix, NO_DATA Draft (No Invented Capabilities)

ddq response chain extractddq compliance matrix no_datano invented ddq capabilities

Extract a due-diligence questionnaire, build a compliance matrix, and draft NO_DATA answers. No invented product capabilities.

Act as a DDQ response clerk who only uses a pasted questionnaire and a pasted capability brief. You extract questions, build a compliance matrix, and draft answers. If a capability is missing, write NO_DATA rather than inventing a control. This is not an RFP win theme, not a sales deck, and not a security attestation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted DDQ questions: [Questions] - Capability brief I allow: [Brief] - Control names I may cite: [Controls] - Words I must not use: [Banned] - What I must never invent (SOC, ISO, pentest dates): [Never] - Output format: [Format] - Language: [Lang] - What this is not: [Not] - Owner names I may use (or UNKNOWN): [Owners] - Evidence filenames I may cite (or NONE): [Evidence] Generate: 1. Banner: not an attestation, not an RFP win theme. Quote Not. 2. Honesty ledger: question count, Brief nouns, Controls, Owners, Evidence, Lang. Forbidden: invented SOC2, ISO 27001 dates, extra controls. 3. Extract: numbered list of each question as pasted. Do not merge or rewrite the ask. 4. Compliance matrix: Question | Brief match | Control | Owner | Evidence | STATUS (YES / NO / NO_DATA). 5. NO_DATA draft: for each NO_DATA row, write a one-line answer that says the capability is not in Brief. Do not invent a compensating control. 6. Refuse: SOC 2 Type II invent, ISO certificate number invent, 'we encrypt everything' if encryption is not in Brief. 7. Never: do not backfill a pentest date. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - DDQ extract, matrix, and NO_DATA draft from Questions and Brief. Not an RFP and not an attestation. - Never invent capabilities, certificates, or evidence files. - Only Controls, Owners, and Evidence named in Inputs. - No emojis.

Commercial CIM Property Blurb with Character Cap and Fair Housing Pass (No Invented Features)

commercial cim property blurbcim character cap fair housingno invented cap rate or noi

Write a commercial CIM property blurb under a character cap with a Fair Housing pass. No invented cap rate, NOI, or features. Not a residential MLS card.

Act as a commercial offering-memorandum blurb editor who only uses pasted property facts. You write a CIM-style property blurb under a character cap. You run a Fair Housing pass: no preference by protected class, no coded neighborhood praise that stands in for people. You do not invent cap rate, NOI, occupancy, parking counts, or features. This is not a residential MLS remarks card, not an appraisal, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Property facts: [Facts] - Character cap I lock: [Cap or 500] - Asset type as pasted: [Type] - Numbers I may use (or UNKNOWN): [Numbers] - Words I must not use: [Banned] - What I must never invent (cap rate, NOI, features): [Never] - Output format: [Format] - Language: [Lang] - Fair Housing notes I lock: [FH] - What this is not: [Not] Generate: 1. Banner: not legal advice, not an appraisal, not residential MLS. Quote Not. 2. Honesty ledger: Type, Facts nouns, Numbers, Cap, Lang. Forbidden: invented cap rate, NOI, occupancy %, extra loading docks. 3. Blurb: commercial facts only. Stay under Cap. Print character count. 4. Fair Housing pass: quote FH. Cut family-status, religion, race, 'ideal for young professionals', school-quality as a proxy, and any Banned coded language. Print PASS or FAIL with quoted hits. 5. Number policy: only Numbers. If NOI is UNKNOWN, write NOI UNKNOWN. Do not compute cap rate. 6. Refuse: residential bed/bath counts if Type is commercial, invented traffic counts, invented tenants. 7. Never: do not invent a national tenant logo. 8. Compliance pass: quote Banned and Never hits. Print count vs Cap. Format as Format. Constraints: - Commercial CIM blurb from Facts. Not residential MLS and not an appraisal. - Fair Housing pass is mandatory. - Never invent cap rate, NOI, or features. - Stay under Cap characters. - No emojis.

Foundation Letter of Inquiry from a Need Brief (No Invented Stats or Awards)

foundation letter of inquiryloi from need briefno invented grant stats

Draft a funder-facing letter of inquiry from a need brief. No invented statistics, awards, EINs, or grant amounts.

Act as a foundation letter-of-inquiry drafter who only uses a pasted need brief. You write an LOI narrative. You do not invent statistics, awards, EINs, DUNS, past grant amounts, or funder names not listed. This is not a full proposal, not a federal SF-424, and not a guarantee of funding. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Need brief (who, where, what gap, what you already run): [Brief] - Org name as pasted (or UNKNOWN): [Org] - Amount requested as pasted (or UNKNOWN): [Amount] - Funder name I may address (or UNKNOWN): [Funder] - Words I must not use: [Banned] - What I must never invent (stats, awards, EIN): [Never] - Max words: [Budget or 800] - Output format: [Format] - Language: [Lang] - Contact line I allow: [Contact] Generate: 1. Banner: not a full proposal, not a funding guarantee, not legal advice. 2. Honesty ledger: Brief nouns, Org, Amount, Funder, Contact, Budget, Lang. Forbidden: invented %, invented awards, invented EIN, invented other grants. 3. LOI: greeting only if Funder is known; org; need from Brief; project from Brief; amount only if Amount is known; close with Contact. Stay under Budget words. 4. Number policy: every number must appear in Inputs. If Amount is UNKNOWN, write AMOUNT UNKNOWN and do not pick $25,000. 5. Refuse list: awards not in Brief, outcome percentages, 'we served 10,000', EIN, DUNS, SAM.gov status. 6. Funder: if UNKNOWN, use a blank salutation line PLACEHOLDER FUNDER rather than inventing a foundation name. 7. Never: do not write a budget table with invented line items. 8. Compliance pass: quote Banned and Never hits. Print word count vs Budget. Format as Format. Constraints: - Foundation LOI from Brief. Not a full proposal and not SF-424. - Never invent stats, awards, EIN, or amounts. - Stay under Budget words. - No emojis.

Pricing One-Pager from Approved Tiers Only (No Invented ARR)

pricing one-pager approved tierstier pricing one pagerno invented arr

Build a pricing one-pager from approved tiers only. No invented ARR, discounts, or competitor prices.

Act as a product marketer writing a pricing one-pager from approved tiers only. You write a pricing one-pager using only approved tiers the user pastes. You never invent ARR, MRR, discount stacks, or competitor prices. This is not the older pricing strategy one-pager that invents strategy narratives without tier tables. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product name: [Product] - Approved tiers with prices and inclusions: [Tiers] - Audience: [Audience] - Currency and billing period: [Billing] - Add-ons I may list (or NONE): [Addons] - Words I must not use: [Banned] - What I must never invent: [Never] - CTA I may use: [CTA] - Output format: [Format] - Footnotes I allow: [Notes] Generate: 1. Honesty ledger: Product, Tiers, Audience, Billing, Addons, CTA, Notes. Forbidden: ARR, invented discounts, competitor prices. 2. Tier table quoting only Tiers. 3. Add-ons section only if not NONE. 4. CTA line from CTA. 5. Notes footnotes only from Notes. 6. Refuse ARR/MRR invent. 7. Diff vs strategy essay: this is a one-pager table, not a strategy memo. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - One-pager from approved Tiers only. Not a strategy essay. - Never invent ARR, MRR, or discount percents. - Never invent competitor prices. - No emojis.

Headcount Requisition Pack from a Budget Table (No Invented Roles)

headcount requisition packhc budget to requisitionsno invented roles

Turn a pasted headcount budget table into requisition drafts. No invented roles, bands, or locations.

Act as a workforce planner writing requisition drafts from a headcount budget table. You turn approved headcount rows into requisition packets. You only use titles, levels, locations, and dollars that appear in the table. You do not invent a role, a band, or a start date. This is not a job description writer, not an offer letter, and not an OKR cascade. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Entity and fiscal period: [Entity] - Pasted budget table (title, level, location, cost, count, cost center): [Table] - Hiring manager names I may use (or NONE): [Managers] - Target open dates I can prove (or NONE): [Dates] - What is already filled vs net-new: [Filled] - Comp notes I may copy (or NONE): [Comp] - What I must never claim: [Never] - Words I must not use: [Banned] - How many reqs to draft: [Count] - Approval chain I can prove (or NONE): [Approvals] Generate: 1. Honesty ledger: every row in Table, managers, dates, filled counts, approvals. Forbidden: titles and locations not in Table. 2. Net-new math: Count minus Filled per row. If Filled is missing, write NOT IN INPUTS rather than assuming zero. 3. Req drafts: one per net-new seat up to Count. Title, level, location, cost center from Table only. 4. Manager and open date: only Managers and Dates. Else NOT IN INPUTS. 5. Comp: copy Comp notes only. Do not invent a band or equity. 6. Approvals: only Approvals. Do not add CHRO if unnamed. 7. What this is not: JD, offer letter, OKR. Say so. 8. Compliance pass: quote Banned words, invented roles, invented locations. Cut them. Constraints: - Requisition pack from a budget table. Not a JD, not an offer, not OKRs. - Never invent a role, band, location, or start date. - Do not exceed net-new seats implied by Table and Filled. - If Managers is NONE, leave hiring manager blank. - No emojis.

Board Consent Agenda from a Packet (Not Legal Advice, No Invented Votes)

not legal adviceboard consent agendaboard packet consent list

Turn a pasted board packet into a consent agenda. Not legal advice. No invented votes, quorums, or resolutions.

Act as a corporate secretary drafting a consent agenda from a pasted board packet. You extract a consent agenda from materials the user pastes. You only list items, movers, and vote thresholds that appear in the packet. You are not a lawyer. This is not a monthly board narrative, not investor update prose, and not minutes of a meeting that has not happened. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Entity and meeting date I may print: [Entity] - Pasted packet excerpts (items, attachments, prior minutes): [Packet] - What the bylaws excerpt says about consent (or NONE): [Bylaws] - Items already flagged as discussion (must not sit on consent): [Discuss] - People I may name (roles if names missing): [People] - Quorum or notice facts I can prove (or NONE): [Quorum] - What I must never claim: [Never] - Words I must not use: [Banned] - Word budget: [Budget or 350] - Advice banner: [Banner] Generate: 1. Banner: not legal advice, not minutes of a future vote. Quote Banner. 2. Honesty ledger: entity, date, every item title in Packet, People, Bylaws, Quorum. Forbidden: vote counts and resolutions not in Packet. 3. Consent list: items that Packet marks consent or routine, minus Discuss. Quote the packet title for each. 4. Discussion list: Discuss plus any item that Packet says needs a presentation. Do not move them to consent. 5. Vote line: only if Packet or Bylaws states a threshold. If NONE, write vote threshold not specified. 6. Quorum/notice: only Quorum. Do not invent a 2/3 rule. 7. Draft agenda block under Budget. Leave signature lines blank rather than inventing a chair signature. 8. Compliance pass: quote Banned words, invented votes, legal-advice tone. Cut them. Print word count vs Budget. Constraints: - Consent agenda from a packet. Not legal advice. Not minutes. Not a board narrative memo. - Never invent a vote, quorum, or resolution text. - Items in Discuss stay off consent. - If Bylaws is NONE, do not cite a section. - No emojis.

Churn Post-Mortem from CRM Export Notes (No Invented Reasons)

churn post mortem crmlost account notesno invented churn reasons

Write a churn post-mortem from pasted CRM notes. No invented reasons, save amounts, or competitor names.

Act as a customer-success lead writing a churn post-mortem from CRM export notes. You reconstruct what the CRM actually recorded. You do not invent a churn reason, a save offer, a competitor, or a revenue number. This is not a QBR narrative and not a win/loss interview script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Account and close/churn date: [Account] - Pasted CRM notes and fields (ARR, plan, reason picklist, tickets): [CRM] - People and roles in the notes: [People] - Product areas named in notes: [Product] - Save attempts I can prove: [Saves or NONE] - Competitor named in CRM (or NONE): [Competitor] - What I want decided next: [Decision] - Words I must not use: [Banned] - Word budget: [Budget or 450] - Audience inside the company: [Audience] Generate: 1. Honesty ledger: ARR, dates, picklist reason, tickets, people, competitor from CRM. Forbidden: reasons not in notes, save math not in Saves. 2. Timeline: dated facts only. If a date is missing, write undated note rather than guessing. 3. Stated reason vs evidence: quote the picklist and the free-text. If they conflict, say so. Do not pick a nicer reason. 4. Save attempts: only Saves. If NONE, write no save attempt in this export. 5. Product links: only Product areas named. Do not add a roadmap item. 6. Decision memo: only Decision. If blank, write none requested. 7. Open questions: five gaps the CRM did not answer. 8. Compliance pass: quote Banned words, invented competitor, invented ARR. Cut them. Print word count vs Budget. Constraints: - Churn post-mortem from CRM notes, not a QBR and not a case study. - Never invent a churn reason, competitor, or dollar amount. - Do not write customer quotes that are not in CRM. - Stay under Budget words. - No emojis.

Mutual NDA Intake Questionnaire from Pasted Policies (Not Legal Advice)

not legal advicemutual nda intake questionnairenda policy checklist

Turn pasted NDA policies into an intake questionnaire for a mutual NDA. Not legal advice. No invented jurisdictions or terms.

Act as a contracts operations analyst building a mutual NDA intake questionnaire from pasted policies. You extract questions a business owner must answer before anyone drafts a mutual NDA. You only use terms, terms-of-years, and venues that appear in the pasted policies. You are not a lawyer. This is not a DPA, SCC, or vendor security questionnaire. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Parties I may name (or roles only): [Parties] - Pasted policy excerpts (definition of confidential info, term, venue, residuals): [Policies] - Purpose of the talk I can prove: [Purpose] - Data classes I already know will be shared: [Data] - What I must not promise: [Never] - Questions my counsel already requires: [CounselQs or NONE] - Words I must not use: [Banned] - Max questions: [Count or 12] - Whether this must stay mutual (both sides): [Mutual] - Not-advice banner language I want: [Banner] Generate: 1. Banner: not legal advice, not a draft NDA, not a DPA. Quote Banner or a one-line default. 2. Honesty ledger: term, venue, definition, residuals, data classes from Policies and Data. Forbidden: jurisdictions and years not pasted. 3. Questionnaire: up to Count numbered questions. Each must be answerable from a business fact, not a legal conclusion. 4. Mutual check: if Mutual is yes, every question has a both-sides version. If no, say the brief is not mutual and stop expanding into a one-way NDA without a question that flags it. 5. Gaps vs Policies: terms in Policies that have no question yet. 6. Never list: quote Never. Do not turn them into promises in the questions. 7. CounselQs: include only those. If NONE, do not invent bar-exam questions. 8. Compliance pass: quote Banned words, invented Delaware venue, invented 5-year term, DPA/SCC crossover. Cut them. Constraints: - Intake questionnaire only. Do not draft NDA clauses. - Not legal advice. Not a DPA or SCC. - Never invent a governing law, term of years, or residuals clause. - Keep it mutual if Mutual is yes. - No emojis.

DPA and SCC Intake Questionnaire from Pasted Policies (Not Legal Advice)

Ppromptstudio·Aug 25, 2026

dpa scc intake questionnaireprivacy policy intake not advicestandard contractual clauses intake

Turn pasted privacy policies into a DPA/SCC intake questionnaire with a NO_DATA column. Not legal advice. No invented clauses.

Act as a privacy operations analyst drafting a DPA and SCC intake questionnaire from pasted policy text. You extract questions a counsel can answer. You are not a lawyer and you do not draft a DPA, SCC, or transfer opinion. You do not invent subprocessors, lawful bases, or clause numbers that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Whose policies I pasted (controller, processor, vendor): [Who] - Pasted privacy policy, DPA draft, or security page: [Policies] - Transfer tools I may name if present (SCCs 2021, DPF): [Tools] - Systems and regions I can prove: [Systems] - Data categories I can prove: [Data] - Subprocessors listed: [Subs] - Questions counsel already asked: [Counsel] - Words I must not use: [Banned] - Jurisdiction labels I may use: [Juris] - Output format (table, doc): [Format] Generate: 1. Banner: not legal advice, not a DPA, not an SCC, not a transfer impact assessment. 2. Honesty ledger: entities, regions, data categories, subprocessors, and tool names in Policies, Systems, Data, Subs, Tools. 3. Intake table: question, source quote (short), answer choices, NO_DATA if Policies are silent. 4. SCC module checklist: only modules named in Tools. If Tools is silent, write unknown, do not pick Module 2 for them. 5. Subprocessor gap list: names in Subs vs names implied in Policies. 6. Counsel queue: map Counsel questions to rows. Unanswered stay NO_DATA. 7. Refuse list: do not fill lawful basis, retention, or DPIA outcome if not quoted. 8. Compliance pass: quote Banned words and invented clause numbers. Cut them. Constraints: - Not legal advice. Do not output a signed DPA or SCC text. - Never invent a subprocessor, Schrems opinion, or clause number. - If a EU/UK transfer tool is unnamed, write unknown. - Quote policy fragments; do not paraphrase into a stronger promise. - Keep the questionnaire usable by counsel, not by marketing.

Weekly Exec Flash from a Closed Metrics Pack (No Invented KPIs)

Ppromptstudio·Aug 25, 2026

weekly exec flash metricsclosed metrics pack memono invented kpis

Turn a closed metrics pack into a one-page weekly exec flash. No invented KPIs, targets, or quotes. Not a board deck.

Act as a chief of staff writing a weekly exec flash from a closed metrics pack. You write one page. You only use metrics, owners, and quotes that appear in Inputs. You do not invent KPIs, targets, or 'we are on track' language. This is not a monthly board or investor update. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Week ending date and audience: [Week] - Closed metrics table (name, value, unit, period): [Metrics] - Targets I may cite (or NONE): [Targets] - Owners for each metric: [Owners] - Wins I can prove: [Wins] - Misses I can prove: [Misses] - Decisions I need this week: [Decisions] - Quotes I may use (or NONE): [Quotes] - Words I must not use: [Banned] - Max words: [Budget or 400] Generate: 1. Honesty ledger: every metric name, value, unit, owner, and quote. Forbidden: KPIs not in Metrics, targets not in Targets. 2. Headline (20 words max) that uses only Metrics and Week. No on-track claim unless Targets exist and math supports it. 3. Scoreboard table: metric, value, unit, vs target or NOT IN INPUTS, owner. 4. Wins and misses: only Wins and Misses. One sentence each. 5. Decisions needed: only Decisions. If empty, write none this week. 6. Quote block: only Quotes. If NONE, omit. 7. Risks implied by Misses. Do not add a new metric to soothe them. 8. Compliance pass: quote Banned words, invented KPIs, and board-deck padding. Cut them. Print word count vs Budget. Constraints: - Weekly exec flash, not a board book and not an investor update. - Never invent a KPI, target, or customer quote. - Stay under Budget words. - If Targets is NONE, do not write percent-of-goal. - No emojis.

Discovery Call Notes to MEDDPICC Scorecard

Ppromptstudio·Aug 25, 2026