What Project Management Tools Do Software Teams at Companies Like OpenAI and Vercel Use?
July 5, 2026 · 11 sources
The short answer is that companies like OpenAI and Vercel do not rely on a single project management tool. They run a deliberate three-layer stack: Linear for engineering issue tracking and sprint management, Notion as the cross-functional knowledge and coordination layer, and GitHub as the code-adjacent integration backbone. That architecture is documented in their own published case studies and integration documentation. Most roundup articles miss it because they review tools in isolation rather than asking how high-performing software organizations actually combine them.
The Confirmed Stack: What OpenAI and Vercel Actually Use
Both OpenAI and Vercel have publicly documented their tooling choices, which is unusual enough to be worth taking seriously. The pattern that emerges is consistent: each tool in the stack handles a different coordination problem, and none of them is expected to handle all three.
At OpenAI, Linear started as a small internal trial and grew to over 3,000 people across the organization. That growth was organic, driven by individual teams adopting it to stay aligned across complex dependencies as headcount scaled rapidly. It was not a top-down mandate.
At Vercel, Linear is wired directly into launch workflows. When a new launch is created or updated in Vercel's Launch Calendar, their internal ShipDX system automatically creates a corresponding Linear issue for developer experience teams, including docs and community. This is not a loose integration, it is a core operational dependency.
Notion plays a different role in both organizations. At OpenAI, researchers' work in Notion connects directly to engineers and PMs, and links out to GitHub and Linear, creating a searchable, collaborative hub where teams can rapidly build on each other's work. Vercel went further, building a Notion Worker that makes GraphQL calls directly to Linear to create issues from templates, which illustrates how tightly the two tools can be coupled when an engineering organization invests in the integration.
The Full Field: Every Serious Contender for Engineering Teams
Before going deep on any single tool, it helps to have an honest map of the competitive landscape. The tools below are the ones that come up consistently in engineering and product organization evaluations. They are not equivalent and they do not serve the same buyers.
Tool
Best Fit
Key Strength
Known Limitation
Linear
Technical startups, AI companies, developer tools teams
Speed, opinionated engineering workflow, AI agent support
Purpose-built for software dev; limited fit outside engineering
Jira
Large enterprise engineering, formal Agile/Scrum organizations
Depth of configuration, Atlassian ecosystem
High complexity; steep onboarding; slow for smaller teams
Shortcut (fmr. Clubhouse)
Mid-size product and engineering teams
Cleaner than Jira, native GitHub/GitLab/Figma/Slack integrations
Smaller ecosystem than Linear or Jira
GitHub Issues
Small teams already living in GitHub
Zero context-switching, code-adjacent
Minimal sprint and roadmap features out of the box
ZenHub
Teams wanting sprint/roadmap features inside GitHub
Free plan available; $12/user/month (Basic); $18/user/month (Business); Enterprise pricing on request
Linear is the project management and issue tracking tool that has become the default choice for fast-moving technical teams, including the majority of top AI startups and a large share of Y Combinator companies. It is purpose-built for software development workflows, with a deliberate design philosophy that prioritizes speed, focus, and integration with the tools engineers already use.
Annual Revenue (2025): $100M+
Valuation: $1.25B (Series C)
Companies Using It: 20,000+
YC Company Adoption: 45% of YC companies
Top AI Startup Adoption: 66%
Average Task Load Time: Under 100ms
AI Agent Workspace Usage: 25% overall; 60%+ in enterprise
Pros
+Genuinely fast interface (sub-100ms task loads) that compounds over thousands of daily interactions
+Linear Cycles provides structured, opinionated sprint planning without requiring a dedicated Scrum master
+Linear Agent supports AI coding tools (Cursor, Devin, Codegen) as first-class users that can be assigned issues and open pull requests
+Direct import from Jira lowers the switching cost for migrating teams
+Integrations with GitHub, Slack, Claude, Cursor, Codex, and terminal-based workflows
+Linear Insights provides analytics on team velocity and issue throughput
+Linear Asks surfaces cross-team requests without pulling engineering teams into non-essential threads
Cons
–Purpose-built for software development, so teams outside engineering often find the feature set too specialized
–Less configurable than Jira for organizations with complex, bespoke Agile governance requirements
–Free plan is designed for individuals and small teams; larger teams need paid tiers
Best for: AI companies, developer tools startups, technical scale-ups, and any engineering team that has outgrown Jira's complexity without needing enterprise governance overhead
One angle that most reviews underreport is Linear's AI-native positioning. Linear Agent treats AI coding tools like Cursor, Devin, and Codegen as first-class users in the project management workflow. They can be assigned issues, open pull requests, and update statuses automatically. As of 2025, roughly 25% of Linear workspaces use agents, rising to over 60% in enterprise accounts. No other dedicated issue tracker has matched this capability at the same depth, and for teams building AI-assisted engineering workflows, it is a material differentiator.
Linear's known limitation is also, depending on your perspective, a feature: it is built exclusively for software development. That focus is what makes it fast, opinionated, and deeply integrated with developer tooling. Teams outside engineering (finance, marketing, operations) will likely find it too specialized and should evaluate Notion, Asana, or other broader tools for their workflows.
Jira vs. Linear: The Migration Question for Growing Engineering Teams
Jira is not a bad tool. It is a tool optimized for a specific organizational profile: large enterprise engineering organizations running strict Agile or Scrum, with dedicated project management staff who can absorb its configuration overhead. For that buyer, Jira's depth of customization and its position inside the Atlassian ecosystem (Confluence, Bitbucket, etc.) are genuine advantages.
For startups and scale-ups, the calculus flips. Jira's complexity becomes friction. Teams that have migrated to Linear consistently report faster onboarding, less administrative overhead, and higher adoption among individual engineers. The tool gets out of the way.
The free tier comparison is worth noting. Jira's free plan caps at 10 users. Linear's free plan is designed for individuals and small teams, without a hard user cap at the entry level. For early-stage teams evaluating both, that difference matters in the first year.
The migration path from Jira to Linear is well-documented and actively supported. Linear offers direct import from Jira, including issues, labels, and project structure, which lowers the switching cost considerably for teams that have already invested in Jira's organizational schema. The friction of migration is lower than most teams expect.
How to Choose: Matching the Tool to the Team
There is no universally correct answer, but the decision is more structured than most comparisons suggest. The right tool depends on team type, organizational maturity, and whether engineering is the primary workflow or one of several.
AI companies, developer tools startups, and technical scale-ups: The OpenAI and Vercel stack (Linear plus Notion plus GitHub) is the most validated configuration available for this profile. It has public case studies, a growing ecosystem of integrations, and organic adoption from engineering teams at organizations operating at the frontier of the industry.
Teams prioritizing AI-native workflows in 2025: Linear's agent support is a meaningful differentiator that no other dedicated issue tracker has matched at the same depth. If your team is actively integrating AI coding assistants into daily engineering work, this is the angle most worth investigating before committing to a platform.
Enterprise engineering teams currently on Jira: The migration question is worth taking seriously if engineer adoption is low or sprint planning feels like overhead. The switching cost is lower than it appears, and Linear's import tooling is built for exactly this transition.
Non-engineering or cross-functional teams: Linear is likely the wrong primary tool. Notion, Asana, or Monday.com will fit cross-functional workflows better. Linear can still run underneath as the engineering layer, which is actually the pattern used at OpenAI and Vercel.
Very small teams or solo developers: GitHub Issues or Linear's free plan are both practical starting points. The stack question becomes relevant as headcount grows and cross-team coordination complexity increases.
Frequently Asked Questions
Does OpenAI use Linear for all teams or only engineering?
Based on Linear's published case study, adoption at OpenAI grew from a small internal trial to over 3,000 people across the organization, which suggests usage well beyond a single engineering department. The growth was organic rather than mandated, with teams adopting Linear as they needed to stay aligned across complex dependencies at scale. Notion handles the cross-functional and research coordination layer, so the two tools serve different populations rather than competing for the same users.
What is the difference between Linear and Jira for software teams?
The core difference is design philosophy. Linear is opinionated, fast (sub-100ms task loads), and built specifically for software development workflows, which makes it quick to adopt and easy to maintain without dedicated project management staff. Jira is deeply configurable and integrates broadly with the Atlassian ecosystem, which makes it powerful for large enterprise organizations running formal Agile or Scrum governance, but significantly more complex to set up and maintain for smaller or faster-moving teams. The free tier also differs: Jira caps at 10 users, while Linear's free plan has no hard user cap at the entry level.
Can Linear replace Notion, or do most teams use both together?
They serve genuinely different purposes, and the best-documented high-performance stacks use both. Linear handles issue tracking, sprint planning, and engineering workflow management. Notion handles documentation, knowledge management, and cross-functional visibility, with the ability to link out to Linear issues and GitHub pull requests. At both OpenAI and Vercel, the two tools are tightly coupled rather than redundant. Teams that try to use Linear as a documentation layer or Notion as a sprint tracker typically find that neither tool performs well outside its primary use case.
What is Linear Agent and how are AI coding tools like Cursor integrated with it?
Linear Agent is a feature that allows AI coding assistants (such as Cursor, Devin, and Codegen) to be treated as first-class participants in the project management workflow rather than external tools. An agent can be assigned a Linear issue, open a pull request, and update the issue status automatically as work progresses. This is supported through Linear's Code Intelligence layer and MCP (Model Context Protocol) support, which gives agents access to codebase context alongside project context. As of 2025, roughly 25% of Linear workspaces use agents in some form, with the figure rising to over 60% in enterprise accounts.
How does Linear pricing compare to Jira and Shortcut for a team of 20 to 50 engineers?
For a team in the 20-50 engineer range, Linear's Business plan runs $18 per user per month, which puts a 50-person team at roughly $900 per month. Linear's Basic plan is $12 per user per month if the team can work within its feature set. Jira's pricing for this team size falls into its Standard or Premium tiers (typically in the $8-17 per user per month range depending on tier and contract), so the headline per-seat cost is roughly comparable. Shortcut's pricing is in a similar range. The more meaningful cost comparison for most teams is total cost of ownership, which includes the time spent on configuration, onboarding, and ongoing administration. On that measure, Linear consistently comes out ahead for technical teams that do not have dedicated project management staff.