Pricing architecture

Price the decision layer by access, modules, volume, and enterprise fit.

AlphaWeave Capital is designed to sit beside institutional data, strategy, risk, execution, and reporting systems. Pricing should reflect that role: a durable platform fee for the control layer, modular fees for capabilities, usage fees for scale, and enterprise fees for integration and support.

Base platformPay for the governed decision infrastructure that every workflow uses.
ModulesAdd backtesting, policy simulation, paper trading, live trading, and white-label reporting as needed.
UsageScale pricing with assets, sleeves, strategies, runs, AI reviews, and reporting volume.

Commercial model

A pricing structure that matches how institutions adopt allocation software.

The cleanest model separates the always-on platform from optional modules and measurable usage. That gives smaller teams a practical entry point while giving banks and asset managers a way to expand into deeper integrations, more desks, and stricter governance.

01

Base Platform Fee

The base platform fee covers the core decision infrastructure: authenticated access, organization controls, run records, entitlement checks, audit trails, dashboard replay contracts, and the shared workflow for strategy, asset, sleeve, risk, and policy review.

  • Core application access
  • Control DB, authentication, roles, and scopes
  • Standard run and replay records
  • Baseline dashboards and audit trails
  • Standard deployment support
Economic logic: customers pay for the operating layer that makes allocation decisions inspectable and repeatable.
02

Module Fees

Modules price the specialized capabilities layered onto the platform. A research team may start with backtesting and attribution, while a trading desk may add paper trading, live trade scheduling, policy simulation, or white-label reporting.

  • Backtest and attribution module
  • Policy simulator and economic review module
  • AI/PSM decision review module
  • Paper trade scheduler module
  • Live trading governance module
  • White-label reporting and portal module
Economic logic: teams pay for the capabilities they actually deploy instead of buying one oversized bundle.
03

Usage And Volume Fees

Usage fees meter the workload created by the platform. The natural units are not page views; they are investment workflow units: assets reviewed, strategies compared, sleeves governed, backtests run, AI reviews completed, trade windows scheduled, and reports generated.

  • Number of active users or service accounts
  • Number of assets, strategies, and sleeves
  • Backtest and simulator run count
  • AI/PSM decision-review count
  • Paper and live trade windows monitored
  • Report, export, and white-label portal volume
Economic logic: cost scales with the customer footprint and compute-intensive decision work.
04

Enterprise Support And Integration Fee

Enterprise deployments often require more than software access. They may need private cloud or internal deployment, security review, custom data connectors, broker integration, model governance, report packaging, SSO, network controls, and desk-specific rollout support.

  • Private cloud or customer-controlled deployment
  • SSO, API key governance, and audit integration
  • Market data, risk, execution, and reporting connectors
  • Custom strategy onboarding workflow
  • Support SLAs and implementation services
  • Model risk, compliance, and operational documentation
Economic logic: enterprise value comes from fit, control, and successful adoption inside existing infrastructure.
05

Optional Performance-Linked Contract

Performance-linked terms can make sense in limited cases, but they should be handled carefully. AlphaWeave Capital should usually price as software and infrastructure first. A performance-linked component may be appropriate only where the customer, mandate, legal structure, attribution method, and compliance posture support it.

  • Use only where legally and contractually appropriate
  • Define the benchmark and attribution methodology upfront
  • Separate AlphaWeave contribution from manager discretion and market beta
  • Use high-water marks, caps, or review periods where needed
  • Preserve the base software fee so support and infrastructure are funded regardless of short-term returns
Economic logic: performance linkage should be an upside alignment mechanism, not the foundation of the business model.

Billing controls

Roles, scopes, and usage records make the model enforceable.

Authentication identifies the subject and organization. Scopes determine whether that subject can create backtests, run paper trades, schedule live trades, update policies, or access exports. Entitlements define the licensed modules and limits.

Every protected production action can write to the control database: who called, which organization, which feature, which route, whether it was allowed, and what usage counts were consumed. That creates a practical billing and audit trail without tying the business model to unverifiable return claims.

Recommended packages

Start with a simple ladder, then customize enterprise terms.

Published pricing can stay conversational while enterprise pricing is quoted after scope. The product should make clear that institutions can plug AlphaWeave into components they already have rather than replacing the whole stack.

Research

For strategy teams that need backtests, attribution, policy simulation, and evidence review before production deployment.

Base platform + backtest/policy modules

Trading Operations

For desks that need paper trade scheduling, replay dashboards, risk-capped weights, position size multiple review, and operational audit trails.

Research + paper trading + workflow monitoring

Enterprise / White Label

For banks and asset managers that need internal deployment, custom connectors, SSO, live-trading governance, and branded client-facing reporting.

Full platform + enterprise integration

Price AlphaWeave Capital around the workflow it governs: decisions, capital, risk, and evidence.

A Walkthrough