Technology
Linear
Linear is how we keep a project from becoming a folklore of Slack threads. Issues, cycles, and a changelog you can read.
What it is
Linear is an issue tracker for product teams that want speed and a keyboard: issues, cycles, roadmaps, and a graph that does not feel like Jira. Runway, Ramp, Cursor, and a lot of other product-led companies run the board there. It is project tracking, not a CMS, not a wiki.
The product is opinionated. Statuses, estimates, and git integrations assume a certain kind of team. That is why people switch to it, and why a programme-management office sometimes will not.
What it does
Engineering and product use Linear to plan cycles, triage bugs, and attach pull requests. Designers live in the same issues. The API and the Slack integration are how it sits next to the repo.
We work from Linear when the client already does. We do not force a Jira shop onto Linear as a personality. The board is yours.
Why we use it
The board we use so the build stays visible.
A short backlog from the brief. Cycles that match the prototype and the build. You are on the workspace. After launch, bugs and copy changes are issues, not emails. A retainer matches the board. A launch leftover list is visible. Nothing important lives only in someone's head.
If the invoice and the board disagree, the board is behind, or the invoice is. We fix that.
Built on it
Runway
A public Linear customer in machine learning and film tools.
Ramp
The finance product team has been a visible Linear shop.
Cursor
The coding editor's team uses Linear in public view.
Perplexity
Has been listed among Linear's product-led customers.
Linear itself
The company runs on its own tracker, which is the honest demo.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.