Discuss your workflow
Free initial conversation
One repeated workflow problem that needs a fit decision.
ConversationFree
RecurringNone
Pricing
Start with one defined workflow.
The initial discussion and ASHVUN Audit are free. Paid implementation separates one-time setup from ongoing support, with larger work defined through a written scope.
Engagement options
Know what is free, what is setup, and what recurs.
Prices below preserve the accepted local commercial baseline for implementation. The Free ASHVUN Audit has no checkout or payment requirement.
Option
Best fit
One-time
Monthly
Next step
ASHVUN Audit
Existing operational Audit workflow
A suitable workflow that needs documented findings before scope.
AuditFree
RecurringNone
Custom Workflow Agent
Focused implementation
One repeatable workflow after matching Audit findings and a written scope are approved.
Setup$2,999 setup
Ongoing$499 / month
Advanced Workflow System
Multi-workflow written scope
Multiple workflows, deeper controls, or higher-consequence review.
SetupStarting at $7,500 setupTypical range: $7,500–$15,000 setup
OngoingStarting at $999 / monthTypical range: $999–$2,500/month
Approved scope only: this payment destination is not the next step before the free Audit and written scope. It preserves the existing approved Custom Workflow Agent destination exactly. That destination may still show the prior Cliphorium billing identity until separate human Stripe review. This local rebuild did not access Stripe or change any product, price, link, webhook, return URL, secret, or account setting.
Commercial boundaries
Setup, support, and additional work do different jobs.
Exact terms are defined by the approved package or written scope. The statements below avoid adding unapproved promises.
Implementation setup
Setup covers the mapping, configuration, testing, and launch work named in the approved scope.
- Defined trigger, inputs, reviewer, and permitted action
- Named connection or configuration work
- Agreed test cases and acceptance review
- Handoff material stated in scope
Ongoing support
Ongoing support, monitoring, maintenance, and adjustment allowances are only what the approved package or written scope states.
- Named monitoring and maintenance boundary
- Defined support route
- In-scope adjustment allowance, when written
- No implied 24/7 or guaranteed response
Separately scoped work
Additional workflows, material expansion, and work outside the approved boundary require a separate written decision.
- New workflows or systems
- Custom connections not named in scope
- Third-party subscriptions, usage, or transaction fees
- Data cleanup, migration, or emergency work not included
Why a scope changes
Complexity comes from the workflow boundary, not a generic “AI” label.
The written scope accounts for the number of workflows, systems, roles, exception types, permissions, data quality, reporting, test depth, fallback, and support expectations.
Client inputs
Your team identifies the current process, source material, decision owners, exceptions, policies, access approvers, test participants, and sign-off owner.
Third-party costs
New software, model usage, subscriptions, transaction charges, and other provider costs are not assumed to be included. They are addressed in writing when relevant.
Changes after approval
Material changes to the workflow, tools, access, volume, policy, or support boundary may require a revised scope and price. No unlimited-revision promise is made.
Billing, cancellation, refunds, ownership, and exit
Use only the terms in the applicable approved agreement. This page does not create a refund promise, cancellation right, warranty, ownership transfer, or offboarding commitment beyond those terms.
Review current termsNot sure which paid scope fits?
Start with the free discussion. If the workflow is suitable, the Free ASHVUN Audit provides findings before any paid implementation decision.