Design your AI-powered feature
Imagine you’re pitching an AI chatbot, writing assistant, or recommendation engine for a brand. These sliders let you estimate what it would actually cost to run. Don’t worry about getting every number exactly right — start with a scenario above, then tweak.
Think of this like choosing between economy, business, and first class. Cheaper models are fast and handle straightforward tasks (FAQ bots, subject-line generators). Premium models reason better but cost 100–200× more — use them only when the task truly demands it (complex strategy advice, nuanced creative writing).
Every time a customer interacts with your AI feature, the conversation has several parts — think of the bill as being built from these building blocks:
Anatomy of an API Call
Each bar below is one turn in the conversation. Watch how each bar grows taller as previous messages pile up — that’s the history tax.
Before any customer ever types a word, you’ve already written a set of instructions that tells the AI who it is and how to behave. For example: “You are a friendly product advisor for Patagonia. Always recommend items from our current catalog. Never discuss competitor brands.” This is called the system prompt, and it gets sent with every single message — so its length directly affects every call’s cost.
This is the live information your app sends alongside each message so the AI can give a relevant answer. Think of it like handing a salesperson a cheat sheet right before they talk to a customer. Examples:
- E-commerce chatbot: the customer’s cart items, browsing history, and loyalty tier
- Support bot: the customer’s open tickets and account details
- Email assistant: the recipient’s name, segment, and past purchase data
- No context needed: a simple FAQ bot that answers the same way regardless of who’s asking (set to 0)
What the customer actually types (or what your app sends on their behalf) each turn.
- “What’s your return policy?” ≈ 8 tokens (short question)
- “I bought a blue jacket last week and it doesn’t fit. Can I exchange it for a medium? I have my receipt.” ≈ 30 tokens
- Pasting a product review for analysis ≈ 150–300 tokens
How much the AI writes back each turn. This is the most expensive part per token (output tokens cost 2–4× more than input tokens).
- Quick answer (“Yes, you can return it within 30 days.”) ≈ 15 tokens
- Short paragraph (product recommendation with reasons) ≈ 80–150 tokens
- Detailed explanation (full email draft or analysis summary) ≈ 300–600 tokens
How many times the customer and the AI go back and forth in a single session. This is the most important cost driver that beginners miss — in a multi-turn chat, the entire conversation history gets resent every turn, so costs grow faster than you’d expect.
- 1 turn: “Generate 3 subject lines for my spring email blast.” (one-shot, no follow-up)
- 3–5 turns: Customer asks a question, gets a recommendation, asks a follow-up, refines their choice
- 8–15 turns: Full support conversation — greeting, problem description, troubleshooting, resolution
How many total customer conversations your AI feature handles each month. This is your scale — it multiplies everything above.
- 100–500: Internal team tool or pilot program
- 1,000–10,000: Mid-size e-commerce site or B2B SaaS support bot
- 50,000–500,000: Major consumer brand or high-traffic app
Compare against the human alternative
AI doesn’t exist in a vacuum — it replaces (or augments) work that humans currently do. Fill in these two numbers to see an ROI estimate.
What does it cost when a human handles this task instead? Include salary, overhead, and tools — not just a wage estimate.
- $5–$15: Customer support ticket (blended cost with agent salary + tools)
- $1–$5: Manually writing/editing a product description or email subject line
- $15–$40: An analyst running a report or answering a data question
- $0.10–$0.50: Basic data entry or classification task
What percentage of interactions can the AI handle without human help? Be realistic — even great chatbots escalate 20–40% of conversations.
- 50–70%: Customer support chatbot (common queries answered, complex ones escalated)
- 80–95%: Batch tasks like subject lines, descriptions, or sentiment tagging
- 30–50%: Complex advisory tasks (analytics, strategy recommendations)
Real enterprise AI has tooling, developer maintenance, prompt tuning, and human QA audit costs beyond raw token fees.
- $0: Pure toy / hobbyist script (API token spend only)
- $300–$800: Batch marketing automation or content generation tooling
- $1,000–$3,000: Customer-facing chatbot with vector database, logging, and human QA spot-checks