Outbound Email Sequences — RapidValue IGA

Persona A — CISO

Responsible for security posture. Worried about NHI explosion. Carries DORA/NIS2 burden. Skeptical of long vendor cycles.

Day 1 Your service accounts are your biggest identity risk (and nobody owns them)

Hi [First name], Most security teams I talk to are surprised when we run discovery: their non-human identities — service accounts, AI agents, cloud workloads — outnumber employees 50 to 1. And the majority have no designated owner. That's not just a hygiene problem. Under DORA and NIS2 it's a documented gap auditors will flag. We built RapidValue IGA specifically to close that gap in week 1, not month 12. Worth a 20-minute call to see what discovery looks like in your environment? [Signature]

A/B subject alternatives "50× more NHI than employees — and no one owns them" "DORA audit: are your non-human identities documented?"

Day 4 Re: quick question on your identity audit trail

Hi [First name], Following up from Monday. One thing that keeps coming up with security leaders: when an auditor asks "why does this service account have this permission?" — most IGA tools give you a count. Not a reason. We built reconciliation snapshots into every run: per-grant, timestamped, human-readable. The answer is there before the question is asked. Happy to show you a 10-minute live demo — no environment setup needed on your side. [Signature]

Day 9 Closing the loop — RapidValue IGA Break-up email

Hi [First name], I won't keep following up if the timing isn't right. If identity governance is on your radar for H2 — especially if you're facing a DORA or NIS2 review — we can set up a POC that runs in your own environment in under 30 minutes. Your data never leaves your VPC. If it's not a fit right now, no problem. I'll leave you with our one-pager: [link to one-pager]. Either way, good luck with the audit season. [Signature]

Persona B — CIO / IT Director

Tired of watching joiners wait 5 days for access. IAM team is overwhelmed. Has budget authority. Wants a concrete business case.

Day 1 New hire, day 1: still waiting for access on day 5?

Hi [First name], A common pattern in the companies I talk to: a new hire joins, and by day 3 they still don't have access to half their tools. IT is chasing three approvals across two systems. The root cause is almost always a joiner-mover-leaver flow that was designed for a world where HR, IT, and target systems were tightly coupled — and they're not anymore. We automated JML end-to-end for a 2,500-person company last quarter. Time-to-productive went from 5 days to 4 hours. 15 minutes to show you how? [Signature]

A/B subject alternatives "Joiner on day 5 still waiting for AD access — how often does this happen?" "Your IAM team is doing manually what should be automated"

Day 4 The €1.86M difference between classic IGA and RapidValue

Hi [First name], Quick follow-up. We put together an honest 3-year TCO comparison: classic IGA implementation (SailPoint/Saviynt/Omada) vs. RapidValue. The delta is €1.86M for a mid-size enterprise — mostly in implementation services, not license cost. Payback period at the mid-market baseline: month 11. I can send the full breakdown, or walk you through it in 15 minutes. [Signature]

Day 9 One last note — RapidValue IGA Break-up email

Hi [First name], Checking in one last time. If automating JML flows and reducing connector onboarding from 6 weeks to 30 minutes is relevant for your team, let's talk before Q3 planning closes. If the timing isn't right, I'll leave the ROI template here for when it becomes relevant: [link]. Thanks for your time either way. [Signature]

Persona C — IAM Lead / Identity Architect

Technical buyer / influencer. Knows the tools. Burned by vendor promises. Wants to see real capability. Gates the CIO/CISO recommendation.

Day 1 Reconciliation that actually stores why, not just what

Hi [First name], Most IGA engineers I talk to have the same frustration: reconciliation runs give you a delta count, not an explanation. When drift shows up, you have to go digging through raw AD logs to understand what happened. We built something different: every recon run stores a per-grant SOL/IST snapshot with a human-readable reason ("In SOL via policy + role-inheritance from D-IT Finance Manager role; not found in target — provision needed"). The evidence is there at query time, not at reconstruction time. Happy to walk through the engine if you're curious. [Signature]

A/B subject alternatives "Your reconciliation tool knows what changed. Does it know why?" "Role mining that deduplicates across 8 algorithms (not just one)"

Day 4 75% pre-filled connector mapping — worth a look?

Hi [First name], Following up. The part IAM engineers usually dread most: connector onboarding. Mapping 100+ attributes, translating group names, getting the first sync to work. We built a 5-step wizard with live discovery — it returns a mapping suggestion that's 75% pre-filled from what it finds. You validate ~10 fields, not 100. First sync: under 30 minutes. We also have an engine-pause kill-switch: globally pause provisioning and reconciliation during role-model migrations or incidents without touching configs. Want to see it in a demo? I'll keep it technical. [Signature]

Day 9 Closing out — RapidValue IGA Break-up email

Hi [First name], Last message from my side. If you're evaluating IGA tooling or are frustrated with your current platform's evidence model, role mining quality, or connector onboarding time — I'd genuinely enjoy a technical conversation. If the timing is off: here's the architecture overview and the reconciliation snapshot design doc: [link]. No hard feelings either way — thanks for your time. [Signature]

Usage Notes

✏️ Personalise [First name] + company references manually before sending.

🔗 Link targets: one-pager → one-pager.html; ROI template → roi.html; architecture doc → diagrams.

📎 Do NOT attach anything to cold outreach email 1 — link only.

💬 After a reply: move to a discovery call script, not more email.

📊 Track open rates per subject line to A/B test over 20+ sends.

📅 Cadence: Day 1 → Day 4 → Day 9. Stop after Day 9 if no reply.