TL;DR Verdict
June So scores 8 out of 10 for small B2B SaaS teams that need company-level analytics fast and do not want to spend a week configuring dashboards. It is not the right tool if you run a consumer app, need deeply custom funnels, or want granular session replay. Its biggest strength is pre-built report templates that surface real metrics within minutes of connecting your data. Its biggest weakness is that it starts to feel limiting once your team’s analytics questions grow beyond the defaults.
What June So Actually Is
June So is a product analytics platform built specifically for B2B SaaS companies. Where most analytics tools think in terms of individual users clicking buttons, June thinks in terms of companies adopting features and paying customers churning. That distinction sounds small, but it changes everything about how the dashboards are structured, what data gets surfaced, and how quickly you can get an answer to “which companies are not activating?”
The company was founded by Enzo Avigo and Ferruccio Balestreri and went through Y Combinator. By 2026 the product has matured well past early-startup roughness. The core experience is stable, the integrations are reliable, and the documentation is actually maintained. The team has stayed focused on the B2B SaaS niche rather than trying to serve every possible use case, which shows in the product decisions.
The target user is a founder, product manager, or growth analyst at a SaaS company somewhere between 10 and 200 employees. You are probably tracking somewhere between a few hundred and a few thousand companies. You want to know which features drive retention, which customer segments activate fastest, and where your trial-to-paid conversion is leaking. June is built to answer those questions without requiring you to hire a data engineer first.
It is not a business intelligence tool. You will not be writing SQL or connecting a data warehouse. Everything runs on top of event data you send through a JavaScript SDK or via Segment, and the platform surfaces that data through opinionated, pre-built reports rather than a blank canvas. That philosophy is exactly the point and also the primary constraint.
Pricing And Plans
June So has a free tier and then paid plans that scale with the number of tracked companies and monthly tracked users.
| Plan | Price | Companies | MTUs | Key Limit |
|---|---|---|---|---|
| Free | $0/month | Up to 300 | Up to 1,000 | All core reports included |
| Starter | Around $149/month | Up to 2,000 | Up to 10,000 | Full integrations |
| Growth | Around $349/month | Up to 10,000 | Up to 50,000 | Slack alerts, API access |
| Enterprise | Custom | Unlimited | Unlimited | SSO, dedicated support |
The free tier is genuinely useful, not a crippled demo. You get access to the core report templates, which means a real solo founder or a very early team can get value without paying anything. That is not common in this category.
The gotchas are predictable. If you are tracking companies with a lot of individual user seats per account, your monthly tracked user count climbs fast even if you only have 200 paying customers. A single enterprise customer with 80 seats counts as 80 MTUs. You can hit the Starter plan ceiling earlier than the company number suggests, so model your actual user volume before picking a tier.
Annual billing brings roughly a 20% discount on paid plans. There is no per-seat pricing for your own team, which is a clean advantage over tools that charge you for every analyst you add.
Setup Experience
The first 30 minutes with June So feel surprisingly smooth. You land on an onboarding screen that asks you to connect a data source. Your options are Segment, a direct JavaScript SDK, or the Amplitude import. If you are already on Segment, you are sending data to June in under five minutes. The Segment connector is a destination you add in one click, and June starts ingesting your existing events immediately.
If you are not on Segment, the direct SDK is clean but requires a developer. The code snippet is short and the docs walk through the identify and group calls clearly. The group call is where June’s B2B model lives. You call analytics.group(companyId, { name, plan, mrr }) and June starts organizing your data around companies rather than individual users. If you skip the group call, the platform still works but you lose the company-level analysis that makes June worth using.
What tripped me up in early testing was the event naming. June’s pre-built templates rely on you having clean, consistent event names. If your track calls are inconsistently named across your codebase, “Feature Viewed” in one place and “feature_viewed” in another, the templates surface partial data and you spend time wondering why numbers look low. Running a quick audit of your event taxonomy before connecting is worth the extra hour.
The docs are good. They are concise, kept up to date, and the examples use realistic B2B scenarios rather than generic e-commerce examples. The in-app onboarding checklist does not nag you excessively, which is a relief compared to tools that fire five emails in the first 48 hours.
By the end of your first session you can have an activation report, a retention chart, and a feature adoption breakdown all running on real data. That speed is the headline feature even before you look at any specific functionality.
What It Does Well
Company-Level Analytics
Most analytics tools aggregate at the user level and require custom work to roll up to accounts. June makes the company the first-class object. Every report can be filtered by company, every retention curve can be segmented by plan type or company size, and every feature adoption view shows you which of your paying accounts have actually used a given feature. For B2B SaaS this is not a nice-to-have. It is the core question you need to answer.
Pre-Built Report Templates
June ships with templates for activation, retention, feature adoption, power users, and churned companies. You do not configure these from scratch. You map your events to the template slots and the report builds itself. A retention cohort chart that would take a full afternoon in Mixpanel or Amplitude to configure takes about ten minutes here. The templates encode B2B best practices by default, so even a non-technical founder is looking at the right metrics.
Slack Alerts For Company Events
The Slack integration sends you a notification when a specific company hits a milestone. When a trial company completes your activation checklist, your Slack channel gets a message. When a paying customer goes 14 days without logging in, you get a heads-up. These alerts are set up through a point-and-click interface rather than code, and they close the gap between analytics and action without requiring a separate tool like Customer.io for this specific use case.
Segment and HubSpot Sync
June pushes computed traits back to your CRM. If you calculate a company’s activation score or feature adoption percentage inside June, that number can sync to HubSpot as a contact or company property. Your sales team can then filter their pipeline by product engagement without ever opening June. For small teams where product-led sales is the motion, this integration removes a lot of manual spreadsheet work. Read more about building this kind of data pipeline in our guide to connecting product analytics to your CRM.
Attio and Linear Integrations
Beyond HubSpot, June connects to Attio for modern CRM workflows and can push issues to Linear when a product signal suggests a customer is at risk. These are niche but genuinely useful for the teams that use those tools. The integrations are not afterthoughts; they surface contextual company data inside the destination app rather than just dumping raw event names.
Clean, Fast UI
The interface loads quickly and avoids the dashboard sprawl that plagues heavier tools. You can pull up a company profile, see their full event history, filter by date range, and jump to their activation status in under 30 seconds. For teams doing daily account reviews or weekly product meetings, the snappy UI reduces the friction of actually looking at data regularly.
Where It Falls Short
No Freeform Query Layer
If you need to ask a question that falls outside the pre-built templates, you are stuck. There is no SQL access, no custom metric builder, and no way to write an arbitrary query against your event data. Teams that outgrow the templates quickly find themselves exporting CSVs and doing the analysis in Python or a BI tool anyway. Check out our overview of BI tools for small teams if you find yourself hitting this wall often.
Limited Funnel Flexibility
The funnel reports work well for standard activation and conversion paths, but multi-path funnels, branching flows, and step-level dropout attribution are constrained compared to what Mixpanel or Amplitude offer. If your product has a complex onboarding with multiple valid paths to activation, the funnel template will not capture that nuance cleanly.
No Session Replay or Heatmaps
June is a quantitative analytics tool and does not include session replay, click tracking, or heatmaps. You will need a separate tool like PostHog or FullStory if you want to understand the “why” behind the numbers. That is an extra cost and an extra tab to manage.
Company Attribution Can Be Messy
If your app allows users to belong to multiple companies, or if your data model includes guest users before account creation, the group-based attribution logic can produce confusing results. June assumes a relatively clean one-user-to-one-company model, and edge cases outside that require careful event architecture to handle correctly.
Reporting Depth on Higher Plans Only
Some of the most useful features, including the API access for pulling computed metrics into other tools and advanced Slack alerting rules, sit behind the Growth plan. For a team that needs them, $349/month is reasonable. But it means the Starter plan at $149/month can feel like a halfway experience once you know what is available above it.
Best Alternatives To Consider
Mixpanel is the most direct comparison. It has deeper funnel and flow analysis, a freeform query layer, and broader integrations. The tradeoff is setup complexity and a steeper learning curve. If your team already has an analyst who wants full control over how reports are built, Mixpanel is the better fit.
PostHog is open-source and self-hostable, which makes it attractive for teams with data sovereignty requirements or strict privacy constraints. It includes session replay and feature flags in addition to analytics. It is more technical to run but covers more ground in a single platform. We reviewed it in detail in our PostHog review for startups.
Amplitude is the enterprise option. It has the deepest analysis capabilities, a data warehouse connector, and a large ecosystem of integrations. It is also significantly more expensive and takes longer to configure correctly. Worth considering if you are scaling past 50,000 MTUs and need predictive analytics or complex behavioral cohorts.
Heap takes a different approach by capturing every user interaction automatically without requiring manual event instrumentation. That retroactive data collection is useful if you have not been tracking events consistently. The B2B account-level analysis is less developed than June’s, but the auto-capture model reduces the upfront engineering lift.
Who Should Use June So
The Founder Running Product Solo
If you are the only person making product decisions and you do not have an analyst or a data engineer, June fits well. You can connect it to Segment or instrument your app in an afternoon, and the pre-built templates give you activation, retention, and feature adoption data without any configuration work. You will know which companies are stuck, which features your best customers actually use, and where your trial flow is leaking, all without learning a query language or hiring anyone.
The Product Manager at a Series A SaaS Company
If you are at a company with 50 to 500 paying customers and a small product team, June gives you the company-level visibility your sales and customer success teams will actually read. The Slack alerts and CRM sync mean the data leaves the analytics tool and shows up in the systems where your colleagues already live. You stop being the person who manually exports CSVs and pastes numbers into HubSpot. For more on picking the right analytics stack at this stage, see our guide to product analytics for Series A companies.
The Growth Analyst Supporting a PLG Motion
If your company uses product-led growth where free users self-activate before talking to sales, June’s activation and power user reports are directly relevant to your daily work. You can identify which companies have hit activation milestones and pass those signals to sales automatically. The feature adoption reports tell you which capabilities drive expansion revenue, which informs where the growth team focuses next. June is not a marketing analytics tool, but for the product-to-revenue part of PLG, it handles the core questions well.
Frequently Asked Questions
Does June So have a free tier that is actually useful?
Yes, the free tier supports up to 300 companies and 1,000 monthly tracked users, and it includes access to the core report templates. For a very early-stage company or a solo founder validating a product, the free plan is enough to get meaningful data without paying anything.
How hard is June So to set up if I am not technical?
If you already use Segment, setup takes under ten minutes with no code required. If you do not use Segment, you will need a developer to drop in the JavaScript SDK and add identify and group calls. The actual instrumentation is not complicated, but it does require someone comfortable with code.
Does June So integrate with my CRM?
Yes, June integrates with HubSpot and Attio and can push computed traits like activation scores or last-seen dates back to company records in your CRM. The sync runs automatically so your sales team sees fresh product data without any manual export.
Can I migrate my event data from Mixpanel or Amplitude to June?
June supports importing historical data from Amplitude directly. For Mixpanel you would typically re-route your Segment events to June and use the historical Mixpanel export as a reference rather than a live migration. You will not lose future data, but backfilling years of history requires some work.
What is the learning curve like compared to Mixpanel or Amplitude?
Significantly shorter. The pre-built templates mean you do not need to understand funnel configuration or cohort logic to get useful reports. Most product managers are comfortable using June within a day. The tradeoff is that when your questions go beyond the templates, there is no freeform query layer to fall back on.
Bottom Line
June So earns its place as a strong first choice for B2B SaaS teams that need company-level product analytics without investing weeks in setup or training. The pre-built templates, clean UI, and Slack and CRM integrations cover the analytics needs of most early-to-mid-stage SaaS products. You will eventually want a more flexible tool as your team’s questions get more complex, but for the first one to two years of serious product analytics, June handles the job well. Score: 8 out of 10. The free tier makes it low-risk to try, the paid plans are reasonable, and the B2B focus means the defaults actually fit your use case rather than needing to be reconfigured around it.
Want to try June So? Start with June So and see if it fits.