Koala

What it is

Koala shut down on September 30, 2025. The product is no longer available for new sign-ups or existing use. Cursor (parent company Anysphere) acqui-hired the Koala team in July 2025 to build out Cursor’s enterprise offering; the Koala CRM product was not integrated into Cursor. This page documents Koala as it existed for historical context and to help former customers evaluate the alternatives that now cover its use case.

Koala was a product-led sales (PLS) signal platform built specifically for B2B SaaS companies with self-serve or trial products. Where most intent tools identified companies visiting your marketing site, Koala uniquely combined website visitor identification with product usage telemetry — pulling in event streams from Segment, Amplitude, or Mixpanel — to surface accounts that were showing real buying behavior, not just page views. A free user hitting three pricing-page visits in a week plus feature-usage milestones fired a Slack alert to the rep with account context attached. The “Plays” feature let RevOps encode those threshold combinations into reusable triggers, pushing qualified accounts into Outreach or Salesloft cadences automatically. The closest remaining alternatives are Common Room (designated the official migration partner, which matched Koala’s pricing tiers) and Pocus (which now sits inside Apollo’s platform).

Why it showed up in RevOps stacks

• PLG-native signal combination. Koala was purpose-built for companies where free trial sign-ups and enterprise upsells coexist. It joined product event streams with website visit data in one view — the combination that competitors either split across two tools or required a data warehouse to assemble. For a PLG team without dedicated data engineering, that was the entire value proposition in one place.
• Fastest time-to-signal in the category. Setup required a JavaScript snippet and a Segment connection; a non-technical RevOps admin could be live with signals in hours. Competitors with comparable product-signal depth (Pocus, MadKudu) required data warehouse connections and multi-week configurations.
• Transparent, self-serve pricing. Koala published its pricing on its website — a practice rare in the intent-signal category — and offered a free plan with 100 credits and 2 seats, letting teams prove value before committing. The Starter plan ran $200/month and the Growth plan $1,000/month (pricing confirmed on getkoala.com before shutdown).
• Champion tracking. Koala automatically surfaced job-change events for contacts at target accounts, alerting reps when a champion who had evaluated the product moved to a new company — a signal bucket most PLS tools ignored.

Pricing reality (historical)

Koala’s published pricing was: Free (100 credits/month, 2 seats), Starter at $200/month (1,000 credits/month), and Growth at $1,000/month (5,000 credits/month). Business tiers were custom. This was among the most transparent pricing in the PLG-signal category — Pocus and MadKudu both required demos. The product shut down before any material pricing change.

What it was best for

RevOps leads and growth-stage GTM teams (roughly $3M–$30M ARR) at SaaS companies with a meaningful self-serve or trial product, an active Segment or Amplitude instrumentation, and a desire to have their first PLS signal layer running within a week rather than a quarter. The Starter plan at $200/month penciled out immediately for teams with 100+ active trial accounts per month.

Koala was the wrong pick for companies without a self-serve product — the entire value proposition rested on product usage signals. It was also a poor fit for enterprise-first, outbound-only teams with no free tier, and for non-PLG companies whose buyers never touch the product before buying.

Versus the alternatives (now that Koala is gone)

Common Room was Koala’s official migration partner and matched Koala’s pricing tiers for equivalent packages. Common Room adds community signals (GitHub, Discord, Slack communities, social mentions) that Koala never tracked, making it the more complete signal aggregator; the trade-off is a higher starting price ($1,700/month on Starter) and a more complex configuration. Pick Common Room if you want to expand beyond product signals over time. Pocus is the PLS workflow-depth pick — stronger playbook templating, rep-facing inbox, and direct SEP push, though it requires a data warehouse connection and runs at mid-five-figures annually. RB2B covers the website visitor identification slice of what Koala did (person-level identification for US traffic), without the product-usage layer, at a lower entry cost. 6sense is the enterprise ABM pick when you want third-party intent aggregated across the web, not first-party product usage — a different motion entirely but often the next step as companies mature past PLG.

Watch-outs (for teams evaluating what Koala replacements)

• Product signals require pre-existing instrumentation. Every Koala replacement that surfaces product usage signals (Common Room, Pocus) requires Segment, Amplitude, or a warehouse event stream to be already in place. Teams that assumed Koala would also build their analytics layer were disappointed. Guard: audit your current event instrumentation before selecting a replacement — if fewer than 60% of your key activation events fire reliably, fix the instrumentation before buying the signal tool.
• Website visitor identification accuracy degrades with VPN and remote-work traffic. Koala’s IP-resolution-based deanonymization matched roughly 20–40% of website visitors to companies (a typical rate across the category). VPN usage and hybrid work have compressed that further. Guard: run a free-plan test or trial with any replacement before committing to a paid plan, and measure actual match rate on your traffic, not vendor-quoted category averages.