An AI assistant that knows your product.
Copilot started as a single conversation interface. Over ten major iterations, it became the connective tissue between every part of the Chameleon platform.
One interface for everything Chameleon can do.
Chameleon customers build in-app Experiences — tours, modals, microsurveys, banners — to guide their users. The problem isn't capability. It's that building well requires navigating a complex dashboard, understanding segmentation, writing copy, and knowing which Experience type fits the moment.
Copilot was the bet that a conversational AI layer could collapse that complexity. Instead of learning the dashboard, customers describe what they want — and Copilot builds it.
Ten iterations, not one launch.
Most AI features ship once and stall. Copilot shipped every month. Each update expanded what it could do — and each was scoped to one new capability, tested, and shipped before the next began.
- Nov 2025: Create or optimize Experiences through conversation.
- Dec 2025: Segment users in plain English. New debugging and analysis skills.
- Feb 2026: Microsurvey insights — instant answers from response data. A/B test variant creation.
- Mar 2026: Account audit — every Experience, every gap, one prioritized plan. Refine copy in the Builder.
- Apr 2026: Daily personalized suggestions on every Experience. Translation generation.
- May 2026: Turn your designs into a Theme. Ranger integration.
- Jun 2026: Copilot in Linear. Connect to your AI tools or use it in Slack.
- Jul 2026: Copilot on a schedule — ask once, let it run on its own.
- Aug 2026: Product knowledge (teach Chameleon once), Memory, and always-on help.
Knowing when Copilot should stop.
The easiest mistake with an AI feature is letting it do too much. Early Copilot prototypes would happily create five Experiences when the customer described one vague goal. It would suggest changes to Themes the customer hadn't asked about. It would keep going when the right answer was "done."
The guardrail wasn't a prompt tweak — it was a product decision: Copilot proposes, the customer confirms. Every action Copilot takes is visible, reversible, and requires a human yes. That constraint shaped the entire interaction model.
The discipline isn't making the AI smarter. It's deciding what it shouldn't do — and defending that boundary when someone reasonable argues "but what if."
AI features are a cadence, not a launch.
The biggest lesson from Copilot is that shipping it once was the easy part. The hard part is maintaining a release cadence that keeps the feature ahead of customer expectations — and ahead of every competitor who also has access to the same models.
The moat isn't the model. It's the product surface area the model can act on, the guardrails that keep it useful, and the iteration speed that lets you learn faster than anyone else.