#startups
This study suggests that the further you stray from your comfort zone as an investor, the worse you perform. Seems like common sense, but valuable advice nonetheless. Note that it’s worth being cautious when looking at any studies on the VC industry: the goal of VC is to be an outlier, so aggregate data studies like this aren’t always valuable.
One thing I’ve noticed when talking to startups is how DevOps and product management are adopted to solve many of the same problems. While I think most companies will eventually require both, I’ve come to believe that it is more valuable to invest early in DevOps than product management.
By being intentional about what types of experience are most important for each role, and considering team-wide capability rather than individual capability, leaders and founders can create powerful teams and nail the first and most crucial step of startup building.
Many leaders view their responsibilities as a list of leadership and management tasks they need to complete. This mindset ignores that the best way for a team to get most things done is through shared ownership and leadership. This week, we explore why leaders should delegate to shared responsibilities rather than individuals.
While many product development leaders obsess over the positive habits their teams should adopt, they rarely pay enough attention to the downside of bad habits and over operationalisation.
Assembling your team is one of the most important responsibilities for any founder or leader. But, most startups I’ve worked with fail at effectively onboarding new staff, which can lead to false starts and failure.
This week we explore a versatile research exercise that can help you to pivot or improve your product based on the needs of your users.
Sales model innovation is the most underrated challenge in conversations about product-market fit. Failing to experiment and innovate on the sales layer causes many startups to lose hope in markets, problems, and solutions with huge potential. Founders assume that because their solution isn’t selling, it must be an inadequate solution, or the market and problem they’ve identified are not big enough. Many teams expect product innovation to solve the product-market fit problem single-handedly, so they abandon anything that isn’t easy to sell, and burn their early-stage runway on product iterations. Often, some discipline and experimentation in the sales process could’ve successfully brought their early solutions to market. The problem with the typical framing of the product-market fit mental model is that it suggests that a startup will succeed so long as it finds a big problem and solves it. Unfortunately, it is rarely this simple. I encourage startups to adopt a disciplined, data-driven approach to marketing and sales to expand their criteria for product-market fit to consider the suitability of the sales model to the market and the product.
Investing in product design (i.e., user experience and user interface design) can lead to fantastic outcomes for product development teams of all sizes because it reduces the number of iterations required to produce a great product or feature. However, most product companies approach product design in manner that excessively slows down the development of new solutions and blows out budgets. This has led to product designers being ostracised from many initiatives and decision-making processes/rituals. By embracing a DesignOps approach to product design, companies can instead move faster and get more done with less resources.
Most startups are idea-rich and resource-poor. Founders and product managers are constantly bombarded with feature requests, so a lack of ideas is rarely the biggest problem. At the same time, startups typically try to achieve something ambitious with limited resources. Startup success is thus heavily dependent on what you say yes and no to and how you prioritise these initiatives against each other. I encourage teams to focus on complex problems faced by many rather than those faced by few. This is the best way to differentiate your product and find product-market fit.
Despite all startups being resource-poor relative to what they are trying to achieve, many founders invest in solutions (e.g., specific product features, technology improvements, and internal systems/processes) that require effort beyond what is desirable from an ROI perspective.
Startup success is all about momentum. This is because startups do not have a great starting position to fall back on — they typically start with no customers, a small team, and no viable product. This means that you’re catching up for as long as you’re a startup. You’re catching up to the incumbents you’re trying to disrupt, to the competition which got a head start, to unrelated businesses with whom you’re competing for investment capital.
For many enterprise SaaS products, a layer of professional services is essential because enterprise customers tend to have diverse needs from each other. Professional services enable deeper customisation on a per-customer basis while keeping the core product focused on the target market rather than the needs of specific customers. Another benefit of providing in-house professional services is that they can provide a significant revenue stream during the early days of finding product-market fit. Many bootstrapped companies use this revenue to keep the lights on as they build recurring revenue momentum.
While every company should approach this somewhat different, there are a handful of principles that apply to most product companies that I think you should consider.
Customer success is a critical function within the B2B software industry. It is typically staffed by customer success managers who are tasked with managing the experience of existing customers throughout their journey with the product, with the assistance of automation. Every B2B software startup eventually finds itself in need of a customer success function, but most struggle to spin one up without a few hurdles and misfires. This is because the focus of customer success is very broad, with diverse goals and roles required to succeed.
Most companies stumble across a market with a problem and spend most of their early-stage investment on finding the solution. So, while you can be strategic about choosing the right market and problem (mostly by pivoting to different problems that your target market is facing, or solving the same problem for a different target market), most companies leave this up to luck. What should never be left to luck is the discovery of a solution for your market. This is where great product management principles and operations can make or break a startup, and much of the time this means prioritising the right solutions and finding the best way to tackle them.
Startup leaders are constantly facing decisions of whether they should build something themselves, or buy an out-of-the-box third-party solution. I believe startups should be biased against building anything inessential that doesn’t pose a legitimate opportunity to create a competitive advantage. In other words: only do what you’re positioned to do better than anyone else.
Products with product-market fit are products that have found an adequately sized market that they can be sold into. It’s more of a spectrum than a binary state — some products are more suitable for their market than others.
While losing staff to customers and partners is pretty common in B2B SaaS, I would advise against having any sort of non-compete/anti-poaching clause in your standard customer and partner terms. First of all, this is bad for your employees. As an employer, you should be competing in talent market by providing a great place to work, with fair compensation and benefits, not trying to lock them in with contracts they don’t have any influence over and may not even be aware of. If an employee wants/needs to leave, and their best prospects are with a partner or customer, it’s unfair to limit their options.
The best product teams I’ve worked with embrace the iterative nature of software development. Instead of committing to roadmap items, they commit to high-level, long-term goals. These goals are the focus of one or more teams for at least a year, and teams work towards these goals by tackling small chunks of work and constantly re-prioritising and re-thinking their approach.
In SaaS, your customers repurchase your product every month, quarter, or year. Your product should improve at this same pace. Renewals are so automated they feel like a passive process. But this is a false sense of security. Every time a customer pays, they should receive compelling value. This week, we explore why and how startups should operationalise their investment in software development.
A common topic in product companies is the prioritisation of so-called customer-facing initiatives versus so-called technical initiatives (e.g., automated testing, reusable technical patterns, SDKs, automation, API-first services).
Assumptions around both expected value and effort required are usually wrong, often dramatically. The outputs of ROI algorithms can lead you astray if the inputs are incorrect, making prioritisation based on this method an exercise in futility. This is why teams should factor confidence into their ROI estimations, recalculate and reflect on ROI estimates after work has been completed, and assemble around long-term areas of focus where multiple hypotheses can be tested.
While this is a word that often comes with negative connotations, I believe that great products, particularly in the B2B world, are usually very opinionated. They come with a strong view of how they should be used, and how the problem they are solving should be solved. These products differentiate themselves from the herd and disrupt incumbents by doing things differently. Many B2B SaaS products are simply automated workflows built from the opinionated views that you should solve that problem in this specific way.
A trend I’ve noticed amongst the most effective people I know is that many of them are keeping a personal knowledge base (which you could also call a personal wiki, a professional journal, or many other things). This is clearly a trend beyond my immediate network, given the glut of new tools at least partially designed with this purpose in mind (e.g., Notion, Craft, Clover, Roam Research, or Obsidian). I started my personal knowledge base in 2010 (using Evernote) and it has been incredibly valuable to me throughout my career, so it has been great to see this trend take off recently.