Technical abilities

• Outbound prospecting and pipeline building [8/10]: This is where Alok feels most confident, and it comes through clearly in the interview. He laid out a structured five-step process involving ICP definition, market sizing, competitor research, segmentation, and enrichment, and he was able to explain it with real context from his time at RazorSign. The $400k pipeline his SDR team generated across six months, alongside the 120% increase in qualified leads he attributed to rebuilding the outbound workflow, gives us enough reason to believe the process he describes actually works in practice. When we asked him about how market sizing actually influences his decision-making day to day, he initially gave a broad answer, but when pressed, he gave a reasonable explanation around how persona differences between founders in smaller markets versus CXOs in larger ones affect messaging strategy. We also liked his unprompted shift from volume-based thinking to signal-based thinking when asked about his biggest learning. He was candid that he used to treat outbound as a numbers game, and that he's moved away from that.

• Email and multi-channel outreach execution [7.5/10]: The email task was the most revealing part of the call. He was given roughly eight to ten minutes and came back with two versions, one signal-led and one event-led, which showed he understood the brief and was thinking contextually rather than generically. The fact that he structured it around the signals he'd already identified for Clemon, and offered two angles rather than one, suggests he has a working understanding of how to tailor outreach to context. That said, we think his instincts on messaging are still at a functional rather than refined level. When asked what he'd change if reply rates dropped, his first answer was subject lines, which is a reasonable starting point, but he needed prompting to move beyond that to channel diversification and sequence design. For a role where the writing is doing most of the heavy lifting, we'd want to see a bit more creative problem-solving around message construction. His touch-point count of 15 to 16, which he acknowledged was high and context-specific to RazorSign's competitive environment, did correct itself when pushed, landing at four emails and three LinkedIn messages, which is a more defensible number.

• CRM Management and Pipeline Discipline [7.5/10]: Alok has hands-on experience across Zoho, Salesforce, HubSpot, and Apollo, which covers the bases the role needs. More usefully, he seems to understand what CRMs are actually for, i.e. tracking the full lifecycle of a contact, maintaining stage accuracy, logging last conversations, and using that data to inform follow-up timing. He described CRM as "a brain for the company," which sounds simple but actually reflects the right mindset; most candidates we've interviewed treat CRM as a reporting obligation rather than a working tool. His proficiency with Clay and Apollo for enrichment and sequencing is also relevant here, given the role's appetite for smarter tooling. The personalized prospecting tool he built for Klimon ahead of the interview, processed nine industry-specific signals and produced a warm/hot lead classification and a draft email, which gives us confidence that he's genuinely engaged with AI-powered workflows and isn't just name-dropping tools he's seen in job descriptions.

• Resourcefulness and AI/automation capability [8.5/10]: This is probably the area where Alok feels most differentiated from a typical SDR profile, and we think it's genuine rather than surface-level. The clearest evidence of this came before the technical interview had even started as had built a working HTML-based prospecting tool specifically for Klimon, incorporating nine food-service-specific signals such as sustainability pushes, menu launches, plant-based initiatives, and trade show activity, and designed it to output lead classifications and draft emails from a single company name input (here's a link to the demo). He'd also pre-loaded Klimon's product context into the tool so every output was framed from its point of view. Beyond that specific example, his day-to-day workflow already leans heavily on AI. He's built Claude-powered research artifacts that pull together GTM strategies, hiring signals, and product pain points for any company he's prospecting, and he mentioned using Clay for enrichment logic built on firmographics, technographics, and intent signals. He also tracks spam ratio using custom triggers he's built himself, which suggests he's thinking about the infrastructure of outbound, not just the messaging layer. We feel his comfort with these tools comes from genuine hands-on experimentation during his consultancy period, where he had the freedom to build without the constraints of a corporate tech stack.

Areas of growth