Every workspace gets $250 in free credits to explore. When Clearskies becomes part of your operating rhythm, move to a flat annual plan with no per-seat fees and no MCP/API limits for resolved revenue context.
Pay-as-you-go gives your team room to connect sources, query complete context, and prove the first use cases. It is for trying and light use. Unlimited Context is the simpler path once usage is real.
Clearskies grants every new workspace $250 in credits for resolved context calls.
Connect sources, test questions, briefs, workflows, and apps, and prove what complete context changes.
When credits run out, stay pay-as-you-go at $0.75 per resolved context call or move to Unlimited Context for predictable, ongoing usage.
Annual Unlimited Context plans remove the MCP/API meter for resolved revenue context. Revenue bands keep pricing predictable as usage spreads across teams, AI clients, and internal tools.
Company revenue (TTM)
Up to $10M
$12,000/yr
$1,000/mo equivalent
Company revenue (TTM)
$10M-$50M
$36,000/yr
$3,000/mo equivalent
Company revenue (TTM)
$50M-$250M
$72,000/yr
$6,000/mo equivalent
Company revenue (TTM)
$250M+
Custom
Custom terms
| Plan | Company revenue (TTM) | Price |
|---|---|---|
| Starter | Up to $10M | $12,000/yr$1,000/mo equivalent |
| Growth | $10M-$50M | $36,000/yr$3,000/mo equivalent |
| Scale | $50M-$250M | $72,000/yr$6,000/mo equivalent |
| Enterprise | $250M+ | CustomCustom terms |
Company revenue is based on trailing twelve months. Unlimited Context plans include no MCP/API usage limits for resolved revenue context, subject to commercial terms and fair use.
The expensive part is not connecting data once. It is keeping context correct as your systems, teams, workflows, and AI clients change.
2-4
to build the first production version of a governed revenue context layer.
6-12 mo
before it is ready for governed workflows across real revenue systems.
1-2
to maintain APIs, schemas, permissions, MCP servers, AI-client integrations, and answer quality.
RevOps
to encode sales process, territories, product lines, lifecycle rules, and operating context.
Directional estimate: at roughly $200k-$300k fully loaded per engineer per year, the first year of an internal build can land around $500k-$1.2M+ before RevOps time, opportunity cost, and ongoing maintenance.
Your engineers should be building the workflows that create leverage, not the context infrastructure every workflow needs.
No per-seat fees, user caps, or extraction fees
Unlimited connected sources
Unlimited MCP/API access to resolved revenue context
Claude, ChatGPT, and API access to the same resolved context
Complete revenue and business context from CRM, calls, email, calendar, Slack, sales process, territories, operating rules, and more
Permissions, audit trails, and source-level controls for governed AI workflows
No. Clearskies grants every new workspace $250 in credits to get started. Credits apply to resolved context calls, so you can connect sources, test questions, briefs, workflows, and apps before choosing an annual plan.
Pay-as-you-go meters resolved context calls: MCP/API calls that retrieve resolved revenue context. After credits, usage is $0.75 per resolved context call. It is built for exploration, testing, and light use before Clearskies becomes part of your operating rhythm.
Unlimited Context means no MCP/API usage limits for resolved revenue context on annual plans, subject to commercial terms. It does not automatically include unlimited production agent workflows.
Company revenue is a simple proxy for operating complexity and value captured. As companies grow, Clearskies typically has to resolve more systems, teams, territories, product lines, permissions, historical activity, and AI surfaces. Revenue bands keep pricing predictable without turning usage into a per-seat or raw data-volume tax.
Agent workflows are scoped separately for now. Some teams may only need resolved revenue context through Claude, ChatGPT, or API. Others may want Clearskies-run workflows with their own run volume, orchestration, and support needs.
We will map expected usage, pick the right plan, and scope any production workflows you want to run on top of that context.
Prefer email? Contact support@clearskies.cc.