How Linear Runs a ~100-Person Remote Company on a Published Handbook and 1–2 Week Cycles

Snapshot

Linear was founded in 2019 by Karri Saarinen (CEO, ex-Airbnb design), Tuomas Artman (CTO, ex-Uber), and Jori Lallo (CPO, ex-Coinbase). It is a remote-first, globally distributed company that builds project management software for software teams. Linear’s own materials describe ~99 people across 15+ countries. They closed an $82M Series C on June 10, 2025 at a $1.25B valuation (Accel-led, with Sequoia and 01A continuing), on the back of a $35M Series B (Accel-led, with Sequoia participating) and an earlier Sequoia-led Series A. (About, Series C, Series B)

What makes Linear instructive in this dataset is scale. Almost every other handbook-first company profiled here — GitLab, Automattic, 37signals — operates at hundreds or thousands of people. Linear operates at ~100 and publishes one of the most comprehensive operating handbooks in software: The Linear Method. It is the rare data point for “what handbook-first looks like at the size most readers actually operate at.”

The Method is principle-first: a published set of operating principles, planning practices, and product-execution norms that the company follows internally and exports as a recruiting filter and marketing asset. It is unusual that a company this small writes this much operating philosophy down. The page below is unusually source-rich for a company of this scale because of it.

Core Philosophy

The Linear Method names a small set of published principles that shape how the company operates and how the product is built:

• Build for the creators. Software for software builders should be designed by people who understand the work.
• Purpose-built. Productivity software needs to be designed for purpose, not for everyone.
• Create momentum — don’t sprint. Find a cadence and routine of working. Sustainable rhythm over short bursts.
• Meaningful direction. Understanding long-term goals matters even when daily work involves smaller tasks.
• Aim for clarity. Don’t invent terms when familiar ones exist; use language that doesn’t fragment meaning.
• Say no to busy work. A tool should work for you, not the other way around.
• Simple first, then powerful. Tools should be easy to start with and grow more capable as teams scale.
• Decide and move on. Sometimes the most important thing is to make a decision and move on.

(Source for all)

These are not aspirational values — they are decision-making criteria. When a tradeoff is unclear, the relevant principle in the Method is the tiebreaker. This compresses a lot of debate that other companies handle in meetings.

Communication Model

Default mode: async, written, inside Linear. Issues, projects, comments, and Linear’s own docs are the primary coordination layer. The product is the company’s communication infrastructure. (Source)

Meetings are minimized and require explicit justification. This is a stated norm in the Method, reinforced through hiring and onboarding. Sync time is the exception, not the baseline.

Slack is for chat, the artifact is for durable. Slack is used for transient communication; structured discussions and decisions move into Linear comments, project descriptions, or longer-form docs. The chat-vs-artifact split is a routing decision: chat is for transient, the artifact is for durable, meeting is for explicit justification.

The Linear Method itself is part of the communication layer. New hires read it. Team discussions reference its principles. It is the company’s published anchor and is functionally a piece of always-on communication infrastructure.

Planning and Cadence

Cycle-based planning. Linear plans work in cycles — fixed-length iterations, typically 1–2 weeks (Linear’s cycle feature supports 1–8 weeks; ~2 weeks is the most common length). Inside a cycle, scope is committed and shipped; outside the cycle, work is shaped and re-prioritized. (Source)

Cycles include a built-in cooldown window between iterations for review, planning, and reset. This is the difference between a cycle (sustainable) and a sprint (debt-accumulating). The cooldown is structural, not a bonus.

Projects sit above cycles. Longer-than-cycle initiatives live as projects with their own scope, milestones, and tracking. A project can span multiple cycles; the cycle is the iteration unit, the project is the deliverable unit.

Roadmap views aggregate projects at the company level. Strategic planning happens by curating the roadmap, not by running annual planning theater.

Continuous deploy at the engineering layer. The cycle is the planning rhythm; deploys happen continuously inside it. The cycle is not a release train.

Decision-Making Model

Decisions are made by the people closest to the work. Founders and team leads provide direction; ICs make most product and engineering decisions inside the framing the leadership has set.

Founder team retains operational involvement at Series C scale. Karri Saarinen (CEO), Tuomas Artman (CTO), and Jori Lallo are all hands-on. Product taste is consistent because the people responsible for it are still in the room.

Hiring is the highest-leverage decision and is treated accordingly. Linear hires deliberately slowly. The operating constraint is “small team, high quality.” Headcount growth lags revenue growth on purpose. (Source)

The Linear Method is the decision-making anchor. When a decision is unclear, the relevant principle in the Method is the tiebreaker. This is one of the highest-leverage uses of a published handbook — it compresses ambiguous tradeoffs into a faster decision.

“Taste” is the explicit hiring filter — defined as the judgment to make non-obvious choices that improve the product over time. Stated outright across founder interviews and the Linear Method. Most companies hire for skill, fit, or self-direction; Linear hires for judgment.

Org Structure

• ~99 employees across 15+ countries as of 2025 (per Linear’s own published materials).
• Founder-led at Series C scale — three co-founders still in operational leadership.
• Globally distributed; remote-first since founding. No office mandate.
• Org structure is flat by design. [Inferred — consistent with the Method’s language about trust and minimal management; specific reporting depth is not publicly published.]
• Specialist roles are intentionally lean. No large product-management organization, no extensive enablement / ops layer. The Method de-emphasizes role specialization.

Tools and Stack

The defining choice: the company runs on Linear. Issues, projects, cycles, roadmap, comments, decisions — all of it lives in the product the company sells. The dogfooding loop is unusually tight: using Linear shapes how teams work, which shapes the next version of Linear. (Source)

Rituals

What They Do Well

• Handbook-first at ~100 person scale. This is the rare data point. Most operating handbooks come from 1,000+ person companies; Linear shows the form works — and arguably is more valuable — at small scale, because it compresses decision overhead before the team is large enough to absorb it informally.
• Cycles compress planning overhead. A 1–2 week cadence with built-in cooldown means planning meetings are short, scope changes are bounded, and shipping rhythm is predictable. The cooldown is the structural detail most “agile” implementations skip.
• Quality bar as operating constraint. Quality is binary. It ships or it doesn’t. This is the most recognizable export from Linear’s culture and is the structural reason the product feels unusually focused.
• Founder-led at scale-of-50. Three co-founders still operationally involved means product taste does not get diluted through translation layers. Most companies lose this by 30 people because of growth pressure.
• The Method as recruiting filter. Candidates who do not resonate with the Method self-select out before applying. The hiring funnel benefits from the public document the same way Tom Preston-Werner’s “Optimize for Happiness” essay benefited early GitHub or DHH’s writing benefits 37signals.

Tradeoffs and Weaknesses

The handbook works because the team is small and taste-aligned. Replicating the Linear Method at 500+ people without continuing to maintain the same hiring substrate produces ceremony, not quality. The handbook is downstream of the hire pool; not the other way around. [Inference]

“Build for the long term” is easier with strong product-market fit and venture funding. Cash-constrained or pre-PMF companies face a different tradeoff between speed and craft. The Method is harder to maintain when shipping speed is existential. [Inference]

Cycle-based planning at <100 is a feature; at 1,000 it becomes coordination overhead between many cycles, dependencies, and team boundaries. The two profiled companies that have scaled past 1,000 (GitLab, Automattic) explicitly do not run the company on cycles. [Inference — based on cross-company observation.]

Founder-led depth has a ceiling. The current model relies heavily on the three co-founders being in the work. The transition to a model that survives founder-step-back is not yet documented (and may not have happened).

No public compensation transparency. Unlike Buffer’s published salaries, Linear does not disclose its compensation philosophy at the formula level. Compensation is mentioned in careers material but not at the level a Buffer-style transparency commitment would imply.

What Founders Can Copy

1. Write the operating handbook before you need it. The Linear Method is a ~100-person company’s handbook. Most companies wait until 200+. Writing it earlier compresses recruiting, onboarding, and decision-making at the same time. (Applies cleanly at 10–100; gets harder above 200 because the document calcifies.)
2. Cycles, not sprints. Use 1–2 week iterations with built-in cooldown windows. The cooldown is the difference between a cycle (sustainable) and a sprint (debt-accumulating). (Applies at any scale where iteration matters; especially valuable at 10–100.)
3. Hire deliberately slowly. Headcount growth should lag revenue growth on purpose. Slow hiring is an async-culture protector and a quality-bar enforcer. (Universal; cost is real and worth paying.)
4. Make the product the operating model when the product is a workflow tool. Linear runs Linear; GitHub ran on PRs; Basecamp runs on Basecamp. The dogfooding tightens both surfaces simultaneously. (Applies when the product is a workflow / collaboration tool; not all companies have this option.)
5. Quality as binary, not tunable. Treat the quality bar as a ship-or-don’t-ship criterion rather than a slider. This is the Linear-distinctive choice and is the most operationally consequential one for product orgs. (Applies most cleanly at <100; harder above 500 because of role specialization and review chains.)

Where This Model Breaks

• Above ~200 people, taste alignment fragments. The model depends on the team being small enough that the founders’ taste anchors the standard. Past a certain scale, taste calibration becomes a managerial problem and the handbook alone can’t carry it. [Inference — based on cross-company evidence; the transition has not yet occurred at Linear.]
• In commodity / fast-following markets. “Build for the long term” assumes the market rewards craft. In commodity markets where speed-to-feature dominates, the Linear approach is a competitive disadvantage.
• Without strong product-market fit. The Method is partly a luxury of resources and time. Pre-PMF companies usually need to ship faster and rougher than the Method allows. (Trying to operate Linear-style pre-PMF often produces beautifully crafted unused features.)
• Below 5 people. At very small scale, the handbook is overkill. A 3-person team should just talk.

Related Practices

• Planning Cycles — Linear’s 1–2 week cycle with cooldown is one of the cleanest cycle-based cadences in the dataset
• Async Communication — async-first inside the product the company sells
• Documentation Systems — the Linear Method as a published handbook + the artifact-driven decision-making it enables
• Decision Ownership — “decisions made by the people closest to the work” backed by the Method as tiebreaker

Related Frameworks

• 20-30 Person Fracture Point — Linear is a counter-example: they wrote the handbook before the fracture point, which is one of the documented escapes from the pattern
• Sync vs Async Decision Matrix — Linear’s chat-vs-artifact-vs-meeting routing is the cleanest articulation in the dataset

Sources

1. The Linear Method (Introduction): https://linear.app/method/introduction
2. Linear Docs — Cycles: https://linear.app/docs/use-cycles
3. About Linear: https://linear.app/about
4. Linear Blog: https://linear.app/blog
5. Building Linear (engineering blog series): https://linear.app/blog/building-linear
6. Linear Series C announcement (Building Our Way): https://linear.app/now/building-our-way
7. Linear Series B announcement: https://linear.app/now/series-b
8. Linear Careers: https://linear.app/careers

Inferences

• The Linear Method works because the team is ~100 and taste-aligned. Most companies that try to copy it without the same hiring substrate produce ceremony, not a quality bar. The handbook is downstream of the hire pool, not the other way around — which is why “write your own Linear Method” is not the right takeaway. The right takeaway is “write down the principles you actually use to make decisions, before you have so many people that nobody can read them all.”
• “Build for the long term” is easier with strong product-market fit and venture funding. Linear has both. Cash-constrained or pre-PMF companies face a different tradeoff between speed and craft. The Method is harder to maintain in that setting and reads as a luxury, not a discipline.
• The Linear Method is functioning as a recruiting filter and a marketing asset simultaneously, in the same way that Tom Preston-Werner’s “Optimize for Happiness” or DHH’s writing did for prior companies. Candidates who don’t resonate with the Method self-select out before applying — the hiring funnel benefits from the public document.
• Cycle-based planning at <100 people is a feature; at 1,000 it becomes overhead. Most cycle-based methodologies (Basecamp’s Shape Up at 6 weeks, Linear’s at 1–2 weeks) lose efficiency above a certain scale because the coordination tax between cycles compounds. The two profiled companies that have scaled past 1,000 (GitLab, Automattic) explicitly do not run the company on cycles.
• The product (Linear) and the operating model (cycles + projects + Linear Method) are co-designed in a way that is unusually tight. Using Linear shapes how teams work; how teams work shapes the next version of Linear. The dogfooding loop is faster and tighter than at most companies — which is the structural reason the product is as opinionated as it is.

Work with Alex

If you are running a small team and want the operating-system clarity that handbook-first companies have, Alex helps founders and leadership teams write the operating handbook that compresses recruiting, onboarding, and decision-making at the same time.