What does an outbound sales stack actually cost?
The price of outbound is rarely one subscription. A functioning sales machine combines people, prospect data, CRM, dialing, carrier usage, email infrastructure, meetings, reporting and management. The useful question is not 'what does the dialer cost?' but 'what does it cost to create and manage a qualified conversation?'
By Ariyan Ramnarain · founder/operator, Cupids Network
The eight cost layers
1. SDR capacity
Salary, contractor or managed SDR cost, plus incentives and any seniority premium.
2. CRM
Lead/contact records, pipeline, activities, permissions and reporting.
3. Dialer
Power/parallel/predictive features, call controls and any plan-gated add-ons.
4. Telephony
Carrier minutes, phone numbers, destination rates, messaging and usage fees.
5. Data
Company/contact sourcing, phone/email enrichment, verification and specialist datasets.
6. Email infrastructure
Mailbox seats, sending domains, authentication, warm-up or deliverability tooling where used.
7. AI + conversation intelligence
Transcription, summaries, scoring, coaching or agent usage where enabled.
8. Management
Team lead time, QA, reporting, training, campaign strategy and client communication.
Start with the person doing the work
For managed SDR capacity, Cupids Network currently positions dedicated SDRs from £1,250 per month, with the final scope depending on experience level and specialist campaign/data requirements. That figure is deliberately a starting point rather than a promise that every campaign costs exactly the same.
The more important management question is utilisation. If a rep spends a large share of the day copying numbers, switching between CRM and calendar tabs, searching for missing contact data or writing repetitive admin notes, the stack is consuming labour even when the software subscription looks cheap.
Software consolidation changes the denominator
Many outbound teams assemble a CRM, data provider, dialer, sequencer, meeting tool, QA tool and reporting layer separately. Sometimes that is the right architecture: specialist tools can be excellent. But every additional system introduces another subscription, integration, permission model and place where data can diverge.
Cupid's value proposition is consolidation around one lead record: CRM history, power and parallel dialing, email workflows, meetings, analytics and team controls. The wider Cupids Network can then add data and SDR capacity. This does not mean every external tool disappears; it means the default stack can be materially simpler.
Telephony should be calculated from real usage
Carrier economics vary by country, destination, number type and calling architecture. A team calling the US from a US number has a different cost profile from a team calling multiple international markets. Parallel dialing can also consume more carrier minutes because several prospect legs may be open before one live answer is routed.
Cupid's supported bring-your-own-carrier model keeps the carrier relationship separate from the software seat. That lets teams compare Twilio, Telnyx or Plivo against the markets they actually call rather than relying on one generic per-minute claim. Read the BYOC dialer guide for the trade-offs.
Data cost is really data waste plus data value
Buying more records is not automatically buying more pipeline. The cost of data includes duplicates, invalid numbers, wrong job titles, out-of-market companies and contacts the team cannot legally or practically reach. A smaller campaign-ready list can outperform a huge database export when targeting is better.
Measure data against conversations and qualified meetings rather than records downloaded. Cupids Network can scope standard campaign data with managed SDR campaigns; unusually specialist or expensive datasets should be agreed before launch rather than hidden inside a generic calculator.
A better cost equation
Monthly outbound operating cost = SDR capacity + software + carrier + numbers + data + email infrastructure + optional AI + management.
Cost per qualified conversation = monthly outbound operating cost ÷ qualified conversations.
Cost per meeting = monthly outbound operating cost ÷ qualified meetings booked or attended, depending on the metric you use.
Those equations expose bad trade-offs. A platform that saves £50 per seat but reduces rep utilisation can be more expensive. A more capable dialer that doubles conversations at the same headcount can justify a higher software fee. And an all-in-one platform can win simply by removing duplicate subscriptions and admin.
Questions to ask every outbound vendor
- Which features require a higher plan or separate add-on?
- Are phone numbers and carrier minutes included, marked up or billed separately?
- What happens to my numbers if I leave?
- Does parallel dialing consume additional minutes or credits?
- Are data/enrichment credits separate from software?
- Is AI mandatory or optional, and how is usage charged?
- Can the platform replace my meeting scheduler, QA tool or reporting layer?
- Can it plug into my existing team, or do I need to rebuild my operating process around the vendor?
Then compare the answers against your real workflow, not the vendor's longest feature list.