Start with credits.
Scale with Unlimited Context.

Every workspace gets $250 in free credits to explore. When Clearskies becomes part of your operating rhythm, move to a flat monthly plan sized to your go-to-market team, with no per-seat fees, no metering, and no limits on context calls.

Start fast, then scale predictably.

Pay-as-you-go gives your team room to connect sources, ask real questions, and prove the first use cases. Once usage is real, Unlimited Context is the simpler path.

01

Get $250 in credits

Clearskies grants every new workspace $250 in credits for context calls.

02

Explore generously

Connect sources, run real questions, briefs, and workflows — and prove it on your own data.

03

Top up or upgrade

When credits run out, stay pay-as-you-go at $0.30 per context call or move to a flat monthly plan sized to your team.

Flat pricing, sized to your team.

Unlimited Context plans remove the meter on context calls, subject to fair use. Plans are sized by your go-to-market team: the people whose email, calendar, Slack, calls, and CRM activity flow into your context graph. That isn’t a seat count. Anyone on your team, and any AI client, can use the context on every plan.

Starter

GTM team size

Up to 10 people

Monthly · $1,250/mo

Annual (save 20%) · $12,000/yr

Growth

GTM team size

11–25 people

Monthly · $2,500/mo

Annual (save 20%) · $24,000/yr

Scale

GTM team size

26–50 people

Monthly · $5,000/mo

Annual (save 20%) · $48,000/yr

Enterprise

GTM team size

50+ people

Monthly · From $7,500/mo

Annual (save 20%) · From $72,000/yr

Let’s talk

The in-house alternative is a platform team.

The expensive part isn’t connecting data once. It’s keeping context correct as your systems, teams, workflows, and AI clients change.

2-4

dedicated engineers

to build the first production version of a governed revenue context layer.

6-12 mo

to production reliability

before it is ready for governed workflows across real revenue systems.

1-2

engineers ongoing

to maintain APIs, schemas, permissions, MCP servers, AI-client integrations, and answer quality.

RevOps

systems time

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.

The full picture for every AI tool.

Unlimited users and AI clients: no per-seat fees, user caps, or metering

Unlimited connected sources

Unlimited context calls over MCP and API

Claude, ChatGPT, and API access to the same context

Complete revenue and business context: CRM, calls, email, calendar, Slack, sales process, territories, and operating rules

Permissions, audit trails, and source-level controls for governed AI workflows

Questions

Do I need to pay to get started?

No. Every new workspace gets $250 in credits. Credits apply to context calls, so you can connect sources and test briefs, workflows, and apps before choosing a plan.

What does pay-as-you-go meter?

Every MCP or API call that pulls context from your graph counts as one context call. After credits, usage is $0.30 per call. Pay-as-you-go is built for exploration, testing, and light use before you move to a plan.

What does Unlimited Context mean?

Unlimited Context plans have no limits on context calls, subject to fair use.

How are plans sized?

By your go-to-market team: the people whose work flows into your context graph, including reps, SDRs, customer success, RevOps, and their managers. Count anyone whose email, calendar, Slack, calls, or CRM activity you connect. It isn't a seat count: anyone on your team, and any AI client, can use the context on every plan.

Why not price by seats, usage, or company size?

Context is most valuable when everyone and every AI tool can reach it, so we don't charge per user. Usage pricing makes bills unpredictable, so plans aren't metered. Team size keeps the price flat and tied to what Clearskies actually maintains for you.

What exactly counts as a person?

Anyone on your team whose work flows into the graph from a connected source. Connecting an org-wide source like your CRM or call library counts everyone active in it. Former employees don't count, but their history stays as context. Customers and prospects in your data never count.

What if only part of my team will use it?

Using it is free, since users are unlimited. Plans count whose work is in the graph, not who queries it. You can connect a subset of your team; just know the graph only knows what those people touched, so briefs on shared accounts will have gaps where the rest of the team's activity lives. Most teams connect everyone.

We're a services business, marketplace, or investment firm. Does that change anything?

No. Only your go-to-market team size matters, not revenue, margins, contractors, or assets under management.

Monthly or annual?

Monthly plans are flat, billed monthly, and can be cancelled anytime. Annual plans are the same plan billed once a year, at the annual rate shown above.

What happens when my team grows?

On annual plans, nothing until renewal. Your bill never changes mid-term because you hired. On monthly plans, team size is reviewed each month, and if you've grown into a new band the new price starts with your next monthly cycle.

Bring one real workflow.

We’ll map your team and sources, pick the right plan, and scope any production workflows you want on top of that context.

Prefer email? Contact support@clearskies.cc.