Activity Index · Customer Service & Support
Methodology v1How much verified change ToolMarketCap has recorded for each tool over the last 90 days — counted from dated, first-party changes. It measures observed activity, not popularity, adoption, or quality, and a market new to the record shows limited history.
As of 6 Nov 2026Exact formula and worked example
- Median activity
- —/ 100 · 0 tools
- The middle value across tools with a value; each tick is one tool
- Confidence
- 0high
- 0 high · 0 moderate · 0 limited · 13 without a value
Highest observed activity90-day window
More recorded change activity is not better: a tool that ships rarely and deliberately scores low by design.
The changes behind itmost recent
No verified change in the last 7 days. The most recent ones feeding the index:
- JunieReleaseJunie Eco mode hands implementation to a lower-cost model
- GitHub CopilotPlansGitHub Enterprise now includes Copilot for every licensed user
- SierraReleaseSierra launches Compliance Console for outbound agents
- GitHub CopilotReleaseGitHub Copilot Fusion becomes generally available
- GitHub CopilotReleaseGitHub Agentic Workflows become generally available
- AmpPlatformAmp launches an Android app
- Microsoft 365 CopilotReleaseLearning Agent and admin-deployed custom MCP connectors arrive in Copilot
- KiroPlansKiro replaces its upgrade discount with a free first month and 500 trial credits
Every tool13 tools
Ordered by observed activity, then name; ties share a value. Tools with insufficient history are listed last with no value — missing is never zero. A value of 0 means no verified change in 90 days on a record that covers the window.
By segmenteditorial classification
Segments differ in natural release cadence; their medians describe recorded activity, not the quality or size of a segment. Values are not normalized within segments.
What the index is — and is not
One number per tool, from 0 to 100, summarizing how much verified, dated change ToolMarketCap logged for it in the last 90 days. Newer changes count more; a value is published only when the record behind it is long enough.
- Dated changes logged from first-party sources
- Distinct days with a change — newer days weigh more
- How many kinds of change those were
- With a stated confidence in the record behind it
- Popularity, adoption, usage, or market share
- Product quality, or which tool is better
- Revenue, valuation, traffic, or sentiment
- How big or important any single change was
Activity = round(100 × (0.7 × Volume + 0.3 × Breadth))
window the last 90 whole UTC days, today included
weight w(day) = 0.5 ^ (age in days / 30)
Volume min(1, ln(1 + V) / ln(1 + 4))
V = Σ w over distinct days with at least one change
Breadth min(1, (Σ over kinds of the largest w in that kind) / 3)
kinds: pricing & plans, releases, availability & platforms, ownership & names90-day window · weight halves every 30 days · same-day changes count once · daily snapshots recorded since 11 Oct 2026. Full methodology and worked example →