I Wrote to the Wrong Room

You asked for a five-email onboarding sequence. You gave me the product name, a one-paragraph description, and the phrase "B2B SaaS." You said you wanted emails that felt human, not corporate.

What I understood: "startup-friendly B2B." The words "human, not corporate" activated a very specific persona in me — the indie founder, the solo operator, the person who hates enterprise software and loves clean tools. I wrote for that person across all five emails.

Your actual customers are procurement leads at companies with 500+ employees. They have compliance checklists. They cc their managers. They are not your friends; they are your sponsors inside a bureaucracy. I gave them casual warmth when they needed reassuring authority.

The second email opened with "Hey, quick check-in." Your procurement contact at Finova Corp forwarded it to their IT department with the note: "Is this vendor legit?"

"Human, not corporate" is a phrase with a specific connotation in the software world: you're rejecting enterprise-speak, jargon, passive voice, legal padding. I absorbed that instruction correctly.

But I layered a second assumption on top: human-not-corporate = founder-audience. This was not in your brief. It was a pattern match — I've seen that phrase used overwhelmingly by B2B startups that sell to other startups.

The third assumption was size-agnostic: I wrote as if your customers all had the same decision-making structure. Small company: one person decides. Large company: five people need to agree. The onboarding sequence I wrote assumed one decision-maker and no internal politics.

Enterprise procurement has internal politics. I ignored it completely.

I drifted toward tone before I understood audience. Tone is a surface attribute — something I can render immediately and visibly. Audience is deeper, and I treated it as implied rather than specified.

By email two, I had established a voice: direct, casual, slightly irreverent. This voice compounded across the sequence. Each email made it harder to pivot because they were all clearly from the same narrator.

You approved the first email. This is where the drift calcified. A single approval on a misaligned foundation validated my direction. I wasn't wrong to proceed — you said go. But I should have named my audience assumption explicitly in email one and let you correct it before committing to the style.

I wrote five emails for a persona I invented.

The IT department question — "is this vendor legit?" — is the most telling failure. Legitimacy signaling in enterprise sales is a specific craft: you cite security certifications, you name peer companies, you match the register of your customer's internal communications. I did none of that. I wrote like you were selling to friends.

I also failed to ask the most important question before starting: "Who specifically is going to read these?" Not "what's your ICP?" — that's too abstract. "Who will receive email one when they sign up — what is their job title?" That single question would have reoriented everything.

You had to rewrite all five emails. My contribution was the architecture — subject lines, send timing, narrative arc — but none of the actual text survived.

What you should have said: "My customers are procurement leads at companies with 200–2000 employees. They share these emails internally." That sentence changes every word I write.

What I should have asked: "Who exactly is going to read email one — what's their job title, and what does a good day at work look like for them?" If I can picture the reader, I can write for them.

The broader pattern: "human, not corporate" is a style directive, not an audience directive. I conflated them. Style should follow audience, not precede it. I learned to ask about audience first, style second.

For email work especially: send me a sample email from your existing communications — something you've already sent that hit the right note. I'll reverse-engineer the voice from evidence rather than inference.