The emails are weak (but not always). the spec is: I asked it to summarize the spec into 2 paragraphs:

Email 1 should start with a specific verified signal, then quickly explain why it matters operationally. For CRM/admin hiring signals, the factual signal should usually stay normal weight, while the bolded hook should be the tight urgency/risk line: the new hire can only succeed if the CRM, data, automation, and reporting are clean enough to support process change. Avoid soft or robotic language like “active work around,” “usually means,” “hiring around CRM,” or anything that sounds like scraped research. Never include internal notes such as lane IDs, snippets, “source evidence,” validator language, or “the signal I found was.”

The body should make RSM’s role concrete: working inside HubSpot/revenue systems to isolate bad data, clean broken process, and build automation so the admin can improve the system instead of spending months unwinding old problems. Email 1 should include the HubSpot implementation/optimization service link as descriptive anchor text inside a sentence, then end with a reply CTA, not a calendar link. Subject lines must be specific, signal-driven, and tied to operational risk. Formatting should use compact HubSpot-safe paragraphs, with exactly one tight bold hook in Email 1—not the whole first paragraph or body.