Clay · Go-to-market · Senior · 45 to 60 minutes
Which customer should Clay bet on?
Clay is a software product that connects internet data sources to a spreadsheet-like workspace so teams can enrich data and automate workflows. Answer this product management case and get it graded line by line against a weighted rubric.
- Segmentation
- GTM strategy
- Prioritization
- Positioning
- Hypothesis design
The situation
You are the PM leading growth and market strategy at Clay in its early years. The product can pull and transform data from many external tools and databases inside a spreadsheet-like interface, and early prospects across several groups find it impressive. Recruiters want help sourcing candidates, sales teams want support for prospecting and enrichment, some engineers see it as a low-code backend, and one customer is even using it to move data into accounting software. The problem is that interest is broad but behavior is messy. Many users say the product feels powerful, then fail to return consistently. Each customer conversation seems to produce a new use case, a new positioning angle, or a custom request that could pull the roadmap in a different direction. The founders are debating whether Clay should stay broad and flexible, or commit to a narrower customer and use case so the team can learn faster. Assume the team can support only one primary ICP and one clear go-to-market motion over the next two quarters. Kareem asks you for a recommendation on where to focus, how to message it, and how to avoid being distracted by attractive but misleading opportunities.
What to produce
Write a 1 to 2 page strategy memo for the CEO recommending Clay's near-term go-to-market focus.
Your answer must
- Recommend one primary ICP and one initial use case for the next two quarters, or clearly argue for a different structure, with rationale.
- Compare at least three plausible customer segments or use cases already visible in the write-up, using explicit decision criteria.
- Describe the go-to-market motion, core positioning, and product boundaries needed to support your choice, including what Clay should say no to.
- Define the leading indicators and learning milestones you would track to judge whether the focus is working, not just top-of-funnel interest.
- Explain the main risks, second-order effects, and triggers that would make you revisit the decision.
Constraints
- Use only customer patterns and product capabilities described in the write-up, do not assume new markets, partnerships, or major product rewrites.
- You cannot run multiple equally weighted ICP strategies in parallel over the next two quarters.
- The team needs fast learning from repeatable usage, not a plan that depends on heavy custom services or long enterprise implementations.
Format
Use clear section headers such as recommendation, options considered, decision criteria, execution plan, metrics, and risks.
How Clay actually played it
Covers how Clay narrowed a broad no-code idea to a single ideal customer profile, outbound sales teams, and sold the same product repeatedly to learn. A clear lesson in narrowing scope to find fit.
- Narrow the ICP even if the product feels general
- Selling one use case repeatedly reveals what works
Built from Clay's Path to Product-Market Fit: A 7-Year Overnight Success by First Round Review.
Related case studies
- Linear GTM for 1,000 Plus Engineer OrgsLinear · Go-to-market · Mid
- GTM plan for team routing to existing Calendly usersCalendly · Go-to-market · Entry
- Razorpay's Next SMB Market Beyond MalaysiaRazorpay · Go-to-market · Senior
- Zoom AI Premium Packaging and PricingZoom · Go-to-market · Senior
- Grow Headspace sales to employersHeadspace · Go-to-market · Mid
- How should Slack launch to teams?Slack · Go-to-market · Mid