}
Join us to elevate your outreach!
Because it describes a category rather than a problem. Every AI company opens that way, so the reader has seen the same sentence many times that week. It also raises the headcount question in the first line, which is the fastest way to get an email forwarded to nobody.
Not in a first email. The buyer deciding whether to reply is almost never the person who cares which model you use, and naming one invites a technical objection before you have a conversation. Save it for the call.
Technical enough to prove you understand their process, not technical enough to describe your architecture. One accurate sentence about how their workflow currently runs beats a paragraph about your stack.
Only if the number is theirs. A generic claim about saving twenty hours a week reads as marketing, since the reader knows you have not measured their process. Asking what the current process costs them works better than telling them.