Read Your SaaS P&L Like a Kitchen Brigade: Revenue to EBITDA, Cook by Cook

Your SaaS P&L is a kitchen brigade, and revenue is the price you charge for the plate before a single cook on the line has touched it. The plate leaves the dining room as a full order. Then it travels down the line, and every cook takes a portion of it. One cook hosts the servers. Another sells the next table, and a third builds the recipe nobody has tasted yet. What reaches the pass at the far end, after the whole brigade has had its share, is EBITDA.

EBITDA is earnings before interest, taxes, depreciation, and amortization. It is the measure of what the kitchen keeps from running the operating business on its own.

So if you only ever watch the menu price, you are the founder at the front door admiring the order, with no idea who took how much before it reached the plate.

What a SaaS P&L is

The profit and loss statement is one of the core financial statements. It reports what a company earned and what it spent over a period, a quarter or a year, and ends with a measure of profitability. For a software business the structure is a line of cooks. The first cook gets the full price of the plate. Each one after takes a cut for the work of the station. What is left when the last cook hands it to the pass is EBITDA.

EBITDA measures the profitability of the operating business alone, before the effects of debt, taxes, and the decline in asset value. You get there by subtracting from revenue all the costs of running the kitchen, but not interest, taxes, depreciation, or amortization. That is why founders and investors reach for it. It shows how much the business keeps from selling its product, with the financing and accounting noise set aside.

Most founders only ever look at the menu. They watch the price grow and treat it as the whole meal. But the profit is made or lost on the line, in the stretch between the order and the pass.

A dollar of revenue and a dollar of EBITDA are the same plate. The whole brigade stands between them, and each cook takes a portion on the way to the pass.

The order: revenue

Revenue is the price on the menu, the full amount the company earns before any cook has touched the plate. For most SaaS companies this is recurring, a continuing and renewable stream from subscription and usage-based fees. The subscription model is the standing reservation. The same table books week after week, which is why investors love it. But a reservation can cancel. If a meaningful number of customers churn, the orders thin out and the whole line has less to work with.

Recurring revenue is the strongest order a kitchen can take, because you can model what is coming. Still, a full order is only the first cook on the line. Plenty of companies serve a wide menu and run a loss, because too many cooks take too much before the plate reaches the pass.

The first cook: cost of goods sold

The first cook on the line is cost of goods sold, or COGS. Gross margin is the difference between revenue and COGS, divided by revenue, and for software it should be high. The cost of goods sold for a SaaS product is the direct cost of serving the dish: hosting and cloud infrastructure, the servers the product runs on, and the support staff who keep the customer fed and live.

Revenue minus COGS leaves gross profit. Gross margin is the share of every plate that survives the first cook, and for a healthy SaaS company it sits around 70 to 80 percent. A thin gross margin here is a red flag. If the first cook on the line already takes half the plate, there is almost nothing left for the rest of the brigade.

The long line: operating expenses

Below gross profit is the longest stretch of the brigade, where operating expenses pull from the plate. These are the costs of running the company, and for SaaS they fall into a few stations.

Sales and marketing is usually the hungriest cook. It is the spend that brings the next table in, the customer acquisition cost made plain on the statement: marketing programs, sales wages, and the overhead behind them. Early companies hand this cook a big portion on purpose, trading near-term profit for a fuller dining room next year.

Product and engineering, often labeled research and development, is the cost of building and improving the software. It is the station that writes the recipes the kitchen will serve in future years.

General and administrative is the rest of the brigade: the wages of the people running the kitchen, rent, and the overhead that does not sell or cook anything but keeps the doors open. Operating profit is gross profit minus total operating expenses. Subtract all three stations and you are one cook away from the pass.

The pass: EBITDA

What reaches the pass at the end of the line is EBITDA. It is operating profit before the decline in asset value, with interest, taxes, depreciation, and amortization left off, so it shows the profitability of the operating business on its own.

A negative EBITDA means the kitchen has a basic problem: the brigade takes more than the order can cover. A positive EBITDA means something reaches the pass.

There is one thing to correct before you treat the pass as your bank balance.

I watched a founder do exactly this last spring. Her ARR was up 60 percent and she ran a wide menu, but she could not work out why payroll kept running tight. We walked her P&L cook by cook. Sales and marketing was taking 55 cents of every plate, and the support staff inside COGS had crept up with every new customer. The order was huge, and almost nothing reached the pass. She had been reading the menu and skipping the whole brigade.

Frequently asked questions

What is the difference between revenue and EBITDA?

Revenue is the order, the full menu price before any cost. EBITDA is what reaches the pass, after cost of goods sold and operating expenses are subtracted, but before interest, taxes, depreciation, and amortization. The whole SaaS P&L is the line of cooks between the two.

Should an early SaaS startup have positive EBITDA?

Often no. Early companies hand a big portion to sales, marketing, and product to fill the dining room, which can push EBITDA negative on purpose. The point is not a positive number at every stage. It is knowing which cook took what, and having a credible path to a fuller pass.

How is a SaaS P&L different from a normal P&L?

The structure is the same line of cooks, but the stations differ. A SaaS company’s cost of goods sold is mostly hosting, cloud infrastructure, and support, which gives high gross margins. Its hungriest operating cook is usually sales and marketing, the cost of bringing recurring customers to the table.

Is EBITDA the same as cash flow?

No. EBITDA measures operating profitability with financing and accounting effects removed. Cash flow also accounts for capital spending, taxes, interest, and working capital. A company can show positive EBITDA and still come up short on cash.

Walk the line, do not just read the menu

Watching only the top line is the original mistake of SaaS finance. Revenue grows, the menu looks rich, and founders relax without walking the line to see which cook took the plate apart. The profit is made or lost between the order and the pass. A founder who can name every cook on the brigade understands the business better than one who only reads the menu price.

CX Cash was built to walk the line with you, to show which cook takes what off every plate and how much reaches the pass, so the trip from revenue to EBITDA is something you read at a glance instead of guess at. Join the CX Cash waitlist, grab the SaaS KPI dashboard and ARR growth tracker, and share this with a founder who is still reading the menu.