BASHO Email: Four Sentences Built on One Insight
A BASHO email is a short cold email, usually four or five sentences, built on one verifiable piece of research about the individual recipient rather than their company. The name comes from the poet Matsuo Basho rather than from an acronym. Its defining constraint is that it cannot be produced at volume.
Key takeaways
- The research has to be about the person rather than the company, and it has to connect logically to the reason for writing, or the opening advertises effort and wastes it.
- BASHO is not an acronym. Hoffman's own published page attributes the name to the poet Matsuo Basho and to haiku that were precise and spare.
- The published shape is one insight, one connection, one proof point and one small ask, which is four sentences with a fifth optional.
- At roughly twenty minutes of research per email the format is a tier for the accounts where a single meeting matters, not a template for a whole list.
A BASHO email is a short, highly personalised cold email built on one specific piece of research about the individual you are writing to, rather than about their company. Jeff Hoffman's own page describes it as an email "built on a single piece of relevant research about the specific person" you are contacting, with the structure reduced to "One insight. One connection. One clear ask." and a length of "four sentences, occasionally five", as published on sellhoffman.com and read on 2 September 2026.
The name is not an acronym, which is the first thing most people get wrong about it. The same page attributes it to the Japanese poet Matsuo Basho, whose haiku it describes as "precise, spare, and earned every word", and that is the standard the format is asking a rep to hold: every line has to earn its place or come out.
What separates it from an email with a merge tag in it
Almost every cold email claims to be personalised. What it usually means is that a field was filled in. First name, company name, industry, headcount, a funding round scraped from a database and dropped into the opening line. That is a template with a variable in it, and by 2026 the people receiving it have seen the same variable in a hundred other messages.
A BASHO email starts somewhere else. The research is about the person, not the account, and it has to be something a machine could not have supplied: a post they wrote, a panel they spoke on, a report they published, a role change, an initiative they are visibly running. Hoffman's page calls for "one specific, verifiable, relevant piece of information about this person" and is explicit that it should not be about the company.
The second requirement is the one that gets skipped. The insight has to connect logically to why you are writing. A researched opening that leads nowhere is worse than no opening, because it advertises effort and then wastes it. If the only bridge from their post to your product is that both involve sales, the research did not qualify the send and the email should not go.
- First name, company, industry, headcount
- Available for every row in the file at no extra cost
- Identical in structure to the last hundred messages received
- Says nothing about why this person specifically
- Scales to any list size
- One verifiable thing this individual said, wrote or did
- Costs a person real minutes per recipient
- Cannot be produced from a database export
- Connects logically to the reason for writing
- Scales to the accounts worth the minutes
The structure, and why it is this short
The published shape is five steps and it is short on purpose. The opening sentence surfaces the insight, so the page tells the writer to "open with something specific about them". The second draws the line from their situation to your reason for writing. The third adds one relevant proof point. The fourth makes one focused, low friction ask. That is four sentences, and the fifth is optional.
Length is doing real work here rather than being a style preference. A four sentence email is read in full on a phone without a tap. It contains no space for hedging, no space for a paragraph about your company, and no space for the three secondary asks that usually creep in. The constraint removes the parts of a cold email that reduce reply rates, which is why the format survives as a named technique rather than as generic advice to write shorter.
The ask is the part teams get wrong most often after the research. A twenty minute call is proportionate to a first message. An hour, a demo, a discovery call with two of your colleagues and a shared document are not, and an ask that is out of proportion to the relationship reads as a request for a favour from a stranger.
- Step 1Find the insight
One verifiable, relevant thing about this person rather than their company.
- Step 2Open on them
The first sentence surfaces the insight. No greeting, no throat clearing.
- Step 3Make the connection explicit
One sentence drawing the line from their situation to your reason for writing.
- Step 4Add one proof point
A single relevant example or result that earns credibility without pitching.
- Step 5Ask for one small thing
A focused, low friction ask proportionate to a first message.
Why it matters to a sending programme
The obvious cost of a BASHO email is time. Hoffman's page puts it at "twenty minutes of research per email" and reserves the format for "the ones where a single meeting could change your quarter". That number is what makes the technique a decision rather than a template, because twenty minutes per recipient is a hard ceiling on volume and an equally hard floor on which accounts deserve it.
The less obvious cost is the one that decides whether a programme should use it at all. A researched email cannot be delegated to a sequence builder, so it does not accumulate. Every send is a fresh act of work, and a team that commits to BASHO across a whole target list has quietly committed one person full time to producing a few dozen emails a week.
The argument in its favour is that the alternative fails differently. A high volume programme running weak personalisation puts pressure on the sending infrastructure while producing replies from a small fraction of a large audience, and every non reply is a person who now associates the brand with something irrelevant. A small number of researched emails to accounts that were chosen for a reason produces fewer conversations from fewer sends, on a domain that is not being asked to carry the volume.
Both are legitimate motions. What is not legitimate is describing the first as the second, which is what happens when a team adopts the vocabulary of the format and keeps the send volume of a sequence.
How it is used in outbound
In a live programme, BASHO sits at the top of the account list rather than across it. The practical pattern is a tiered send: a researched message to the accounts where one meeting justifies the research time, and a house standard cold email to the rest, sent on the same authenticated infrastructure and against the same criteria.
Three operational points decide whether the tier works.
The research has to be recorded, not remembered. The insight goes in a field on the record with its source URL, for the same reason a price belongs to a page. A researched claim you cannot show the source of is a claim you will eventually get wrong in front of a senior buyer, and the correction costs more than the meeting was worth.
The insight decays. A post from last week is a reason to write. The same post in eleven weeks reads as an admission that the message sat in a queue. Research that is not sent inside its own window has to be redone, which means the research step and the send step belong in the same working session rather than in separate sprints.
One message per campaign still applies. The format's discipline is one insight, one connection, one ask, and that is the same rule the rest of the programme runs on. A BASHO email followed by four automated bumps has replaced a precise message with a sequence, and the person who did not reply to the first one is not more likely to reply to the fourth.
- Yes: One meeting at this account would materially change the quarter
- Yes: The insight is about the individual rather than the company
- Yes: The insight is verifiable and its source is recorded on the record
- Yes: The bridge from the insight to your reason for writing is logical rather than forced
- Yes: The ask is one low friction step proportionate to a first message
- Yes: The insight is recent enough that sending it this week still makes sense
- No: Using the format as the opening of an automated multi step sequence
- No: Treating a funding round or a headcount band as the researched insight
The measurement question is the one teams skip. A BASHO tier is worth running when its reply rate and its meeting rate justify the labour against the base lane, and that comparison is only meaningful if both lanes ran against comparable accounts in the same period. Comparing a researched tier aimed at the best fifty accounts against a broad send aimed at everybody measures the account list rather than the technique. The open rate benchmarks are the wrong instrument for that comparison too, because they describe programmes rather than tiers.
What the format does not fix
A BASHO email inherits every constraint the rest of the programme has. It arrives through the same mailbox, on the same domain, under the same sender requirements as everything else, and a researched message from a domain with a reputation problem lands in the same folder as an unresearched one. Google requires senders to authenticate, and its published guidance asks senders to "Set up SPF or DKIM email authentication for your sending domains", which is a floor rather than an advantage.
It also does not fix a list. If the person is genuinely not a buyer for what you sell, twenty minutes of research produces a well written email to the wrong reader, and the polite reply you get is not pipeline. The account list is upstream of the technique, and no amount of craft in the message compensates for a target chosen because they were available rather than because they fit.
The last thing it does not fix is the follow up problem. The format is built for a first touch. What happens after a non reply is a separate decision, and copying the researched message into a sequence is the move that converts a precision technique back into volume.
Related terms
A BASHO email is one shape of cold email, and the surrounding vocabulary is where the operational detail lives. Plain text email covers the format the message should be sent in, and spintax covers the variation technique that belongs to the volume lane rather than this one. Lead list is where the account selection that decides whether the research is worth spending gets made, and hiring signal is one example of an insight class that carries a live reason to write.
On the writing itself, how to write a cold email walks the structure the volume lane runs on step by step, and quality leads over quantity sets out the account-selection argument that decides which tier a send belongs in. If the question is which tier a given account belongs in, B2B prospecting is the filter versus signal argument that decides it.
The short version
A BASHO email is four or five sentences built on one verifiable piece of research about a specific person, connected logically to one reason for writing and closed with one small ask. It is named after a poet rather than an acronym, it is documented by the person who developed it, and its defining property is that it cannot be produced at volume.
That constraint is the whole technique. Used on the accounts where a single meeting matters, it earns its time. Used as a template across a whole list, it becomes an ordinary cold email with a longer first sentence, and the twenty minutes go to waste.
RevenueFlow runs cold email and LinkedIn outreach for B2B teams, one message per campaign, against criteria agreed in writing before launch. See how the campaigns work.
Technique description verified as of September 2026 against Hoffman's own page, and sender requirements against Google's sender guidelines. Verify current guidance with the source before relying on it.
Frequently asked questions.
Frequently asked questions- What does BASHO stand for?
- Nothing. It is not an acronym, which is the most common misunderstanding about the term. Hoffman's own published page attributes the name to the Japanese poet Matsuo Basho and describes his haiku as precise, spare, and earned every word. The point of the reference is that every line in the email has to earn its place.
- How long should a BASHO email be?
- The published format is four sentences, occasionally five. The opening surfaces one researched insight, the second connects it to the reason for writing, the third adds one relevant proof point, and the fourth makes one focused ask. The length is a constraint rather than a style preference, because it removes the hedging and the secondary asks that reduce replies.
- How is a BASHO email different from ordinary personalisation?
- Ordinary personalisation fills a field: first name, company, industry, headcount, a funding round pulled from a database. A BASHO email is built on one verifiable thing the individual said, wrote or did, which no database export can supply. The first costs nothing per recipient and the second costs a person real minutes, which is why they belong in different tiers.
- When is a BASHO email worth the research time?
- When one meeting at that account would materially change the quarter, and when the insight is recent enough that sending it this week still makes sense. Hoffman's page reserves the format for high value target accounts and for senior recipients whose filters delete anything that reads like a template. Everywhere else the volume lane is the honest choice.