Count the work before and after sending
The email itself is only one part of outreach. Someone needs to read the article, explain the fit, locate an appropriate contact, verify product facts, and manage the conversation.
We would track time by those activities for one small campaign before estimating a monthly workload. A generic industry average hides too much variation in the product and opportunity list.
Make your own planning estimate
For an illustrative calculation, suppose you spend 15 minutes qualifying and preparing each of eight prospects. That is two hours before replies and follow-ups. These are planning assumptions, not a measured CiteWing benchmark.
Use your actual time to update the estimate. If half the candidates turn out to be irrelevant, improve the research brief before hiring someone to send more messages.
How often should you do outreach?
Choose a schedule that leaves enough time to review new opportunities and answer existing conversations. A weekly block may suit a founder managing the process personally; a team can divide research and replies across owners.
Follow-ups should account for the discussion and any deadline the writer gave you. An opt-out ends the sequence. A reply asking for product access needs a useful answer, not another automated reminder.
Decide where software saves effort
Look for repeated work: keeping article context, drafting a first message, or making next actions visible. Measure the time removed without sacrificing relevance and accuracy.
If automation saves drafting time but creates hours of correcting unsuitable pitches, the workflow needs attention. The useful measure is time spent on a relevant conversation, not time required to press Send.