ChatGTM: built one problem at a time, never as an 'app'

ChatGTM: built one problem at a time, never as an 'app'the flagship problem→tool evolution

Cursor's sales team had the universal GTM problem: an SDR burns 2-3 hours prospecting a single account across five tabs - Salesforce, Gong, usage dashboards, LinkedIn, enrichment. George, a self-described non-engineer, did not set out to build an app. He solved one small problem at a time, right inside Cursor, and the rest snowballed.

1. 1Consolidate the data. Describe in plain English what data exists and where; the agent writes the SQL to pull it together. Reps eyeball the output (“numbers too low” / “looks good”) and iterate.
2. 2Encode the scoring. Describe the business logic - seniority, usage recency, when the lead came in - in natural language; the agent writes a Python scoring file. Test it against experienced reps' gut and adjust the weights.
3. 3Draft the outreach. Encode outreach guidelines, not rigid templates, so the agent researches the account and drafts contextual messages.

Demand snowballed - pull contacts, then who to reach out to, then draft messaging, then account research and an account plan, then renewal prep. They wrapped the same tools every rep was reaching for into one internal product, ChatGTM, built in a number of weeks, not months.