Read the last one you sent. Count what you asked for before you gave anything.
Most of them go like this. Congratulations, welcome aboard, we're excited to work with you. Then: we'll need your prior documentation, access to the system, a completed questionnaire, the name of your internal owner, and a signed form. Reply when you've got all five.
That's not a welcome. It's a requisition, with a greeting on top.
What it costs
The customer opens it about twenty minutes after deciding to trust you. They're at the top of the good part, and what arrives is homework from someone they've never met.
So they stall. Not out of annoyance, usually. They stall because five things is a project, the project needs a free afternoon, and there isn't a free afternoon. It goes in the pile.
Then it becomes the most expensive item in the whole first year. In a lot of businesses the single largest source of onboarding delay is one document nobody sent back, and the vendor ends up asking three separate times over several weeks. Every one of those asks costs somebody an hour, and each one makes the relationship a little more about compliance.
Meanwhile nothing is happening. The customer paid, and their experience so far is being chased.
Nobody designed this
That's the part worth understanding, because it decides how you fix it.
There was a welcome email once. Then someone noticed the analyst couldn't start without the prior documentation, so that got added. Then the system needed access, so that got added. Then a form. Every addition was individually correct, made by someone solving a real problem, and nobody ever read the result as one message from the customer's side.
It got optimized for completeness of the ask. And the ask is the part the customer experiences.
What to do instead
Split the two jobs, because they were never one job.
The first message gives. It confirms who you are, what happens next, and when. Nobody expects you to solve their problems twenty minutes after they sign. They expect to be welcomed and told what's coming.
It doesn't depend on anything, so it could go out within minutes. Be careful with that. A warm personal note arriving forty seconds after signature tells the customer a machine sent it, and the speed itself is the tell even when every word is right. Let the machine do the work and let the pace stay human.
And it should not be the person the customer is about to work with, introducing themselves. That's the expensive mistake hiding inside a good welcome email. At the moment somebody signs, the only person at your company they trust is the one who sold to them. Everyone else starts from zero. So the introduction comes from the salesperson, who has the trust to hand over, and it says why this person specifically is right for them. That's a trust transfer, and it takes about two sentences.
Someone introducing themselves cold has to establish their own credibility from a standing start, in an email, to somebody who has no reason to read it carefully. Same information, a fraction of the effect.
The second message asks, and it arrives with context and a reason. We need these two documents, and this one is what unblocks your kickoff. It can come from a different person, and often should. It can come the same day. What it can't do is be the first thing.
If you want one message rather than two, then say the ask is coming rather than making it. You'll get a note from Priya tomorrow asking for a couple of things so we can get started, so keep an eye out for it.
That costs you nothing. It converts a surprise into an expectation, which is most of the work.
The test
Read your welcome email and ask what a stranger would conclude about your company from it alone.
If the answer is that you're organized and they're in good hands, keep it. If it's that you need a lot from them before anything happens, you already know what it's doing to your start dates.
