Skip to content
ELEV8

Explore · Investment

Are AI usage and tokens included?

How ELEV8 includes normal operating AI usage without turning the Executive Partner into a token wallet, and where materially expanded workload becomes a separate capacity decision.

The short answer

Yes. Normal AI usage for the agreed operating scope is included in the managed ELEV8 relationship.

ELEV8 does not sell the Executive Partner as a prepaid bag of tokens or ask you to meter routine work prompt by prompt.

If a workload materially changes in scale, cost, modality, or infrastructure needs, ELEV8 treats that as an expanded workload and works with you on the right capacity, BYOK, or scoped path.

Your normal operating work is included.

AI models consume tokens. Browsers use runtime. Tools, APIs, and external services can have real costs. ELEV8 meters and manages those things underneath the relationship.

But ordinary Executive Partner work is not supposed to feel like feeding a parking meter. When the work is reasonably consistent with the agreed operating scope, normal AI usage is part of the managed relationship.

The customer should experience the capability. ELEV8 manages the meter underneath it.

The boundary is an Operating Envelope, not a token bucket.

The Operating Envelope is the managed capacity ELEV8 expects to carry for the customer's agreed work. It can account internally for model usage, browser time, tool calls, media generation, compute, concurrency, retries, and other real costs.

That does not mean the customer gets a public token allowance to babysit. The point is to let ELEV8 manage normal variability while still having a clear way to recognize when the nature of the workload has materially changed.

Included Operating Envelope

Normal operating work

Routine Executive Partner work · managed AI usage · ordinary tools and runtime

Scale
High-cost modality
Concurrency
Infrastructure

Materially expanded workload

Surface the impact, protect against runaway consumption, then choose the clean path.

Optimize
Add capacity
BYOK
Scope separately
Normal operating work stays inside the managed envelope. Materially expanded workload becomes a governed capacity decision instead of a silent overage.

What usually sits inside it?

The exact scope depends on the relationship, but normal operating usage can include the everyday work you would expect an Executive Partner to perform: research, document work, meeting preparation, email and calendar assistance, ordinary browser or software interaction, recurring workflows, reasonable background follow-up, and normal use of approved AI models and tools.

A task does not become an exception merely because it is difficult. What matters is whether the pattern, scale, modality, infrastructure requirement, or cost has materially changed.

What can move outside the normal envelope?

Examples include a sudden mass batch campaign, very large media generation, sustained high-frequency autonomous jobs, specialized high-performance compute, additional dedicated managed computers, unusual licensed software, or a completely new workload category that changes how much capacity the relationship needs.

A runaway retry loop or exposed automated trigger can also create abnormal consumption even when nobody intended to request more work.

What happens when the workload expands?

ELEV8's operating policy is to detect and surface materially abnormal consumption rather than silently treating it as ordinary usage. Where necessary, the offending workload can be paused or throttled while unrelated authorized work continues.

Then the clean options can be considered: optimize the workload, schedule it differently, use a more efficient approved route, add managed capacity, use a customer-provided provider account for that bounded workload, approve a separate scope, or stop/defer the work.

Expanded workload is a decision, not a surprise overage.

What about using my own AI account?

Customer-provided AI or provider accounts can be useful for specific workloads, enterprise requirements, unusual media generation, temporary overflow, or cases where the customer's own provider economics make more sense.

That is an additive option. It is not the default funding model for normal ELEV8-managed operating work, and it does not make the customer responsible for choosing models and routes every time.

So is it unlimited?

No. Included usage is designed around normal operating work, not legally unbounded compute.

ELEV8's goal is a simple managed experience without pretending that 10,000 videos, a new GPU-heavy workload, or an accidental runaway loop is the same thing as normal executive operating work.

The practical answer.

Use your Executive Partner for the work you agreed to use it for. You should not have to count routine tokens.

If the workload materially changes, ELEV8 should make that change visible and work through the right capacity or commercial path with you. The applicable signed agreement remains the final authority.