RReshape.
← All articles

Reactivation Email Drafts in Claude: 81 Drafts and a Daily Send Limit of 40

By Alex Regueiro · November 17, 2026 · 5 min read

Eighty-one reactivation emails were drafted during a single call, and the harder question came right after: how do you send them without flooding people or losing track of who replied? The answer was a daily batch limit and one place to run it from.

The owner runs a data service that sells to real estate investors. The business had dormant contacts to win back, a stack of business cards from networking events, and several tools that did not talk to each other. We built one Claude operating hub on top of them.

The situation

The owner wanted to reactivate contacts who had gone quiet. Meanwhile there was a stack of unprocessed business cards from recent networking events. That was potential outreach, and none of it was in a system.

The owner also ran a second real estate business and did not want the two mixed together. That requirement shaped the build.

What was scattered

Operations lived in several places at once. Email was in Gmail, files were in Google Drive, meetings were on the calendar and booking links were in Calendly. Payments came through a payment platform, and some clients paid in other ways that the revenue view could not see.

Property emails from vendors were handled by hand: a virtual assistant and a chain of forwarded messages. Decisions, weekly plans and outreach notes had no single home.

What we built

On the call we built the operating hub in Claude and connected Gmail, Google Drive, Google Calendar, Calendly and the payment platform. It holds the decisions, the weekly plan, outreach tracking and the roadmap in one place, and the owner is to operate from it each morning.

Then we used it for the first job. Claude generated 81 reactivation email drafts during the call, each with a Calendly booking link and source tracking. The plan is to send them in batches of 40 drafts per day, so volume stays steady.

  • The two businesses stay in separate Claude artifacts, so nothing from one leaks into the other.
  • The owner will photograph the business cards and upload them to Claude for outreach.
  • A workflow to parse the vendor property emails is next, replacing the manual forwarding.
  • A results-tracking template for clients is on the list, because the new positioning is to track results together with clients, not only deliver data.

What changed

Sending was still ahead when the call ended, so there is no reply or booking number to report. What changed is the process: the drafts exist, the daily volume is capped, and every email carries a booking link and source tracking.

A check-in was set for the end of the first week of sending, to review how it went and refine from there.

What to take from this

If you have past customers you have not contacted, cap the daily send volume before you write a single email. A batch limit gives you a clean read on replies and helps you avoid sending more than you can follow up on. Put a booking link and a source label on every message so you can see where replies come from.

Frequently asked questions

How many reactivation emails should I send in a day?

There is no universal number. In this case the plan was batches of 40 drafts per day from a set of 81. The point is to pick a volume you can follow up on and hold it steady, so replies can be read batch by batch.

Can Claude draft reactivation emails from my own data?

Yes, once it is connected to the places your data lives. Here Claude was connected to Gmail, Google Drive, Google Calendar, Calendly and a payment platform, and it produced 81 drafts during the call, each with a booking link and source tracking.

Why keep two businesses in separate Claude artifacts?

The owner did not want the two businesses mixed together, so each has its own artifact. Separate spaces help keep contacts, plans and outreach for one business from showing up in the other, which also makes each one easier to review.

Did the reactivation emails produce bookings?

Not yet at the time of the call. The drafts were ready to send, and a check-in was set for the end of the first week of sending to review what happened.

If you have a list of past customers sitting idle, book a 30-minute AI follow-up and reporting audit. We look at where the list lives and show you how a capped daily send could run.