Set up Product Inflection.

Enter your time zone and make any needed changes to your default experience such as dark mode, AI vocal response speed, reduce motion, and screen magnification.

Enter your company URL and local currency.

Review and configure the security settings for your workspace such as session time-out and MFA.

Add the product team members who will help enter information about your products, market, competitors, and related context.

Role guidance: CEO, CPO, VP of Product, and Product Operations have broad capabilities that other roles do not. Product Operations is the system’s super-user role.

Select either Google Gemini only, or OpenAI and Google Gemini, or Anthropic and Google Gemini.

Option 1: Google Gemini performs all AI functions. This configuration does not support direct import or export of Microsoft Office file types.

Option 2: OpenAI performs most AI functions. Google Gemini creates analysis of uploaded videos. This configuration provides near real-time spoken audio when conversing with Sense, when at 1.x speed.

Option 3: Anthropic performs most AI functions. Google Gemini transcribes speech entry, generates voice responses, and creates analysis of uploaded videos.

Connect Atlassian Rovo MCP. This two-way integration enables ticket analysis, real-time status views on roadmap tiles, and risk reporting. You can also create Jira tickets from a PRD with one click.

You can connect HubSpot, Zoho, or both. These read-only integrations provide CRM data for sentiment analysis, win-loss analysis, and related insights.

If your organization uses Google Drive for product artifacts and data, you may also connect it so users can load and download files through Drive rather than only from their local machines. Additionally, Product Inflection can operate in a hybrid or headless mode in organizations that use Google Drive and Google Chat, where it watches folders for new documents to ingest and analyze, etc., and interactions and actions can occur via chat with team members.

SharePoint is not supported. For other CRM and support systems, export reports and upload them as CSV files.

Enter information about the products your organization will manage in Product Inflection.

Product Inflection calls feature requests created by stakeholders Opportunity Documents and documents created by the product team for committed work PRDs.

If your organization uses other terms for these documents, change their names here to what your co-workers are familiar with.

If your organization has multiple names for different types of PRDs or Opportunity Documents, such as MRDs, Customer Requests, requirements documents for services, or cross-sell product documents, identify the unique name of each additional type when you import or batch import those documents in a later step. Product Inflection tags each document with its custom document type and lets users filter by that type, preserving your organization’s documentation taxonomy.

Review the questions asked in Opportunity Documents and PRDs. If any questions your organization needs are missing, add them here.

Note: When you batch import your existing product documents in a later step, Sense will prompt you to add custom questions in a quick batch process if it cannot map imported questions to existing ones.

Some organizations use tables in their document templates to guide and ensure that product managers think about the right questions and plan properly. You can easily create those tables in any documents that need them.

Note: When you batch import your existing product documents in a later step, Sense will prompt you to add custom tables if it cannot map imported tables to existing ones.

Enter information and artifacts in each section. The progress indicator at the top of the page shows your setup status.

Have the person responsible for strategy, competitive intelligence, battle cards, or related work complete this step.

Sense will then begin monitoring social media reviews of competitors, press releases, and other sources. It summarizes these findings in the Market Intelligence Library for product research.

The Market Intelligence Partner will also create Opportunity Documents for recommended work based on market gaps and changes, and contribute its analysis during Partner Huddles.

Have the person responsible for customer interviews, feedback, and discovery research complete this setup.

Uploaded videos will be analyzed by the Discovery Partner. Key moments are provided as image evidence, and timestamps link directly to the corresponding scene in the video player. Audio files will be transcribed and summarized, with key moments highlighted.

The Discovery Partner will then generate Opportunity Documents based on voice-of-customer (VOC) evidence and contribute its analysis during Partner Huddles.

Have someone who works closely with Jira tickets and customer-experience issues complete this setup.

The Customer Experience Partner will then review bug tickets and support tickets from your CRM for causal analysis. It will also generate a Jira quality report, create Opportunity Documents based on identified needs, and contribute its analysis during Partner Huddles.

Create your strategic themes and objectives. You may create key results during meetings with product leads, but key results are required.

A PRD can be created from each key result, establishing a direct strategic link to work that may be considered and executed. Assign objectives and key results to people. When they are tied to Jira work, progress at the assignee and owner levels is automatically tracked and reported. The report can be used to bring data to 1 on 1s and performance reviews.

Opportunity Documents and PRDs can be linked to OKRs to show strategic alignment. Most views of work within Product Inflection can be filtered by OKR.

Import your existing PRDs, MRDs, BRDs, and related documents by Google Drive folder. Select the product, then choose whether they should be imported as Opportunity Documents or PRDs.*

Each imported document has a clickable link at the top that takes the user back to the original document in Google Drive.

Questions and tables are mapped automatically to the appropriate Opportunity Document and PRD questions. If needed, you will be prompted to approve new custom questions or tables before they are added to these forms.

If your organization has multiple names for different types of PRDs or Opportunity Documents, such as MRDs, Customer Requests, requirements documents for services, or cross-sell product documents, identify the unique name of each additional type when you import or batch import those documents. Product Inflection tags each document with its custom document type and lets users filter by that type, preserving your organization’s documentation taxonomy.

*Important: Do not import any product documents as PRDs unless they have already been committed for development. Feature requests must be imported as Opportunity Documents.

Use this setting if your organization follows a headless or hybrid workflow in which teams continue creating PRDs and other product documents in Google Drive.

Within the Drive location that Product Inflection can read and write, create a separate folder for each product. Inside each product folder, create a folder for every document type. Keep approved and unapproved work in separate folders.

Product Inflection checks these folders every 15 minutes. It imports new Google Docs and monitors previously imported documents for revisions.

If users will create, view, and edit PRDs or Opportunity Documents in Google Drive instead of Product Inflection, add RICE and Kano fields to your Google Docs templates. This gives Product Inflection important information it needs to help rank opportunities by strategic value.

Assign each person the appropriate role, then have the team begin creating PRDs from understood priorities and the roadmap.

PRDs can generate Jira stories and epics as well as roadmap items. They are the source of truth for planned work and work in progress.

Add the non-product teams that will create and rank opportunities based on customer, pipeline, or infrastructure needs. Examples include Support, Revenue, Customer Success, regional teams, and Technical Services. Add your engineering team and UX team here. Customize permissions if any group needs access to screens that are not default for stakeholders. Manage AI use at the group level.

Add your stakeholders, assign the Stakeholder role, and select the appropriate stakeholder group for each person.

Send the invitations and ask users to begin creating requests in Ideas Creation and ranking their team’s top 10 in Stakeholder Ranking.

Enter the names of your software engineering teams and add their members. If your company assigns work in Jira to pods rather than engineering teams, check the box to remove engineering teams from appearing in the UI.

Enter the names of your pods and add their members.

Product Inflection includes an innovative Learn while loading experience after login. While the home dashboard loads data in the background, users see a brief screen of training content they can learn in about 20 seconds.

The platform includes about 100 learning concepts in each of three subjects: Product Management, plus the optional AI Product Management and Marketer Needs subjects. As an administrator, you can create your own bank of learning concepts, enable the optional subjects as needed, and precisely control how often each subject and your custom learning concepts are shown to users at login.

Users can heart concepts they want to explore further and find them later in the Knowledge Library, where each concept includes links to study resources. Users can also see how many teammates hearted each concept, encouraging social learning.