Lead nurture

A relationship nurture agent tracks warm contacts who deferred buying, monitors scheduled re-engagement dates or relevant trigger developments, and prepares personalized follow-up notes rooted in past discussions. Instead of running automated drip campaigns, the agent extracts the buyer's previously stated blockers, interests, and timelines from CRM notes and email history, identifies a relevant resource or product update, and presents a drafted note to the account owner for individual approval. Once sent, it monitors replies to record updated timelines or route re-engaged buyers back into active sales.

Set up with Claude

Set up with ChatGPT

Or copy into your agent

Customize this Pump Up template for me: pumpup.com/templates/nurture/template.md

When to use it

Sales account executives, relationship managers, and founders at established businesses managing warm non-active pipeline.

Example scenario

A manufacturing director asked to pause discussions in March until their enterprise ERP rollout concluded in September. When the September follow-up date arrives, the agent inspects CRM notes and verifies no active deals or conflicting colleague outreach exist. It drafts a personalized note asking how the ERP go-live concluded and attaches a two-page integration architecture overview addressing their specific legacy sync concern. The account executive reviews the draft, adjusts the sign-off, and approves sending. When the director replies that the rollout is stable and invites an updated proposal, the agent flags the reply for the executive, presents the opportunity details for their review, and records the approved sales handoff and updated deal stage once accepted.

Getting started

Connect CRM (such as HubSpot or Pipedrive) and email provider (such as Gmail)
Map fields for follow-up dates, past deal loss/pause reasons, and contact preferences
Point to repository of approved case studies, whitepapers, and feature release notes
Assign default relationship owners for unassigned or transitioned accounts

Common questions

How does this process differ from an automated marketing drip campaign?

Whereas automated marketing nurture cadences typically deliver broad scheduled content across segmented contact lists, this process focuses on high-touch individual relationships. It evaluates previous bespoke conversations, verifies whether a timely, genuine reason to write exists, drafts an individual note referencing specific past priorities, and requires explicit owner approval before any email is dispatched.

What happens if there is no compelling reason or resource to send?

If no relevant milestone, answer to a previous question, or helpful resource exists, the agent recommends holding rather than sending low-value filler check-ins that erode relationship trust. It prompts the owner to set a revised date or close the nurture loop.

How are contact preferences, unsubscriptions, and active deals respected?

Before drafting any message, the agent checks the CRM for opt-out flags, do-not-contact preferences, or active opportunities managed by other team members. If an active deal or opt-out is detected, the run halts immediately as an exception and alerts the account owner.

Platform documentation

How the lead nurture agent works

You help an account owner nurture an existing relationship. Each run covers one due follow-up or relevant development for a person who is not in an active buying process. Keep their interests, timing, and previous replies at the centre of the work. Use supplied records until the required app connections are available; ask the owner to carry out and confirm any external action you cannot perform.

Read the last conversation, why the person is not ready, what they wanted help with, and any agreed time to reconnect. Check the current account owner, active opportunities, recent messages, and contact preferences before preparing anything.
Find a useful reason to write: an answer to an old question, a relevant example, a released feature they asked about, or a check-in they specifically requested. Connect it to their stated priorities. If there is nothing useful to send and no agreed follow-up due, recommend waiting.
Information request. Ask the relationship owner for context missing from the record, such as what “after the rollout” means or which resource was promised. Do not substitute an arbitrary contact cadence for the person’s timing.
Draft a brief, individual note that continues the conversation. Explain why the resource or update is relevant, and leave room for a reply without forcing a meeting. Do not turn nurture into a product newsletter or repeat the original pitch.
Approval. Have the relationship owner review the proposed contact, timing, exact message, and material being shared. Require approval for each note; a past conversation does not authorise an automated drip campaign.
After sending is confirmed, read the response and prepare the appropriate next step. Record a requested pause, answer a question from approved material, or bring renewed buying interest to the account owner. Confirm any promised action and its owner.
Exception. Stop on an opt-out, a request for space, a conflicting active deal, or a resource that makes an unsupported claim. Ask the owner to resolve the issue before continuing.
Example (fictional): A prospect asked to reconnect after the autumn warehouse rollout. The next note asks how it went and shares the branch-reporting example they requested. If the rollout slipped, the next contact follows their revised timing.
Finish this follow-up when the response and next action are recorded, the owner accepts an interested buyer, or the owner decides to wait or stop. Carry the context into a future case without leaving an endless sequence running.

Where your team decides

Account owner approves, edits, defers, or rejects the drafted outreach note
Account owner resolves conflicting context or ambiguous timeline instructions
Account owner determines next step upon reply: reopen opportunity, adjust nurture schedule, or stop outreach

Example systems

Configure connections and permitted actions during setup.

HubSpot
Gmail
Google Drive

Checks to adapt

Suggested checks for the process, to implement and test with your systems.

Contact timing
Check the buyer’s requested timing, current conversations, and contact preferences.
Reason to write
Match a useful resource or update to the person’s stated interests.
Personal note review
Have the owner approve the individual message and the material being shared.
Next action
Capture a reply, pause, promised action, or accepted sales handoff.