The SaaS founder’s operating system.

You started the company because you saw a thing the market needed and you knew how to build it. The first 18 months were focus. The roadmap fit on an index card. You shipped weekly. Then you raised. Then you hired. Then customers happened. Now there are 47 tickets, two integrations a customer is threatening to leave over, a hire you keep meaning to backfill, a board meeting in 11 days, and you can’t remember the last time you were actually building the product instead of triaging it.

The full picture: This is one operator cut of the 5-folder LEGOS system. The framework is the same for every operator. The application changes when the work is software.

Most founder advice tells you to “focus on one thing.” Cool. Which one? Every input feels load-bearing. The integration request is from your second-largest account. The bug is breaking onboarding. The investor wants a churn cut by segment. The hire is six weeks overdue and the role is the difference between you doing the work and you leading the company. They all feel P0 because your brain has stopped sorting and started reacting.

The problem was never your focus. You were running the company without a frame for what kind of work goes where. Roadmap-and-backlog is a planning tool. It is not an operating system. Below is the operating system that sits one level above it.

Why your Linear board doesn’t calm you down.

Linear (or Jira, or Shortcut, or whatever you use) is excellent at telling you the state of the work. It is terrible at telling you the kind of attention each piece of work deserves. A P0 bug in checkout and a P0 “we should rebrand the dashboard” sit next to each other in the same priority column. The board doesn’t know one is an emergency and the other is an opinion.

So your brain compensates. Every time you open the board, you do a manual triage. That triage is what’s draining you. Forty-seven separate mini-decisions, every time you context-switch back. Multiply by ten context-switches a day. That’s why you finish a Tuesday and can’t remember what you did.

You need a sorting frame that lives above the board, not inside it. Most of what you’re calling priorities are actually unsorted.

The 5 folders, mapped to a SaaS company.

Launch — named work with a finish line.

Specific shipping commitments. The Stripe migration. The annual-plan rollout. The new pricing page. The hire of the senior engineer. The Series A close. The integration with the partner. Each of these has an end. Each can be named in a single line. Each has a check-in cadence.

Rule: a sub-15 person SaaS can carry 4 to 6 real Launches at once. Not 12. Anything more and your team can’t tell what’s important either. The 12-Launch SaaS is the company that ships nothing in particular for six months and then panics about velocity in the board meeting.

Guard — the operations that decay if you stop.

This is where most of a founder’s day actually goes, and where almost none of a founder’s identity actually wants to live. Guard at a SaaS includes: customer support escalations, infra reliability, the security review, the SOC2 evidence collection, the monthly board update, payroll, the standup cadence, the on-call rotation, the data export request from a customer, the sales pipeline reviews, the churn analysis, the cash burn check.

None of it ends. All of it matters. If you put any of it in Launch, you’ll burn out chasing a finish line that doesn’t exist. The relief is in admitting Guard work has no finish line and just needs a rhythm.

Elevate — the operator you’re becoming.

SaaS founders almost always run a deficit on Elevate. The CEO skills you’re growing into. The deep technical learning you used to do. The “I wanted to read three books this year” that became zero. The therapy you keep meaning to start. The way you want to show up for your marriage and your kids when you finally stop checking Slack at the dinner table.

Elevate is identity work. It is not a Launch (it doesn’t end) and it is not Guard (it doesn’t decay in a week, but it decays in a year). It needs its own folder so that when you look at your week and the folder is empty, you notice.

Orbit — ideas that have not earned a quarter yet.

Founders attract product ideas the way coastlines attract driftwood. The mobile app. The AI feature. The vertical-specific edition. The free tier. The community. The conference. The newsletter. The pivot you keep thinking about at 11 PM.

Orbit is the place where ideas live without applying for your attention every day. The rule: any idea you can’t say no to but can’t commit to either goes in Orbit with a single sentence. Revisit Orbit once a quarter. If an idea has survived two quarters of you reading it and still feeling pulled, it has earned the right to become a Launch. Most won’t. That’s the design, not a failure.

Storage — what you’ve already shipped.

Every shipped feature. Every closed deal. Every postmortem you actually wrote. Every onboarding flow that worked. Every customer interview transcript. The launch announcement copy you wrote that crushed. The framework you presented at the offsite that the team still references.

Most SaaS founders are sitting on five years of latent leverage in Storage. You wrote the playbook once. You don’t have to rewrite it. You just have to remember where it is. The five folders give Storage a home so you can actually find it.

The Sunday Operator Review for SaaS founders.

Twenty minutes. Sunday afternoon. Phone face-down. Not Monday morning, because Monday is when your team is watching.

1. Walk Launch. Every Launch gets a single line: status, next move, owner. If a Launch has no next move, it’s not a Launch this week. Demote to Orbit.
2. Walk Guard. Are customer support SLAs being met? Is infra green? Is the board update on schedule? Is anything in Guard quietly drifting toward red?
3. Open Elevate. What does “the version of me running this company in 12 months” need from this week? Calendar one block.
4. Skim Orbit. Has any idea earned the move to Launch? Has any idea died? Delete the dead ones without grief.
5. Mine Storage. One asset to reuse this week. The old positioning doc. The customer interview from March. The internal explainer.

After three weeks of this, your Monday standup will sound different. You’ll lead with two Launches and a Guard concern, not nine fires. Your team will calibrate faster than you expect.

The brick for tonight.

Don’t open Linear. Open a blank doc. Five headers: Launch. Elevate. Guard. Orbit. Storage. Spend ten minutes putting the company’s open loops into those headers. Be ruthless about Launch (max 6). Be honest about Guard (it’s bigger than you think). Be kind about Elevate (you are allowed to want this).

When you’re done, look at Launch. Find the one Launch where you, personally, are the bottleneck on the next move. That’s the brick. Do that move tomorrow morning, before your inbox. Then the next one. Then the Sunday review. That’s the system.

OOPS. Adjust. Continue. You don’t need a new tool. You don’t need a new framework on top of the framework. You need the five folders and the rhythm.

Common SaaS-founder questions.

Is the product itself a Launch or Guard?

The product is Guard. Specific releases of the product are Launches. The product as an entity does not end, so it is not a Launch. The v3 release is a Launch. Keeping v3 stable is Guard. Most founder overwhelm comes from treating “the product” as one giant unfinishable Launch instead of an ongoing Guard with discrete Launches inside it.

How do bugs fit?

Severity decides. A blocking bug that hits revenue is in Launch (it has a finish line: fixed). A long tail of paper-cut bugs is Guard (no finish line, just rhythm). Most engineering teams already do this triage informally. The LEGOS folders give the founder the same language so the conversation with the team stops being a translation exercise.

Where does the investor update live?

Guard. It is a recurring rhythm, monthly or quarterly. The Series A close is a Launch. The act of keeping investors informed is Guard. Treating the investor update as a Launch every month is why so many founders dread it.

How does this interact with our sprint planning?

It sits above it. Sprints are how the team operates inside Launches. LEGOS is how the founder operates above the team. The two don’t replace each other. A founder who walks into sprint planning having done the Sunday Operator Review brings clarity into the room instead of pulling clarity out of it.