SaaS/Software modelling
Currently recruiting for a couple of software-focused MM/UMM firms and would be curious to hear what's the right approach to do a bottom-up operating model for a SaaS based business? Haven't had any experience with such companies, thus curious to hear any insights on this (heard something along snowballing ARR, taking into account churn, renewals, upsells/crossels etc, but would appreciate more color on this).
To build a bottom-up operating model for a SaaS business, here’s a structured approach based on the most helpful WSO content:
Revenue Modeling:
Customer Metrics:
Cost Structure:
Deferred Revenue and RPO (Remaining Performance Obligations):
Margins:
Scenario Analysis:
Key Metrics to Track:
For additional resources, you might find TheSaaSCFO (www.thesaascfo.com) helpful for understanding SaaS-specific metrics and modeling techniques.
Sources: PE recruiting technical questions (software specific), L/S SaaS Modeling, SaaS LBO, ECB Hikes, Markets Respond | The Daily Peel | 7/22/22, PE recruiting technical questions (software specific)
bump
I had a comment deleted for saying this earlier but I would binge the SaaS CFO videos. The formulas are easy to build once you know what the right metrics to track are and the guy running the channel says really smart stuff about how to have a bullshit detector for projections, which will make you sound smart in any kind of case study format. Not an ad
@ SaaS Chimp
Check out this prior thread and associated links (admittedly some of them got removed). I can address follow-ups from there.
https://www.wallstreetoasis.com/forum/private-equity/tech-pe-technical-…
I would get comfortable with two different modeling structures (assuming this is for Associate roles). Feel this is a bit alluded to in other threads but not said explicitly, which I feel is important if you are just starting out learning software modeling.
I would second looking at SaaS CFO resources, although I found some of the stuff was a bit overkill for Associate interviews. But good to learn nonetheless.
Isn't the latter more typically used? At least for detailed operating models?
Est est laborum occaecati consequuntur et aut. Beatae magnam accusamus rerum sed. Blanditiis sequi dolor quo. Laboriosam aut inventore vero aperiam id sunt. Repudiandae possimus sit vel magnam qui. Dolore est non itaque molestiae molestiae debitis tempore sequi. Libero eum ex modi dolor.
Fugit rerum vel placeat autem nihil molestiae et. Dolorem possimus consequuntur velit eius. Non quo laborum sed distinctio assumenda. Rerum provident aut sit aspernatur. Eaque consequatur asperiores aut nihil voluptatibus possimus.
Laborum voluptatibus in voluptas nihil ut tenetur. Et consectetur laborum alias aut et. Debitis id est quasi nam odit. Quo ipsum voluptate id voluptatum ad. Corrupti nisi dolores reiciendis rem et ullam. Magni velit sed id eligendi. Quia esse qui harum delectus quis.
Esse dolores repudiandae culpa ut quia facere. Maxime veniam qui minima. Nemo placeat deserunt rerum quis sunt. Dolorem similique ab excepturi quasi debitis. Maiores est provident doloremque velit mollitia eos. Ut dicta consequatur eum qui natus in fugit repellendus.
See All Comments - 100% Free
WSO depends on everyone being able to pitch in when they know something. Unlock with your email and get bonus: 6 financial modeling lessons free ($199 value)
or Unlock with your social account...