**Exactly five filled fields:** - **PROSPECT**: Name: Maya Chen | Role: VP of People | Company: Cedarloop (fictional) | Industry: B2B SaaS - **SIGNAL**: Buyer-provided mock hiring-page snapshot lists eight engineering roles | Source: fictional Cedarloop careers snapshot | Dated: 2026-10-01 | Not independently verified - **PRIORITY**: Outcome: consistent engineering onboarding | Hypothesis: coordinating new-hire handoffs can take extra effort when recruiting across teams - **OFFER**: OnboardFlow provides engineering onboarding checklists and automated owner reminders | Proof: None; no approved performance statistics - **CTA**: Ask whether to send a one-page engineering onboarding checklist | Tone: helpful, concise | Signature: Alex **Illustrative example output (not a recorded model run):** ## Personalization Basis The buyer provided a dated mock hiring-page observation for the fictional company Cedarloop; it has not been independently verified. Version A uses this conditional hiring context, while version B focuses on VP-of-People workflow ownership. Neither email claims that the company has an onboarding problem. ## Subject Lines 1. engineering onboarding at Cedarloop 2. an onboarding handoff checklist 3. a quick People-team question The first line is context-led, while the others prioritize a useful asset and the prospect's role without an invented result. ## Cold Email A Subject: engineering onboarding at Cedarloop Hi Maya, If Cedarloop is adding engineering hires right now, one useful area to review might be how onboarding tasks move between managers and People Ops. OnboardFlow puts role-specific checklists and owner reminders in one workflow, so teams can see who is responsible for each step. I'm not assuming anything about your current process; I thought a simple checklist might be useful as you evaluate what fits. Would you like me to send the one-page engineering onboarding checklist? Best, Alex ## Cold Email B Subject: an onboarding handoff checklist Hi Maya, One challenge People leaders often choose to review is the handoff between the manager, IT, and People Ops when someone joins. The tricky part is making ownership visible without adding another administrative layer. OnboardFlow offers practical role-specific checklists with task-owner reminders. I can share the underlying checklist structure even if you are not evaluating software right now, so you can see whether any part is useful for your process. Would a one-page example be helpful? Best, Alex ## Follow-Up 1 Suggested timing: Day 3–5 Subject: the checklist structure Hi Maya, A helpful way to assess engineering onboarding is to mark an owner, due point, and handoff status for each task before adding automation. That tends to reveal which steps need clearer ownership, regardless of the tools involved. Should I send over a one-page example of how the checklist is organized? Best, Alex ## Follow-Up 2 Suggested timing: Day 7–10 Subject: close the loop Hi Maya, I'll leave this here rather than add more messages to your inbox. The engineering onboarding checklist is available if a lightweight ownership map becomes useful later. No reply needed; I will step back now. Best, Alex ## QA & Send Checks Verify the mock hiring-page observation against the real prospect's current source before sending Email A. Confirm that OnboardFlow actually supports the named checklist and reminder features. Avoid claiming the team is struggling. Check sender identity, any required identification and opt-out details, and applicable outreach rules before use.