Fulcrum vs June
Side-by-side trajectory, velocity, and editorial themes.
Field-data captures grow a BI layer while mobile coasts on fixes.
Fulcrum continues steady weekly shipping across web, iOS, and Android, but the substance is concentrated on the web. Recent releases add a freehand lasso selection on maps, a Power BI connector, and time-aware Insights (Beta) queries. Mobile cadence is dominated by single-issue stability fixes rather than new capabilities.
The product is widening from pure field-data capture into the analyze-and-share layer above it. Web work is going into bulk-action ergonomics, BI tooling integration, and growing the Insights surface. Mobile platforms are tracking a maintenance pattern, with versioned releases shipping one or two narrow fixes at a time and no new user-facing capabilities.
Expect Insights to gain depth toward general availability, with more BI-side integrations and richer bulk operations on web selections. Mobile is unlikely to see significant new capabilities in the next cycle.
June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.
See more alternatives to Fulcrum →
See more alternatives to June →