Tools for Teams
We love software. We like to build it, use it, talk about it, and read about it.
We know the same is true for many of you. Whether you’re a software builder or user, you’re sitting in the middle of one of the great technology transitions in history. Because of what we do at Variance, we have a front-row seat to the big show, and we want to start to share some of what we’re reading, hearing, and learning about the world of SaaS with all of you. Our mission is to help you master your tools, and we think better understanding the context in which they live can only help us achieve that.
So we want to update you more frequently on how we are thinking about the market and the tools we see every day from our customers and who we follow. We thought about building a sub-brand to Variance News, but for now our thought is to keep it at the Variance News level (this is Vol. 28!) and try to keep this community up to date. As always, feel free to unsubscribe if this isn’t particularly relevant to you, and as we plan to pick up the pace. Here is a little brief on how we are thinking about it:
Working Title: Tools for Teams
Description: A newsletter about software and how teams master it
Objective: Build the Variance brand with a community of people we know and respect. Build top of the funnel awareness with our target audience as the newsletter grows.
Audience: People that manage and are passionate about software inside of their company
Where We Began v Where We are Today
When we started Variance we were leaning into a big trend:
According to IDC, between 2018 and 2023, 500 million new software applications will be introduced, which is equal to the number of apps built over the last 40 years. Most enterprises living through this Cambrian explosion of tools define it as their digital transformation, a process that 89% of companies are in or actively planning.
The question for software buyers, and in the end the employees expected to use these tools, is how do you strike the right balance between integrating technology into the work and making it the work itself?
How does this problem get even bigger? We found out in March.
To give a sense of the scale, check out the Bank of America chart below on quickly changing budgets of companies in 2020, even as these organizations face increasing uncertainty and are looking to cut their budgets where possible.
Compounding growth is always difficult to explain and get our heads around. We have evolved as a species in local areas where we generally encounter linear growth. As a globally connected world, we now have to think in exponentials. Whether it’s Facebook or COVID, networks, and their effects, rule culture. Software is also growing this way, and the knock-on effect of exponential growth is that work is going to look a lot different than it did before. Here is another way to think about exponential growth, in this case, we look at CAGR (Compound Annual Growth Rate) of the %IT spend on cloud infrastructure in the next 5 years.
Why this new approach?
As we make the shift from our four dimensions down to two, the role of these tools in our work lives is only going to become more important. We want to use our unique position in the market to share thoughts, ideas, insights, and best practices around how teams are choosing, implementing, adopting, and using their software. It’s an acknowledgment that no problem that involves people at companies is ever 100% a tech problem. We hope to up the cadence slightly to a few times a week and would encourage you to ask questions and share it with friends. We’ll continue to update you on our progress at Variance and, of course, are still actively recruiting teams for our Alpha.
Please let us know if you have any questions and thanks for reading.