Estimate first, then firm bid
Example ranges help with planning, but Oreniss still reviews the current environment, customer workspace needs, and scope before confirming a responsible fixed project path.
Pricing and delivery model
Request, scope, contract, execute, invoice, maintain
Oreniss pricing is built for SMBs that need managed outcomes rather than open-ended tool seats. Work can be quoted as a scoped project, assisted setup package, Oreniss Token-funded execution, or maintenance plan, with approvals and customer-visible billing context before anything becomes billable.
Approvals gate assisted delivery
Human-assisted setup, infrastructure help, customer-facing updates, and operator-coordinated delivery lines stay behind explicit approval before they become billable.
Local billing authority stays primary
Oreniss keeps local customers, token balances, invoices, invoice events, and case-linked billing visibility authoritative even when Stripe handles hosted invoices, checkout, and automatic tax.
Oreniss Tokens
Prepaid tokens for approved agentic work
Oreniss Tokens are the customer-facing unit for approved agent runs, repeat requests, maintenance batches, and assisted automation inside an Oreniss workspace.
Nominal pricing starts at USD 1.00 per token before tier discounts, tax, and any approved invoice adjustments.
How token usage is consumed
Approved agentic work draws down the token balance as tasks run, complete, and reconcile. The exact debit depends on the accepted scope, recorded run activity, and any human-assisted review needed for the work.
Selecting a tier is not a live charge. Purchases require the approved checkout or invoice path, and live billing only proceeds after the customer confirms the payment boundary.
-
Approve
Confirm the checkout or invoice path before a token purchase becomes billable.
-
Fund
Purchased Oreniss Tokens land in the customer-visible balance and ledger.
-
Execute
Approved agent runs, repeat requests, and maintenance batches draw from the balance.
-
Reconcile
Usage, invoices, and maintenance history stay attached to the same workspace.
100 Tokens
0% discount- Calculation
- 100 x USD 1.00 = USD 100
- Unit price
- USD 1.00 per token
- Savings
- USD 0 savings
Small follow-up batch, lightweight agent run, or first maintenance request.
500 Tokens
10% discount- Calculation
- 500 x USD 1.00 - 10% = USD 450
- Unit price
- USD 0.90 per token
- Savings
- USD 50 savings
Monthly request batch, portal adjustments, and several approved agent runs.
1,000 Tokens
20% discount- Calculation
- 1,000 x USD 1.00 - 20% = USD 800
- Unit price
- USD 0.80 per token
- Savings
- USD 200 savings
Active workspace maintenance, implementation batches, and recurring automation work.
2,500 Tokens
30% discount- Calculation
- 2,500 x USD 1.00 - 30% = USD 1,750
- Unit price
- USD 0.70 per token
- Savings
- USD 750 savings
Larger agentic delivery queue, ongoing product work, or multi-surface support.
5,000 Tokens
40% discount- Calculation
- 5,000 x USD 1.00 - 40% = USD 3,000
- Unit price
- USD 0.60 per token
- Savings
- USD 2,000 savings
High-volume maintenance, repeat delivery work, and sustained agent-assisted operations.
- Taxes, invoice settings, and hosted checkout details are finalized in the approved billing flow.
- Unused tokens remain visible in the portal balance and ledger.
- Scope changes and assisted setup still require explicit approval before they can consume tokens or become invoice lines.
Scoped delivery
Best for defined website, integration, automation, AI-agent, or product work with a clear acceptance path.
Best for: Customers who can describe a clear outcome and want Oreniss to convert that scope into a responsible fixed project path.
Typical range: USD 750 to USD 15,000+ Estimate first, firm bid after review, contract before delivery.Example scenario
A website rebuild, customer portal, or workflow implementation where the business goal is clear but the exact delivery scope still needs review.
Billing example
The reviewed scope becomes a fixed project invoice line only after the firm bid, responsibilities, and contract path are accepted.
Scope changes create a new approval item instead of silently changing the invoice.- Range examples are planning signals, not automatic final quotes.
- Oreniss reviews the current environment before firming the bid.
- Final price depends on scope clarity, integrations, assets, and approval needs.
Human-assisted setup
Best when access, environment setup, credentials, content, or stakeholder review needs operator coordination.
Best for: Projects where manual access coordination, content collection, setup help, or approvals are part of the real delivery cost.
Typical range: USD 150 to USD 2,500+ Billed as setup lines, approved work items, or case-specific invoice items.Example scenario
An operator helps with launch access, browser or connector installation, content uploads, stakeholder coordination, or secret-safe setup tasks before execution can continue.
Billing example
Connector help, content loading, access coordination, or stakeholder review is listed as an assisted setup line before it can become an invoice candidate.
No setup line becomes billable until the customer approval gate is satisfied.- Assisted work stays behind explicit approval gates before it becomes billable.
- Unapproved work does not become an invoice or token-debit candidate.
- Assisted setup can sit beside a scoped project or a repeat-request Oreniss Token model.
Oreniss Tokens
Best for repeat requests, maintenance, agent runs, and task batches inside the same customer workspace.
Best for: Customers who expect recurring tasks, iterative improvements, or maintenance work in the same reusable workspace.
Token bundles: USD 100 to USD 3,000 before tax Five prepaid tiers use 100, 500, 1,000, 2,500, and 5,000 tokens with 0, 10, 20, 30, and 40 percent discounts.Example scenario
A customer keeps one workspace open for monthly request batches, portal improvements, agent runs, billing tweaks, or maintenance follow-up work.
Billing example
A monthly batch of portal tweaks or agent runs draws from an approved Oreniss Token balance recorded in the local ledger.
Token debits follow approved work items and reconciled agent-run usage; checkout opens only inside approved billing boundaries.- The local Oreniss Token ledger stays authoritative for customer balance.
- Base pricing starts at USD 1.00 per token before tier discounts and tax.
- Usage is debited as approved agentic work, repeat requests, or maintenance batches are executed and reconciled.
Maintenance
Best for post-launch support, monitoring, updates, content changes, small automations, and periodic improvements.
Best for: Customers who want continuity after launch without starting a new procurement process for every small improvement.
Typical range: USD 250 to USD 5,000+ per month Maintenance can combine reserved capacity, Oreniss Tokens, and approved invoice lines.Example scenario
A delivered website, portal, or workflow moves into a support path that covers updates, fixes, content changes, and repeat technical improvements.
Billing example
A support month can combine reserved maintenance capacity, Oreniss Tokens, and approved support invoice lines.
Renewal and support changes stay explicit before the next invoice candidate is created.- Maintenance can be planned as reserved capacity, Oreniss Tokens, or approved invoice lines.
- The same customer workspace can carry project delivery into ongoing upkeep.
- Billing visibility remains connected to the same case, invoice, and approval history.
Billing examples
How pricing turns into approved billing lines
These examples show how scoped work, assisted setup, Oreniss Tokens, invoices, and maintenance become customer-visible billing context inside the same workspace. They explain planning paths and do not execute Stripe or ledger changes.
Firm-bid project invoice
A fixed build is estimated, reviewed, and converted into a contract-backed invoice line only after scope, responsibilities, and the customer workspace path are accepted.
No intake form submission sets the final price.Approved setup line
Access coordination, connector setup, content loading, and stakeholder review are separate setup items when they affect delivery cost.
No setup line becomes billable until explicitly approved.Approved token ledger
Repeat requests and agent-run batches draw from an approved Oreniss Token balance in the local Oreniss ledger.
Tier discounts, purchases, and token debits require checkout or approval review.Test-mode invoice execution
Local invoice lines define what Stripe should execute in test mode first, including hosted invoice links and tax-ready values.
No live Stripe mutation happens without explicit target approval.Same workspace after launch
After launch, support can continue in the same workspace as reserved capacity, token-funded tasks, or approved support invoice lines.
Maintenance work stays tied to the same workspace, approval history, and billing context.Token economics
How Oreniss Tokens connect price to work
Nominal token pricing starts at USD 1.00 per token before tier discounts and tax. Approved agentic work consumes tokens from the customer balance as runs and tasks are executed, recorded, and reconciled.
-
Base unit
Start from USD 1.00 per token
The public package math uses the token count, the nominal unit price, and the published tier discount.
-
Discount tiers
Larger packages lower the unit price
Five purchase options discount the nominal package by 0, 10, 20, 30, or 40 percent.
-
Usage debit
Agentic work draws from the balance
Approved runs, task batches, and maintenance work debit tokens according to recorded execution and review state.
-
Approval gate
Checkout and live billing stay explicit
Stripe can execute hosted checkout and tax, but local invoice, token, and approval state stay authoritative.
Billing controls
Stripe test mode first
Catalog sync, checkout, invoices, tax handling, and webhook mapping are designed to run in Stripe test mode before live target confirmation. No live Stripe mutation is allowed without explicit target approval.
Invoice safety
Local invoices lead, Stripe executes
Oreniss local invoices, lines, and invoice events define what should be billed. Stripe is the downstream invoice, payment, and tax execution layer rather than the only source of billing truth.
Customer visibility
Invoices and tokens in the portal
Customers see billing status, issued invoices, hosted invoice links, token ledger entries, and case-specific billing context beside work items and messages.
Assisted delivery
Approved setup lines only
Human-assisted setup, infrastructure coordination, and approval-required work items do not become invoice or token-debit candidates until the approval gate is satisfied.
Tax handling
Tax handling where enabled
Stripe tax calculation can be part of the planned invoice and checkout path when enabled, but customer identity, product tax behavior, and invoice values still start from the Oreniss local billing contract.
Maintenance
One buying path can continue after launch
Completed delivery can move into maintenance through reserved capacity, Oreniss Tokens, or approved invoice lines without forcing the customer into a brand-new workflow.
Does Oreniss sell open-ended builder seats?
No. Oreniss prices managed delivery outcomes, approved setup work, Oreniss Tokens, and maintenance rather than open-ended self-serve seats.
Are prices fixed automatically from the intake form?
No. Example ranges help customers understand typical buying paths, but Oreniss still reviews the current environment and scope before issuing a firm bid or contract-ready price.
How do Oreniss Tokens work?
Oreniss Tokens cover approved repeat requests, maintenance, and agent-execution batches inside the same customer workspace. The portal keeps the approved token balance, ledger activity, invoices, and checkout state visible before any live billing action proceeds.
What is the difference between assisted setup and Oreniss Tokens?
Assisted setup covers operator-coordinated access, content, installation, or secret-safe setup work. Oreniss Tokens cover approved execution capacity and task batches after the workspace and billing path are already in place.
When does work become billable?
Execution lines, assisted-delivery tasks, infrastructure work, maintenance changes, and contract changes move through explicit approvals before they become invoice or token-debit candidates.
How does Stripe fit into billing?
Stripe is the checkout, invoice, and tax execution layer, but Oreniss keeps local billing, invoice, and token state authoritative. Stripe work stays test-mode first until an explicit live target is approved.
Can billing run automatically without approval?
No. Pricing examples, token purchases, invoice candidates, Stripe checkout, and tax execution stay test-mode-first and approval-gated before any live billing target is used.