Hacker News Reader

Comment by sytse | Hacker News Reader

Totally agree that those numbers would make an outsized burn rate. The team member number is from a different date than the revenue number. Our team member number is public on https://about.gitlab.com/company/team/ (currently 383). Our current ARR is multiple times the number cited.

We're not profitable but on some months we're cash flow positive. We don't aim to be cash flow positive until 2022.

View on HN

Considering Gitlab’s revenue model, how come you’re only cash flow positive some months?

I’d assume both income and employee count is mostly steady, unless you’re hiring people just about as fast as cash flow is increasing?

Servers and Data Centers cost money... operations scaling, advertizing, etc.

Income as in revenue is steady. Cash flow has more variance since people pay for GitLab one or more years upfront.

On average we have negative cash flow since we're investing the money we raised in growth by doubling incremental annual contract value every year.

But in some months we have a few large orders that push us to cash flow positive.

We could be cash flow positive every month but that would at the cost of our rate of development. Right now we're focussed on making GitLab a single application for the entire DevOps lifecycle. That means we have to make a lot of progress every month https://about.gitlab.com/2018/10/22/gitlab-11-4-released/

Reply on news.ycombinator.com