2 min lesson
Cursor's GTM motion in context
Give a plain answer to "Why does the JD insist systems be 'scalable across segments, geographies and program types,' and what does that imply about how you build?" Then ground it in one lesson detail.
Step 1 of 2
Cursor grows the way developer tools grow: bottom-up. Individual engineers adopt it, the habit spreads through a team and eventually a company buys it. The plumbing you build has to serve that shape and a generic B2B-SaaS answer will read as someone who didn't think about this business.
The motion is developer-led PLG: self-serve adoption that expands into teams and lands as enterprise. That changes what your systems optimize for. You aren't pushing leads through a top-of-funnel form fill; you're reading product usage signals to find accounts that are already adopting and routing them at the right moment.
The JD names three Growth Programs explicitly. Treat each as a distinct audience primitive with its own entry rules, data and actions - not three flavors of the same campaign.
Credits, perks and onboarding for early-stage companies.
Entry signal: funding stage, team size, accelerator membership.
Reaching individual developers where they already are.
Entry signal: community presence, OSS activity, usage depth.
Co-marketing and integration with adjacent tools and platforms.
Entry signal: partner fit, shared accounts, joint motion.
Now the explicit design constraint makes sense. The JD says systems must be scalable across segments, geographies and program types. That clause is a warning against building three bespoke pipelines, because a fourth program is always coming. The reusable thing is a program abstraction; the throwaway thing is a one-off per audience.