The honest answer is that no universal number exists, and any number you copy from a published benchmark was calculated for a different motion. The useful approach is to derive the target from your own conversion math, then check whether the resulting workload fits inside a real working day.
Deriving the number from your funnel
Work backward from the pipeline requirement.
| Step | Input | Example logic |
|---|---|---|
| 1 | Pipeline needed per rep per quarter | From quota and coverage requirement |
| 2 | Opportunity count | Pipeline divided by average deal size |
| 3 | Meetings required | Opportunities divided by meeting-to-opportunity rate |
| 4 | Touches required | Meetings divided by touch-to-meeting rate |
| 5 | Daily target | Touches divided by selling days in the quarter |
Different roles need different targets
SDR output is meetings created, so volume drives the result and a daily touch target makes sense. AE output depends on advancing a smaller set of open deals, where a single well-prepared multi-threaded conversation beats twenty logged emails. Applying one activity standard across both roles produces AEs who optimize for the log instead of the deal.
Segment matters as much as role. Enterprise cycles carry larger buying committees and longer timelines, so touch volume per deal rises while deal count per rep falls. Transactional motions invert both. Comparing a rep in one segment against a rep in the other on daily activity count tells you nothing about either.
Where activity targets go wrong
Any activity number that becomes the goal stops measuring the thing it was built to measure. Reps meet the count with touches that satisfy the logging rule and move no buyer, and the report looks healthy while pipeline creation stays flat.
Activity quality is the better read, and it is measurable. ORM treats a change in stage, close date, or amount as meaningful activity on a deal, which separates a touch that advanced something from a touch that only got logged. That distinction also catches the failure mode that matters most, where the earliest warning sign on a deal is the absence of any signal rather than a bad one. See deal slippage for what that pattern looks like as it reaches the forecast, and win rate for the outcome measure that should move if activity volume is doing real work.
Frequently Asked Questions
Why not use a published activity benchmark?
Published targets come from a different motion with a different average deal size, cycle length, and buying committee. An enterprise AE working six-figure deals and an SMB rep working transactional cycles need different daily volumes, and one number cannot serve both.
What is the right way to set the target?
Work backward. Take the pipeline a rep needs to create, divide by average deal size to get opportunity count, then apply your own meeting-to-opportunity and touch-to-meeting rates. The result is a daily number derived from your funnel instead of someone else's.
Should AEs and SDRs have the same target?
No. SDR output is measured in meetings created, so their activity target is volume-driven. AE output depends on progressing a smaller number of open deals, so their target should be measured in deal-level advancement rather than raw touch count.
What happens when you raise activity targets alone?
Volume rises and quality falls. Reps hit the count with low-effort touches that meet the logging requirement without moving a buyer. The activity report improves while pipeline creation and win rate stay flat, which is the signal that the target became the goal.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how many activities should a rep log per day? into prescriptive action for your team.
Schedule a Demo