# Evidence finds its way into the work

**Date:** 2026-10-01 | **Period:** October 2026 | **Edition:** monthly | **Canonical URL:** https://outcomet.app/changelog/2026-10-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.

---

## 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.

- **Choose which meetings arrive:** Granola imports selected folders and leaves private scratchpad notes and unfiled meetings out. Sync pauses when all selected folders have been removed.
- **Keep the original conversation:** Granola uses speaker-attributed transcripts by default, offers transcript-only or summary-only imports, and falls back to the summary when no transcript exists. Sync Now shows import progress.
- **Connect participants to records:** Optional Contact and Company linking brings external attendees into the imported Signal. External participants without email addresses remain part of the conversation.
- **Inspect speakers and purpose:** Signal details distinguish the conversation's format from the channel that captured it. The Brief shows speakers, while the Technical view carries conversation segments and Evidence classifications.
- **Separate customer input from agent observations:** The published October 31 capture changes retain interview, sales-call and messenger formats. Autonomous observations can identify the authenticated AI client as their reporter.
- **Choose the analysis action:** Re-run full analysis extracts Evidence again while preserving confirmed Problem and learning links. Find Problems works with the Evidence already present.
- **Read the Problem before opening its evidence:** Signal Brief keeps Problem severity, title and summary visible, with supporting Evidence expandable underneath. This detail presentation was verified in production.
- **Keep classification at the right level:** The Technical view separates the Signal's context from each Evidence item's classification. Reporting can group interview Signals across their Evidence issue types and layers. These changes were verified in production.
- **Follow a report into the source:** Selecting a reporting KPI, chart or cohort filters the Signal table and opens the selected Signal beside it. Reporting sections collapse independently, and the table has its own sorting and column choices.
- **See progress without losing closed Problems:** Signal cards distinguish Evidence progress from Problem progress. Closed Problems remain available below open and proposed ones in the detail view.

## 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.

- **Compare a possible duplicate:** The comparison shows both Problems, cited Evidence, shared aspects, differences and a recommendation. Link to the existing Problem or keep a separate one. Reopening an unchanged comparison reuses its result.
- **Work through a decision queue:** Discovery places the prioritized queue beside the Decision Brief. Open related Problems and delivered Changes without leaving the decision view, with one primary next action for the current phase.
- **Archive without losing the history:** Archived Initiatives retain linked Problems, Evidence and Decisions and can be restored. Include archived is separate from the Open/Closed filter.
- **Check whether the work resolved the Problem:** Review resolution against linked Changes and documented Initiative Decisions, inspect the supporting explanation and use verified proof when preparing a closure note. Changed supporting context marks an older verification as stale.
- **Choose what closes together:** Problem and Initiative closure show the affected supporting Evidence and let you leave it open. Feedback resolution can include Evidence and linked Problems, with the scope chosen before confirmation.
- **Keep the customer job with the Problem:** Customer Jobs and Done When targets stay alongside the Problem, rather than requiring a separate note to explain the desired result.
- **Use the right work type:** Fast-Tracks cover direct Problem fixes, Routines cover ongoing work, and ordinary Initiatives retain their goal-led flow. The creation Brief accepts a prompt or starts from the Problem catalog.
- **Build a readable hierarchy:** Drag Problems under a parent or back to the top level. Parent rows show the combined Evidence and sub-problem count, and a merge moves the linked product context to the selected target.
- **Organize the unclustered work:** Organize topics runs from the table or the Unclustered group with visible Nexus progress. Pending proposals join the same topic view as canonical Problems, including Emerging topics without a corresponding Capability.
- **Review Capability suggestions:** Specific, high-confidence Initiative matches are selected first. Change exploration distinguishes changed product behavior from incidental maintenance, can propose a new ability alongside an existing one, and keeps the review decision with you.
- **Make deliberate links in chat:** Nova can link or unlink Initiative Capabilities and remove a Strategic Opportunity Capability link. Each change asks for confirmation, and inspection includes linked Capability maturity.
- **Read Capability health consistently:** Composite health breakdowns and historical sparklines now use the same rolled-up view instead of showing disconnected direct-Problem history.

## 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.

- **Stay inside the campaign member:** Open the linked Contact or Company in the same panel and return directly to the member. Other campaigns and prior interactions remain close to the next action.
- **Log a run of touchpoints:** Expand logging inside the member panel, use date presets, add notes and links, then choose Add & Log Another. Previously logged touchpoints can be edited, and mistaken entries can be removed after confirmation.
- **Import the history with the people:** Campaign imports accept members and touchpoint history from Markdown or JSON, with import guidance available to operators.
- **Make the next action explicit:** Schedule an outreach step and due date from the member view, and edit the selection rationale as rich text.
- **Coordinate the operators:** Assign campaign members, filter the pipeline by assignee or Unassigned, and see who logged each touchpoint. Cards and tables display the same ownership context.
- **Keep profiles useful across channels:** Contact and Company profiles cover LinkedIn, X, Bluesky, Facebook, TikTok, GitHub, websites and email. Campaign enrollment follows the relevant channel profile, including when it is added later.
- **Store workspace-specific context:** Administrators and editors can define Contact and Company custom fields. Values can be edited in the Technical view and included in supported imports and connected-client updates.
- **Review fit where outreach happens:** Inspect or edit ICP fit from the campaign or the Contact and Company record. Campaign Reporting adds origin filters, a funnel and diagnostic context.
- **Finish HubSpot setup deliberately:** The production setup shows Not connected before authorization and Needs setup afterwards until a Deal pipeline is selected. Save & Sync HubSpot starts the first import. The unlisted, 25-install limit still applies.
- **Keep responsibility separate from access:** A shared member/team directory and compact assignment controls support work across records. Assigning an owner does not change who may access the workspace.

## 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.

MCP is the connection used by external AI clients for these tasks. The following additions remain subject to their explicit grants and enabled tool groups. Their coordinated production release was not verified in the source evidence. Problem writes remain off by default, and external proposal creation remains disabled.

- **Maintain an existing Capability:** Authorized member or admin connections can edit supported fields with version checks, rather than only reading the catalog. Older connections may need to approve additional access.
- **Create a Problem from real Evidence:** Where Problem writes are enabled, a connected client can create the Problem from its supporting source and explicitly link it into the chosen Initiative.
- **Create a Campaign draft:** An authorized connection can prepare a Campaign without sending messages. Repeating the same request returns the existing draft.
- **Carry the relationship explicitly:** Connect selected Evidence and an existing Problem to an Initiative, or link a Capability. Creating a record alone does not silently make those connections.
- **Prepare an Initiative goal:** Trusted callers can inspect prepared goal suggestions and confirm a chosen or custom goal. Returned Initiative links use the current application route.
- **Review a proposal with its context:** Connected clients can read active Problem proposals, background, exclusions and per-chunk outcomes. Approval and rejection require the corresponding enabled write access.
- **Maintain contact history:** Authorized contact writes can merge tags, record supported interactions and remove a Campaign enrollment without deleting the Contact, Company or interaction history.
- **Understand a failed action:** Permission, validation and temporary-service failures carry more specific reasons, while unsupported access remains unavailable.

## 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.

- **Begin with the website:** Review the synthesized Product Brief, its intended audience and starter Capabilities before accepting the setup. Crawl progress, cancellation and recovery stay visible.
- **Keep existing work:** Starter content is limited to eligible empty workspaces. Going back through an accepted step does not duplicate records, and an existing account can opt into guidance without replacing its Product Context.
- **Ask in the context of the current step:** Nova and Polaris introduce their role during guidance and answer using the active step and ready website context.
- **Use examples that fit the product:** Demo customer messages are prepared from the accepted context and pass through ordinary Signal, Evidence and Problem review. They remain identifiable as Demo data.
- **Bring your own input too:** Own Feedback stays alongside Demo examples. Saved messages and preparation progress survive reload, and an unsuccessful later stage offers recovery from what was already saved.
- **Choose when to connect GitHub:** Add GitHub later keeps setup available in Delivery. A provider connection alone does not stand in for a successful import or reviewed Feedback.
- **Continue or replay the guide:** The later tutorial introduces the workspace areas in sequence. Back preserves progress, and an explicit reset keeps real product data and connections.
- **Remove examples deliberately:** Delete individual Demo Signals or remove a completed package through the supported confirmation flow, while preserving additional real-data relationships.

## 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.

The supporting changes cover the controls used repeatedly throughout the day:

- **Keep actions available across tabs:** Primary actions, linking controls and terminal actions remain accessible in Brief and Technical detail views.
- **Use the keyboard in inline editing:** Enter or Space opens supported fields, Escape cancels the edit, and a failed save preserves the draft.
- **Read and edit on narrow screens:** Detail titles, tabs, metadata and action rows wrap instead of hiding essential controls. Long dialogs scroll inside the viewport.
- **Choose the table you need:** Sort, choose visible columns and retain per-user preferences across the updated data tables. Contact and Company sorting applies to the full dataset before pagination.
- **Work with the Capability hierarchy:** Aligned tree columns and drag-and-drop support sibling order and movement under another Capability.
- **Keep the report beside its detail:** Larger screens open report details alongside results. Shared report headers and transparent sparkline cards keep the reading pattern consistent.
- **Keep historical gaps honest:** Initiative and Metric history do not invent a zero baseline when tracking is missing.
- 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.

## Carry the decision into planned work

Delivery Timeline can hold the work before an implementation exists. A Proposed Change opens with its implementation context, desired outcome and success criterion already filled in. Create work item is available directly, and one Initiative can contain several proposals with several Work Items under each.

The reviewed handover stays with the proposal as the work develops. Existing Work Items remain visible even when they do not yet have a Change, and the Timeline distinguishes draft, open, merged and closed-without-merge pull requests. These planning changes were verified in production on October 10. Live tracker export acceptance and the installed GitHub App's end-to-end transport remained unverified, so proposal-specific tracker destinations retain their release gates.

- **Start from the prepared brief:** Create a Work Item without a separate Prepare/Save step, or edit the proposal first. A failed save preserves the draft.
- **Plan more than one piece of work:** Add another Work Item while retaining the Initiative, proposal and destination context. Work already on the Initiative is not silently assigned to a new proposal.
- **Keep the handover inspectable:** Open the full reviewed context on demand, link existing work explicitly, or archive and restore a proposal.
- **Preserve proposals when work moves:** Merging Initiatives retains proposal identities and reviewed snapshots under the target Initiative.
- **Navigate future work:** A Timeline containing only planned work opens on those future columns, including after reload. Adding another Work Item keeps the current camera position.
- **Read the actual PR state:** Draft, Open, Merged and Closed have distinct badges and symbols. Closed without merge remains different from completed implementation.
- **Keep newer tracker information:** An older GitHub delivery or import no longer replaces a newer stored status. A merged PR or new Work Item does not automatically close its proposal or Initiative.

## Compare competitors with their own words in view

Competitor Intelligence brings a profile, landscape map and risk view together. Open a competitor to read its website pitch separately from the workspace's strategic assessment. That separation matters when a vendor's claim and your interpretation of it are different things.

The map can compare dated assessments and show movement, while the detail view keeps the underlying website material available for inspection. The early-October production database release verified competitor access and related Company/Contact lookup. Broader release of the map and scanning changes was not established by those database checks.

- **Switch the view without losing the subject:** List, Map and Risks present the tracked competitors, with profile details and linked Contact and Company context available alongside them.
- **Read the two briefs separately:** Their pitch shows the vendor's self-description. Our read and Against us carry the workspace assessment, with the scoring breakdown in the Technical tab.
- **Inspect literal claims:** Value propositions are checked against website copy, and verified quotations remain distinguishable from unverified claims.
- **Compare assessment dates:** Historical snapshots update the landscape and can show prior positions and movement paths. Search filters the visible competitor markers.
- **Read a crowded landscape:** Concentration and threat can be shown as contours or relief. Labels, own-product position, camera controls and saved map preferences remain available.
- **Follow a website scan:** A live progress view and expandable step history show the crawl, extraction and verification stages.
- **Distinguish scan outcomes:** Dead domains are reported separately from temporary server errors and bot protection, so a blocked request is not presented as a vanished competitor.
- **Inspect through a connected client:** MCP support covers competitor profiles, landscape snapshots, risks, assessments and their relationships under the connection's permissions.
