Paitho
Manifesto · v1.2 · published Mar 2026

Stop sending
the send button.

A short document on why cold outbound became noise, who pays the bill for that noise, and what we intend to do about it.

7 min read·By the Paitho team

Outbound sales has collapsed into a volume game, and everyone knows it. SDRs send 200 templated emails a day so that five of them stick. Agencies spin up dozens of burner domains. Deliverability tools sell inbox placement the way ad networks used to sell impressions. The rep is a cost center whose only lever is more.

The defenders of the status quo will tell you this is a deliverability problem — a domain problem, a warmup problem, a timing problem. It is not. It is a message problem.

When your email reads like it was written by someone who has not met you, who is not in your industry, and who does not know what you are currently on fire about, your prospect's ignore reflex fires before the second sentence. They do not need a better subject line. They need a reason to believe there is a human on the other end of this thread who actually understood their last quarter.

The entire industry has optimized the wrong half of the funnel. Everyone is fighting for placement in an inbox that has given up on reading anything it does not recognize.

"Personalization" is not mail-merging a first name into a template someone else wrote six months ago. It is writing a letter.

Who pays

The founder who hired an outbound agency for $5,000 a month and got four meetings in a quarter pays. The prospect whose inbox is now a landfill of thinly-disguised template variations pays. The SDR paid $65k to be a drone with a quota pays. The domain reputation of an entire category of business — the cold-but-honest introduction from one builder to another — pays.

We lose, together, the single most efficient mechanism that existed for a new company to reach someone who might benefit from it. And we lose it to automation that does not, in any meaningful sense, automate the work that mattered.

What mattered

What mattered was the research. Not the sending. Sending is the cheapest thing in the chain. Research — real research, the kind a senior enterprise rep does before writing a six-sentence note to a VP — is where deals start. It's reading the 10-K. It's finding the retro on the incident. It's noticing that the company just hired three platform engineers and deciding this is the week to bring up runbooks.

For two decades, we accepted that research did not scale. You either paid a senior rep $200k a year to do it on twelve accounts, or you paid an agency $5k a month to skip it entirely. Anything in between was impossible.

It is no longer impossible.

What we're building

Paitho is not an email-sending tool. It is the research layer that was missing.

We read what a senior rep would read — hiring posts, blog signals, engineering retros, pricing pages, funding announcements, product changelogs, public Slack communities, the telltale "interim" in a VP's LinkedIn title — and we convert all of it into a pain signal: a specific, dated, cited observation that a particular company is, right now, suffering a problem your tool solves.

Then we write the note. Grounded. Specific. Short. Not "quick question" — the actual question.

A human — you, the operator — reviews. Accepts or rejects or edits. That feedback trains the model on your voice and your ICP and your winning angles, not on the median output of the internet.

Principles

01
Research is the product.
Everything else — the sending, the scheduling, the follow-ups — is a commodity. We obsess over the 12 seconds before the draft is written.
02
Never ship a template.
Every outgoing email is written from scratch against a specific pain signal. If the draft could be sent to two companies, it's a failed draft.
03
Humans review. Every time.
We do not auto-send. A human accepts, rejects, or edits every draft. The loop that closes is the loop that teaches.
04
Your domains, your data, your keys.
We touch nothing you don't own. Your sending domains. Your CRM. Your LLM keys. BYOK, or don't come.
05
Verticals, not horizontals.
A generic outbound tool is a slightly worse agency. Every pack we ship is tuned by operators who've actually sold in that industry.
06
Transparent prompts. Versioned angles.
You can read every LLM call. You can fork every prompt. Nothing the model does to your name is a black box.

Who this is for

Paitho is for the founder who does not want to hire an SDR yet, who does not trust an agency not to burn her domain, and who still wants a pipeline next quarter. It is for the operator who knows her ICP better than any outsider ever will. It is for the small GTM team that has decided good outbound is a moat and is willing to do the review work to build one.

It is not for teams that want to 10x volume. There are cheaper ways to fail at that.

What we owe you

We owe you a tool that respects your prospects' time more than it respects your send counter. We owe you published reply-rate data, per vertical, per angle — so you know what's working before you commit. We owe you the ability to leave with every byte of data you generated on the platform.

And we owe you an honest statement of what we are: a small company trying to repair one very specific thing in how builders reach other builders. If that repair looks like software today, it is only because software is the cheapest material we know of for it. The thing we actually want to bring back is the letter.

Between the raw list and the Send button, there used to be a person who had done their reading. We are building that person back.

— The Paitho team
Brooklyn · Lisbon · remote

If this reads like
your outbound, email us.

Tweaks
Theme
Accent color
Background tone