SaaS cost of goods sold is the cost of serving customers who are already paying. Gross margin comes out of it, and gross margin sets CAC payback, gross-margin-adjusted LTV, and every efficiency ratio built from them. A margin that is wrong by a few points makes the entire unit economics model wrong in the same direction.
The delivery test
Run each cost line through one question. If the cost continues as long as a single paying customer keeps using the product, it belongs in COGS. If it exists to win customers who have not bought yet, it belongs in sales and marketing. If it builds capability that does not exist yet, it belongs in R&D.
The standard classification
| Cost | Line |
|---|---|
| Production hosting and infrastructure | COGS |
| Third-party software embedded in the product | COGS |
| Data, API, and content fees passed through to customers | COGS |
| Customer support and technical support | COGS |
| Implementation and onboarding delivery | COGS |
| Payment processing on subscription revenue | COGS |
| Amortization of capitalized development | COGS |
| DevOps maintaining production systems | COGS |
| Engineering building new features | R&D |
| Free-tier infrastructure | Usually sales and marketing |
| Customer success focused on expansion | Sales and marketing |
| Finance, legal, HR, facilities | G&A |
The lines teams argue about
Customer success is the largest and the most consequential. A team that puts all of customer success in sales and marketing reports a materially higher gross margin than a team that puts all of it in COGS, and both can defend the choice. What cannot be defended is switching the treatment between quarters.
Engineering time splits the same way. The engineer keeping production stable is delivering the service. The engineer shipping a new module is building the product. Splitting by function rather than by team is the version that survives audit.
Services sold at a loss is the third. When professional services are discounted to close software deals, the loss is an acquisition subsidy wearing a COGS label. Keeping a separate view of that shortfall stops it from quietly depressing gross margin and lengthening reported payback.
Set the policy once
Write the classification into the metrics definitions, restate prior periods if the policy changes, and change it only at the start of a fiscal year. Stable definitions are what make gross margin trends readable and keep CAC payback period comparable across quarters. The same margin assumption flows straight into the revenue plan, so it also belongs in the process behind how you forecast revenue.
Frequently Asked Questions
Is customer success part of COGS?
Split it. The portion delivering onboarding, adoption, and support belongs in COGS because it serves revenue already booked. The portion driving upsell belongs in sales and marketing. Whichever split you choose, apply it consistently, because moving customer success between the two lines changes gross margin by several points with no operational change.
Does hosting for free users belong in COGS?
Many teams put free-tier infrastructure in sales and marketing instead, because it exists to acquire customers rather than serve paying ones. Keeping it in COGS understates gross margin on the paid business and makes a product-led model look structurally worse than it is.
Where do implementation services go?
Services delivery cost belongs in COGS alongside the services revenue it produced. When implementation is sold below cost to win a software deal, the shortfall functions as acquisition spend in economic terms even though the accounting keeps it in COGS. Track that gap so payback calculations reflect it.
How much does a misclassification actually move the numbers?
A gross margin overstated by five points shortens reported CAC payback and raises LTV proportionally, with nothing about the business having changed. Every efficiency ratio downstream inherits the error, which is why the classification policy belongs in the metrics definitions rather than in the close checklist.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like what belongs in saas cogs into prescriptive action for your team.
Schedule a Demo