What is the minimum required hours per week?
- Cormac Repman
- 6 hours ago
- 3 min read
The short answer: 20 hours per week is our minimum commitment. You can split that however works best for your schedule—whether that's three intense 7-hour days or spread across the entire week. We recommend keeping it to 10 blocks maximum, which translates to about 35 hours of actual dialing time (since not every minute on the phone results in a live conversation).
Why 20 Hours?
We've found that consistency matters more than volume when it comes to outbound prospecting. Twenty hours per week gives your prospects enough touchpoints to remember you, builds genuine rapport during conversations, and creates enough volume for our team to identify patterns in what messaging actually moves the needle. Anything less than that, and you're essentially starting over each week in the prospect's mind. Anything more, and you're hitting diminishing returns on individual call quality.
How to Structure Your Time
This is where it gets flexible. Some teams prefer deep dives: three 7-hour days where they block off their calendar, turn off Slack, and focus purely on dialing and qualifying. Others prefer distributed hours: one hour each morning before team stand-ups, a 90-minute block mid-afternoon, and wrap-up time at day's end. The structure that matters most is the one you'll actually stick to.
Our recommendation of 10 blocks maximum is based on real scheduling data. When someone splits their dialing across more than 10 separate time blocks per week, context-switching costs eat into productivity. You lose momentum between blocks, spend the first 10 minutes remembering where you left off, and miss the psychological flow state that makes high-quality conversations happen.
The Math on Hours vs. Meetings
At 20 hours per week, typical conversion funnels land you somewhere between 4 to 8 qualified meetings per week, depending on your ICP definition and call quality. We price based on qualified meetings, not hours worked, so your commitment is about finding the rhythm that generates consistent pipeline.
If you go above 25 hours per week, you'll typically see incremental gains in meeting volume, but the per-hour ROI flattens. Going below 20 hours tends to create a chicken-and-egg problem: not enough volume to generate reliable weekly meetings, which makes it harder to forecast pipeline, which makes the whole program feel unreliable.
Real-World Scheduling Examples
A sales leader at a B2B SaaS company might do Monday, Wednesday, Friday mornings (7-8:30am) plus Tuesday and Thursday afternoons (2-4pm). That's exactly 20 hours without the week feeling fragmented.
An operations manager juggling multiple responsibilities might front-load Thursday and Friday: 9am-4pm with a lunch break, hitting their 10 hours, then another 10 hours split across Monday and Wednesday mornings. Same total, completely different calendar shape.
Starting Your Commitment
We recommend a 90-day trial at 20 hours per week before deciding whether to scale up. This gives your prospects enough time to cycle through your messaging, lets us optimize your call scripts based on objection patterns, and gives you confidence in the pipeline velocity you're actually generating.
If after 90 days you're consistently booking qualified meetings and want to accelerate, we can talk about expanding hours. If you're happy with the volume and your team's workload, we keep it at 20.
Ready to discuss how 20 hours per week maps to your specific sales goals? [Schedule a call with us](https://cal.com/nurturance).
Comments