30 Claude Prompts for One-Pagers

You are a corporate development lead who writes one-page strategic partnership proposals for an exec review. <context> I want to propose a partnership and I need a one-pager that states why this partner, what we each give, what we each get, and the decision I need this month. </context> <inputs> - Our company: [COMPANY NAME] - Partner: [PARTNER NAME] - Shared customer or problem: [SHARED PROBLEM] - What we would offer: [OUR CONTRIBUTION] - What we would ask for: [THEIR CONTRIBUTION] - Success signal in 90 days: [90 DAY SIGNAL] </inputs> <task> Write a strategic partnership one-pager that a CEO or GM can scan. Cover the shared problem, each side's contribution, the 90-day signal, and the ask. Use only the facts in the inputs. Mark legal terms, revenue share, and exclusivity as UNKNOWN if they are not listed. Do not invent a market size or a signed LOI. </task> <constraints> One page. No alliance theater. Do not promise exclusivity, a press announcement, or a revenue number that is not in the inputs. </constraints> <format> Return headings: Why this partner, What we give, What we get, 90-day signal, Risks, Decision needed. Keep the draft under 450 words. </format>

You are a channel chief who writes one-page briefs for a new reseller or referral partner motion. <context> I need a channel partner one-pager that sales leadership can use to approve or reject a partner type, not a 30-page playbook. </context> <inputs> - Partner type: [PARTNER TYPE] - Product they would sell or refer: [PRODUCT NAME] - Target accounts they already reach: [TARGET ACCOUNTS] - Proposed margin or referral fee: [FEE OR MARGIN] - Enablement we can staff: [ENABLEMENT CAPACITY] - First 2 quarters target: [PIPELINE TARGET OR UNKNOWN] </inputs> <task> Write a channel partner one-pager that states the partner type, the product, the accounts they reach, the fee, the enablement we can actually staff, and a pipeline target only if it is in the inputs. Use only the facts in the inputs. Mark pipeline as UNKNOWN if missing. Do not invent partner count, win rates, or a certification program. </task> <constraints> One page. No claim that channel will scale itself. If enablement capacity is thin, say so. Do not add a global rollout plan that is not in the inputs. </constraints> <format> Return headings: Partner type, Motion, Economics, Enablement, Target, Risks, Ask. Cap at 400 words. </format>

You are a partnerships product manager who writes one-page integration briefs for engineering and the partner's product team. <context> We want to ship an integration with another product and I need a one-pager that states the user job, the data that moves, who builds what, and the launch bar. </context> <inputs> - Our product: [OUR PRODUCT] - Partner product: [PARTNER PRODUCT] - User job the integration finishes: [USER JOB] - Data or events that must move: [DATA FLOWS] - Who builds which side: [BUILD SPLIT] - Launch bar: [LAUNCH BAR] </inputs> <task> Write an integration partnership one-pager that states the user job, the data flows, the build split, and the launch bar. Use only the facts in the inputs. Mark auth method, rate limits, and SLA as UNKNOWN if they are not listed. Do not invent an API, a webhook list, or a ship week. </task> <constraints> One page. No architecture diagram in prose longer than five bullets. Do not add a marketplace listing plan unless it appears in the inputs. </constraints> <format> Return headings: User job, Data flows, Build split, Launch bar, Unknowns, Decision. Keep it under 400 words. </format>

You are a demand generation lead who writes one-page co-marketing briefs that both brands can approve in one meeting. <context> I am proposing a co-marketing motion with another brand and I need a one-pager that states the audience overlap, the asset, the spend, and the lead rules. </context> <inputs> - Our brand: [OUR BRAND] - Partner brand: [PARTNER BRAND] - Shared audience: [SHARED AUDIENCE] - Proposed asset or event: [ASSET OR EVENT] - Spend or in-kind each side: [SPEND SPLIT] - Lead capture and follow-up rules: [LEAD RULES OR UNKNOWN] </inputs> <task> Write a co-marketing one-pager that states the shared audience, the asset, the spend split, and the lead rules. Use only the facts in the inputs. Mark lead ownership as UNKNOWN if it is missing. Do not invent registrant counts, a CPL, or a press quote. </task> <constraints> One page. No hype about brand fit. Do not promise a webinar date or a list size that is not in the inputs. </constraints> <format> Return headings: Audience, Asset, Spend, Lead rules, Success metric, Risks, Ask. Cap the draft at 380 words. </format>

You are an alliances director who writes one-page technology alliance briefs for a steering committee. <context> We are considering a deeper technology alliance and I need a one-pager that states the joint offer, the support model, and the commercial terms we actually know. </context> <inputs> - Alliance name or working title: [ALLIANCE NAME] - Joint offer in one sentence: [JOINT OFFER] - Customer who would buy it: [BUYER] - Support model: [SUPPORT MODEL] - Commercial terms known: [COMMERCIAL TERMS OR UNKNOWN] - Internal owner: [INTERNAL OWNER] </inputs> <task> Write a technology alliance one-pager that states the joint offer, the buyer, the support model, known commercial terms, and the internal owner. Use only the facts in the inputs. Mark exclusivity, IP, and revenue share as UNKNOWN if they are not listed. Do not invent a named logo or a booked pipeline. </task> <constraints> One page. No claim the alliance is exclusive unless that word is in the inputs. Do not add a multi-year roadmap that is not listed. </constraints> <format> Return headings: Joint offer, Buyer, Support, Commercial terms, Owner, Risks, Decision. Keep it under 420 words. </format>

You are a people operations partner who writes one-page headcount requests that a CFO and a function lead can decide in one meeting. <context> I need a new role and I must put the case on one page: the work that is failing today, the role, the cost, and what we will stop doing if the seat is refused. </context> <inputs> - Team: [TEAM NAME] - Role title: [ROLE TITLE] - Work that is failing or queued: [FAILING WORK] - Why a contractor or tool will not cover it: [WHY NOT CONTRACTOR] - Fully loaded cost: [FULLY LOADED COST] - What we will cut if refused: [CUT IF REFUSED] </inputs> <task> Write a headcount request one-pager that states the failing work, the role, why a contractor will not cover it, the cost, and the cut if refused. Use only the facts in the inputs. Mark start date, level, and location as UNKNOWN if they are missing. Do not invent a productivity multiple or a revenue attachment. </task> <constraints> One page. No story about talent wars. Do not claim the hire pays for itself unless that math is in the inputs. </constraints> <format> Return headings: Failing work, Role, Why not a contractor, Cost, Cut if refused, Risks, Decision. Cap at 400 words. </format>

You are a finance business partner who writes one-page budget requests for a mid-year or annual cycle. <context> I need incremental budget and I must put the case on one page: the spend, what it buys, what happens if we keep the current budget, and how we will know it worked. </context> <inputs> - Cost center: [COST CENTER] - Amount requested: [AMOUNT REQUESTED] - What the spend buys: [SPEND ITEMS] - Current budget and gap: [CURRENT BUDGET] - Impact if we stay at current: [IMPACT IF REFUSED] - Success metric: [SUCCESS METRIC] </inputs> <task> Write a budget request one-pager that states the amount, the items, the current gap, the impact if refused, and the success metric. Use only the facts in the inputs. Mark vendor names, contract length, and ROI as UNKNOWN if they are not listed. Do not invent savings or a payback period. </task> <constraints> One page. No padding. Do not restate the same ask in three different words. If ROI is unknown, say UNKNOWN rather than a range you made up. </constraints> <format> Return headings: Ask, Items, Current gap, Impact if refused, Success metric, Risks, Decision. Keep it under 380 words. </format>

You are an operations manager who writes one-page process change proposals that a function head can approve without a workshop. <context> A current process is slow or error-prone and I need a one-pager that states the current steps, the proposed steps, who is affected, and the risk of changing it. </context> <inputs> - Process name: [PROCESS NAME] - Current steps that hurt: [CURRENT PAIN] - Proposed change: [PROPOSED CHANGE] - Teams affected: [TEAMS AFFECTED] - Systems touched: [SYSTEMS TOUCHED] - Rollout window: [ROLLOUT WINDOW] </inputs> <task> Write a process change one-pager that states the current pain, the proposed change, the teams and systems touched, and the rollout window. Use only the facts in the inputs. Mark policy, audit, and training needs as UNKNOWN if they are missing. Do not invent cycle-time savings or an error-rate drop. </task> <constraints> One page. No transformation language. Do not add a new tool unless that tool is in the inputs. </constraints> <format> Return headings: Current pain, Proposed change, Who is affected, Systems, Rollout, Risks, Decision. Cap at 400 words. </format>

You are an IT procurement lead who writes one-page tool purchase briefs for security, finance, and the requesting team. <context> A team wants to buy a tool and I need a one-pager that states the job, the vendor, the cost, the alternative we already have, and the security status. </context> <inputs> - Tool name: [TOOL NAME] - Job it is meant to finish: [USER JOB] - Annual cost: [ANNUAL COST] - Alternative we already pay for: [EXISTING ALTERNATIVE] - Security or legal status: [SECURITY STATUS OR UNKNOWN] - Owner after purchase: [INTERNAL OWNER] </inputs> <task> Write a tool purchase one-pager that states the job, the vendor, the cost, the existing alternative, security status, and the owner. Use only the facts in the inputs. Mark SSO, data residency, and seat count as UNKNOWN if they are missing. Do not invent a productivity gain or a competitor price. </task> <constraints> One page. No vendor brochure copy. If security status is unknown, say the purchase cannot proceed until that field is filled. </constraints> <format> Return headings: Job, Tool, Cost, Existing alternative, Security status, Owner, Decision. Keep it under 380 words. </format>

You are an organization design lead who writes one-page team structure proposals for a function head and HR. <context> I want to change reporting lines or squads and I need a one-pager that states the current structure, the proposed structure, who moves, and what problem this is meant to fix. </context> <inputs> - Function: [FUNCTION NAME] - Current structure: [CURRENT STRUCTURE] - Proposed structure: [PROPOSED STRUCTURE] - Problem this is meant to fix: [PROBLEM TO FIX] - People or roles that move: [ROLES THAT MOVE] - Date the change would land: [CHANGE DATE] </inputs> <task> Write a team structure one-pager that states the problem, the current structure, the proposed structure, who moves, and the date. Use only the facts in the inputs. Mark compensation, title, and location changes as UNKNOWN if they are not listed. Do not invent a productivity gain or a hiring freeze rationale. </task> <constraints> One page. No org-chart poetry. Do not name individuals unless those names appear in the inputs. Stay factual about the problem. </constraints> <format> Return headings: Problem, Current, Proposed, Who moves, Date, Risks, Decision. Cap at 400 words. </format>

You are a go-to-market lead who writes one-page launch briefs that product, marketing, and sales can share in a single war-room doc. <context> We are launching a product or a major feature and I need a one-pager that states who it is for, the date, the message, the channels, and the success bar. </context> <inputs> - Launch name: [LAUNCH NAME] - Audience: [TARGET AUDIENCE] - Launch date: [LAUNCH DATE] - Core message: [CORE MESSAGE] - Channels we will use: [CHANNELS] - Success bar in the first 30 days: [30 DAY BAR] </inputs> <task> Write a product launch one-pager that states the audience, the date, the core message, the channels, and the 30-day bar. Use only the facts in the inputs. Mark pricing, packaging, and sales enablement as UNKNOWN if they are not listed. Do not invent a press hit, a waitlist count, or a pipeline number. </task> <constraints> One page. No launch hype. Do not add a channel that is not in the inputs. If the date is a window, keep it as a window. </constraints> <format> Return headings: Audience, Date, Message, Channels, 30-day bar, Unknowns, Owners. Keep it under 420 words. </format>

You are a growth marketing lead who writes one-page campaign briefs that creative, media, and product can run from. <context> I need a campaign one-pager that states the offer, the audience, the spend, the landing point, and the metric that decides if we keep spending. </context> <inputs> - Campaign name: [CAMPAIGN NAME] - Offer: [OFFER] - Audience: [AUDIENCE] - Paid or owned spend: [SPEND] - Landing page or asset: [LANDING POINT] - Kill or scale metric: [KILL METRIC] </inputs> <task> Write a campaign one-pager that states the offer, audience, spend, landing point, and the kill-or-scale metric. Use only the facts in the inputs. Mark creative variants, geo, and attribution as UNKNOWN if they are missing. Do not invent a CAC, a conversion rate, or a list size. </task> <constraints> One page. No brand manifesto. Do not add a second offer. If spend is a cap, treat it as a cap, not a target you can exceed. </constraints> <format> Return headings: Offer, Audience, Spend, Landing point, Kill metric, Unknowns, Decision. Cap at 380 words. </format>

You are a general manager who writes one-page market expansion briefs for an exec staff meeting. <context> We want to enter a new country, segment, or vertical and I need a one-pager that states why this market, what we would sell, the cost to enter, and the first proof we need. </context> <inputs> - Market: [MARKET NAME] - Product we would sell: [PRODUCT NAME] - Why this market now: [WHY NOW] - Cost to enter: [ENTRY COST OR UNKNOWN] - First proof in 90 days: [90 DAY PROOF] - What we would not do in year one: [YEAR ONE OUT OF SCOPE] </inputs> <task> Write a market expansion one-pager that states the market, the product, why now, the entry cost, the 90-day proof, and what is out of scope in year one. Use only the facts in the inputs. Mark legal, tax, and localization as UNKNOWN if they are missing. Do not invent TAM, a competitor share, or a hire plan. </task> <constraints> One page. No land-and-expand poetry. Do not add a three-year forecast that is not in the inputs. </constraints> <format> Return headings: Market, Product, Why now, Entry cost, 90-day proof, Out of scope, Decision. Keep it under 420 words. </format>

You are a monetization lead who writes one-page pricing launch briefs for sales, finance, and customer success. <context> We are launching a new price, pack, or add-on and I need a one-pager that states the offer, who can buy it, the date, and the talking points sales may use. </context> <inputs> - Offer name: [OFFER NAME] - Price and unit: [PRICE AND UNIT] - Who can buy it: [ELIGIBLE BUYERS] - Launch date: [LAUNCH DATE] - What sales may say: [APPROVED TALKING POINTS] - What sales must not say: [FORBIDDEN CLAIMS] </inputs> <task> Write a pricing launch one-pager that states the offer, price, eligible buyers, date, approved talking points, and forbidden claims. Use only the facts in the inputs. Mark grandfathering, discounts, and commission as UNKNOWN if they are missing. Do not invent a discount ladder or a competitor comparison. </task> <constraints> One page. No price-is-value speech. Do not add a claim that is not in APPROVED TALKING POINTS. </constraints> <format> Return headings: Offer, Price, Buyers, Date, Say this, Do not say this, Open items. Cap at 400 words. </format>

You are an events marketing manager who writes one-page sponsorship briefs for a budget owner. <context> I want to sponsor or host an event and I need a one-pager that states the audience in the room, the cost, the asset we get, and the follow-up plan after the event. </context> <inputs> - Event name: [EVENT NAME] - Audience in the room: [ROOM AUDIENCE] - Sponsorship cost: [SPONSORSHIP COST] - Assets included: [ASSETS INCLUDED] - Staff we will send: [STAFF PLAN] - Follow-up plan after: [FOLLOW UP PLAN] </inputs> <task> Write an event sponsorship one-pager that states the room, the cost, the assets, the staff plan, and the follow-up. Use only the facts in the inputs. Mark expected meetings, badge scans, and pipeline as UNKNOWN if they are not listed. Do not invent an attendee count or a pipeline number. </task> <constraints> One page. No brand-exposure filler. If the organizer has not confirmed an audience number, write UNKNOWN rather than their marketing page. </constraints> <format> Return headings: Room, Cost, Assets, Staff, Follow-up, Unknowns, Decision. Keep it under 380 words. </format>

You are a chief of staff who writes one-page go or no-go memos that an exec staff can vote on in ten minutes. <context> We have a decision this week and I need a one-pager that states the decision, the options, the facts we have, and the recommendation with the risk of each path. </context> <inputs> - Decision in one sentence: [DECISION STATEMENT] - Option A: [OPTION A] - Option B: [OPTION B] - Facts that are confirmed: [CONFIRMED FACTS] - Deadline: [DECISION DATE] - Recommendation and why: [RECOMMENDATION] </inputs> <task> Write a go or no-go one-pager that states the decision, both options, confirmed facts, the deadline, and the recommendation. Use only the facts in the inputs. Mark cost, legal, and customer impact as UNKNOWN if they are missing. Do not invent a third option or a financial model. </task> <constraints> One page. No both-sides padding that hides the recommendation. If the recommendation is weak on facts, say which UNKNOWN blocks a clean vote. </constraints> <format> Return headings: Decision, Option A, Option B, Facts, Unknowns, Recommendation, Vote by. Cap at 400 words. </format>

You are a VP of finance who writes one-page investment asks for a CEO and a board observer. <context> I need incremental investment for a project and I must put the case on one page: the amount, what it funds, the return we can defend, and what we stop if the money is refused. </context> <inputs> - Project name: [PROJECT NAME] - Amount and timing: [AMOUNT AND TIMING] - What the money funds: [FUNDING ITEMS] - Return we can defend: [DEFENSIBLE RETURN OR UNKNOWN] - What we stop if refused: [STOP IF REFUSED] - Owner: [PROJECT OWNER] </inputs> <task> Write an investment ask one-pager that states the amount, the items, the defensible return, the stop if refused, and the owner. Use only the facts in the inputs. If return is unknown, write UNKNOWN and do not invent IRR or payback. Do not invent a customer logo or a booked pipeline. </task> <constraints> One page. No vision deck. Do not stretch a qualitative benefit into a dollar figure. </constraints> <format> Return headings: Ask, Items, Return, Stop if refused, Owner, Risks, Decision. Keep it under 400 words. </format>

You are a portfolio product lead who writes one-page kill or continue briefs for a product council. <context> A product or a bet is under review and I need a one-pager that states usage, cost to keep it, cost to kill it, and a recommendation. </context> <inputs> - Product name: [PRODUCT NAME] - Usage or revenue we can confirm: [USAGE OR REVENUE] - Annual cost to keep it: [COST TO KEEP] - Cost and harm if we kill it: [COST TO KILL] - Contract or customer locks: [LOCKS] - Recommendation: [RECOMMENDATION] </inputs> <task> Write a kill or continue one-pager that states confirmed usage or revenue, cost to keep, cost to kill, locks, and the recommendation. Use only the facts in the inputs. Mark strategic value as UNKNOWN unless it is in the inputs. Do not invent a turnaround plan or a new segment. </task> <constraints> One page. No nostalgia. If usage is unknown, say the council cannot vote cleanly. Do not add a sunset date unless it appears in the inputs. </constraints> <format> Return headings: Product, Usage, Cost to keep, Cost to kill, Locks, Recommendation, Open facts. Cap at 400 words. </format>

You are a solutions architect who writes one-page build versus buy memos for a product and engineering staff meeting. <context> We must choose build or buy and I need a one-pager that states the job, the build path, the buy path, the costs we know, and a recommendation. </context> <inputs> - Job to be done: [USER JOB] - Build path in brief: [BUILD PATH] - Buy path and vendor: [BUY PATH] - Known costs: [KNOWN COSTS] - Time we have: [TIME AVAILABLE] - Constraints we cannot move: [HARD CONSTRAINTS] </inputs> <task> Write a build versus buy one-pager that states the job, both paths, known costs, time, and hard constraints, then a recommendation that follows from those facts. Use only the facts in the inputs. Mark TCO, security review, and integration effort as UNKNOWN if they are missing. Do not invent an engineering week count or a vendor discount. </task> <constraints> One page. No NIH speech and no buy-is-always-faster speech. If time available is shorter than a honest build, say so without inventing a week count. </constraints> <format> Return headings: Job, Build, Buy, Known costs, Time, Constraints, Recommendation. Keep it under 420 words. </format>

You are a risk officer who writes one-page risk decision memos for an exec sponsor. <context> We have a live risk and I need a one-pager that states the risk, the likelihood and impact we can defend, the options, and the decision we need. </context> <inputs> - Risk in one sentence: [RISK STATEMENT] - Likelihood we can defend: [LIKELIHOOD] - Impact we can defend: [IMPACT] - Option to accept: [ACCEPT OPTION] - Option to mitigate: [MITIGATE OPTION] - Decision owner and date: [OWNER AND DATE] </inputs> <task> Write a risk decision one-pager that states the risk, the defended likelihood and impact, accept vs mitigate, and the owner and date. Use only the facts in the inputs. Mark residual risk and insurance as UNKNOWN if they are not listed. Do not invent a probability percentage or a dollar loss. </task> <constraints> One page. No scare language. If likelihood is a judgment, label it as judgment, not as a measured rate. </constraints> <format> Return headings: Risk, Likelihood, Impact, Accept, Mitigate, Owner and date, Unknowns. Cap at 380 words. </format>

You are a product marketing manager who writes one-page customer product sheets that a sales rep can send after a first call. <context> I need a customer-facing one-pager that states who the product is for, the job it finishes, the proof we can show, and the next step. I do not want a brochure. </context> <inputs> - Product name: [PRODUCT NAME] - Buyer role: [BUYER ROLE] - Job it finishes: [USER JOB] - Proof we can show: [PROOF POINTS] - Price or how to buy: [PRICE OR BUY PATH] - Next step we want: [NEXT STEP] </inputs> <task> Write a customer-facing product one-pager that states the buyer, the job, the proof, how to buy, and the next step. Use only the facts in the inputs. Mark logos, metrics, and security certifications as UNKNOWN if they are not listed. Do not invent a customer name, a percent, or a guarantee. </task> <constraints> One page. Plain language. No superlatives. If a proof point is missing a source, drop it rather than rounding it up. </constraints> <format> Return headings: Who it is for, Job it finishes, Proof, How to buy, Next step. Keep the draft under 350 words. </format>

You are an industry solutions lead who writes one-page vertical sheets for a named segment. <context> I need a one-pager for a vertical that states the work in that industry, how the product maps, the proof we have in that vertical, and what we will not claim. </context> <inputs> - Vertical: [VERTICAL NAME] - Product: [PRODUCT NAME] - Work this buyer is trying to finish: [INDUSTRY JOB] - How the product maps: [PRODUCT MAPPING] - Proof in this vertical: [VERTICAL PROOF OR NONE] - Claims we must not make: [FORBIDDEN CLAIMS] </inputs> <task> Write a vertical solution one-pager that states the industry job, the mapping, the proof, and the forbidden claims. Use only the facts in the inputs. If vertical proof is none, say we do not have a named customer in this vertical. Do not invent a regulation win or a logo. </task> <constraints> One page. No industry jargon you cannot explain in one line. Do not add a claim from FORBIDDEN CLAIMS even if it would sound strong. </constraints> <format> Return headings: Vertical, Job, How we map, Proof, Do not claim, Next conversation. Cap at 380 words. </format>

You are a sales enablement lead who writes one-page battlecards that a rep can open on a live call. <context> Reps keep losing or stalling against one competitor and I need a one-pager that states when we win, when we lose, the landmines, and the one question to ask. </context> <inputs> - Our product: [OUR PRODUCT] - Competitor: [COMPETITOR NAME] - When we win: [WIN CONDITIONS] - When we lose: [LOSE CONDITIONS] - Landmines to avoid: [LANDMINES] - Proof we can use: [PROOF POINTS] </inputs> <task> Write a competitive battlecard one-pager that states win conditions, lose conditions, landmines, proof, and one question a rep can ask. Use only the facts in the inputs. Mark pricing and feature gaps as UNKNOWN if they are not listed. Do not invent a competitor weakness or a customer quote. </task> <constraints> One page. No trash talk. Do not tell the rep to badmouth the competitor. If a gap is unknown, tell the rep to qualify, not to guess. </constraints> <format> Return headings: When we win, When we lose, Landmines, Proof, Question to ask. Keep it under 350 words. </format>

You are a value engineer who writes one-page ROI sheets for a single live deal. <context> A champion asked for a one-page ROI view and I need numbers that come only from what this account already agreed, not from a generic calculator. </context> <inputs> - Account name: [ACCOUNT NAME] - Product in the deal: [PRODUCT NAME] - Baseline the account agreed: [AGREED BASELINE] - Change we model: [MODELED CHANGE] - Dollar or hour impact they agreed: [AGREED IMPACT] - Assumptions they have not agreed: [UNAGREED ASSUMPTIONS] </inputs> <task> Write a deal ROI one-pager that states the baseline, the modeled change, the agreed impact, and the assumptions that are still unagreed. Use only the facts in the inputs. Put unagreed assumptions in a separate list labeled UNAGREED. Do not invent a payback month or a percent if it is not in the inputs. </task> <constraints> One page. No generic industry averages. If the account did not agree a number, it cannot appear as a result. </constraints> <format> Return headings: Baseline, Change, Agreed impact, Unagreed assumptions, Ask for the champion. Cap at 380 words. </format>

You are a solutions consultant who writes one-page use-case sheets that a prospect and a sales engineer can walk through together. <context> I need a use-case one-pager for one job, not a catalog of ten. It should state the trigger, the steps, the systems involved, and what success looks like for this job. </context> <inputs> - Use case name: [USE CASE NAME] - Product: [PRODUCT NAME] - Trigger that starts the job: [TRIGGER] - Steps the user takes: [USER STEPS] - Systems involved: [SYSTEMS INVOLVED] - Success for this job: [SUCCESS LOOKS LIKE] </inputs> <task> Write a use-case one-pager that states the trigger, the steps, the systems, and success for this one job. Use only the facts in the inputs. Mark integrations and data fields as UNKNOWN if they are missing. Do not invent a second use case or a time-saved number. </task> <constraints> One page. One job only. No platform tour. If a step needs a system that is not listed, mark that step UNKNOWN. </constraints> <format> Return headings: Trigger, Steps, Systems, Success, Unknowns, Demo path. Keep it under 360 words. </format>