Lays out your options when a client asks to buy your AI workflow, producing AI Workflow Handover Options that compare keeping it as a service, a fixed-fee build and handover, a handover with training and support, and declining, with what the client gets and what you keep in each, plus IP and licensing questions for an adviser. Use for "run price-ai-workflow-offer", "client wants to buy our AI workflow", "sell my workflow", "license my process", "handover offer", "client wants to do it in hous...
Installs into .claude/skills of the current project.
Are you the author of Price Ai Workflow Offer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/polar-bear-org-price-ai-workflow-offer)
---
name: price-ai-workflow-offer
description: Lays out your options when a client asks to buy your AI workflow, producing AI Workflow Handover Options that compare keeping it as a service, a fixed-fee build and handover, a handover with training and support, and declining, with what the client gets and what you keep in each, plus IP and licensing questions for an adviser. Use for "run price-ai-workflow-offer", "client wants to buy our AI workflow", "sell my workflow", "license my process", "handover offer", "client wants to do it in house", "price a workflow build", part of the Pricing Under AI Pressure Pack by Polar Bear.
---
# AI Workflow Handover Offer
## When To Use
Clients are asking to buy access to your AI workflows instead of hiring you. Use this when a specific client has asked and you need to answer with options rather than a reflex yes or no. It answers: what could I offer, what would each cost them and me, and what must an adviser look at first?
## When Not To Use
If the client has sent contract clauses about how you use AI on their work, that is AI Contract Questions. If the request is really for the same service at a lower price, package it with the Productized Service Sheet or answer it as a discount request.
## Inputs
- The client's request in their own words (email, call notes)
- What the workflow is: steps, prompts, tools, the judgment you apply around it
- Your floor per day from the Floor Rate Calculator and the days a build or handover would take
If you have none of this, I start from your description of the request and the workflow, and mark the options as a first draft.
## Approach
A build and handover offer is described here generically: you build or adapt the workflow, hand it over, and either step away or stay on for a set period. The judgment is in what the client is really buying. Often it is control or cost, not the prompts, and the prompts alone do not carry the judgment that made the work good. The failure this prevents is a quick sale that hands over your edge for one fee and leaves you supporting it for free. Claude lays out the options and never drafts a licence or an IP clause.
## Workflow
1. Ask at most three questions: what exactly did the client ask for, what do you think sits behind it (cost, control, speed, keeping know-how in house), and is any part of the workflow built from another client's work?
2. Restate the request and the interest behind it from the client's words. If the interest is unclear, write the question to ask them before any price.
3. Lay out four options side by side: keep it as a service; fixed-fee build and handover; handover with training and support for a period you set; decline.
4. For each option write: what the client gets; what you keep (judgment, updates, know-how from other work); the support load on you; the risk to your edge; the price basis from your own numbers (build days x floor per day, plus support days). No prices are suggested.
5. List the questions for the adviser: who owns the workflow and prompts, the scope of any licence, confidentiality, warranty, liability, and use of third-party AI tools under their terms. Each ends "check with a qualified adviser".
6. The owner picks one option, or two to offer, and writes one line of reason.
## Output Format
```markdown
# AI Workflow Handover Options
**Client:** [code or name] | **Their request:** [their words]
**Interest behind it:** [cost / control / speed / know-how, or the question to ask]
## Options
| | Keep as a service | Build and handover | Handover with training and support | Decline |
|---|---|---|---|---|
| Client gets | [ ] | [ ] | [ ] | [ ] |
| You keep | [ ] | [ ] | [ ] | [ ] |
| Support load | [ ] | [ ] | [support period you set] | [ ] |
| Risk to your edge | [ ] | [ ] | [ ] | [ ] |
| Price basis | [ ] | [build days x floor] | [build days x floor + support days] | n/a |
## Questions for an adviser
- [Ownership of workflow and prompts]: check with a qualified adviser
- [Licence scope, confidentiality, warranty, liability, third-party AI tool terms]: check with a qualified adviser
## Decision
[Owner] picks the option to offer and books the adviser review by [date].
```
## Done When
- The client's interest is stated or turned into a question for them
- All four options are shown, decline included
- Every price basis comes from your floor and your day estimates
- Each IP and licensing point ends with "check with a qualified adviser"
## Quality Bar
- The client's request is recorded as given, never paraphrased into a quote
- No licence wording, IP clause or legal conclusion anywhere
- Another client's material is flagged, never folded into a handover
- No pressure tactics in how the options are presented
- Claude lays out the options; IP and licensing go to a qualified adviser, and the owner decides.
## Next
Run price-value-discovery-questions (Value Discovery Questions) to learn what the work is worth to the client.
## About the makers
This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).