Is the cloud deployment/managed solution requirement a hard qualification?
- Cormac Repman
- 4 days ago
- 3 min read
No, cloud deployment or managed solutions are not hard qualifications for us. We work with companies across the full spectrum, from self-hosted on-premises deployments to fully managed SaaS platforms. What matters far more is whether we can identify and reach the right buyer within your sales motion, and whether a qualified meeting has real probability of converting.
Why We Treat It as Soft
The reason we soften this qualification is practical. We've found that the *capability* to close deals depends on your product's value proposition and your sales process, not the deployment model itself. A company running a self-hosted solution with a $500K ACV and a procurement-heavy buying process is actually more qualified than a SaaS startup with a $20K ACV and no clear buying committee. The underlying economics matter more than infrastructure.
When prospects ask this question, they're usually worried about one of two things: either they think their customers are unsophisticated (less likely to buy), or they're concerned their deployment model makes them a poor fit for the outbound model. Neither is necessarily true.
What We Actually Need to Qualify
Instead of deployment type, we look at the specific factors that predict deal success. Does your ICP include companies with $50M+ revenue or higher? Do they have budget cycles we can map? Is there a clear economic buyer we can reach? These questions tell us more about your market viability than whether your product runs in AWS or an air-gapped data center.
We've closed qualified meetings for both. Self-hosted customers tend to have longer sales cycles and higher-touch procurement, which can actually *increase* the value of a qualified meeting because the buyer has done real homework. SaaS customers often move faster but have more competition. Neither is disqualifying.
The Gray Area
This is exactly like the decision-maker vs. influencer question. Yes, reaching a VP of Engineering is ideal when they have budget authority. But we also book meetings with Staff Engineers who have no budget authority but huge influence over the RFP—and those meetings convert. We don't skip someone just because they're not the theoretical perfect title.
Same with deployment. If your product is self-managed and your customers are Fortune 500 companies buying it anyway, we're not going to decline the opportunity because they're self-hosted. We'll adjust our messaging and buyer targeting to fit the reality of your market.
When Deployment *Does* Matter
There are a few legitimate cases where the deployment model signals something real. If your product only works for companies with specific technical infrastructure (say, a tool that requires Kubernetes), that's a hard technical qualification, not a soft one. Or if you're an enterprise SaaS platform and your only customers are using your cloud offering, then self-hosted isn't your segment.
But "we sell to on-premises customers" isn't the same as "we can't run your outbound motion." We can. We'll just be smarter about which buyers we target and how we position the value.
The Conversation That Matters
What we actually need is clarity on three things: your ACV and deal size, the typical buying process (how many people need to sign off?), and whether you can tell us who typically approves this kind of purchase. Whether they're running your software in their own data center or logging into your cloud dashboard matters way less than whether they exist, how to reach them, and whether they'll take the meeting.
If you're unsure whether your business model fits our motion, the best move is to talk it through. We've learned that almost every deployment model works if the buying process is real.
Ready to see if we're a fit? Book a time to chat.
Comments