Tehodemo@northstar.example

Tools

Customer-system activity routes through 4-5 tool hops per ticket. The biggest hopping loop is Email → Teams → CRM → Meeting.

Top hopping loops
3
AI tools in use
0 (baseline)

Tool footprint

38

Distinct safe tool footprint inside the function boundary.

Top-five tool concentration

64%

Share of reportable tool signal represented by the top five safe tool categories.

Switching load

High

Baseline field; real pipeline switching confirmation is not yet available.

Switching flows

1

Function-level ordered paths in the current workspace contract.

Catalogue links

2

Safe tool categories linked back to catalogue patterns.

Function-level tool evidence

How tools shape work

This view uses safe tool categories and aggregate states to explain how work moves through the function digital estate. It does not show individual app usage or productivity rankings.

Tool inventory

Safe categories and proportions

Usage shares are shown only when safe. Suppressed values remain visible as protected aggregate states instead of zero or blank cells.

Tool labelCategoryShareConfidenceCoverage
CRMCustomer system22%High confidenceFunction-level reporting inside agreed Northstar boundary.
SpreadsheetProductivity18%High confidenceFunction-level reporting inside agreed Northstar boundary.
MessagingCollaboration14%Medium confidenceFunction-level reporting inside agreed Northstar boundary.
Below-threshold toolsRare or sensitive tools are aggregated to avoid exposing small slices.AggregateSuppressedNot applicable confidenceRare or sensitive tool observations are aggregated.

Switching flows

Function-level movement between tools

Flow order is preserved from the workspace contract. Qualitative or source-not-ready switching signals stay qualitative.

Tool-to-pattern lineage

Where tools meet the Work Catalogue

Links point toward related patterns, hotspots, and opportunities without repeating those tabs or implying missing links are irrelevant.

AI adoption

Later ready

AI adoption fields are represented for future providers but are not required for this baseline fixture.

Signal setting
not_enabled_in_baseline_fixture
Readout state
later_ready