One portfolio. Clear prices. Clear ways to buy.

ONSET covers different operating needs, but a customer account should activate only the modules required for its agreed outcomes. The wider portfolio allows the same operating layer to expand without replacing the whole system.

Yes where a published standalone rate or scoped engagement is shown. The public catalogue shows only services currently available to discuss; supporting capabilities are supplied only as part of managed ONSET delivery.

A package bundles several capabilities within stated credits, channels, and deliverables. A standalone price is for a deeper dedicated scope around one specialist outcome; it is not an extra charge on top of a package. Enterprise work such as BEACON is scoped separately.

They are recommended starting points based on buyer fit, purchase clarity and investment range. ONSET does not publish a best-seller ranking until meaningful paid-sales history supports one.

No. CORTEX and Mothership are supporting intelligence infrastructure, not separate subscriptions. ONSET uses the relevant parts behind a purchased package or specialist engagement when the agreed work requires them. Buying a package does not provide unrestricted access to every internal platform tool.

BEACON is a separate enterprise visibility engagement, not a hidden package feature. Its audit, sprint, Sprint + Demand, and retainer ranges are published on the services page, and the final scope is agreed before work begins.

No. Each package has a separate setup fee for discovery, account and provider connection, knowledge setup, approval design, configuration, and acceptance testing. The setup fee and first monthly retainer are paid before onboarding starts.

The services catalogue shows the standard starting setup for each standalone service. It covers the bounded onboarding needed for that service. If data migration, extra channels, custom integrations, or unusual security work increases the scope, the complete setup price is stated in the written service order before payment.

Starter, Growth, and Pro have a six-month initial term. Growth Pilot is the lower-commitment three-month managed launch route. Monthly retainers are billed in advance.

Credits are workload units for completed customer work. The public schedule states the credit value of each covered outcome. Background technical processing does not deduct customer credits, and credits are not money, LLM tokens, or provider balance.

No. ONSET credits are service workload units. They are not money, LLM tokens, or a balance held with OpenAI, OpenRouter, WhatsApp, Stripe, or another provider.

We show the remaining workload and discuss an approved top-up or a package change. ONSET does not silently add credits, charge an overage, or expand the scope without written approval.

Customer-owned provider keys are the default. Managed-provider usage is offered only when a written allowance and an enforceable account budget are configured; otherwise it remains unavailable. Unpriced provider calls stay visible and are never presented as zero-cost usage. Customer-owned account charges are paid directly by the customer.

Supported LLM calls label cost data as recorded when a provider returns the charge, estimated when ONSET calculates it from measured usage and a published rate, or unpriced when no reliable rate is available. This operational telemetry is separate from customer workload credits and never authorises a customer charge.

Yes. Each account receives only the services stated in its signed order. Pausing or removing a service from operational use does not silently change the signed commercial terms; any billing change follows the written variation or cancellation process.

We begin with the operating problem, required systems, responsible owner, expected result and approval boundary. The smallest module or package that can prove that result is the recommended starting point.