June
Company-level product analytics for B2B SaaS, wound down into Amplitude in August 2025
June was a product analytics tool built specifically for B2B SaaS, distinguished by treating the company account rather than the individual user as the primary unit of analysis. It connected to Segment, RudderStack, Freshpaint, or its own SDKs and auto-generated a starter set of reports (active users, retention, power users, feature adoption, funnels) within minutes of connecting a data source. June's founding team joined Amplitude in 2025 and the standalone product wound down on 8 August 2025; new signups are no longer possible and the recommended path is Amplitude.
Overview
June started from an observation that most product analytics tools were built for consumer software and then sold to B2B companies that did not fit the model. In a consumer product, the user is the account, so a retention curve of individual users answers the business question. In B2B SaaS, twelve people at one customer share a subscription, and knowing that seven of them logged in last week matters far less than knowing that the account as a whole has gone quiet three weeks before renewal. June's core design decision was to make the company the first-class object: every report could be flipped from user-level to company-level, and a company profile page showed usage, active seats, key events, and CRM context in one view.
The second decision was to remove setup as a barrier. Most analytics deployments stall at the instrumentation stage, where someone has to design a tracking plan before any chart exists. June connected to an existing Segment, RudderStack, or Freshpaint stream and auto-generated a set of templated reports immediately: active users and active companies, user and company retention, power users, feature reports, sign-up conversion funnels, and slipping-away accounts. Teams got a working dashboard on day one and refined the tracking plan afterwards, which is the reverse of how Amplitude or Mixpanel deployments usually go.
The commercial story is the part a buyer in 2026 needs. June launched with a free tier and a $149 per month Growth plan, and for several years it was one of the cheapest credible ways for a seed-stage B2B company to get real product analytics. In October 2024 the company removed the free plan and collapsed everything into a single quote-only all-in-one plan tiered by monthly active users, stating publicly that June was a good fit for companies with at least $1M ARR and that there would be no startup plan. Nine months later, on 8 August 2025, the standalone product wound down entirely: the founding team joined Amplitude, monthly subscribers were billed pro rata, annual contracts were refunded for unused days, and customers were given a thirty-day window to export data or migrate events into an Amplitude workspace. June is documented here as a discontinued product, not a purchasable one.
Best for
Historically: seed to Series A B2B SaaS teams that needed account-level usage analytics fast, without a data team or a tracking plan, and that already ran Segment. As of 2026 the honest answer is that it is not for anyone, because the product no longer exists; the profile is retained for teams evaluating its successors or planning a migration off it.
Not the right fit for
- Anyone buying analytics today; June wound down on 8 August 2025 and cannot be purchased, trialled, or signed up for.
- Consumer or B2C products, where the company-level model that justified June's existence adds nothing.
- Teams needing session replay, feature flags, or experimentation, none of which June offered.
- Data teams wanting full SQL control over a warehouse-resident event store rather than a hosted, opinionated report set.
- Mobile-first products; June's strength was web SaaS, and its templates and identity model assumed a logged-in web application.
- Small startups after October 2024, when the free plan was removed and pricing moved to a quote-only plan explicitly aimed at companies above $1M ARR.
How it works
- 1
You connected a data source rather than instrumenting from scratch. June supported Segment, RudderStack, and Freshpaint as CDP sources, plus its own SDKs for browser, React, Node, Python, Ruby, and raw HTTP. No-code importers backfilled historical events from Mixpanel and Amplitude so the first reports were not empty.
- 2
Identity was resolved at two levels. Standard identify calls established the user, and group calls attached that user to a company account with traits such as plan, MRR, industry, or seat count. The group call was the hinge of the whole product: without it, company-level reporting silently degraded to user-level reporting.
- 3
On connection June auto-generated a report set from templates rather than presenting an empty query builder. Active Users, Power Users, User Retention, Company Retention, Active Companies, Power Companies, Feature reports, Funnels, Sign-up conversion, and Slipping Away lists all existed before anyone opened a chart builder, and each could be narrowed with audiences (saved filters over user or company traits).
- 4
Findings moved outward through Slack alerts, CRM sync, and the embed API. A two-click Slack alert notified a channel when a company hit a milestone or went quiet; Salesforce, HubSpot, and Attio integrations wrote usage traits back onto the CRM record so account executives saw product engagement without opening June; and the embed API let teams surface June charts inside their own application.
- 5
For questions the templates could not answer, June AI provided an AI-assisted SQL editor over the underlying event data, and computed traits let a team define derived properties (for example, weeks since last active) once and reuse them across reports and audiences.
Feature breakdown
28 features in 4 modulesCompany-level analytics
The reason June existed: the account, not the individual, as the unit of analysis.- Company profiles
- A page per customer account showing active seats, event history, adopted features, and CRM traits, so a CSM could answer 'how is this account doing' without building a report.
- Company retention
- Retention curves computed at the account level, which is the metric that actually predicts B2B renewal, rather than individual-user retention that noise from seat turnover distorts.
- Active Companies
- Daily, weekly, and monthly active accounts as a headline chart, defined by any tracked event from any user belonging to that company.
- Power Companies
- A power-curve view identifying accounts in the heaviest usage band, used both for expansion targeting and for finding candidates for case studies and referrals.
- Slipping away lists
- Automatically maintained lists of accounts and users whose activity dropped against their own baseline, the closest thing June had to a churn early-warning system.
- Auto-generated companies
- Where group calls were missing, June could infer company grouping from email domain, which got teams to company-level reporting before their engineers shipped proper group tracking.
Reports and analysis
A templated report set that existed before you asked for it, plus escape hatches for harder questions.- Active Users report
- Generated automatically on connection, counting any user performing any tracked event as active, with daily, weekly, and monthly views.
- Power Users curve
- Distribution of users by number of active days in a period, the standard engagement-depth view, produced without configuration.
- Feature report
- Adoption and penetration of a single feature within a chosen audience, answering whether the thing you shipped last quarter is used by the customers it was built for.
- Feature audit
- A ranked view across all tracked features showing which are widely adopted, which are used by a narrow set of accounts, and which are effectively dead.
- Funnel report
- Drop-off between steps of a linear flow such as onboarding or checkout, with the ability to open the list of users or companies stuck at any step.
- Activation explorer
- A view for finding which early behaviours correlate with users who stick, used to define an activation metric rather than guessing one.
- The Explorer
- The free-form chart builder for questions the templates did not cover, with event, property, and audience filters.
- June AI SQL editor
- An AI-assisted SQL surface over the event data for custom analysis, aimed at analysts who hit the ceiling of the visual builder.
- Computed traits
- Derived properties defined once (days since last session, count of a key event, seat count) and reused across reports, audiences, and alerts.
- Benchmarks
- Comparison of your headline metrics against aggregate ranges from similar B2B SaaS products, which gave small teams a reference point they otherwise lacked.
Audiences, alerts, and distribution
Getting the finding to the person who acts on it, usually in Slack or the CRM.- Audiences
- Saved filters over user or company traits and behaviour, reusable across every report so a definition like 'paying accounts on the Pro plan' existed once.
- Slack alerts
- Two-click alerts posting to a channel when an account hit a milestone, adopted a feature, or went quiet, which is how most non-analyst users experienced June day to day.
- Company and audience alerts
- Threshold and event-based notifications scoped to a single account or a whole audience, rather than only global metric alerts.
- Dashboards
- Collections of reports pinned into a single view for a team or a weekly meeting, shareable across the workspace.
- Embed API
- Programmatic embedding of June charts inside your own product or internal tools, included on the all-in-one plan.
- User milestones
- A timeline of significant first-time actions per user and per account, useful for spotting where an onboarding sequence actually completed.
Data plumbing and integrations
How events got in and how insight got back out to sales and success tooling.- CDP sources
- Native connections to Segment, RudderStack, and Freshpaint, so teams already streaming events could turn June on without engineering work.
- First-party SDKs
- Browser, React, Node, Python, Ruby, and HTTP libraries for teams that did not run a CDP and wanted to send events directly.
- Historical backfill importers
- No-code importers from Mixpanel and Amplitude that loaded past events so a new June workspace had history rather than starting from zero.
- CRM sync
- Salesforce, HubSpot, and Attio integrations pushing product usage traits onto account records, which is where the sales team actually works.
- Stripe integration
- Revenue and subscription data joined to usage so accounts could be filtered and ranked by MRR alongside engagement.
- Data enrichment
- Automatic enrichment of user and company records with firmographic detail, reducing the amount of context a team had to pass in manually.
Use cases
4 documentedCustomer success lead at a 40-person B2B SaaS company
Renewals are handled from a spreadsheet of gut feel, and the team finds out an account has disengaged when the cancellation email arrives.
Company retention plus a slipping-away audience wired to a Slack channel gives the CSM a weekly list of accounts whose usage fell against their own baseline, moving the first renewal conversation weeks earlier.
Solo product manager at a seed-stage startup with no data team
Segment is already streaming events, but nobody has built a report, and the PM does not want to spend a sprint designing a tracking plan before seeing a single chart.
Connecting the existing Segment source produces active users, retention, power users, and a sign-up funnel the same afternoon; the tracking plan gets refined afterwards against reports that already exist.
Founder deciding whether a newly shipped feature earned its build cost
The feature was built for enterprise-tier accounts, but the only evidence of use is a raw event count that mixes trials, internal users, and paying customers.
A feature report scoped to an audience of paying accounts above a set MRR shows penetration within exactly the segment it was built for, which either justifies further investment or ends it.
Head of growth wiring product signals into sales
Account executives have no visibility into what a trial account is doing, so outreach is timed by calendar rather than by behaviour.
The HubSpot integration writes usage traits onto the company record and a Slack alert fires when a trial account crosses an activation threshold, so outreach follows the signal instead of the day of the week.
Pricing
from No longer sold (product wound down 8 August 2025); the last published self-serve price was $149 per month on the Growth plan before it was retired in October 2024Historic. June began with a freemium model (free up to roughly 1,000 active users, Growth at $149 per month, custom pricing above that). In October 2024 it removed the free plan and moved to a single all-in-one plan, quote-only, tiered by monthly active users, with every feature included at every tier and a 14-day trial. The product wound down on 8 August 2025 and is no longer sold; no current price exists.
| Plan | Price | Includes |
|---|---|---|
| Free (retired October 2024) | $0 per month |
This tier was what made June popular with early-stage startups, and removing it was the clearest signal of the company's move upmarket. |
| Growth (retired October 2024) | $149 per month |
The last transparent, self-serve price June published. |
| All-in-one (October 2024 to August 2025) | Quote only tiered by monthly active users |
Publicly positioned as a fit for companies with at least $1M ARR, with the company stating plainly that there was no startup plan. |
Billing notes
- Nothing in this section is purchasable; it is recorded so teams comparing successors understand what June cost and how the meter worked.
- The all-in-one meter counted monthly active users, defined as unique users who logged in or performed an action; anonymous visitors were not charged for.
- Removing the free plan in October 2024 came with a stated rationale: the company wanted pricing high enough to fund 1:1 support, and accepted losing the bottom of the market to do it.
- Existing free and Growth customers were allowed to keep their access at the October 2024 change rather than being forced to upgrade immediately.
- At wind-down, monthly subscribers were charged pro rata to 8 August 2025 and annual or multi-year customers were refunded for unused contract days.
Value assessment: For its first four years June was one of the best value purchases in product analytics for small B2B SaaS: $149 a month bought account-level retention and adoption reporting that would otherwise have meant an Amplitude or Mixpanel contract plus a data person to configure it. That value evaporated in two steps. The October 2024 move to quote-only pricing aimed at companies above $1M ARR removed the segment the tool was best for, and the August 2025 wind-down removed the product. Any team currently budgeting for June should redirect the line item; the vendor-recommended destination is Amplitude, and the closest self-serve substitutes for the company-level model are Mixpanel with group analytics enabled or PostHog with a group type configured.
Strengths & limitations
Strengths
- The company-level data model was genuinely differentiated: B2B retention, expansion, and churn questions answered at the account level by default rather than by workaround.
- Time to first insight was measured in minutes because reports were auto-generated from templates on connection rather than built from an empty canvas.
- It fitted the existing stack instead of replacing it, reading from Segment, RudderStack, or Freshpaint rather than demanding fresh instrumentation.
- Slack alerts and CRM write-back put usage signals in front of sales and customer success, who are the people who act on them.
- Deliberately narrow scope meant a small team could actually use all of it, in contrast to enterprise platforms where most surface area goes untouched.
- Support quality was a consistent theme in user reviews, with a 5.0 average on G2 across a review base that was roughly ninety percent small business.
Limitations
- The product no longer exists. June wound down on 8 August 2025, signups are closed, and the website now serves an acquisition notice; the YC profile lists the company as inactive.
- Data was not retained indefinitely after the wind-down: customers had a thirty-day export window, so a team that missed it has no route back to its historical event data.
- Company-level reporting depended on correctly implemented group calls. Where engineering had not sent group traits, June fell back to inferring accounts from email domain, which broke for customers using consumer email addresses or multiple domains.
- No session replay, no feature flags, no experimentation, and no in-app guides, so June was always one tool among several rather than a platform.
- Analytical depth was shallow compared with Amplitude or Mixpanel: no meaningful path analysis, limited multi-step behavioural cohorting, and templates that were fast but not extensible far beyond their intent.
- The October 2024 removal of the free plan and shift to quote-only pricing cut off the early-stage segment that had adopted June in the first place, roughly nine months before the shutdown.
- SOC 2 was available on request rather than published, and there was no advertised EU data residency option, which made procurement harder for European buyers with strict requirements.
Head-to-head comparisons
5 alternativesJune vs Amplitude
from $0 (Free, 2M events per month forever); Plus starts at $0 with the first 2M events freeThis is the succession, not a live comparison. June's founding team joined Amplitude in 2025 and Amplitude published the migration path for June event data, so any team still running June was pointed here. The trade is real in both directions: Amplitude is far deeper analytically and has an accounts-level model of its own, but it is a bigger tool with a longer setup and a heavier commercial process than June's two-click reports. Teams that liked June for its speed should expect Amplitude to take longer to reach a first useful chart.
Full June vs Amplitude comparisonJune vs Mixpanel
from $0 (Free plan, 1M events per month), Growth starts at $0 and scales with volumeThe closest self-serve substitute for a small B2B team. Mixpanel's group analytics can make the company the unit of analysis, which recovers June's core idea, but it is a setting to configure rather than the product's default posture, and nothing auto-generates a starter report set. Mixpanel also has a usable free tier and transparent event-based pricing, which is what June looked like before October 2024. Expect more configuration and more analytical ceiling.
Full June vs Mixpanel comparisonJune vs PostHog
from $0 (generous monthly free tiers; pay only past the allowance)The broadest replacement, and the usual landing spot for startups that liked June's price point. PostHog supports group types for account-level analysis and adds session replay, feature flags, experiments, and surveys under one event meter, all with a generous free allowance. The cost is scope: PostHog is a platform with many surfaces where June was one opinionated view, and small teams should expect to ignore most of it initially.
Full June vs PostHog comparisonJune vs Pendo
from Free up to 500 monthly active users; paid tiers are quote-only, with reported contracts commonly starting around $15,000 per yearOverlapping ambition, different centre of gravity. Pendo sits closer to the in-app layer, pairing analytics with guides, onboarding walkthroughs, and feedback collection, and it has account-level reporting for B2B. June never touched the in-app experience at all. Pendo is also a larger commitment with a sales-led motion, so teams that chose June for its price and speed rarely found Pendo a like-for-like swap.
Full June vs Pendo comparisonJune vs Kissmetrics
from Free for 100,000 events per month; paid plans from $99 per month ($79 per month billed annually)Both answer person-level and cohort questions rather than pageview counting, but they come from different eras and different buyers. Kissmetrics is older, ecommerce and marketing-funnel oriented, and organised around individual customer journeys and revenue attribution. June was B2B SaaS and organised around the account. For a subscription software company the June model was the better fit; for a transactional store, Kissmetrics addresses questions June was never built for.
Full June vs Kissmetrics comparisonImplementation & onboarding
- Setup time
- Historically the fastest in the category: connecting an existing Segment, RudderStack, or Freshpaint source produced auto-generated reports within minutes, and a direct SDK install was an afternoon. Getting company-level reporting right took longer, since it required engineering to send group calls with the right traits.
- Learning curve
- Low by design. The templated reports meant most users never had to learn a query builder, and the vocabulary (active companies, power users, slipping away) mapped onto questions teams already asked. June AI's SQL editor was the only surface that assumed technical skill.
- Onboarding
- Self-serve for years, then 1:1 onboarding included with the all-in-one plan from late 2024. The founders stated they had personally onboarded more than a thousand startups, which is consistent with the support scores in public reviews.
- Migration notes
- The only migration that matters now is off June. Customers had thirty days from 8 August 2025 to export data or run the documented import into an Amplitude workspace; that window has closed. If you are still finding June SDK calls or a Segment destination pointed at June in a codebase, they are sending events nowhere and should be removed. Teams rebuilding elsewhere should carry over the group call implementation first, since that is the piece that makes account-level analysis possible in Amplitude, Mixpanel, or PostHog.
Platform, API & security
- Platforms
- Web application (SaaS)JavaScript and React SDKsNode, Python, and Ruby server SDKsHTTP APISegment, RudderStack, and Freshpaint as CDP sources
- API
- REST and HTTP tracking endpoints for sending identify, group, track, and page events, plus an embed API for rendering June charts inside a customer's own product. Historical backfill was handled by no-code importers from Mixpanel and Amplitude rather than a general import API.
- Compliance
- GDPRSOC 2 (report provided on request)DPA available
- Data residency
- No published regional data residency option; the company was US-incorporated with a distributed European team.
- SSO
- Available on the all-in-one plan; not published as a standalone tier feature.
- Security notes
- June positioned itself as GDPR ready with a DPA available on request and a SOC 2 report supplied through support rather than published on a trust page. Since the service has shut down, the practical security question is no longer about June's controls but about removing any residual SDK or CDP destination still transmitting user data to a dead endpoint.
Support & resources
- Channels
- In-app chatEmail1:1 onboarding on the all-in-one planHelp center
- Documentation
- A well-organised help centre covering installation, data sources, each report template, audiences, Slack alerts, and migration, still publicly readable after the shutdown and useful as reference for teams reconstructing the same reports elsewhere.
- Community
- A visible founder-led presence rather than a large user community: the CEO published extensively on B2B product analytics and answered questions publicly, including through the acquisition. All channels ceased with the wind-down.
Company
- Founded
- 2020
- Headquarters
- San Francisco, California (distributed team, largely European)
- Ownership
- Acquired by Amplitude (2025); standalone product discontinued
- Founders
- Enzo Avigo, Ferruccio Balestreri
- Employees
- ~6 at YC listing; team joined Amplitude in 2025
- Funding
- Venture-backed. Seed round of about $1.85M in 2021 led by Point Nine Capital, with Y Combinator, Speedinvest, Kima Ventures, eFounders, and Base Case participating.
Funding history
| Round | Amount | Year | Notes |
|---|---|---|---|
| Seed | ~$1.85M | 2021 | Led by Point Nine Capital following the Y Combinator W21 batch. |
Timeline
- 2020Founded by Enzo Avigo and Ferruccio Balestreri, initially as two-click analytics reports built on top of Segment data.
- 2021Y Combinator Winter 2021 batch; raises roughly $1.85M seed led by Point Nine Capital.
- 2022Pivots the product around company-level analytics, making the B2B account rather than the individual user the default unit of analysis.
- 2023Relaunches publicly as product analytics for B2B SaaS, adds auto-generated company profiles, Slack alerts, and CRM integrations.
- 2024Adds June AI with an AI-assisted SQL editor and the Attio integration; in October removes the free plan and moves to a single quote-only all-in-one plan aimed at companies above $1M ARR.
- 2025Founding team joins Amplitude; the standalone product winds down on 8 August 2025 with a thirty-day export window and refunds for unused annual contract time.
- 2026Website serves an acquisition notice, the Y Combinator profile lists the company as inactive, and Amplitude is the vendor-recommended destination.
Integrations
- Segment
- RudderStack
- Freshpaint
- Slack
- HubSpot
- Salesforce
- Attio
- Stripe
- Mixpanel (historical import)
- Amplitude (historical import and final migration path)
- Zapier
- June SDKs (browser, React, Node, Python, Ruby, HTTP)
Frequently asked questions
12 questionsIs June still available?
No. The standalone June product wound down on 8 August 2025 after the founding team joined Amplitude. New signups are closed, the website serves an acquisition notice, and the Y Combinator company profile lists June as inactive. Existing customers were given thirty days to export data or migrate events into Amplitude, and that window has long since closed.
Who acquired June?
Amplitude. The arrangement was announced in July 2025 and the product shut down on 8 August 2025. Co-founders Enzo Avigo and Ferruccio Balestreri joined Amplitude along with several team members, with Avigo taking a product management role there. The June brand was not continued as a separate product line.
What was June used for?
Product analytics for B2B SaaS, with the customer account as the primary unit of analysis. Teams used it to see which companies were active, which were disengaging ahead of renewal, whether a new feature had been adopted by the accounts it was built for, and where users dropped out of onboarding, all without building reports from scratch.
How much did June cost?
It changed twice. Originally there was a free plan up to roughly 1,000 active users and a Growth plan at $149 per month, with custom pricing above that. In October 2024 the free plan was removed and everything collapsed into a single quote-only all-in-one plan tiered by monthly active users, with a 14-day trial and a stated fit for companies above $1M ARR. No price is obtainable now because the product is discontinued.
What is the best alternative to June?
Amplitude is the vendor-recommended destination and the one with a documented import path for June data. For teams that valued June's price and simplicity, PostHog and Mixpanel are the usual self-serve substitutes; both support account-level analysis (group types in PostHog, group analytics in Mixpanel), though neither auto-generates a starter report set the way June did.
What made June different from Mixpanel or Amplitude?
Two things. Company-level analysis was the default rather than a configuration option, which matched how B2B subscriptions actually work, and reports were auto-generated from templates the moment a data source connected instead of being built in a query builder. The trade was analytical depth: June deliberately had a lower ceiling than either.
Can I still get my data out of June?
No. The export window ran for thirty days from 8 August 2025 and has closed. If your only copy of historical product events lived in June, it is gone; if you sent those events through Segment, RudderStack, or Freshpaint, the CDP or your warehouse may still hold the raw stream, which is the place to look.
Why did June shut down if it was profitable?
The founders addressed this publicly. Their stated ambition was a breakout company rather than a small profitable one, and they judged that scaling from the bottom of the market without substantial further funding was not viable. Joining Amplitude was framed in their own words as choosing to join rather than to keep competing.
Did June do session replay or A/B testing?
No to both, and it never did. June covered analytics only, with no session replay, feature flags, experimentation, or in-app guides. Teams that wanted those ran a separate tool alongside it, which is one reason PostHog became a common destination after the shutdown.
How did June's company-level analytics actually work?
It relied on group calls in the tracking implementation: an identify call established the user and a group call attached that user to a company with traits such as plan, MRR, or seat count. Where group calls were missing, June could infer accounts from email domain, which worked for business domains and broke for customers signing up with consumer email addresses.
Do I need to remove June from my codebase?
Yes, if it is still there. June SDK calls and any Segment, RudderStack, or Freshpaint destination pointing at June are now sending user data to an endpoint that no longer serves a product. Removing them cuts unnecessary network calls and closes a stale data flow that a privacy review will otherwise flag.
Was June suitable for small businesses?
It was, until October 2024. The free tier and the $149 Growth plan made it one of the few genuinely small-business-priced product analytics tools, and its review base on G2 was roughly ninety percent small business. The move to quote-only pricing aimed at companies above $1M ARR ended that, and the shutdown ten months later ended everything else.
Editorial verdict
June was a good product with a real idea: in B2B SaaS the account is the unit that renews, so the account should be the unit the analytics tool reasons about, and reports should exist before anyone asks for them. For four years that combination made it the most sensible product analytics purchase a small B2B software company could make, and its support and speed-to-insight earned it a review record most vendors would envy. None of that is buyable now. The company removed its free plan in October 2024 to chase customers above $1M ARR, then wound the product down entirely on 8 August 2025 when the founding team joined Amplitude, leaving customers a thirty-day export window. This profile exists as a record and a migration aid rather than a recommendation: if you are here because a spreadsheet still lists June as a vendor, the line item should be closed and the tracking code removed, and the realistic replacements are Amplitude if you want the documented path, or PostHog and Mixpanel if you want June's old price point and are willing to configure account-level analysis yourself.
Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.