15-Day FREE Trial

Free Trail
Try it today!

Use customer feedback to prioritize for profit and increase customer satisfaction. 

Learn More

We are presenting Agile Product Management @ DevTeach

DevTeach will be presenting a conference in Montreal. This event taking place on December 10 to 12 2012 at the Delta Centre-Ville. It will have 2 full days of main conference (Dec. 10,11) and a Post-Conference (Dec. 12th).

Montreal Sessions are now online. Check it out!


Product Management Community

Quantum Whisper is proud to support the Product Management Community and sponsoring ProductCamp SoCal being held on February 27, 2010 in Irvine, California

ProductCamp SoCal


Subscribe by Email

Your email:

Meet our Bloggers

Posts by Month

Look Familiar?

  • Average age is 37
  • Responsible for 3 products
  • 89% claim to be "somewhat" or "very" technical
  • 34% female & 64% male
  • 95% have completed college
  • 44% have completed a masters program

The above product manager profile is an excerpt from a survey by Pragmatic Marketing, Inc.

Proud Sponsors of ProductCamp Toronto: 2009 & 2010

ProductCamp Toronto

Product Management Tidbits

Current Articles | RSS Feed RSS Feed

SaaS Product Management Challenges


In recent years, the software industry has transformed itself. SaaS adoption is wide spread and is now a credible business model. Looking beyond Salesforce.com, other companies like ConcurVocus and RightNow are successful (reads profitable) as well. The advent of SaaS has left many antiquated companies like SAP and Microsoft struggling to adapt. Interestingly (and a topic for another post), others like Lawson's CEO, Harry Debes, believes SaaS is doomed to collapse. Regardless of where you stand, the reality is that many companies are practicing SaaS and there are thousands of SaaS product managers that are similarly struggling to adjust. Making matters worse, is the product management industry has been equally slow to adapt and provide new guidance or practices.

I'm not sure why, but many product management evangelist and training companies have yet to address the impact of SaaS on product management. At least one leading consulting firm in the field minimizes SaaS to a mere delivery model, suggesting product management is "business as usual". In doing so, they reinforce traditional practices --- ignoring the obvious nuances of SaaS. Perhaps it's been too long since these "gurus" have been product managers themselves. Staying connected has always been a challenge for consultants... (I should know, I am one).

Below are a few points illustrating how the industry is changing and a sampling of how product management responsibilities and skills are evolving under SaaS.

  • Market Intelligence: Traditional product managers make client calls, win/loss reports and customer visits. For product managers, this is a primary source of market intelligence. It is these activities that allow them to observe customers and understand business problems. This approach has historically been product management "best practice". But how practical are they for SaaS companies? With 1000's of customers rather than dozens or hundreds, SaaS product managers can't possibly call or visit enough customers to return any statically relevant data.

    SaaS Approach - To address this problem, software product managers will turn to on-line communities. Pressure to keep cost down, increased user influence and an attempt to increase customer value (overall experience) are some of the more obvious factors that will drive this initiative. Product based communities will drive product direction and development and force product managers to adapt their techniques and skills for the new paradigm.
  • Pricing: Gone are the days of 90% margins and basic P&Ls.

    SaaS Approach - SaaS product managers must now become intimately familiar with pro forma statements and product BOMs, more specifically, fixed vs. variable cost. What is the cost of a single new customer? How do I integrate computing consumption into my pricing? What is the total cost to service a customer? How many customers do we need and when can we expect to make a profit? What is my target margin? What is the expected payback period? Two, three or four years? How do I account for the marketing ramp-up, new sales commissions, and support (the old days of X % of license price are over!)?  

    Perhaps is time to add management accounting (advanced) to the list of product management skills.
  • Packaging and Fulfillment: Do I want a single offering and a single price? It worked before --- right? But now that we are targeting volume (i.e., customer acquisition), how do I accommodate the less sophisticated and budget sensitive customers? How do I simplify my offering, provide enough business value to warrant subscription costs and simultaneously preserve value for more sophisticated customers?

    Historically, software product management addressed these concerns with "lite, professional" and "enterprise" applications (remember "standard" and "basic" versions...  I have yet to meet anyone that wants to buy anything standard or basic). In most instances, each version was a code branch with a set of features turned on or off. Over time, they increasingly became distinct products. Some even eventually needed full-time product managers.

    SaaS Approach - Today, these customer segments (and more) are addressed in a single code base. Customers are free to upgrade or down grade almost at will. To manage these requests and to minimize the overhead (fulfillment, billing etc.), SaaS product managers need to consider new fulfillment (on-boarding) tools (e.g., OpSource and Aria) to provide this flexibility but also to enhance customer experience. While you still have to determine the feature set for each version, you can minimize the transition and switching costs.
  • Change Agents: Unless you are one of the fortunate product managers that is employed by a company that was conceived with SaaS from day one, you will evidently be challenged to align your organization to the new on-demand model and subsequent culture required to sustain it (see my earlier post, "Shifting from Product to SaaS" for tips on how to get senior management on board). Although it may appear counter intuitive, the application development is actually the easy part. It's getting the rest of the organization in-line that is demanding. Unless the organization adjusts, the promise of on-demand will elude both you and your customers.

    No doubt, companies that are introducing SaaS are building solid applications. What escapes most of these organizations are the skills and systems required to support the service model. Many fail because they conduct sales, marketing, support, services, and finance using the same tools and resources used to support traditional grounded software. Takes Sales & Marketing for example, many continue to practice direct marketing, print ads, customer visits, trade shows, etc. While these activities do have a positive influence on sales, the issue lies in their cost. Scaling these activities is simply not congruent with the SaaS business model.

    In an effort to call out some nuances, below are a few examples how SaaS touches every department.

    SaaS Approach
  1. Product Management
    • Thought leadership
    • Serial releases - requires increased communication (inside and out)
    • Smaller iterations - constant prioritization
    • Customer (community) feedback - product requests, self-service, and best practices
  2. Marketing
    • Continuous marketing with constant up-sell and cross-sell
    • Touch users early, often with business relevant information
    • Marketing targets new and existing customers
    • Provides services throughout the organization
  3. Sales
    • Low cost, higher volume sales model (e.g., on-line)
    • Shorter sales cycles with increased focus on business relevance
    • Compensation (what happened to my big fat check?)
  4. Services
    • Setup, installation and upgrades are no longer the focus of services
    • More business consulting and education versus technical implementation
  5. Support
    • Support provides as a critical touch point that requires and experienced skill set
    • Switch to a true 24x7 multi-channel support
    • Shift from issue resolution (break-fix) to ensuring ongoing customer success
    • Balance need for higher-volume, lower cost to serve
    • Customer monitoring and subsequent coaching becomes strategic
  6. Finance
    • Revenue recognition, financial system for tracking deferred revenue
    • Billing systems with tiered products, metering service levels, and managing renewals
  7. Engineering
    • Architected for multi-tenancy and high scalability
    • Infrastructure to support tier management, customer metering, service levels, retention policies, and self-configuration
    • Agile to support faster release cycles

To conclude, fundamentally the role of product management hasn't changed but the nature of the job is absolutely evolving. SaaS product managers face different challenges and must adopt new tools and allocate their time wisely and efficiently. SaaS companies must use technology to drive automation, reduce cost and increase customer self-service.  Product managers must deliver applications that scale with volume but maintain fixed cost and overhead. As a SaaS product manager, your service offering permeates the entire organization. Be prepared to lead --- if you don't, it's likely no one else will.


Hi Barry. Interesting topic. I'd just like to weigh in on the first bullet.  
I just don't see online communities as a viable alternative to conducting ethnographic research to uncover real business problems. It is a valid additional source of information, and perhaps that is what you meant, but SaaS or not, I just don't see any substitute for observing behaviors in a client's work environment. I want to understand their business processes and see the non-SaaS applications they work with. Understanding the likes and dislikes of the other products can be valuable. In fact, I think that with a SaaS offering, it is often even more important to understand the other products they work with so that you can create a familiar look and feel to make the transition less jarring. This discussion depends of course on how homogeneous your target market is.  
My greatest concern with online communities is that customers are often willing to express what they want, but do not always understand (or can't express) what they need and what will create real value for them. Extracting that information is challenging enough in person and is often best done one-on-one. Trying to manage that process online where people can say anything under the protection of anonymity is challenging. The whole group dynamic adds complexity as well. 
Keep in mind that my opinions are biased toward the B2B world, so I'd love to hear others' opinions. However, even with thousands of clients, a small sampling will go a long way.
Posted @ Thursday, August 20, 2009 4:11 AM by Jaime Sipila
Hi Jamie, 
To begin, thank you for your insightful comment. 
I think we agree --- there is no substitute to customer observations. I also think we agree that product communities will complement traditional methods of gathering customer feedback and not necessarily replace them altogether. However, I also feel that customer visits while ideal --- are somewhat utopic. PMs are usually too busy to get out in the field. Moreover, few executives appreciate their value and therefore don’t “create” time for product managers to pursue these activities. And of course, budget (a common executive excuse) plays a role as well. 
With respect to your concerns about communities --- all valid points. However, what if your customer product community… 
• Was semi private (prospects would have limited access) 
• Was not anonymous but complete with user profiles, including personas 
• Provided all the ancillary product/service requirements (online training, best practices, product road maps etc.) to drive traffic and encourage engagement 
• Captured feedback (e.g., feature request) but in a manner that was conducive to discussion, collaboration and validation 
• Provided a platform for customers to discuss feedback and rank ideas by expressing their disposition (for example, by voting) 
• Provided forums to support “customer to customer” exchange 
• Applied product management best practices to evaluate community buzz and prioritize feedback (e.g., by market evidence) 
Is that more appealing? Valuable? 
Essentially, what I am advocating is a product community combined with a product management tool set designed to provide customer value and simultaneously, extract actionable product information. This is significantly different than generic communities we are familiar with today. In addition to supporting a community, its primary goal would be to provide a platform for product managers to identify, develop, and groom product requirements and backlog items (before they hit development). Let me ask you --- how do you develop your backlog today? What systems and approaches do you use? 
My position is that there is a lot of work that takes place between the time a feature is requested (e.g., from support, an email from sales, or the result of a customer call) and the time when a requirement is identified and development ready. I believe product managers can benefit from a tool that supports this exercise. When combined with an active community to capture and validate product direction, I think you have a strong tool that will help product managers identify business value, minimize feature bloat and reduce wasted (less than optimal) development cycles. 
Again, thanks for your feedback. Looking forward to your thoughts on my proposition. 
Best Success, 
Posted @ Friday, August 21, 2009 12:38 PM by Barry Paquet
Thank you. The post is still relevant for today.
Posted @ Tuesday, October 16, 2012 1:24 AM by kyaw kyaw naing
Post Comment
Website (optional)

Allowed tags: <a> link, <b> bold, <i> italics