Loops, One Month In: What a Nurture Agent Learns From Silence

Three weeks ago we launched Loops, our sales nurture agent, with a claim that made some people wince: most days, most people get nothing — that's the feature. A loop emails a non-responder only when a genuinely new update fits them, and a second AI can veto any send.

The launch post was about the sending machinery. A month of production taught us something we didn't fully appreciate when we shipped: a nurture agent that mostly stays quiet generates a surprising amount of signal around the sends — in the replies that aren't a yes or a no, in accounts that start moving while they're parked in the loop, and in the rhythm of the loop itself.

This is the follow-up in the same spirit as our Clay field report: here's what we learned, what we changed, and four questions we'd genuinely like your take on. We're still looking for design partners who want to argue with us.

Lesson 1: the most valuable reply is "not now" — and nobody was keeping it

When nurture emails get replies, the interesting ones are rarely "yes, book me" or "never contact me again." They're the middle class: "We just signed a two-year contract, check back next year." "Mid-reorg, try me in Q2." "After our ERP rollout."

That's not a rejection. It's a prospect telling you, in writing, exactly when to come back — and in most stacks it gets a mental note from the rep and then evaporates.

So Loops now has a reply reader: a small model reads each reply to a loop email and files it as interested, no, not now, automated, or other. A "not now" puts the person on a Not now, contact later list with four things attached:

• their exact words — the shortest passage that shows the intent, copied verbatim, never paraphrased
• the follow-up date they asked for, worked out from the reply ("next fiscal year" becomes an actual date)
• the date they said it, and which rep the reply came to

A later "no" takes them off the list. A later "interested" does too — for the opposite reason. And if your CRM already has a field that means "not ready yet," Loops can import those people onto the same list, so the parked pipeline from before Loops existed isn't lost either.

The list isn't an archive — it's a queue. "Not now" replies get tagged where reps already work (Today and Actions), and from the panel a rep can add those people straight into their own loop, so "check back in Q3" becomes a loop entry instead of a calendar reminder nobody sets.

The design principle we landed on: never paraphrase the prospect. The rep who picks this person up in February needs the sentence the prospect actually wrote, not a model's summary of it. Summaries drift; quotes don't.

Lesson 2: a nurture agent has to know when to get out of the way

The second thing a month of production made obvious: sometimes an account heats up while a person is sitting in the loop. New visitors from the account on your site, fresh intent, a signal spike — the kind of movement we built the whole signal layer to catch.

The wrong behavior is for the loop to keep cheerfully queueing its next nurture email. Nurture is for the cold middle. The moment an account is moving, it's human work.

So when an account heats up, the loop now pauses that person and files a card into the rep's Actions — "Account heated up," with the reason and who at the account triggered it. The loop page says it in plain past tense with dates: "Account heated up Oct 7 · loop paused until Nov 6." If the account cools back down before the rep gets to it, the card says that too, and the loop resumes on its own.

This changed how we think about the product. Loops isn't just a sender — it's a holding pattern with an ejection seat. The measure of a good nurture agent isn't only "did it send relevant emails," it's "did it notice the moment this stopped being a nurture situation?"

Lesson 3: we got the tempo wrong at launch

Two honest misses from v1, both about rhythm rather than intelligence:

The monthly brief was too slow. Loops researches your company — your posts, your launches — into a brief the loop writes from. We rebuilt it every 30 days, which meant a post you published on the 3rd could wait four weeks before any loop could use it. For an agent whose whole pitch is "only send when there's something genuinely new," a month-old definition of "new" is self-defeating. The brief now rebuilds weekly, and a rebuild no longer costs the loop a day of sends while everything re-enters review — only actually-new items are held back for your approval. (The old 30-day shelf life stays as a safety net, so a failed weekly build never leaves a loop with no brief at all.)

One focus at a time was too narrow. Focus steering lets a rep tell the loop "lead with this update." But reps kept having two or three live things at once — a launch, an event, a case study — and the loop forced a single bet. A focus can now hold one to three updates, and for each person the loop's judge picks whichever of them fits that person best. You set the emphasis; the per-person matching stays with the agent.

There's a theme in both fixes: the agent's judgment was fine, but the clock around it was built for our convenience, not the prospect's. Weekly research and multi-update focus existed in no spec — production pointed at them within two weeks.

The unglamorous column

A month of real sends also produced a stack of rules that will never be in a demo but decide whether reps trust the thing:

• One nurture email per company per day, and one person per company per update — two colleagues comparing near-identical "personalized" notes at lunch is how trust dies
• Sends still waiting on delivery count against the day's budget — the loop can't over-commit because the mail server is slow
• An unknown company industry no longer vetoes an otherwise-fitting update, and "fit unclear" stays a visible state rather than a silent drop
• The people page grew up: server-side sorting on status, fit, priority, last/next email and latest decision; a "Heating up" filter; CSV import and hand-adds with tags; and a person panel with the whole company timeline — because the fastest way to lose a rep is to make the loop's reasoning hard to inspect

That last point is the quiet thesis of the whole month: every state needs a visible reason. The launch post promised a plain-English reason for every excluded person; v2 extends that to every pause, every skip, and every "not now."

What we're still arguing about

Four open questions, numbered so you can answer them by number:

1. Should a "not now" ever re-enter a loop automatically when its follow-up date arrives — or is that a decision a human should always re-make?
2. How hot is too hot? Right now a heated account pauses nurture and pings the rep. Should a mildly warming account instead change what the loop sends, rather than stopping it?
3. Is weekly the right brief cadence — or should a genuinely big update (a launch, a funding round) be able to force an immediate rebuild?
4. Focus caps at three updates. Would you want more, or is three already flirting with "newsletter"?

Reply, comment, or grab 15 minutes. We're looking for design partners running real nurture volume — the not-now reader and hot-account cards are live today, and the people shaping what ships next are the ones in the room.

Loops is part of MarketBetter — the signal layer finds the accounts in motion, humans stay on the send, and Loops keeps everyone else warm until their timing is right.