How Glev’s founder became a one-man revenue pod and tripled his sales with Tamtam

Glev is a six-month-old AppSec SaaS helping dev teams secure the code they ship, including code generated by AI. A 20-person dev team typically produces around 2,000 security flaws per year; Glev identifies the real ones, prioritizes them, and prevents teams from reproducing the same patterns.

Rodolphe is cofounder and the only person running the commercial side. No BDRs, no AEs, no SDR pod. The same person builds the TAM, identifies signals, prospects, runs discoveries, and closes. Before Tamtam, he had two bad options: pay an agency for a frozen list that decays in six months, or attempt to combine company size, dev-team size, function typology, and sector by hand. He picked neither.

His previous experience as a commercial director told him he'd need one or two full-time bizdev hires per five-to-ten reps to make the prospection side work. As a solo founder, that wasn't an option. He needed a way to generate pipeline alone, without recruiting a team he couldn't yet manage.

• 3x more pipeline in the last three months. “In the last three months, we did 3x in pipeline volume,” Rodolphe said.
• 2x average deal size since adopting Tamtam. “By targeting better, you raise your average deal size. We've seen our average basket nearly double, because we target companies that generate more value and we prospect at a higher level.”
• 90% of pipeline companies sourced by Tamtam over the same window. “Almost 90% of the companies that generated this pipeline come from a Tamtam list.”

The velocity story flipped too: Rodolphe's target was 10 qualified meetings per month. The reality, since Tamtam, is closer to 10 per week. Enterprise pilots followed in Q1 with industrial accounts in energy, automotive, and banking, on companies he says he wouldn't have reached at his stage.

For him, the ROI translates directly into avoided hiring. “The impact of Tamtam at Glev, in ROI terms, is the saving of one to two full-time bizdevs who would otherwise be doing this work permanently.”

Rodolphe built his TAM inside Tamtam in the first two to three weeks, then iterated the signal layer with the Customer Solutions team over the following months. His initial bet on hiring as the primary buying signal turned out to be weak. The signals that actually trigger interest in his market are security tech stack and dev-side hiring.

He works one hundred percent from Claude, with Claude connected to his CRM, and still rates Tamtam's meeting prep above his Claude flow for that specific job. Two reasons: the network integration surfaces each attendee's role, journey, and objectives in one glance, and Tamtam knows which value-prop angles fit which client type, so the discovery script is pre-tailored.

For the enterprise pilots, account mapping is the unlock. “The org chart, the ICP cartography: that's insane, because it's extremely precise. There's an amount of information in there that's a goldmine for preparing discovery meetings.” Once Tamtam-generated meetings filled his calendar, he stopped doing his own list-building loop and now hands curated Tamtam lists to a phone-prospection partner. He explicitly rejects the symmetric move for email: “Don't take an agency to write your emails. It's useless.”

Tamtam, HubSpot, Claude, phone partner. That is the stack. No sequencer, no separate enrichment vendor, no email agency. “Before, I felt I was navigating blind. Now I feel in control. I know I'm calling the right companies at the right time, and that's truly reassuring.”