A scoped pilot first. Then choose the deployment, operating capacity, and support your workflow needs.
These are planning prices to validate through pilots. Underlying compute is billed separately.
For a team connecting a bounded workflow with standard integrations.
Plan a Team pilot$5,988 annual recurring equivalent
Calculate with TeamFor teams coordinating multiple environments and deeper enactment evidence.
Plan a Business pilot$17,988 annual recurring equivalent
Calculate with BusinessAnnual figures are twelve-month equivalents, not a discounted offer. Capacity, retention, support, availability, and commercial terms would be agreed after evaluation. Taxes and third-party compute are excluded.
Compare the proposed scope
Start with the workflow you can evaluate. Use deployment complexity, evidence needs, and operating support to guide the next plan.
On smaller screens, scroll the comparison horizontally. Exact operating allowances would be set during scoping.
| What you are planning for | Team$499 / month | Business$1,499 / month |
|---|---|---|
| Workflow and control | ||
| Typical starting point | One focused workflow with standard integrations | Connected workflows across multiple environments |
| Policy checks before dispatch, retry, transfer, and result release | Core scope | Core scope |
| Worker connections | Standard connectors, scoped to the workflow | Multiple private and approved cloud environments |
| Enactment records | Decision and outcome history | Detailed attempt history, recovery evidence, and audit exports |
| Budget and cost evidence | Budget checks and usage records | Detailed reconciliation across attempts and providers |
| Deployment and operation | ||
| Deployment scope | Standard connection to customer provider accounts | Coordinated private and cloud enactment |
| Identity requirements | Standard access configuration | Team access requirements agreed during scoping |
| Capacity and history retention | Defined after the pilot | Defined after the pilot |
| Support model | Asynchronous support | Enhanced operational support |
| Commercial boundaries | ||
| Cloud, GPU, and model-provider charges | Billed separately by your providers | Billed separately by your providers |
| Custom implementation | Separately scoped where required | Separately scoped where required |
| Auctions and marketplace procurement | Future research; excluded | Future research; excluded |
Commercial planning
Explore the improvement your compute spend would need to justify an orchestration subscription. Adjust the assumptions to see the trade-off.
Use the monthly spend within the workflow you plan to manage. Range: $0–$5,000,000.
An assumption to test in a pilot. This is not a measured result or a savings guarantee.
Planning prices for the proposed product. Compute-provider charges remain separate. Compare plan scope.
Estimated net monthly benefit
Projected compute savings after the proposed software fee.
3.0% compute-cost improvement covers the software fee at this spend.
Download a text report with your inputs, results, formulas, and exclusions.
How this is calculated
Gross savings = monthly compute spend × assumed improvement. Net monthly benefit = gross savings − monthly software fee. Annualized net benefit repeats the monthly assumption for twelve months.
This simplified scenario holds workload volume and quality constant. The $7,500 pilot fee, implementation effort, taxes, and changes in provider pricing are outside this calculation. A negative result means the assumed compute savings do not cover the recurring software fee. Actual outcomes require measurement.
Use the pilot evaluation worksheetKeep enactment software, provider consumption, and implementation work visible.
The proposed platform fee covers the agreed deployment, operation allowance, evidence retention, and support.
Pay cloud and AI providers directly. The controller’s cost record would track usage without treating it as software revenue.
Private deployments, custom integrations, and substantial migration work receive their own scope and estimate.
Use the planner to define an evaluation. Review the practical limits and terms before treating any number as a quote.
Get the evaluation worksheetThe planner lets you review a brief and explicitly submit a pilot inquiry for numericspace to review. A confirmed submission is stored with its full brief and provides a downloadable submission document. It does not reserve time, collect payment, or create a contract. Scope, availability, and commercial terms require a separate agreement.
The proposed fixed scope is one workflow, up to two enactment endpoints, a baseline, agreed policy-change scenarios, cost and enactment evidence, and an evaluation summary over 4–6 weeks. Provider compute, substantial custom integrations, taxes, and a continuing subscription are separate. The final deliverables would be agreed before kickoff.
Identify one workflow, its likely endpoints, a policy change worth testing, and measurable success criteria. Include a realistic compute budget and the person who can assess output quality and operational requirements. The pilot planner turns those inputs into a reviewable brief.
The proposed meter is one bounded model or tool operation. Linked retries and fallbacks remain part of that logical operation for platform accounting; underlying provider attempts and costs are recorded separately. Capacity allowances and any overage terms would be defined after benchmarking, before a subscription agreement.
No. The starting model uses customer-owned provider accounts with direct provider billing. A software subscription does not replace those charges. Compute sold or hosted separately would require its own price and terms.
It is the proposed monthly Team or Business price multiplied by twelve: $5,988 or $17,988. It is not an annual discount, a billing commitment, or a live checkout offer. Any custom implementation is scoped separately.
No. It subtracts the proposed recurring software fee from the gross compute savings implied by your input. It excludes the one-time pilot fee, implementation, taxes, and provider price changes. A measured evaluation should hold workload quality and volume consistent and include retries, failures, egress, and operating effort.
That is the proposed path: evaluate a bounded workflow, then scope the deployment that fits. Team is intended for a focused workflow; Business adds coordination across environments, deeper enactment evidence, and enhanced support. Deployment requirements and substantial custom implementation would be scoped separately. A pilot does not automatically enroll you in an ongoing plan.
Auctions and strategic resource allocation remain a future research direction. They are excluded from the initial pilot and the Team and Business plans shown here. The Research page explains the questions that would need to be evaluated.
The planner prepares a brief in your browser. A draft is saved on this device only when you choose “Save draft on this device.” If you review the brief, give consent, and submit an inquiry, numericspace stores your contact details and complete brief for private review and follow-up. Resetting the planner or deleting a local draft does not delete a submitted inquiry. See the privacy notice for the full behavior.