Building AI Copilots Inside B2B SaaS in 2026

"Add a copilot" is the most common ask we get in 2026. Most copilots are trash — a chat box in the sidebar nobody opens. Here's how to build one users actually rely on.

The 3 copilot patterns that work

1. Inline copilot — Suggestions appear in context (Notion, Linear, Cursor style). Highest engagement.
2. Command copilot — Cmd+K launches an action, not a chat. Great for power users.
3. Sidebar copilot — Traditional chat panel. Only works with tight product context.

What we ship inside every SaaS copilot

• Context loader — pulls the current record, tab, or selection into the prompt.
• Tool layer — the copilot performs actions inside the product, not just answers.
• Memory — thread-scoped, org-scoped, and per-user preferences.
• Evals — golden set of 50–200 tasks graded in CI.
• Cost caps per tenant with alerting.

Retention numbers that matter

Across the copilots we've shipped, the correlation with retention is clear:

• Copilot used weekly ⇒ 2.3x higher 90-day retention.
• Copilot completes an action (not just answers) ⇒ 3.1x higher.
• Sidebar-only copilots ⇒ < 12% weekly active use on average.

Pricing the copilot

• Bundle with a higher tier — easiest, drives ARPU 20–40% up.
• Usage-based add-on — works when actions have clear business value.
• Avoid pure "seats + AI included" pricing; costs escape fast.

Common failure modes

1. Copilot has no tools — it can only "explain" the product.
2. No evals — quality drifts silently.
3. Latency > 3s to first token — users bounce.
4. No feedback loop — you never learn which prompts break.

Timeline + cost

A production copilot for an existing SaaS: 6–10 weeks and $35–90k depending on tool depth. We ship these end-to-end as part of AI Engineering.