How to price an AI workflow for clients
Price a packaged workflow around the client outcome, delivery context, reuse, support, and included AI calls—not prompt length.
Do not price by prompt length
The number of words in a prompt does not tell the buyer how reliable the result is, how much testing it required, or what business job it completes. Pricing by the file itself pushes the offer toward commodity comparisons.
Price the delivery context
A workflow included in a strategy engagement has different value from the same workflow sold as a self-serve download. Consider the cost of the problem, frequency of reuse, customization, review, support, licensing scope, and AI calls included.
- Standalone self-serve tool
- Branded tool included in a service
- Customized workflow for one client
- Reusable licensed asset
- Ongoing service with review and updates
Use a pilot to find willingness to pay
For early customers, offer a clearly scoped pilot around one real workflow. Track whether the client uses it, whether it reduces delivery time, and whether access changes the perceived completeness of the engagement. Use that evidence to set packaging and price.
Key takeaway
Price the outcome and the surrounding service. The HTML file is the delivery mechanism, not the unit of value.
Complete guide
Turn a proven method into an AI HTML product you can sell.
Explore the approachConcrete use case
Proposal Builder
See the client workflowTurn your expertise into an AI HTML product.
Build from your sources, approve the method, test the experience, and deliver it as AI-powered HTML.
Create an AI HTML product