ConceptDiscovery layer

Context.dev Credit Burn Ladder

Context.dev bills on credits, not seats, so agency margin is decided at ingestion design time.

By InnovaAI ResearchPublished

What is Context.dev Credit Burn Ladder?

“Credits per client job → plan tier → retainer margin”

Monthly credit load per client book against Context.dev tier ceilings

Context.dev bills on credits, not seats, so agency margin is decided at ingestion design time. The Free tier gives 1,000 credits monthly with no overage and 1 concurrent request, which covers a single low-volume client monitor but stalls the moment two delivery jobs run at once. Pro at $99 buys 125,000 credits, 100 concurrent requests, 12,500 Answers in Fast mode, and 1,000 monitors; Growth at $299 buys 500,000 credits and 250 concurrent requests. The ladder works like this: map each client workflow to a monthly credit estimate, sum across the retainer book, then pick the tier whose credit ceiling sits above that sum with headroom for crawl spikes. An agency running competitor monitoring for six clients at roughly 15,000 credits each lands near 90,000, so Pro holds, but adding a seventh client or a full-site crawl pushes the book toward Growth and the retainer math has to absorb the $200 step.

rag-tooling