In Support, we want 24x7 support at this point, including phone support. Let’s assume that takes 5 headcount, minimum, ideally 6. OK we’re up to ~70 without a single engineer! Now let’s cross over into product and engineering: In Product, we’re going to need at least 4 FTEs: • A VP Product to manage the whole thing • 2-3 Product Managers to manage segments of the product, integrations, releases, etc. In DevOps, we’re going to want probably 3-4 folks to ensure 24x7 coverage. Really, 4 would be a lot better than 3. PagerDuty is tiring. Should we could DBAs etc. in here? Maybe it’s really 6-7. In Engineering, I think rough-and-tough we’ll want 20 folks. That’s two “pizza box” teams plus a few engineers to do crazy / next gen stuff and a few to just focus on refactors, back-end, etc. We’ll want 2 designers that can work with front-end team by this point. And finally, we need QA. You can use RainforestQA or something else to get the headcount down, but otherwise, best case assume 1:2 coverage. So with 20 engineers writing code, we’re gonna need 8 folks on QA team minimum once things are humming. So that’s about 40 in product and engineering. Or 110 altogether. I went over 100 a bit, I know, so cut back from there proportionately. But you’ll need those extra heads to hit your growth plan. I know you’d rather have more in engineering and product, but selling a SaaS product requires the headcount above. SAASTR.COM 84

The Ultimate Guide For Scaling Sales & Raising Capital - Page 88 The Ultimate Guide For Scaling Sales & Raising Capital Page 87 Page 89