October 2026

Evidence finds its way into the work

October connected more of Outcomet's product loop. Conversations can enter Signals with their speakers intact, Problems can be found and reviewed against evidence, and the resulting decision can continue into an Initiative, Capability or campaign without becoming a detached note.

Availability still varies by story. Unless production verification is stated below, these are implemented changes whose production release was not verified in the source evidence. DEV-only flows and default-off connected-client tools retain their limits.

In this edition

From Andy

On October 20 I was waiting in a Google Meet for the second demo guest of the afternoon. A few minutes late, so Syed and I had that small gap where you either stare at the empty call or say the thing you had not planned to say.

That afternoon I noticed how much had changed over the months of building. I could see it in the demos. The work was becoming usable, and that felt good.

October's changes are less about one large screen and more about that path holding together. A customer conversation becomes evidence. Evidence becomes a Problem. The Problem stays visible when the work moves into a decision, a campaign or delivery. Took long enough, honestly.

- Andy

Bring customer conversations into Signals

Granola meetings can enter Signals from selected folders with speaker-attributed transcripts, optional Contact and Company linking and a visible sync process. Messenger conversations are distinct from public community sources, and Signal details show conversation purpose, speaker relationships, buying signals and the Evidence extracted from each participant.

Interviews, sales calls and messenger conversations captured through a connected client or pasted into Outcomet now keep their actual format and attribute external speakers and companies. Agent observations also retain the authenticated AI client as their reporter. These October 31 attribution changes are published. The broader Conversation Analysis v3 work remains held pending its separate reset verification.

Problem interviews without a screen-share now keep their extracted Evidence, and product practitioners at lower-fit prospect companies remain Prospects rather than being classified as non-target peers. Contact and Company details bring role, Voice relationship, buying role and ICP fit into one editable Summary.

Signals Reporting brings volume, age, resolution, source, origin and issue groupings into one workspace. Filters carry into the table and historical cards without rewriting earlier days from today's state. Production release of the Granola connector and these reporting changes was not verified in their source evidence. Later Inbox restoration and reporting work remains outside this edition while its publication receipts are held.

Find the right Problem and carry it forward

Nova and connected clients can search Problems, Capabilities and Signals with ordinary German or English questions as well as titles, identifiers and technical terms. Results preserve scope and coverage warnings, so a shortlist is useful without pretending to be a complete inventory. The verified production workspace had complete Signal embedding coverage for the bounded October 26 check. Other workspaces were not prewarmed, and the coordinated connected-gateway release remained unverified.

Problem review keeps the evidence beside the decision. Duplicate checks compare candidates with existing Problems, closure previews show the affected Evidence and linked work, and a documented Initiative decision can resolve a Problem without pretending that deferral is delivery. Feedback, Problem and Initiative closures retain explicit controls over what else is resolved.

Customer Jobs and Done When targets now sit with Problems, while Initiative views keep the goal, evidence, Decisions and delivery history together. Capability suggestions still require review, distinguish new behavior from maintenance and show when their search coverage is partial. Other late-October changes that remain held are not announced here.

Initiatives now distinguish goal-led work from Fast-Tracks for direct Problem fixes and Routines for ongoing operational work. Creation starts from a full-page Brief or the Problem catalog. Nova can manage confirmed Initiative and Strategic Opportunity Capability links, while suggestions favor specific, high-confidence Capabilities over broad containers.

Signals Problems can group open and proposed Problems by topic, Customer Job, Initiative, triage or hierarchy. Problems can be nested, promoted or merged, with their evidence and product context moving to the selected target. Topic clusters stay aligned with Capability changes and mark recurring workflows that do not yet have a Capability.

Keep campaigns and contacts connected

Campaign member details put the contact, prior touchpoints, other campaigns and next action in the same working view. Large member lists load progressively without narrowing search or reporting to the first rendered rows. Campaign Reporting adds origin filters, a funnel and diagnostic callouts, while ICP fit can be reviewed and edited from the campaign or record detail.

Contacts and Companies gained workspace custom fields plus profiles for LinkedIn, X, Bluesky, Facebook, TikTok, GitHub, websites and email. The relevant profile follows each campaign channel, primary email stays aligned with its account, and connected clients can merge tags or remove a campaign enrollment without deleting the underlying relationship history.

Authorized production workspaces can start connecting their own HubSpot account, choose the portal and select a Deal pipeline before the first import. The app remains unlisted and limited to 25 installs, and synchronization starts only after Save & Sync HubSpot. This setup release does not announce the separately held communications-ingestion work.

Ownership moved closer to the work across Initiatives, Campaigns, Problems, Capabilities and other workspace records. Assignment does not grant access, and an access-check failure keeps already verified content available for retry.

Let connected clients use the same model

Authorized connected clients can work with more of the same relationships used in the app: existing Feedback and Evidence, Problems, Capabilities, Initiatives, Changes, Campaigns, Contacts and Companies. Each write keeps its role, scope and feature-switch boundaries. Older connections may need to approve additional scopes, and several tool groups remain disabled by default.

Problem review context exposes linked Problems and open Evidence versions without turning an analysis result into an automatic decision. Capability, Campaign and contact actions retain confirmation, permission and validation boundaries, with more specific failure reasons when a request cannot be completed.

Start a workspace with something real

A new workspace can turn its website into a reviewed Product Brief, confirm starter Capabilities and prepare Demo customer messages that enter the normal Feedback and Problem review flow. GitHub setup can wait, completed preparation work survives reload and a failed later step can resume without rebuilding everything.

Demo packages keep real workspace data separate from generated examples. They can be removed together or item by item, and website-based examples group Capabilities under product areas inferred from the accepted brief. These guided flows were exercised in DEV unless their source says otherwise. Production rollout was not generally verified.

Product Context also grounds Nova and other native agents in the workspace's own product, audience and pricing rather than competitor material. Competitor Intelligence keeps its own dated website snapshots, assessment rubric and market map, with explicit scan outcomes for dead domains, temporary failures and bot protection.

Make dense workspaces easier to operate

Tables across Capabilities, Companies, Contacts, Campaigns, Stories, Metrics, Work Items, Experiments and Signals Reporting now behave more like workspace controls. They support sorting, sticky headers, responsive column folding and saved column choices. Database-backed Contact and Company fields sort across the full workspace before pagination, and the Capability tree uses aligned columns with drag-and-drop hierarchy editing.

Feedback, Problems, Initiatives, Strategy, Sources and the other dense workspaces share more consistent selection, reading surfaces and narrow-screen behavior. Light and Dark views received clearer canvas and detail treatments, while report details open beside the selected item on larger screens.

Smaller reliability work is easier to miss, but useful in daily work:

Failed saves keep drafts, while stale GitHub deliveries no longer overwrite a newer status.
Onboarding progress survives later failures, and expired sessions can recover without discarding saved data.
The public Product Journal requires a real headline and source-backed sections. A stale Weekly or Monthly edit cannot fall back to a mechanical inventory.