October 29, 2026

Keep interview evidence and contact context together / Connect your own HubSpot account / Finish connecting HubSpot / Organize Problems into topics and hierarchies

In this edition

Keep interview evidence and contact context together

Problem interviews without a screen-share demo no longer lose extracted Evidence because the interview was misclassified. Product practitioners and leaders at lower-fit prospect companies are also classified as Prospects instead of non-target peers.

Contact and Company details now open with a collapsible Summary containing role, email, Voice relationship, buying role, ICP fit and its rationale. You can edit these fields there, and change Voice and buying role directly in Contact headers and the Contacts table.

Detail sections remember whether you left them open or collapsed. Empty HubSpot context stays hidden, text and controls have consistent sizing, and short contact titles no longer wrap prematurely. The Brief and Technical switch sits beside the header actions.

Connect your own HubSpot account

From any authorized Outcomet workspace, you can start connecting your own HubSpot account. HubSpot asks you which account to authorize, and Outcomet shows the selected portal before import. The app remains unlisted and is currently limited to 25 installs. Before connecting, the setup screen shows “Not connected” and makes clear that synchronization starts only after setup.

Finish connecting HubSpot

After you authorize a HubSpot portal, Outcomet shows “Needs setup” until you choose a Deal pipeline. The setup page then points you to “Save & Sync HubSpot”, which starts the first import when you select it.

Organize Problems into topics and hierarchies

In Signals Problems, group open and proposed Problems by Triage, Topic Cluster, Customer Job, Initiative or Hierarchy Only. Sections collapse independently while sub-problems stay under their parent. Signals Inbox and Problems also have clearer group headers and progressive loading as you scroll.

Topic clusters connect Problems to existing Capabilities. Recurring customer workflows without a corresponding Capability are marked as Emerging. Parent Problems show the combined evidence and number of sub-problems.

Drag a Problem under a parent, move it beside another Problem or return it to the top level. Problem details offer Set parent problem, Promote to top-level problem and Merge into problem in both Brief and Technical views. Merging transfers the linked evidence and product context, including child Problems, to the target and marks the original Problem as superseded.