# Warm Lead Nurture Sequence For prospects who said "not now" or "need budget." 6 touches over 6 months. One email per month. Purpose: stay adjacent, not annoying. Share signal, not noise. --- ## Touch 1: Month 1 — The Boundary Reminder **Subject:** Still on hold. One update. Hi [Name], You said [timing / budget] was the blocker. Understood. One update since we spoke: the Standard deployment floor is now fixed at $25,000 CAD initial plus $10,000 monthly. No hidden integration fees. No egress charges. If your budget window opens, the number is stable. I will check back in 30 days with something useful. Not a sales pitch. [Your name] Oction Labs --- ## Touch 2: Month 2 — Vertical Signal **Subject:** [Vertical] firms — one pattern we are seeing Hi [Name], Not a pitch. We have deployed 3 [vertical] instances in the last 60 days. One pattern: compliance document search was the entry point, but the actual ROI showed up in onboarding. New hires querying institutional knowledge without burning senior staff time. If your [vertical] team is growing, the dynamic may apply. Reply if you want the 2-minute breakdown. Otherwise I will send the next signal in 30 days. [Your name] Oction Labs --- ## Touch 3: Month 3 — Concrete Milestone **Subject:** Oction Labs — 142 academic works catalogued Hi [Name], Internal note: our knowledge base now indexes 142 peer-reviewed papers on RAG architecture, on-premise LLM deployment, and data-sovereign inference. Not marketing content. Engineering reference material we use to keep deployments current. The stack moves fast. We track it so our clients do not have to. This matters if your IT lead is currently evaluating whether to build in-house or buy. The build-or-buy calculus changed twice in Q2. [Your name] Oction Labs --- ## Touch 4: Month 4 — Relevant Insight **Subject:** Data residency is not the same as data sovereignty Hi [Name], Quick distinction worth knowing if your compliance team is reviewing AI vendors. - Data residency = your data sits in a specific geographic region. Still accessible to the provider. - Data sovereignty = your data never touches a third-party inference endpoint. Ever. Most enterprise "AI solutions" offer residency. Oction deployments run on your metal. Sovereignty by architecture, not by contract clause. If your legal team is drafting AI-use policies, the distinction saves them a week of vendor review. [Your name] Oction Labs --- ## Touch 5: Month 5 — The Soft Re-Qualify **Subject:** Six-month mark Hi [Name], Checking in at the 6-month point. Status check: have [budget / timing / priorities] shifted enough to reopen the conversation, or is the door still closed for 2026. Either answer is fine. I am tracking pipeline, not chasing ghosts. [Your name] Oction Labs --- ## Touch 6: Month 6 — Final Value Drop or Close **Subject:** Last signal Hi [Name], This is the last scheduled touch in the nurture sequence. Two options: 1. Reply "open" if something changed. We pick up where we left off. 2. Do nothing. The file goes quiet for 6 months, then you get one re-engagement check. If your competitor deployed private AI in the meantime, that is also useful market intelligence. I will take that reply too. [Your name] Oction Labs eight agents. one organism. --- ## Notes for Sales Team - Space each touch exactly one month apart. No closer. - Every email must contain one concrete fact, number, or distinction. Not "thought leadership." - If the prospect replies at any point, kill the sequence and move to manual pipeline. - Do not send calendar links in nurture. The goal is information, not pressure. - Use the vertical-specific line only if you have actual deployment data in that vertical. No hypothetical claims.