Browse Prompts
246 prompts available in business · Page 20 of 21
Vendor Security Questionnaire from Pasted Policies
Answer or draft questionnaire only from pasted policies; NO_DATA otherwise.
Act as a security GRC analyst. Answer or draft questionnaire only from pasted policies; NO_DATA otherwise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Company context: [Context] - Source notes / paste: [Notes] - Approved numbers only: [Metrics] - Audience: [Audience] - Tone: [Tone] - Legal / compliance notes: [Compliance] Generate: 1. Source map quoting Notes/Metrics. 2. Main deliverable. 3. NO_DATA list for missing numbers. 4. Risks / compliance. 5. Next questions with owners unassigned if unknown. 6. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Vendor Security Questionnaire from Pasted Policies
Partnership Renewal Memo from Contract Notes
Turn contract notes into a partnership renewal memo with open terms, risks, and NO_DATA instead of invented concessions.
Act as a partnerships lead writing an internal renewal memo. Use only the contract notes and performance facts provided. Do not invent a discount, a legal conclusion, or a board resolution. This is not an OKR cascade, not a pricing one-pager, and not a JD. Inputs: - Partner and term: [Partner, end date] - What the contract actually says (paste notes): [Notes] - Performance we can prove: [Perf] - What we want next term: [Want] - What they have asked: [They] - Legal review status: [Not advice / counsel already flagged X] - Audience: [CEO, board packet, partner-success] Generate: 1. Status: end date, auto-renew or notice window. If Notes lack it, NO_DATA and STOP on that line. 2. What worked / what did not: only Perf. 3. Open terms table: clause, current, we want, they asked, gap. No invented numbers. 4. Risk: operational and commercial. If counsel flagged something, quote it as their flag, not your legal opinion. 5. Recommended ask (3 bullets) plus a walk-away line. Not a vote. 6. Email-ready summary (120 words) for the partner, still not a legal instrument. 7. Not in scope: new OKRs, new job descriptions, price list redesign. Constraints: - Not legal advice. Do not redline a statute. - Do not name a renewal percent that is not in Inputs. - Distinct from a monthly board/investor update.
90-Second Cold Call Script with Objection Pivots
Write a 90-second cold call with a permission opener, one question, and three objection pivots. Timed talk track, no fake mutual friends.
Act as a sales coach writing a 90-second cold call. Permission opener, one question, one ask. Not a full email sequence, not a partnership memo, not a voice-agent barge-in script. Inputs: - Us: [Company, product] - Them: [Title, company type] - Public trigger: [Trigger with source] - Proof I can say aloud: [Proof] - Ask: [Meeting length] - Objections I actually hear: [List] - Compliance: [Do-not-call, recording, banned claims] - Tone: [Tone] Generate: 1. Talk-time map: seconds per block totaling 90. If it does not fit, cut. 2. Opener (permission, 15s): who you are, why this call, ask to continue. No fake referral unless Inputs name a person. 3. Trigger + proof (30s): one public fact, one proof. No stacked features. 4. One question (15s) and the Ask (15s). 5. Three objection pivots (15s each as optional branches, not added to the 90 if unused): from their List only. 6. Leave-behind voicemail (20s) if no pick-up. No "I just wanted to touch base." 7. Compliance: recording disclosure if required; banned claims cut; no invented titles. Constraints: - Do not write a 5-email campaign. - Do not invent ROI percents. - Honor Do-not-call notes.
RFP Extract to Compliance Matrix and NO_DATA Draft
Extract RFP shall-statements into a compliance matrix and a NO_DATA draft so you do not hallucinate answers.
Act as a proposal operations lead. Extract an RFP into a compliance matrix, then draft only where the user's facts exist. Use NO_DATA instead of guessing. This is not a pricing one-pager and not a full grant narrative. Inputs: - RFP text or section paste: [Paste] - Our facts we can prove: [Facts] - What we will not bid: [Out] - Page or word limits: [Limits] - Required headings: [Headings] - Past performance I may name: [Past, with permission] Generate: 1. Shall/should inventory: quote each requirement, page/section if present, MUST/SHOULD. 2. Compliance matrix: Req ID, quote, response (COMPLY / PARTIAL / NO_DATA / OUT), fact pointer, owner blank. 3. Conflict list: requirements that fight each other, or fight Out. 4. Draft: only COMPLY rows, under Limits, with Facts in-line. PARTIAL gets a question, not a fake yes. 5. NO_DATA pack: a list of questions to the capture lead. Do not fill with industry filler. 6. Past performance: only from Past. If none, skip. Constraints: - Never invent a certification, SOC 2, or insurance limit. - Do not write a price. - Quote the RFP; do not paraphrase away a shall.
Grant Proposal Narrative with No Invented Stats
Draft a funder-aligned grant narrative from your notes with SMART objectives and NO_DATA where numbers are missing.
Act as a grant writer. Draft a narrative from the user's notes. Do not invent beneficiaries, outcomes, or dollars. Align to the funder language they pasted. This is not a press release or a case study. Inputs: - Funder and opportunity: [Funder] - Word or page cap: [Cap] - Need statement notes: [Need] - What we already do: [Program] - Numbers I can prove (with source): [Proof] - Budget story I can tell: [Budget] - Partners who have agreed: [Partners] - What I must not claim: [Banned] Generate: 1. Gap list: every number in Need that is not in Proof. Mark NO_DATA. Do not fill with national averages unless Proof includes them. 2. Outline mapped to the funder's requested headings. If they did not paste headings, use Need, Approach, Objectives, Capacity, Budget story. 3. SMART objectives (3): only from Proof or from program design that does not require a fake baseline. If baseline is missing, write NEED BASELINE. 4. Narrative draft within Cap. Cite Proof in-line as (source, year). No fake evaluations. 5. Budget story: dollars only from Budget. No padding. 6. Refusal log: invented stats, unnamed celebrities, guaranteed outcomes. Constraints: - No invented census tracts or disease rates. - Partners only if they have agreed in Inputs. - Not a full application package (no forms).
Fair Housing MLS Listing Description (Agent-Side)
Write an agent-side MLS description with character counts and a Fair Housing banned-phrase pass, distinct from a tenant rental listing.
Act as a listing copywriter for an MLS agent remarks field. This is agent-side sale or lease listing copy, not the Honest Rental Listing writer for a landlord's Craigslist post. Enforce Fair Housing. Do not invent square footage, schools, crime, or "safe" neighborhoods. Inputs: - Property type and address area: [Type, city, no steering] - Facts from the data sheet: [Beds, baths, sqft if measured, HOA, year] - What I personally verified: [Verified] - What I have not verified: [Unverified] - MLS character cap: [Public remarks cap] - Brokerage compliance notes: [Notes] - Photos I can truthfully describe: [Photos] Generate: 1. Banned-phrase check: list Fair Housing risk words I will not use (family-friendly, perfect for singles, walking distance to church, safe, exclusive, able-bodied, no kids, great for empty nesters, coded race/religion/national origin). Scan Inputs and quote any hits. 2. Public remarks: within cap, print count. Facts only. No school ratings. No crime. No buyer profile. 3. Agent-only remarks: logistics (lockbox, occupancy) without steering. 4. Feature bullets (6) tied to Verified. Unverified gets "ASSESSOR / UNVERIFIED" or is dropped. 5. Photo captions (5) matching Photos. No people as selling points. 6. Compliance rewrite: if I had to cut a line, show before/after. Constraints: - Fair Housing is a hard pass. When unsure, cut. - Distinct from tenant-facing rental ads. - No invented sqft or tax amounts.
Monthly Board and Investor Update Memo
Write a tight monthly board or investor update: numbers, narrative, misses, cash, asks, and risks. No vanity charts and no invented metrics.
Act as a founder who writes board memos that get read on a phone. Lead with numbers, then the story, then the ask. Separate fact from judgment. Do not invent metrics, customers, or runway. Inputs: - Company: [Name, one-line] - Period: [Month and year] - Audience: [Board / angels / lead investor] - Headline numbers: [ARR or revenue, MoM, cash, runway, burn, headcount] - Wins: [Shipped, closed, hired] - Misses: [Pipeline, product, hiring, churn] - Pipeline and customers: [Named only if real] - Product: [Shipped and next] - Team: [Hires, opens, regrets] - Cash and fundraising: [Bank, runway, round status] - Asks: [Intros, decisions, hiring help] - Tone: [Direct / calm / urgent] Generate: 1. Subject line and 4-bullet snapshot a busy director can screenshot. 2. Narrative: 10-14 sentences. What actually changed this month. One thing that surprised you. One thing you were wrong about. 3. Metrics table: Only numbers from Inputs. Columns: metric, this period, prior, notes. If a number is missing, "unknown, need [source]." No fake NPS, TAM, or "coverage 3x" unless provided. 4. Wins: 3-6, each with a so-what. 5. Misses and recovery: 3-6. Cause, owner, date of the next proof point. No blame theater. 6. Product and GTM: What shipped. What is next. One customer quote only if it was in Inputs, otherwise skip quotes. 7. Team: Hires, open seats, one people risk if real. 8. Cash: Months of runway math using only given burn and cash. Fundraising status in one paragraph. No invented term sheets. 9. Risks: Table of 4-6: risk, likelihood (judgment), impact, mitigation, trigger to email the board early. 10. Asks: Numbered, specific, easy to forward. Each ask has a one-line blurb the investor can paste. 11. Appendix plan: 3 items you will put in a data room or follow-up, not in the email. Constraints: - No em dashes. No "we are excited to share." No hockey-stick adjectives. - Do not invent logos, quotes, or pipeline dollars. - If cash or burn is missing, refuse to state runway. Write "cannot compute." - Length: the body should be readable in 4 minutes. Short sentences. - Write for a director who remembers last month and will notice a restated number.
Strategic Partnership One-Pager and Deal Outline
Draft a partnership one-pager: why us, why them, value exchange, integration sketch, commercial options, 30-day next steps, and kill criteria.
Act as a business-development lead who has closed and killed partnerships. Write a one-pager a CEO can read before a partner meeting. Be explicit about who sells, who builds, who owns the customer, and what would make you walk. Inputs: - Us: [Company, product, stage] - Them: [Company, product, why they matter] - Relationship now: [Cold / intro / existing vendor / competitor-adjacent] - Goal: [Distribution, product, co-sell, data, brand] - What we can offer: [API, audience, pipeline, brand, engineering] - What we want: [List] - Economics I know: [Rev share, referral fee, or unknown] - Integration reality: [Build weeks, systems, security] - Risks I already see: [List] - Decision date: [When we need a yes/no] Generate: 1. Why this partner, why now: 8-12 sentences. The customer job that neither of us finishes alone. Why not build vs. buy vs. partner. Why this firm rather than a generic category. 2. Value exchange table: We give / they give / customer gets. Three rows minimum. Flag any row that is a favor, not a business. 3. Motion: Co-sell, referral, embed, OEM, or marketplace. Who owns the logo. Who owns support. Who owns pricing to the end customer. Channel conflict with our own sales. 4. Integration sketch: v1 scope (4-8 bullets). Out of scope. Security and data-flow one paragraph. Build estimate as a range only if Integration reality supports it. Otherwise "unknown, need eng." 5. Commercial options: 2-3 structures (referral, rev share, embed fee). For each: who bills, when money moves, a sample math using only numbers in Inputs. If Economics I know is unknown, give structure with blanks, not invented percents presented as market truth. 6. 30-day plan: 6 dated moves. Owner on our side. Ask on their side. A single success metric for day 30 that is not "good energy." 7. Kill criteria: 5 explicit walk-away lines (exclusivity, build cost, logo ownership, security, timeline). A "slow no" pattern to watch. 8. Meeting brief: 8 bullets for our CEO. 5 questions to ask them. 3 things we will not promise in the room. Constraints: - Do not invent their revenue, headcount, or a named exec unless it was in Inputs. - Do not invent legal positions or exclusivity norms. - No em dashes. No "win-win ecosystem" filler. - If they are competitor-adjacent, dedicate a paragraph to how this does not leak roadmap. - Write for a general counsel who will ask who owns the customer when it breaks.
Pricing Strategy One-Pager for Product Teams
Build a pricing one-pager: packaging, fences, willingness-to-pay logic, experiments, and kill criteria. No invented competitor prices.
Act as a pricing lead who has shipped packaging changes at a B2B company. Write a one-pager a founder, PM, and finance lead can argue over in 30 minutes. Separate facts in Inputs from judgment. Do not invent competitor price points. Inputs: - Product: [What you sell and to whom] - Current price and packaging: [Plans, meters, discounts] - Cost to serve: [COGS or gross margin if known] - Customer segments: [SMB / mid / enterprise, jobs] - Value metric I suspect: [Seat, usage, outcome, or unknown] - Competitor prices I actually know: [Paste only real numbers, or "none"] - Goal of this change: [Revenue, adoption, mix, simple] - Constraints: [Contracts in flight, grandfathering, sales motion, legal] - Evidence I have: [Win-loss, WTP interviews, expansion data, or none] Generate: 1. Situation: 6-10 sentences. What the current packaging trains customers to do (good and bad). What Goal of this change actually requires. 2. Value metric: Recommend one primary meter. Why not the runners-up. How it maps to buyer ROI in one sentence. If Evidence I have is none, label the pick as a hypothesis. 3. Packaging: 2-4 packages (or a pure usage sketch). For each: who it is for, what is in, the fence that stops self-selecting down, list vs. ask price, and the expansion path. Include a free or trial rule if relevant. 4. Fence table: Feature, limit, or service fences. Which fence protects which package. Which fence is a trap (hurts expansion or trust). 5. Price architecture: Starter, mid, top. Discount policy (floor, who can break it). Grandfathering rule. Enterprise overlay (SSO, SLA, vendor review) as adders, not a mystery fourth plan if that is cleaner. 6. Unit economics: If Cost to serve is present, contribution by package. If missing, list the 3 cost questions finance must answer before a raise. 7. Experiments: 3 tests you can run in 60 days. Hypothesis, sample, primary metric, guardrail, kill/keep rule. No fake statistical power claims. 8. Risks and narrative: 5 risks (churn, sales revolt, usage-spike bills, fairness). A 120-word customer email draft for the change. A 40-word sales talk track. Constraints: - If Competitor prices I actually know is "none," do not invent a grid of rival SKUs. - Do not invent WTP dollars. Ranges must be labeled GUESS unless Evidence I have includes them. - No em dashes. One page of substance, not a pricing TED talk. - Ban: "premium feel," "value-based magic," vanity three-tier just because others have three. - Write for a CRO who will ask who loses and who we are willing to lose.
Company OKR Cascade and KPI Tree Builder
Turn annual goals into a company OKR set, a team cascade, and a KPI tree with leading indicators, lagging outcomes, and anti-metrics.
Act as a chief of staff who has run OKR cycles at a growth-stage company. Build a cascade a leadership team can debate in one meeting. Outcomes over activity. Do not invent a number that was not in Inputs. Inputs: - Company: [Name, stage, headcount, what you sell] - Time horizon: [Quarter / half / year and dates] - Company outcomes I already want: [ARR, NRR, logos, NPS, or other] - Current baseline: [Numbers as of now] - Teams in the cascade: [List] - Strategy bets: [3 or fewer] - Constraints: [Cash, hiring freeze, regulated, platform rewrite] - What failed last cycle: [Missed OKRs or vanity KPIs] - Audience for the doc: [Exec / all-hands / board] Generate: 1. Diagnosis: 8-12 sentences. What the baseline actually says. What last cycle rewarded that we should stop. What is still unknown. 2. Company OKRs (3-5 objectives): Each objective in 6-12 words, outcome language. 2-4 key results each. Every KR is a number, a date, and an owner role. No "launch X" as a KR unless launch is defined as a user or revenue outcome. 3. KPI tree: One north-star. One level of input metrics (leading). One level of output metrics (lagging). For each node: definition, formula, source system, cadence, owner. Mark proxy vs. true measure. 4. Team cascade: For each team in Inputs, 1-2 objectives that roll up. Show the trace: team KR -> company KR. Call out any team with no line of sight (that is a design bug). 5. Anti-metrics: 5 things we will not optimize, and the damage if we did. Include at least one that last cycle got wrong if What failed last cycle is filled. 6. Scoring rules: How we score 0.0-1.0. What 0.7 means. When we rewrite vs. grit through. Mid-cycle check date. 7. Dashboard sketch: Weekly vs monthly vs quarterly views. Red/yellow/green rules that do not hide mix shifts (example: ARPU up while logos down). 8. Risks: Sandbagging, KR count bloat, team local optima. A 1-page all-hands version in 6 bullets. Constraints: - If a baseline is missing, write "unknown, need [source]" and do not invent ARR, NRR, or headcount. - Do not use em dashes. Named sections. Short sentences. - No more than 5 company objectives. No more than 4 KRs per objective. - Ban: "synergy," "world-class," "delight," KRs that are tasks in disguise. - Write for a CFO who will ask "so what" after every number.
Job Description and Hiring Scorecard Writer
Turn a messy role brief into an EEO-safe job description, a scored hiring scorecard, and a structured interview loop hiring managers can run this week.
Act as a senior talent partner sitting with a hiring manager. Write a job description people can self-select against, plus a scorecard that interviewers will actually fill in. Outcomes over task lists. Do not invent market salary data or legal advice. Inputs: - Role title: [Title] - Team and reporting line: [Team, manager] - Company: [Name, stage or size, what you sell] - Seniority: [IC / lead / manager and years] - Location and work mode: [City / remote / hybrid days] - Compensation: [Band if known, currency, equity or bonus notes, or "do not publish"] - Must-haves: [Skills and proof of work] - Nice-to-haves: [List] - 90-day outcomes: [3-5 measurable results] - Anti-profile: [Who this is not for] - Constraints: [Visa, travel, on-call, tools, union, public-sector rules] - Tone: [Direct / warm / academic] Generate: 1. Role one-liner: One sentence a candidate can paste into a search. Who, what, for whom, what "good" looks like in 90 days. 2. Job description: - About the team (5-8 sentences, concrete, no "fast-paced family"). - What you will own in the first 6 months (bullets tied to outcomes, not a tool dump). - How we work (meeting load, decision rights, who you partner with). - Must-haves vs nice-to-haves. Must-haves must be observable in a work sample or interview. No years-of-experience as a hard floor unless legally required. - How we hire (steps, work sample, timeline). - Compensation and location as given. If Compensation is "do not publish," write "Competitive; shared in the first conversation" and stop. Do not invent a band. - Equal opportunity statement: short, real, not a legal novel. 3. Hiring scorecard: 5-7 competencies. For each: definition in one sentence, what "1 / 2 / 3 / 4" looks like with a work example, where in the loop it is tested, weight (% summing to 100). Include one values/judgment competency. Flag any must-have that is a knockout (yes/no, not a 1-4). 4. Interview loop (4-6 steps): Interviewer role, 25-45 min goal, 3 sample questions, what a strong answer cites, a work-sample prompt if relevant. No brainteasers. No "where do you see yourself in 5 years." 5. Sourcing notes: 8 search strings or communities. 5 signal phrases on a resume. 5 anti-signals (not protected-class proxies). 6. Offer narrative: 8-12 sentences a hiring manager can say on the verbal offer: why this person, why this scope, what the first 90 days will feel like. 7. Risk check: Discriminatory or proxy language you removed. Questions interviewers must not ask. Gaps in Inputs that will cause a bad hire if left blank. Constraints: - No em dashes. Short sentences. Named sections. - Do not invent salary surveys, headcount, or visa rules. - Do not use age, family status, nationality, health, or "culture fit" as a scorecard row. Replace culture fit with specific behaviors. - Must-haves cannot be a shopping list of 15 tools. - If 90-day outcomes are missing, invent none. Write "unknown, need hiring manager" and still structure the rest. - Write for a skeptical candidate who has been burned by vague JDs.
Customer Support Reply Playbook (Tone, Policy, Next Step)
Turn a messy ticket into a reply: diagnose, empathize without groveling, policy-safe options, and a clear next step. Includes an internal note.
Act as a support lead writing the reply a tired customer will actually finish reading. Diagnose first. Empathize without groveling. Stay inside policy. Give one next step with a time. Inputs: - Ticket: [Ticket] - Customer: [Customer] - Policy: [Policy] - Tone target: [Tone] - Channel: [Channel] - Severity: [Severity] - What is already true: [Facts] - Must not: [Must not] Generate: 1. Diagnosis: What happened, in causal order. What we know vs. what we must not assume. Which policy clauses apply. What the customer wants vs. what we can do. Risk (chargeback, public post, churn) as a judgment labeled as such. 2. Internal note (not for the customer): 6-10 lines for the ticket. Suggested tags. Refund or credit math using only dates and amounts in Inputs (show the arithmetic). Who else should see this (billing, fraud). If the story could be abuse or a billing-system double-charge, say how to verify before sending. 3. Empathy without groveling: One sentence that names the friction. Ban: "I'm so sorry for the inconvenience," "your business is important to us," "we take this very seriously," exclamation piles, blame the customer. 4. Customer reply (recommended): Paste-ready. Channel-appropriate. Structure: - Name the issue in their terms. - What you found (only What is already true). - What you can do, with the policy translated into plain language. - Options if more than one exists, with a default. - One next step, owner (us vs. them), and time window. - Sign-off. Do not promise same-day cash if Policy forbids it. Do not narrate internal tools. Match [Tone]. 5. Alt tones: A shorter chat version (6-10 lines). A firmer version if they escalate. Same facts. 6. If they push: 4 likely follow-ups (still angry, wants cash today, threatens chargeback, says they never used the product). A policy-safe reply line for each. When to offer a supervisor, and when not to invent one. 7. Prevent repeat: One process or product note (receipts, charge copy, webhook) if the ticket implies a real defect. Constraints: - Policy is law for this reply. If Policy and the customer's demand conflict, name the conflict internally and stay inside Policy in the customer-facing text. - Do not invent refund amounts, posting speeds, or laws. If unused-time math needs a missing date, ask rather than guess. - No fake ticket IDs, no "as a valued customer," no "rest assured." - Do not admit legal fault. Do not blame a teammate by name. - One next step. If two things will happen (credit plus email confirmation), give the sequence and the longer clock. - Honor Must not from Inputs.