SaasRise Enterprise Mastermind Call Recap June 16, 2026

Topic 1: Outbound Strategy for Large Non-E-Commerce Deals

• Challenge: Historically focused on D2C e-commerce, but non-D2C inbound deals (e.g., energy, financial services, insurance) are coming in at ~$100K. Need to engineer more of these deals through outbound.
• Advice:
Go vertical by vertical, building a case study for each industry
Use multi-channel ABM: email, LinkedIn, calling, ringless voicemail, matched audiences, and direct mail
Build targeted lists using tools like Clay; track ROI over 12–18 months
Direct mail (e.g., FedEx packages, branded items) can cut through digital noise

Topic 2: Reducing Churn & Getting Product Feedback

• Challenge: Bought a company with 50% churn; reduced to 40% after 18 months. Revenue grew from $300K to $900K but is now stalled. Customers cancel within 90 days before seeing ROI.
• Advice:
40% annual churn (~3.3% monthly) is actually competitive for AI BDR tools
Average customer LTV at $500/month with 3.3% monthly churn is ~$15,000
Align ICP to customers who already know how to work leads
Offer annual contracts (paid upfront) to reduce early cancellations
Move upmarket; higher-paying customers tend to churn less

Topic 3: Overcoming Client Security Concerns with AI

• Challenge: Adding an AI chatbot to a PIM platform; clients worry about data exposure.
• Advice:
Use a privately hosted open-weight model to keep data contained
If using a third-party LLM (e.g., Claude), enable the "don't train on this data" setting
A fine-tuned open-weight model can offer high accuracy at lower operational cost
Clearly communicate data usage policies within the chatbot interface

Here are the tools recommended on the call:

• Clay - for building targeted prospect lists and ABM campaigns
• Ringless voicemail tools - for multi-channel outreach
• LinkedIn - for targeted outreach and matched audiences
• Direct mail services (e.g., FedEx packages, branded items) - to cut through digital noise
• Privately hosted open-weight AI models - for secure chatbot implementation without data exposure concerns