{"id":15651,"date":"2023-02-08T17:15:57","date_gmt":"2023-02-08T14:15:57","guid":{"rendered":"https:\/\/railsware.com\/blog\/?p=15651"},"modified":"2025-02-13T22:22:11","modified_gmt":"2025-02-13T19:22:11","slug":"saas-product-management","status":"publish","type":"post","link":"https:\/\/railsware.com\/blog\/saas-product-management\/","title":{"rendered":"Railsware\u2019s Handbook to SaaS Product Management"},"content":{"rendered":"\n
With the SaaS market expected to be worth $400bn in 2025, the demand for product managers is only set to grow. But why are product managers so instrumental to SaaS companies? How do they contribute to product success, and what does it take to excel in the product management space? This guide is for startup founders and aspiring product managers who want to better understand the role of product managers (PDMs) in SaaS. We\u2019ll explain the key functions, skills, and responsibilities of PDMs, common product management concepts, and what to look out for during the hiring process.<\/div>\n\n\n
\n
\"\"<\/figure><\/div>\n\n\n

What is SaaS product management?<\/h2>\n\n\n\n

Software as a service (SaaS) product management is the end-to-end process of planning, developing, and scaling software products that are delivered to customers as a service over the internet, rather than as a one-time purchase.<\/p>\n\n\n\n

SaaS product managers work closely with engineering, design, marketing, and analytics teams to guide a product through its entire lifecycle. However, unlike project managers, PDMs aren\u2019t responsible for coordinating day-to-day product development activities. Instead, they focus on shaping the product vision, designing a strategic plan, communicating the value proposition, and monitoring product health.<\/p>\n\n\n\n

SaaS vs non-SaaS product management<\/h2>\n\n\n\n

There are some key differences between the workloads and approaches of SaaS product managers and traditional software or hardware product managers. First of all, the latter typically have to grapple with wider development scope. If we compare a product like Fitbit to Strava, then it\u2019s fair to say that Fitbit PDMs have a bit more on their plates; they must deliver a sleek and highly-functional physical product to users, as well as a full-featured fitness app.<\/p>\n\n\n\n

Secondly, SaaS product managers are more likely to leverage agile methodologies (e.g. the Lean Startup model or Scrum) since continuous delivery is standard practice in this domain. SaaS software is typically updated as soon as there is a change. Meanwhile, updates to classic software are less regular. Changes are usually bundled into a major or minor version update.<\/p>\n\n\n\n

It’s also tricky and time-consuming to iterate on a hardware product. Updates take much longer to roll out, as there are more moving parts to consider; certain malfunctions can\u2019t be fixed with a software patch. For example, many companies are integrating features like advanced route optimization<\/a>. These tools are essential for enhancing service quality and meet growing customer demands for faster, more reliable delivery.<\/p>\n\n\n\n

Now, let\u2019s dive into the skills that SaaS product managers need to succeed in this career\u2026<\/p>\n\n\n\n

Key skills for SaaS product managers<\/h2>\n\n\n\n

Leadership<\/h3>\n\n\n\n

Product managers are natural leaders. They trust the expertise of their team\/peers, drive positive change within the organization, and inspire others to do their best. At our software agency, we value product managers who lead by example. They should be willing to delegate responsibility, get hands-on when appropriate, and prioritize shared success over personal gain.<\/p>\n\n\n\n

T-shaped<\/h3>\n\n\n\n

It\u2019s not enough to be skilled at managing processes and people. Product managers should be proficient in one discipline (data analysis, for instance), yet capable of contributing to activities in other departments. For example, they can create rudimentary product designs in Figma, participate in marketing ideation sessions, navigate AWS payment infrastructure, write spreadsheet formulas to analyze data, or even write basic code. Having a robust set of technical and soft skills \u2013 and being a fast learner \u2013 are highly desirable traits.<\/p>\n\n\n\n

Analytical thinking<\/h3>\n\n\n\n

As analytical thinkers, SaaS product managers constantly use data for decision-making. They like to think outside the box and aren\u2019t afraid to challenge their own ideas or those of others. They can also analyze a problem from multiple angles i.e. SaaS PDMs should be able to put themselves in customers\u2019 or stakeholders\u2019 shoes, and spot relationships between seemingly unrelated issues.<\/p>\n\n\n\n

Complex problem-solving<\/h3>\n\n\n\n

SaaS product managers use a combination of data, research, team input, and experience to develop innovative solutions. They are good at breaking down problems into smaller pieces and creating a step-by-step plan on how to investigate and solve them. They\u2019re also open to adapting their plans in response to new information they encounter along the way.<\/p>\n\n\n\n

Decision-making<\/h3>\n\n\n\n

SaaS Product managers must be strong decision-makers since oftentimes, the buck stops with them. They must be able to make time-critical decisions even when they only have limited information at hand. Regarding high-level decision-making, product managers shouldn\u2019t be afraid to leverage frameworks to dive deeper into the context, invite feedback from stakeholders\/knowledge-holders, develop solution variations, and prioritize them.<\/p>\n\n\n\n

SaaS Product Manager responsibilities<\/h2>\n\n\n\n

Here are some of a SaaS product manager’s core responsibilities\u2026<\/p>\n\n\n\n

Shaping the product vision and strategy<\/h3>\n\n\n\n

Product managers are tasked with determining the product vision. They accomplish this by running product discovery sessions, consulting with subject matter experts, utilizing agile startup frameworks<\/a> (such as Lean Startup or Product-Market Fit), performing competitive analyses, and conducting market and customer research.<\/p>\n\n\n\n

Once the vision has been defined, SaaS PDMs are charged with crafting a product strategy<\/a> that takes it from concept to reality. In addition to building a product roadmap<\/a> that supports the initial phases of product development, they will also develop a strategic plan for future growth (more on that later). So, it goes without saying that product managers are responsible for aligning all departments to the product vision and communicating it to stakeholders. They will also be tasked with modifying the vision and\/or strategy throughout the product lifecycle.<\/p>\n\n\n\n

Collaborating with cross-functional teams<\/h3>\n\n\n\n

Essentially, product managers are the glue that binds cross-functional teams together. On any given week, they will liaise with several members of the engineering, marketing, design, or data analytics departments to share expertise, answer tricky questions, communicate the product strategy, and help investigate or resolve any issues that have cropped up.<\/p>\n\n\n\n

\n
\u201c<\/div>\n
\n

At Railsware, product managers are sort of like spiders at the center of a product \u2018web.\u2019 They collect information from all corners of that web \u2014 engineering, marketing, design \u2014 and use those insights to shape the product vision, design new features, or solve complex problems.<\/p>\n<\/div>\n

\"Sergiy\n

Sergiy Korolov<\/h4>\n

Managing Director<\/p>\n<\/div>\n<\/div>\n\n\n\n

For instance, when we are working on a product website redesign, the product manager will coordinate efforts between departments to ensure a cohesive end result. They may collaborate with software engineers to create user stories, with designers to tweak UX flows, and with a SaaS marketing agency<\/a> to fine-tune the digital strategy, develop a content strategy or maximize the impact of the redesigned website.<\/p>\n\n\n\n

Conducting customer research and user testing<\/h3>\n\n\n\n

SaaS product managers are responsible for conducting in-depth market research and coordinating user testing<\/a>. They will gather information on market trends, carry out competitive analyses, and study customer behavior. <\/p>\n\n\n\n

Armed with that knowledge, SaaS product managers may run ideation sessions, design user surveys, build buyer personas, or prepare materials for customer development<\/a> interviews. They will also take the lead in those interviews, and ensure that all research\/test findings (cust dev or otherwise) are carefully recorded and synthesized.<\/p>\n\n\n\n

Identifying and creating opportunities<\/h3>\n\n\n\n

A core aspect of the SaaS product manager role is identifying areas for product improvement<\/a> and growth. They should keep an eye on industry trends and evaluate which ones are worth implementing (for instance, whether or not it makes sense to integrate AI into the product). Whether it\u2019s by running additional product discovery sessions or analyzing the activities of competitors, product managers should constantly seek out new ways to add value to the product<\/a> and attract new customers.<\/p>\n\n\n\n

Now that we\u2019ve explained the intricacies of the role, let\u2019s dig deeper into some of SaaS product management\u2019s most crucial concepts and processes\u2026<\/p>\n\n\n\n

Understanding the product lifecycle stages<\/h2>\n\n\n\n

The product lifecycle<\/a> can be defined as a series of consecutive stages that the product moves through, from inception to eventual decline. It\u2019s an important concept in product management because the manager role typically evolves in tandem with the product\u2019s journey through the cycle.<\/p>\n\n\n\n

The traditional view of the lifecycle has four stages: Introduction, Growth, Maturity, and Decline. However, we\u2019ve adapted the cycle length based on our own experience in product building. It goes something like this:<\/p>\n\n\n\n

    \n
  1. New Product Development<\/strong> is when the product goes through the conceptual and testing stages: ideation, development, and validation.<\/li>\n\n\n\n
  2. Introduction <\/strong>is when the product is launched on the market.<\/li>\n\n\n\n
  3. Growth <\/strong>is when the product establishes its market position and brings profits.<\/li>\n\n\n\n
  4. Maturity or Stabilization <\/strong>is when the product stabilizes on the market and has the highest sales volumes.<\/li>\n\n\n\n
  5. Decline <\/strong>is when the product reaches the extent of its growth and begins to fail.<\/li>\n\n\n\n
  6. Afterlife <\/strong>is what happens after the product dies. There are a few different scenarios \u2013 it can immediately die, inspire a new product idea, or simply become a relic.<\/li>\n<\/ol>\n\n\n\n

    Here\u2019s a visualization of the lifecycle:<\/p>\n\n\n

    \n
    \"Product<\/figure><\/div>\n\n\n

    What to remember about the product lifecycle<\/h3>\n\n\n\n