Skip to content
PM Companionby Response Shift

A work companion for product managers

Pick up the work.
Keep the context.

Your projects, remembered. Your preferred AI, fully briefed.

The interview that changed your thinking. The trade-off behind the roadmap. The decision you need next week. Keep them together, with the sources still attached.

Use your invitation Explore the example

Invitation required. Use or create a Response Shift account to check your existing invitation.

Your assistant is where the conversation happens.
Your workspace is where the work carries on.

Inside a project

A brief with a paper trail.

Synthetic example

Fictional team onboarding project. Every note and response below is an authored example; nothing is sent or saved.

Team onboardingRevision 2

What should we work on next?

Decision with sources

Current decision
Make invitation status visible before expanding the workspace tour. [2]
Why it matters
The uncertainty appeared after the invitation, not while creating the workspace. [1]
Next check
Test whether visible delivery status helps someone explain what happens next. [2]

A useful starting point, with the reasoning still attached.

Follow the source

  1. Interview note · 12 June · fictional

    The invitation was the uncertain step

    The participant could create a workspace, but could not tell whether their teammate had received access.

  2. Decision record · 13 June · fictional

    Make invitation status visible first

    Keep the invitation step in scope. Show its delivery status before adding a longer workspace tour. Revisit after the next test.

01 / CaptureSave the evidence that matters.

02 / ReuseBring its reasoning into the next conversation.

03 / ContinueOpen the work and move it forward.

Your agent. Your project context.

A fresh conversation
doesn’t need a fresh start.

Your chosen assistant can use the project context you give it permission to access. Ask for a brief, capture a selected note, or continue a decision.

  1. Choose the project.Keep work from different projects in its own context.
  2. Choose the permission.Reading, editing and creating projects are explicit choices.
  3. Continue where it helps.Stay in your assistant for the conversation. Open the workspace for a canvas or document.
See beta connection options

A place to do the work

Some thinking needs
more than a chat window.

Turn the context into a working document, a decision canvas or a plan you can change. Your assistant and workspace use the same project records.

Team onboarding Working roadmapSynthetic example

Now

Understand the invitation gap

Interview notes · decision brief

Next

Test the revised explanation

Research plan · survey

Later

Revisit the workspace tour

Roadmap · trade-offs

A plan with its reasoning nearby. Change the work as your understanding changes.

Make the decision

Bring evidence into frameworks, stakeholder maps and working documents.

Make the plan tangible

Shape roadmaps, diagrams, sprint boards and project schedules.

Keep the work moving

Prepare meeting agendas, launch checklists, risk registers and status reports.

Useful between sessions. Under your control.

Decide how much
the companion takes on.

Keep a simple record, review proposed changes, or authorize bounded maintenance. The policy is visible, and your project’s history stays inspectable.

01 Store

Keep what you submit

Save selected context and retrieve it when you need it.

02 Assist

Bring changes to review

Let the companion propose updates for you to inspect.

03 Maintain

Apply the changes you allow

Authorize bounded background updates, with a visible history and correction controls.

Reminders have their own permission. Authorizing maintenance does not turn on emails. Choose your reminders and notification preferences separately.

Only what you submit

Capture selected context. The companion does not silently collect your whole chat history.

Sources before certainty

Review where a claim came from, see open conflicts, and correct what should carry forward.

A connection you can revoke

Disconnect an assistant, review its permissions, and use the workspace’s export and deletion controls.

Beta connection options

Keep the assistant
you prefer.

Beta setup packages and guidance are available; real connections in each host still need verification.

Read the setup and removal guide

Codex desktop

Local plugin package

Connection unverified

ChatGPT web

Remote MCP developer setup · account dependent

Connection unverified

Claude Code

Plugin archive and marketplace guide

Package checked locally · connection unverified

Claude web / Desktop

Remote connector guidance · account dependent

Connection unverified

Before you join

A few clear boundaries.

Can I use my existing Response Shift account?

Yes. Your account identity is shared, while companion access and project data are separate. You need a companion invitation, and you may need to sign in again on this site.

Does creating an account request a beta invitation?

No. This beta is invitation only. Creating an account does not submit an invitation request or guarantee workspace access. If you have an invitation, use the account it was issued to.

Will a new note overwrite an accepted decision?

Sources, proposed updates and accepted understanding are distinct. Conflicting evidence should remain available for review. You can inspect changes and record corrections.

Are voice and video rehearsal part of the beta?

Simulated audio and video rehearsal are optional. Provider availability and session behavior need verification for the pilot. This page does not start a call or request microphone or camera access.

Invitation beta

Let the next conversation
start with what you already know.

A home for your project context. A workspace for the next decision.

Use your invitation

Sign in with the account your invitation was issued to.
Account creation alone does not request or grant beta access.