Integrating Linear Tickets into FP&A
Siqi Chen, CEO of Runway, on building browser-based collaborative FP&A
This points to Runway trying to turn engineering work into a measurable business input, not just a list of tasks. A Linear ticket becomes more than backlog metadata. Inside Runway it can sit next to card spend, CRM lead volume, and forecast logic, so a company can ask whether a feature, launch, or campaign actually changed revenue, margin, or pipeline after the work shipped. That moves FP&A closer to operating the business day to day.
-
Runway frames plans as the core abstraction, meaning roadmaps, hiring plans, marketing plans, and fundraising plans become objects on a timeline with financial impact attached. Pulling in Linear tickets is a concrete way to turn a product roadmap into one of those plans instead of leaving it stranded in project software.
-
That is different from older FP&A workflows where finance teams often gather inputs from other teams through forms or spreadsheets, then paste outputs back into a planning system. Runway is aiming to connect the original operating data source directly to the model, which should make forecasts more reflective of how product, sales, and marketing teams actually run the company.
-
The broader competitive pattern in modern FP&A is convergence with BI and operational reporting. Causal wants to become the home for numbers and data across the business, and Equals combines spreadsheets, connectors, and dashboards. Runway is pushing the same direction, but with a stronger emphasis on tying cross functional plans to outcomes over time.
The next step is that planning tools stop being quarterly budgeting software and become live systems of record for how work turns into results. If Runway keeps widening its integrations and can reliably connect tickets, spend, pipeline, and outcomes in one model, it can become the place companies decide what to build next, not just the place finance explains what already happened.