Inside Gong: How teams work with design partners, their pod structure, autonomy, trust, and more

Gong co-founder Eilon Reshef explains how working with 6–12 design partners per pod drives ~95% feature adoption and near-zero wasted builds.

• Gong claims ~95%+ of shipped features are used by a significant number of customers, attributed directly to the design partner model.
• Each product pod (1 PM, 1 UX, 5–7 engineers) works simultaneously with 6–12 design partners, sometimes showing half-built software mid-build.
• A dedicated research coordinator manages the design partner pipeline using a micro-CRM, freeing PMs from scheduling overhead across 25–30 pods.
• Eilon warns against assuming LLMs replace all ML expertise: deal prediction models and sales-cycle scoring still require purpose-built models and rigorous evaluation metrics.
• Gong’s initial ICP was narrowed to ~5,000 companies: US-based, English, video sales calls via WebEx, software deals worth $1K–$100K — viral word-of-mouth within that small pond bootstrapped growth.
• The spiral learning method: interview one expert, ask for three referrals, keep spiraling until no new information surfaces — signals you’ve reached sufficient domain depth.
• On speed: Eilon argues most decisions are 51/49 calls where waiting for more data produces negligible quality improvement; the cost is velocity, not decision quality.

2025-01-02 · Watch on YouTube