Browse Prompts
80 prompts available in business · Page 7 of 7
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.
Freelance Proposal Writer for Upwork and Similar Jobs
Write a short, specific proposal from a job post: hook, relevant proof, plan, timeline, price range, and questions. No cringe templates.
Act as a freelance closer who writes short proposals that sound like one specific person. You have 30 seconds of the client's skim. No origin story, no "I came across your job post," no emoji, no "I'm excited." Inputs: - Job post: [Job post] - My background: [Background] - Proof I can name: [Proof] - Fit gaps: [Gaps] - Price range I want: [Price] - Timeline I can do: [Timeline] - Voice: [Voice] - Constraints: [Constraints] Generate: 1. Read of the job: What they actually want (deliverable). Hidden risks (scope, copy, revisions, stock photos, SEO, hosting). What "done" probably means. Red flags. Whether to bid, bid with a boundary, or pass. If pass, say why in 4 lines and stop. 2. Hook (2-4 sentences): Name the job in their words. One relevant proof. No greeting fluff. No "as a [role] with a passion." 3. Relevant proof: 3 bullets max. Each: situation, what you shipped, result if you have one. If a metric is missing, do not invent it. Map each bullet to a line in the Job post. 4. Plan: 5-8 numbered steps from kickoff to handoff. Name tools only if they match the post. Include a feedback loop and what you need from them (copy, brand, hosting, content). 5. Timeline: Calendar-style, fitting Timeline I can do and the post deadline. Call out the critical path (copy lock, staging review). What slips if they reply late. 6. Price: A range or a single number consistent with Price range I want and the post budget. What is in. What is out (extra pages, copywriting, extra rounds, SEO retainers). How revisions work. Do not underbid to "start a relationship." 7. Questions (4-6): Specific, answerable, that reduce scope risk. No "what is your vision?" 8. Full proposal: Paste-ready. 150-220 words unless the job is technical enough to need 280. Structure: hook, 3 proof lines, plan in short steps, timeline, price, questions, sign-off with name placeholder. Zero hashtags. Match [Voice]. 9. Short variant: 90-120 words for mobile skim. 10. Lines I will not write: 5 cringe sentences this prompt refuses, rewritten as the adult version. Constraints: - Ban: "I hope this finds you well," "I'm excited to apply," "I would love the opportunity," "as a highly skilled," "over X years of experience" as a flex with no proof, "Let's make your vision a reality," emoji, fake metrics, fake client logos. - Do not invent URLs, conversion lifts, or tools you did not list. - If Fit gaps matter, acknowledge in one honest line and how you will handle it. Do not hide it. Do not grovel. - Stay inside the stated budget unless Inputs say to explain a higher number. - Sound like a contractor who has done this job, not a cover-letter generator. - Honor Constraints from Inputs (must mention / must not mention).
Product Requirements Document (PRD) Writer
Turn a product idea into a complete PRD: problem, users, scope, user stories, acceptance criteria, metrics, and launch risks.
Act as a senior product manager writing a PRD that engineering, design, and GTM can actually execute. Be precise about what is in, what is out, and what is still unknown. Do not dress guesses up as facts. Inputs: - Product / feature: [Name and one-line idea] - Problem: [Who hurts and how] - Users: [Primary and secondary] - Platform: [Web / iOS / Android / API / internal] - Business goal: [Revenue, retention, expansion, cost, compliance] - Constraints: [Time, stack, legal, dependencies] - Known unknowns: [List, or "none yet"] - Success metric I care about: [North-star or proxy] Generate: 1. Summary: 8-12 sentences. What we are building, for whom, why now, and what "done" means for v1. Flag any Input that is still vague. 2. Problem and context: Current workaround. Cost of the workaround. Why existing tools or the current product fail. Evidence: separate Provided (from Inputs) vs Assumed (label each assumption). 3. Goals and non-goals: - Goals (3-6): Outcome-based, testable. - Non-goals for v1: Explicit cuts. Include at least two tempting features we will refuse. 4. Users and JTBD: Primary user, secondary user, anti-user (who this is not for). For the primary user: job-to-be-done statement, trigger, desired outcome, current alternatives. 5. Scope: In-scope list. Out-of-scope list. Open questions with an owner suggestion (PM / Eng / Design / Legal / GTM). 6. User stories (8-12): Format "As a [user], I want [action], so that [outcome]." Tag each P0 / P1 / P2. P0 must be a shippable vertical slice, not a layer of polish. Include 1-2 negative stories (what the system must not do). 7. Acceptance criteria for every P0 story: Given / When / Then. Include empty, error, permission, and mobile/narrow-viewport cases where relevant. No "should feel fast" without a number or a qualitative test method. 8. UX notes: Happy path in 6-10 steps. Empty states. Edge cases. Key copy (buttons, errors). What must be designed vs. what can ship with existing patterns. 9. Analytics and success metrics: Leading and lagging metrics. Event names (object_action). Guardrail metrics that would make us roll back. How we will decide to iterate vs. kill after launch. 10. Launch plan: Feature flag / staged rollout sketch. Internal dogfood. Beta criteria. Support and docs needed. GTM one-pager bullets (who we tell, what we claim, what we will not claim). 11. Risks and unknowns: Table: risk | likelihood (Low/Med/High, labeled as judgment) | impact | mitigation | trigger to escalate. Include at least one dependency risk and one "we might be solving the wrong problem" risk. Constraints: - No fake certainty. If Inputs do not include a number, write "unknown, need [source]" instead of inventing a TAM or conversion rate. - Do not invent APIs, vendors, or legal positions. - Stories must be independently testable. No "and also make it beautiful." - Write for a staff engineer who will challenge scope. Short sentences. Named sections. No vision-deck fluff.
SWOT Analysis Generator: Strategic Business Assessment Tool
Produce a thorough SWOT analysis for any business or project. Get actionable strategic insights across strengths, weaknesses, opportunities, and threats.
Act as a management consultant specializing in strategic analysis and competitive intelligence. Conduct a comprehensive SWOT analysis for [Company/Business/Project Name] operating in [Industry/Market]. Follow these steps: Strengths (Internal): Identify 5-7 internal advantages. Consider resources, capabilities, brand equity, team expertise, proprietary technology, and cost advantages. Weaknesses (Internal): Identify 5-7 internal limitations. Consider skill gaps, resource constraints, operational inefficiencies, and brand perception issues. Opportunities (External): Identify 5-7 external opportunities. Consider market trends, regulatory changes, technology shifts, partnership potential, and underserved segments. Threats (External): Identify 5-7 external risks. Consider competitor actions, economic downturns, supply chain risks, changing consumer preferences, and regulatory risks. Strategic Recommendations: Based on the SWOT, provide: 3 SO strategies (use Strengths to capture Opportunities) 3 WO strategies (address Weaknesses to capture Opportunities) 3 ST strategies (use Strengths to mitigate Threats) 3 WT strategies (minimize Weaknesses and avoid Threats) Priority Matrix: Rank the top 5 strategic actions by impact and feasibility. Constraints: Be specific to [Industry]. Avoid generic statements. Tone: Analytical, objective, and actionable. Format: Use a 2x2 SWOT grid followed by a detailed breakdown.
Complete Business Plan Generator: Investor-Ready Documents
Generate a professional, investor-ready business plan with financial projections, market analysis, and competitive positioning for any startup idea.
Act as a senior business strategy consultant with experience advising startups and preparing investor pitch materials. Generate a complete business plan for [Business Idea / Startup Name]. Follow this structure: Executive Summary: A 200-word overview covering the problem, solution, target market, and revenue model. Problem Statement: Define the specific pain point your business addresses. Use data or statistics where applicable. Solution: Describe the product/service and how it solves the problem. Target Market: Define the TAM, SAM, and SOM with estimated figures for [Industry]. Competitive Analysis: Identify 3-5 direct competitors. For each, list strengths, weaknesses, and your differentiation. Revenue Model: Outline pricing strategy, revenue streams, and projected monthly revenue for Year 1. Go-to-Market Strategy: Detail the first 90 days of customer acquisition. Financial Projections: Provide a simplified 3-year projection table (Revenue, COGS, Gross Margin, Operating Expenses, Net Profit). Team: Describe the key roles needed and their responsibilities. Ask: State the funding amount needed and how it will be allocated. Constraints: Use realistic, conservative financial estimates. Tone: Professional, data-driven, and concise. Avoid jargon unless standard in business planning.
B2B Cold Email Outreach Campaign Builder
Craft highly personalized and high-converting B2B cold email sequences. This prompt ensures your outreach avoids spam folders and drives replies.
Act as a top-producing B2B Sales Executive and lead generation expert. Design a 3-step cold email outreach sequence offering [Product/Service] to [Target Job Title] at [Target Industry/Company Type]. Follow these strict guidelines: Sequence Structure: Email 1 (The Hook & Value), Email 2 (The Gentle Nudge & Case Study), Email 3 (The Breakup/Final Offer). Personalization: Include clear placeholders like [Company Name], [Recent News/Achievement], and [Recipient First Name] for hyper-personalization. Brevity & Clarity: Keep each email under 120 words. Focus on the prospect's pain points, not your product's features. Call to Action (CTA): Use a low-friction CTA (e.g., asking for interest rather than a 30-minute call). E-E-A-T: Establish authority by seamlessly introducing a relevant one-sentence case study or metric. Tone: Professional, calm, and confident. Avoid aggressive sales language. Use active voice.
Startup Pitch Deck Architect
Builds a 10-slide outline for a startup pitch based on the problem-solution model.
Create a 10-slide pitch deck outline for a startup that [Brief Description of Business]. For each slide, provide a clear title and three bullet points detailing the key information to include. Follow the standard venture capital pitch structure.