Outreach in Three Hundred Characters
Some of the most useful messages you’ll send have almost no room in them: a connection request note, an application form’s 300-character “why this role” box, a first message on a platform that cuts you off mid-sentence.
The constraint is a gift. At three hundred characters, everything decorative becomes impossible, and what’s left is the only thing that ever worked: one specific claim, one reason you’re writing.
The anatomy of a very short message
Three elements. Nothing else fits.
- A reason for contact that isn’t “networking.” One clause.
- One specific thing — what you did, or what you noticed.
- A small, single ask — or no ask at all.
That’s it. No greeting beyond a name, no sign-off, no context-setting, no explanation of what you’re generally about.
Worked examples
A connection note to a hiring manager whose role you’ve applied for.
Hi Priya — applied for the Operations Analyst role yesterday. Spent last year consolidating reporting across three regional teams that all disagreed, which looks like most of your second bullet. Happy to answer anything.
232 characters. Names the role, gives the match, offers something rather than asking for it.
A form field: “Why are you interested in this role?” (300 char limit)
Because it’s the narrow version of what I do: internal tooling rather than customer-facing. I’ve spent five years building for other engineers, and most postings for my skills aren’t that. The bit about the reporting pipeline is the project I finished in March.
258 characters, no adjectives, one real preference and one real fact.
A first message to someone whose work overlaps yours, no job involved.
Hi Tomas — you wrote up the two-page findings note format last year. I’ve been trying the same thing on a research team of three and hit a wall on getting delivery to cite it. Did you have to change how it was stored, or just the format?
A genuine question, answerable in one line, and no ask at all beyond an answer. This is the highest-response-rate species of short message and the one people almost never send, because it requires actually having read something.
A note to a recruiter who posted a role.
Hi — re the Data Analyst post: I’ve got three years rather than five, all as the only analyst at a small company, so full-cycle rather than one slice. Worth applying, or is the five a hard floor?
That question is useful to both parties and gets answered surprisingly often.
What to cut first, in order
If you’re over the limit, cut in this sequence. It works every time.
- The greeting boilerplate. “I hope this message finds you well” is 41 characters of nothing.
- Self-description. “I’m an experienced operations professional with a background in…” Replace with the one concrete thing you did.
- Anything evaluative about them. “I’ve long admired your work” is unverifiable and it’s costing you a whole sentence you could spend on a fact.
- The second reason. You have room for one. The strongest one.
- Hedges. “I was just wondering if perhaps you might” → “do you know.”
- The sign-off. In a short message, your name is enough, and often the platform already shows it.
What you never cut: the specific. If the specific doesn’t fit, you’ve kept the wrong things — start again from it and build outward.
The “just connecting” message, and why it fails
Hi, I’d love to connect and expand my professional network!
Nothing here is objectionable and nothing is actionable. It’s the message equivalent of standing near someone at a party. The recipient can accept or ignore, and either way nothing happens next, so the message has cost you your one opportunity to be memorable to that person.
If you have no reason to write, that’s genuinely fine — connect with no note at all, which is normal and unremarkable. What doesn’t work is spending the note on the announcement that you have nothing to say.
Don’t send the long version afterwards
The most common way short outreach goes wrong: a good 250-character opener, followed — immediately, before any reply — by four paragraphs of background and a resume.
That converts a light touch into an obligation, and it retroactively makes the short message feel like a hook. Send the short one and wait. If they reply, then you have permission for detail, and the detail is welcome rather than imposed.
The same restraint applies to the follow-up. One short nudge after a week, then stop.
Where the limit is a real limit
Some fields will silently truncate you. Two habits:
Write it in a plain text editor and count, rather than trusting the form’s counter, which sometimes counts differently than the backend stores.
Front-load the sentence you can’t lose. If the field truncates at 250 and you wrote 280, the reader sees the first 250. Anything essential in the last clause is gone, so the specific goes first and the pleasantries — if any survive — go last.
Why this exercise improves your long letters
Write the 300-character version of any application before you write the letter. It forces you to decide what the single match actually is, which is the decision that most letters never make and consequently spread across four paragraphs.
Then expand: the specific becomes paragraph two, the reason becomes paragraph one, and the question becomes the close. You’ll find the letter writes itself in ten minutes and reads far tighter than one drafted from the top down. If it’s still running long afterwards, what to cut when the letter runs long has the sequence.
And if the short message is going to a hiring manager cold rather than through a form, the rules shift a little — you need a subject line and a reason for the intrusion. That’s covered in cold outreach to a hiring manager.