What changed
In a report published September 30, 2026, ChartMogul analyzed 10.5 million customer purchases from 4,029 private software companies. Customers were grouped into signup cohorts spanning August 2025 through June 2026, and behavior was observed through July 2026. Seat-upgrade rates were 0.83% in the first month, 0.37% in month two, 0.19% in month four and 0.09% by month eleven. Plan upgrades likewise fell from 0.75% in month one to 0.16% in month four, while 40% of first-year plan upgrades occurred at month twelve around renewal. SaaS products saw almost three times the overall plan-upgrade rate of AI-native products; AI-native churners were comparatively more likely to return, with reactivation approaching 10%.
Why it matters
Expansion and retention are not just pricing questions; timing shapes when customers are ready to add colleagues, adopt a higher plan or come back after cancelling. Builders who wait until mid-contract to prompt team invites may miss the period when adoption is still being organized. Annual renewals offer a separate upgrade moment. For small SaaS teams, the actionable implication is to design collaborative activation, feature trials and winback flows around actual lifecycle moments, while testing against their own customer segments rather than assuming the observational report proves that prompts cause upgrades.
The first month is the seat-expansion window
Across the analyzed cohorts, 0.83% of customers added paid seats during month one, versus 0.37% in month two, 0.25% in month three, 0.19% in month four and 0.09% by month eleven. Month one is therefore roughly 9.2 times month eleven on the reported rate. That is a descriptive cohort pattern, not evidence that sending an earlier sales message will itself produce a ninefold uplift. It suggests teams should make invitation and collaboration paths visible during initial activation, when customers are setting up their working group.
Plan upgrades show two distinct opportunities
Plan upgrades ran at 0.75% in month one, 0.32% in month two, 0.28% in month three and 0.16% in month four. A different pattern appears at annual renewal: 40% of first-year plan upgrades happened in month twelve. This supports evaluating early in-product feature previews and trials separately from a renewal-stage value review, rather than relying on an undifferentiated recurring upsell campaign.
SaaS and AI-native businesses do not expand the same way
The study reports about twice the new-customer seat-upgrade incidence for conventional SaaS compared with AI-native products, and nearly three times the overall plan-upgrade rate. ChartMogul suggests AI products may be used more individually or may monetize through usage and credit top-ups instead of conventional seats or plans. It does not establish which explanation dominates; product mix and pricing-model differences are unresolved.
Cancellation does not end the lifecycle
The monthly reactivation rate after cancellation was 2.67% in month one, 1.24% in month two and 1.14% in month three. The report says AI-native churners reactivate at nearly 10%, above conventional SaaS. That may reflect project-based or intermittent use, not necessarily healthier recurring retention. Operators should preserve workspaces and integrations where possible and evaluate winback sequences by cancellation reason rather than treating every churned account identically.
The dataset is large, but it is not a randomized experiment
ChartMogul analyzed 10.5 million purchases from 4,029 private companies, using recent customer cohorts and observing behavior through July 2026. Purchases were commonly self-serve transactions below $100 per month. The vendor both supplies the underlying data and authored the analysis; customer-level data is not independently available. Upgrade percentages are observational monthly rates and should not be misread as causal effects of any particular lifecycle tactic or assumed to generalize to high-touch enterprise sales.
What a small SaaS operator can actually test
Start with the product's natural collaboration milestone, not a blanket popup: invite a teammate after a useful shared artifact is created, make higher-tier benefits concrete in the workflow, and compare cohorts exposed to an early offer with an appropriate holdout. For annual contracts, couple the renewal notice with a usage and value summary. For cancellations, test low-friction reactivation at roughly 30 and 60 days while preserving user consent and avoiding dark patterns.