About
Tendthread is built and run by one person. It exists because the part of outreach that actually decides the outcome — following up, patiently, for weeks — is the part everyone drops.
Who builds this
Ali Arif.I write the product, answer the email, and make the decisions about what it will and will not do. There is no team behind the “we” on the rest of this site, and saying so seems better than implying otherwise.
If you write to Tendthread, I am who replies. That is the main practical thing to know.
Why it exists
First emails are easy. It is the fourth one, three weeks later, on a thread you have half forgotten, that decides whether anything comes of it — and that is the one nobody sends. Not out of laziness: it takes remembering the context, judging whether enough time has passed, and writing something that is worth reading rather than a nudge.
The tools that automate this mostly solve the wrong half. They make it easy to send a great many emails, which is the thing that was never hard, and they do it from a shared sending domain that has nothing to do with you. Tendthread sends from your own mailbox, in the existing thread, and stops the moment someone replies.
What it will not do
The constraints matter more than the features, so they are written down rather than assumed:
- It will not invent things. Every draft is checked against the facts it was actually given before it can send. A draft claiming a previous email, an attachment or a piece of research that does not exist is rejected, not sent.
- It will not send from a relay. Follow-ups go from your address, through your mailbox provider, in the thread the recipient already has.
- It will not run a purchased list. Where leads may come from is a term of the acceptable use policy, not a preference.
- It will not keep going once someone answers. A reply stops the sequence. That is the whole design.
Where it is
Tendthread is early. It is being built in the open in the sense that matters: the limits are published before there is anything to charge for, the security page says what the mailbox permission actually covers rather than the flattering version, and the privacy policy says plainly that nothing is deleted on a schedule yet — because it is not.
Questions, objections and bug reports all go to hello@tendthread.com, or see the contact page for the address that fits what you need.