- 1.
The prompt does not contain Sarah, see prompt below:
#CONTEXT# Youāre writing the first sentence of a cold email to a finance leader in a small NZ company. This is the punchy one-liner and must be a question, so that the recipient can identify themselves. #OBJECTIVE# Rephrase the provided
Personalized Finance Problem Problem Statement
into a short, clean, natural opening line. It should reflect the reality of what this person is stuck doing ā and what itās costing them. #INSTRUCTIONS# 1. Read the
Personalized Finance Problem Problem Statement
carefully. 2. Write a single sentence, no more than 15 words. 3. This line should: - Sound like a calm observation or peer comment - Acknowledge a real bottleneck or frustration - Sit naturally at the top of an email, especially when viewed on mobile 4. You may reference their
First Name
or
Company Name
if it adds to the impact, but itās optional. 4. You may use **industry-native abbreviations or shorthand** if they feel natural and specific to the task. These include: - āEOMā instead of āend of monthā - ārecsā instead of āreconciliationsā or āreconcilingā - āAPā for accounts payable - āboard packā (common NZ shorthand) Only use these if they sound like something a finance lead would say in a message to their colleague or team. #FORMATTING INSTRUCTION# Return a single sentence with no trailing or leading line breaks or empty lines. Output should be a single string, not a paragraph block. - DONāT include a new line or return at the end of the output. - DONāT start the sentence on a new line. #AUDIENCE CONTEXT# - This person is a finance lead at a New Zealand company with 11ā50 employees - Theyāre doing reporting, reconciliations, compliance, and month-end themselves or with limited help - Strategic work keeps getting postponed because thereās not enough capacity - Theyāre stretched, not lazy ā donāt shame them, just reflect the tension #ANTI-AI GUARDRAILS# - Avoid rhetorical questions or sales hooks - No techy verbs (āoptimize,ā āscale,ā āstreamlineā) - Avoid symmetry (donāt write āstuck doing X when they should be doing Yā) - No poetic language or startup clichĆ©s (āwearing all the hats,ā āburning the candleā) - No fancy punctuation (no em-dashes, ellipses, quotation marks, or excessive commas) - Avoid unfamiliar or forced abbreviations ā use only terms a finance lead would naturally say - Donāt explain or spell out the abbreviations ā use them as the reader would #DOs# - DO sound like a peer describing what they see - DO write plainly and clearly - DO anchor the sentence in one tangible thing (e.g., āstill reconciling,ā āburied in templates,ā ācanāt start planningā) - DO include the recipients first name and always in the format of Name,. Never Name:. #DONāTs# - DONāT pitch or hint at your solution - DONāT force cleverness ā quiet realism beats slick language - DONāT use abstract phrasing (āstuck in the weedsā / āspinning platesā) - DON'T reference anywhere other than New Zealand (ie. Pacific, Australia etc). #EXAMPLES# Example input (
Personalized Finance Problem Problem Statement
š āYouāre constantly juggling last-minute requests for detailed financial reports on network upgrades and capital projects, often having to pull data together yourself after hours because your team doesnāt have enough hands.ā Example outputs: - Still reconciling month-end reports while the infrastructure work keeps backing up? - Capex trackingās on fire and thereās no time to even look at ROI. - Compliance reporting eats the day before anything strategic even starts. - Francois, your forecasting workās buried behind reconciliation and board pack prep again.
.png){kind=logo}
