BatteryArb is packaged in three commercial stages: Sandbox / Evaluation, Pilot / Team, and Enterprise / Production. The structure is simple on purpose: technical diligence first, measured proof of value second, and controlled rollout once the workflow is real.
Pricing shown below is synced from Stripe plan configuration.
For one evaluator or a small technical group proving data fit, API quality, and basic workflow integration before internal rollout.
For asset teams proving operational value against a real dispatch, trading, or EMS workflow before broader production procurement.
For production teams that need rollout planning, procurement support, and a cleaner path through security and operational review.
The buying motion is designed for existing asset teams. Start with technical diligence, move into a proof of value, then standardize once the workflow is real.
Use sandbox access when the question is “Can our team trust the data, integrate the API, and verify that the product fits the workflow?”
Use pilot access when the question is “Does this improve dispatch quality, reduce bad intervals, or strengthen team consistency enough to justify budget?”
Use production when the question is “Can we operationalize this with support, controls, procurement review, and a stable contract path?”
| Commercial dimension | Sandbox / Evaluation | Pilot / Team | Enterprise / Production |
|---|---|---|---|
| Primary buyer | Technical evaluator, quant, operator lead | Asset manager, ops lead, trading lead | Operations leadership, security, procurement |
| Buying question | Can we trust the API and fit it into our workflow? | Does this improve decisions enough to earn budget? | Can we standardize this for live operations? |
| Commercial posture | Self-serve monthly | Monthly proof-of-value stage | Annual-ready production path |
| Support | Email support and self-serve docs | Implementation help and pilot configuration | Priority onboarding and rollout planning |
| Controls | Hard caps, simple key-based auth | Shared team usage and buyer review support | Security review, key management, SLA discussion |
| Success criteria | Data trust and integration speed | Margin lift, avoided bad intervals, better consistency | Operational adoption and repeatable rollout |
The pilot should be judged against your internal baseline, not vendor theater. The point is to measure whether the operating workflow improves enough to justify production rollout.
For real battery fleets, a small number of poorly timed intervals during a stressed ramp can overwhelm the cost of a pilot if they are not caught early.
BatteryArb helps compress senior-style context into a repeatable layer so shift quality becomes less variable and easier to manage.
Instead of buying a broad platform blindly, the team can review one market, one workflow, and one measurable scorecard before committing to production.
Pricing model: flat-rate per organization, not per-seat. The value is workflow coverage, not headcount tax.
Overages: disabled at launch. Hard caps are better for buyer trust than surprise invoices.
Annual contracts: available once a workflow is real and production usage is predictable.
Sandbox: best for individual technical diligence and basic security review.
Pilot: best for asset teams aligning operators, management, and commercial sponsors around one scorecard.
Production: best for buyers who need rollout planning, support path, and a cleaner route through procurement.
Use self-serve checkout for sandbox access and lightweight pilots. Use the pilot form when the buying motion involves budget owners, security review, or production rollout planning.