I read 『ALL for SaaS SaaS立ち上げのすべて』宮田善孝（著） (ALL for SaaS: Everything About SaaS Launch by Miyata Yoshitaka), so I’ll share the insights I gained from the book.

Background: Want to Comprehensively Learn Everything Needed for SaaS Launch

I read this book to comprehensively learn everything needed for SaaS launch.

? ALL for SaaS SaaS立ち上げのすべて 電子書籍｜翔泳社の本

Below are quotes and notes from sections that left an impression on me.

As a prerequisite, my current situation is in the phase of creating a product vision, so I’ve focused quotes and notes around that area. This was a good book I’d want to reread regularly as phases progress.

Part 2: Overall Picture of SaaS Construction

Section 1: Role of Product Manager

However, while product managers collaborate with engineers, designers, and business side, they are not in a reporting line, so promotion doesn't mean giving orders. In other words, the responsibility of a product manager is precisely to manage the team while maintaining alignment and autonomy.

? Alignment and autonomy

Part 3: Preliminary/Deep Dive Research and Prototype

Section 1: What is Product Vision

Product vision is a concise summary of what value will be provided through the product to target business operations or markets, and what will be realized, in alignment with the overall company mission. Since this is a highly abstract discussion, let me try to be more concrete. The important points for building and operating a product vision are the following 4 points:

1. Being aligned with the overall company mission
2. Not talking about specific solutions or features, but thinking deeply about the challenges that potential users face and why we should tackle them, starting from the reasons
3. Being something that can attract and excite various members involved in future development and sales
4. Not being something to approach the correct answer, but believing it’s the correct answer and continuing to communicate it, getting as many people as possible to empathize and collaborate

However, there's one commonly heard method for developing product vision that I'd like to introduce for reference. This method starts by writing the press release for the launch before considering product requirements.

? Write the press release first to develop the product vision.

Section 1: Decision-Making Criteria

1 Decision-Making Criteria: The criteria for deciding whether to proceed with development include two perspectives: alignment with mission/vision and business viability (Figure 3.5.1).

Section 2: Reporting Needed for Decision

2 Reporting Needed for Decision: When making decisions to proceed with development, reporting content will be summarized for a total of 6 items: 2 items regarding mission/vision alignment and 4 items regarding business viability (Figure 3.5.2).

Part 4: Development

Section 3: Differences in User Story Mapping Handling Between BtoC Products and SaaS

Therefore, I want to recognize that SaaS tends to have relatively higher importance of user story mapping compared to BtoC (Figure 4.2.2).

Part 5: Go-to-Market Strategy

Section 12: Common Pricing Pitfalls

Feature Shock

First, feature shock might be commonly seen among sincere product managers and engineers. It refers to creating a SaaS packed with various features to make as many potential users as possible feel value, and when stepping back to the potential user’s perspective, it becomes unclear who it’s for, has excessive features, and can only be sold at high prices.

? Want to avoid falling into feature shock.

That’s all from the Gemba, where I want to know everything about SaaS launch.