Day 1: instrument
- Embed the Command+K widget; expose 3 actions tied to core jobs.
- Turn on Monetize ($99/mo); set a per-user cost cap.
- Wire a Stripe meter for "AI usage" with a unit price.
Week 1: price
- Pick markup: 30-40% on managed AI is the comfortable zone.
- Bundle into existing tiers (Pro / Team / Enterprise) — don't sell a separate "AI add-on" SKU.
- Add an Enterprise BYOK path so procurement can bring their own key.
Month 1: prove unit economics
- Dashboard: spend per user, margin per user, top tools by revenue.
- Tune: raise caps for high-margin users, lower for cost-only.
- Decide: is AI a cost line or a revenue line? The math is now in front of you.
One thing this playbook is not about
Command+K itself does not support BYOK: every call the widget makes runs through our managed AI Gateway on prepaid credits, which is what keeps per-model cost reporting exact. The advice above is about how you price your own product, not about how you pay us.
The flip
Most teams start with AI as a cost line and end with it as a revenue line within one quarter. The instrumentation is what makes the flip possible.
FAQ
- Do I need to be on Enterprise to monetize?
- No. Monetize is a $99/mo module on any plan. The math works as soon as you have a few hundred active end users.
- Where does the revenue come from?
- A markup on AI usage you resell to end users. If your customers pay $X for AI features, you keep the spread between $X and the underlying inference cost.
- Do I need my own Stripe?
- Yes, for billing your customers. Command+K forwards usage events to your Stripe meter; you control the price and invoice.