| Service Type | Setup Fee Range | Monthly Retainer | Avg Margin | Best For |
|---|---|---|---|---|
| 💬 Chatbot / Assistant | $1,500–$5,000 | $500–$1,500/mo | 65–75% | SMBs, e-commerce, service cos |
| 📧 Email Automation | $2,000–$6,000 | $750–$2,000/mo | 60–72% | Coaches, SaaS, agencies |
| 🎯 Lead Generation Bot | $3,000–$8,000 | $1,000–$3,000/mo | 55–70% | Real estate, insurance, finance |
| ✍️ Content Automation | $2,500–$7,500 | $800–$2,500/mo | 65–80% | Content creators, media, blogs |
| 🏢 Full Office Automation | $8,000–$35,000 | $2,500–$7,500/mo | 45–65% | Mid-market, growing teams |
| ⚙️ Custom AI Agent | $5,000–$25,000 | $1,500–$5,000/mo | 50–70% | Tech cos, SaaS, operations |
| 📱 Social Media Automation | $1,500–$4,500 | $600–$1,800/mo | 70–82% | Brands, coaches, ecommerce |
* Ranges reflect 2026 US market rates. Final pricing depends on complexity, client size, and your experience level. Model strategy affects margins more than list prices: open-weight stacks (Kimi K3, GLM-5.2) cut the compute line vs. paid frontier APIs.
Agent workflows rarely run clean the first time. On Aug 5, 2026, levelsio (Pieter Levels) reported burning $500 per Gauntlet Loop run — an AI-coding method that fans out subagents and loops until "utterly perfect" — then corrected it to $900 total with 95% of generated code removed. Measured baselines are ~$0.06 per request and "a few dollars per task"; failure modes (retry storms, subagent fan-out, silent misconfiguration) turn that into $500 loops and $2,000 overnight bills. Use this estimator to model what retries actually add to your spend.
Google Cloud's new managed model routing (API Gateway, Public Preview since Aug 3, 2026) accepts your existing OpenAI-compatible chat requests, inspects the model name in each payload, and routes the call to a cheaper foundation model — with no client-side code changes. This estimator shows the potential token-cost savings from routing simple traffic to Gemini Flash-Lite instead of paying Flash/Pro rates for everything.
On August 3, 2026 Google Cloud added managed model routing to API Gateway (Public Preview). It accepts OpenAI-compatible chat requests, transcodes them in-flight, and dispatches them to Gemini, Anthropic Claude, or OpenAI models hosted in Vertex AI Model Garden. Google positions it as a managed replacement for self-hosted proxies like LiteLLM — no proxy server to host, scale, or maintain.
Routing is driven by the model name in each request payload. You define a router with a default model plus rules mapping client model strings to cheaper backends — unmatched traffic falls back to the default. Example: send all traffic to Flash, set the default to Flash-Lite, and route only complex/agentic requests to Flash. Google's own examples use google/gemini-3.5-flash-lite, google/gemini-2.5-pro, anthropic/claude-opus-4-7, and openai/gpt-oss-120b-maas.
Using Google's published list prices: a content agency sending 50M input + 10M output tokens/mo to Flash at $165/mo could route 80% to Flash-Lite and drop to ~$65/mo — ≈ $100/mo (~61%) saved. A multi-tier client setup on 2.5 Pro at $212.50/mo with 70% budget-tier traffic could drop to ~$100.85/mo — ≈ $111.65/mo (~53%) saved. A 5% fallback-traffic leak onto Flash-Lite instead of Flash saves ~$16/mo on that slice alone. Token volumes and split percentages are assumptions; substitute your own usage.
- Public Preview: text-only, name-based routing to MaaS models in Model Garden; request-side streaming, gRPC, WebSockets, Gemini Live, VPC-SC, and Private Service Connect unsupported.
- One-way mode: you cannot retrofit routing onto an existing gateway or remove it — switching requires a new API config + gateway.
- Single-host constraint: all models in one router must share the same hostname (global or one regional endpoint).
- Pricing gap: no model-routing-specific fee was found in the reviewed sources; confirm your exact model versions and region before quoting a client.
- No per-request observability yet: routing decisions aren't attributed per request in logs during preview.
- API Gateway — Overview of model routing (Google Cloud docs)
- API Gateway — Configure model routing (Google Cloud docs)
- Google Developers Blog — A unified API for AI model routing
- Vertex AI — Generative AI pricing (Gemini token rates)
- API Gateway pricing (per-call tiers)
- Google Cloud release notes (Aug 3, 2026)
- TLDR AI — Aug 5, 2026 issue
- API Gateway quotas and limits
2026-08-05: Added Gemini API cost & model routing savings estimator and explainer (Google Cloud managed model routing, Public Preview Aug 3, 2026). Pricing sourced from Google's published Vertex AI / API Gateway list prices; scenario figures are illustrative (directional).
Open-weight models are now a real alternative to paid frontier APIs. Moonshot's Kimi K3 — a 2.8T-parameter open-weight mixture-of-experts model (~104B active, 1M-token context, weights live on Hugging Face since July 27, 2026) — prices at $3 per 1M input tokens and $15 per 1M output tokens, a fraction of flagship paid APIs, while scoring within a few points of Claude Fable 5 and GPT-5.6 Sol on vendor-run coding benchmarks. Zhipu's GLM-5.2 (open weights, MIT license, 1M-token context) is the strongest open-source coding model on Terminal-Bench 2.1. A rumored GLM 5.3 has not been officially confirmed as of August 2026 — build on GLM-5.2 / Kimi K3 today, not on an unannounced model.
What this means for agencies: model strategy is now a pricing lever. The calculator's Model Strategy selector reflects it — open-weight stacks trim the compute line (and lift margins ~5 pts), frontier-only stacks carry a premium. Keep workflows model-portable across at least two providers, benchmark on your own workloads (vendor tables are not your client's workload), and treat AI spend as a managed line item, not a fixed cost.
Sources: Moonshot — Kimi K3 blog · Kimi K3 API pricing · HF model card — moonshotai/Kimi-K3 · zai-org/GLM-5