Writing the ask
Pitch at the right technical depth, combine story with evidence, and run the review cycle that catches what you have gone blind to.
By the end you can
- Adapt technical depth to an engineering audience or a general one
- Combine authentic storytelling with logic and emotional appeal
- Run a three-pass review cycle that catches hidden knowledge gaps
Before writing a word, answer two questions: what do you want, and who is reading it? Almost every weak sponsorship email fails one of those, and no amount of polish rescues it.
Pitch at the right depth
Adapt technical depth dynamically. The same facts, aimed at the wrong level, read as either condescending or incomprehensible.
Writing to an engineering firm, lead with your tool systems and your process. Name the CAD package — Onshape, Fusion, and talk about iteration, tolerances, design reviews, and what you tried that failed. These readers recognise real engineering work, and they are evaluating whether you are doing any. Assume they know what a servo is.
Writing to a general audience, a local restaurant owner, a community foundation, a retired neighbour — drop to plain terms. Explain what FTC is in one sentence. Explain that a season runs September to spring. Lead with students, learning, and community rather than mechanism design. Assume nothing.
Never leave a gap for the reader to fill
Every unexplained term is a place your argument quietly falls apart. A reader who hits "we ran into an issue with our PID loop on the linear slide" and does not know what that means stops evaluating your request and starts feeling excluded. They do not reply to say they were confused. They just do not reply.
Professional does not mean formal
The goal is to be easy to understand, not to sound impressive. Dense, formal writing is harder to read, and harder to read means less likely to be finished.
- A long word that makes a sentence harder to read is a worse word. Big vocabulary does not make you look smarter to someone who has to reread the sentence.
- Short paragraphs. Your email is being read on a phone between meetings.
- One clear ask. If the reader finishes and is unsure what you want them to do, the email failed regardless of how well written it was.
Combine story, logic, and emotion
The three work together, and teams almost always lean on only one.
- Authentic storytelling
Who your team is, where you started, what you have achieved, and your past failures and what you did after them. The failures are what make it credible. A team that says everything went perfectly is either lying or not attempting anything difficult.
- Logic and evidence
Real numbers. Students on the team, children reached through outreach, hours of build time, what the season costs, what their specific contribution would fund. Numbers are what let a sponsor justify the decision to someone else internally.
- Emotional connection
Why it matters, to the students, to the community, to the reader's own stated mission. This is what makes someone want to help, and it is the part that turns a request into a decision.
A weak opening
Hi, we are a robotics team and we are looking for sponsers. Any amount helps. Please let us know if your interested.
Two spelling errors, opens as if they know you, no name, no specifics, and it could have been sent by any team anywhere. There is nothing here to say yes to.
A stronger opening
Dear Ms. Alvarez,
I'm writing on behalf of FTC Team 26336, a student-run robotics team and registered nonprofit in Sammamish. Last season we taught introductory robotics to over 100 elementary students through free weekend classes, and competed at the regional championship.
I saw that supporting local STEM education is part of your community giving programme. We use your sheet metal service for our drivetrain plates, and I wanted to ask whether you would consider supporting our season directly..
It names a person, establishes legitimacy immediately, leads with a concrete outcome rather than a need, connects their stated mission to real work, and makes a specific ask.
Run a real review cycle
Three passes, in this order. Skipping to the last one is the most common mistake.
-
Spelling and grammar checkers. Non-negotiable and takes seconds. A typo in the first line of an email to a company undoes an hour of good writing, and it is the one flaw that is genuinely unforgivable because it signals you did not care enough to check.
-
Team peer review. Every sponsorship document gets read by teammates before it goes out. Catches factual errors, wrong numbers, and claims the team cannot actually back up.
-
External proofing by someone outside robotics. A friend or parent who does not do FTC. This is the pass that matters most and the one teams skip.
Hidden knowledge gaps. You have been inside FTC long enough that you no longer notice which terms are jargon. Ask your reader to mark every word or idea they were not sure about, and do not argue with the marks — every one is a place a sponsor would have stalled.
Speaking it out loud
The same rules apply when you are talking to someone at an event, with two additions. Be visibly excited — if you are not interested in what you are describing, nobody listening will be, and flat delivery reads as a team that does not believe in itself. And do not wait to be approached. People rarely walk up to a table and ask to hear about robotics. You start the conversation.
Check yourself
You are writing to the owner of a local restaurant chain about sponsoring your team. How should the email read?
One last thing worth saying out loud: the email only has to earn thirty seconds of attention. The document it points to does the rest, and that is the next lesson.
Finished this lesson?
Mark it complete to track your progress.