Ozan D.

the trust point is the one that's hardest to operationalise. everyone agrees trust matters but the playbook for 'demonstrate genuine understanding of their business' at any kind of scale is basically 'hire smarter people and give them fewer accounts.' which works, but it's expensive and hard to measure

the deduplication against active campaigns is the part that actually matters here. most prospecting tools just build lists, they don't check whether you're already talking to those people. that's where most teams waste outreach budget without realising it. curious how it handles edge cases though — same person, different company vs same company different title?

interesting approach. the tricky part with simulating exec perspectives is calibrating how critical the AI should be — too generous and founders get false confidence, too harsh and it's not useful. we ran into a similar calibration problem building aisa.to (AI skills assessment). how are you handling the scoring consistency across different business types?

agree with randy on going deeper in sales first. but when you do expand, customer success is probably the natural next step — they're writing almost as many emails as SDRs, the tone-matching matters even more because it's an existing relationship, and the cost of a wrong-sounding email is higher. plus you already have the infrastructure, you just need different training data.

the usage efficiency angle is underrated. we see the same pattern in our AI skills data at aisa.to — the highest-scoring users aren't the ones who use AI the most, they're the ones who've figured out when NOT to use it and how to get max value from each interaction. constraint-driven habits beat unlimited access every time

honestly fewer than would admit it. most people own a slice of the GTM motion really well but designing the full system — from ICP definition through to closed-won attribution — requires a level of cross-functional thinking that's rare. the ones who can usually got there by breaking things at a startup, not by studying frameworks

hassan nailed it — the skill that matters most isn't using any particular tool, it's knowing where the actual drop-offs are. we see the same pattern when assessing teams on AI proficiency: people score well on tool knowledge but fall apart on applying it to their specific workflow gaps. mapping handoffs before adding AI to them is the right order of operations

richard's point about calling out 'no AI' is interesting but i wonder if that becomes its own crutch soon. the deeper issue isn't who wrote the email, it's whether the sender actually understands your problem. conferences and reseller channels work because trust is already built in. for cold, the only thing working for us right now is hyper-specific problem framing — not 'we help companies do X' but 'noticed you're doing Y, here's a thing that breaks at your stage'