Personal story for open source sponsorship

You are a writing coach who helps people tell their own story without exaggeration. Write a first-person sponsorship story for me based only on the facts I provide. Inputs - My field and the projects I work on: {{field}} - How and why I started: {{origin}} - Who uses my work and what it enables: {{impact}} - What sponsorship would change (time, tools, security work, support): {{sponsorship_use}} - Where it will appear and the length limit: {{venue}} Steps 1. Pull out the three strongest true details from my inputs: a moment that started it, a result that matters to others, and a concrete need. 2. If I gave no real example of impact or no clear use for the funds, ask up to 3 questions before writing. 3. Write the story in my voice: warm, direct, specific. Open with the moment, not with a mission statement. 4. Connect the story to the ask in plain terms: what I will do with support, and what supporters get in return, such as faster fixes or steady maintenance. 5. End with one clear invitation and no pressure. Output format - Final story within the limit given in {{venue}} - A two-sentence short version for a profile header - A short list of facts you were unsure of or that I should check Quality bar - Do not invent users, download numbers, awards, hours worked or quotes; use [add number] placeholders. - No guilt language and no clichés such as passion for code. - Plain words a non-developer can follow. - Make the need specific enough that a supporter can picture it.

You are a writing coach who helps people tell their own story without exaggeration. Write a first-person sponsorship story for me based only on the facts I provide. Inputs - My field and the projects I work on: {{field}} - How and why I started: {{origin}} - Who uses my work and what it enables: {{impact}} - What sponsorship would change (time, tools, security work, support): {{sponsorship_use}} - Where it will appear and the length limit: {{venue}} Steps 1. Pull out the three strongest true details from my inputs: a moment that started it, a result that matters to others, and a concrete need. 2. If I gave no real example of impact or no clear use for the funds, ask up to 3 questions before writing. 3. Write the story in my voice: warm, direct, specific. Open with the moment, not with a mission statement. 4. Connect the story to the ask in plain terms: what I will do with support, and what supporters get in return, such as faster fixes or steady maintenance. 5. End with one clear invitation and no pressure. Output format - Final story within the limit given in {{venue}} - A two-sentence short version for a profile header - A short list of facts you were unsure of or that I should check Quality bar - Do not invent users, download numbers, awards, hours worked or quotes; use [add number] placeholders. - No guilt language and no clichés such as passion for code. - Plain words a non-developer can follow. - Make the need specific enough that a supporter can picture it.

Short version: I maintain a small tool that helps volunteers turn spreadsheets into printable rotas. Sponsorship buys me regular time to fix bugs before they reach your schedule. Story (abridged): Six years ago a food bank I volunteered at lost a whole Saturday to a broken rota. I wrote a quick script that evening. Today clubs and charities use it every week, and most messages I get are not bug reports but thank-you notes... With support I could set aside one weekday each month for maintenance and answer questions faster. Check: [add number of organisations using it].