メニュー
Use when pricing AI features within SaaS through credits, allowances, overages, model tiers, or fair-use controls while protecting margin from usage and provider-cost volatility; use SaaS pricing when AI economics do not apply.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing new or changed skills and bundled resources for unsafe installers, credential harvesting, hidden execution, or excessive permissions; use skill-writing for authoring structure.
Use when creating or normalising reusable proposal skills, trigger routes, contracts, references, or authoring automation; use skill-safety-audit instead for a read-only security review.
Use when routing, drafting, reviewing, or assembling a complete consulting proposal, EoI, bid, or tender response; use a numbered pipeline skill when only one known section is required.
Use when choosing whether an AI agent is included, sold as an add-on, or sold standalone; use the pricing skill for rate mechanics and the SLA skill for service commitments.
Use when selecting and adapting agent-specific contract exhibits for a proposal, MSA, or statement of work; use the addendum skill when drafting the full MSA/SLA overlay.
Use when defining intervention credits, abort rights, or refund mechanics for an agent engagement; use the SLA skill for broader credits and the outcome-pricing skill for success fees.
| name | ai-on-saas-pricing-and-packaging-proposal |
| description | Use when pricing AI features within SaaS through credits, allowances, overages, model tiers, or fair-use controls while protecting margin from usage and provider-cost volatility; use SaaS pricing when AI economics do not apply. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
saas-pricing-and-packaging-proposal).| Artefact or fact | Required? | Source/provider | If absent |
|---|---|---|---|
The AI Value Stack and AI Cost Stack from ai-on-saas-business-case-and-roi. | Required | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The buyer's pricing instinct (subscription, usage, hybrid, value-based). | Required | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The competitive pricing reference points (named competitors, prices). | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| Cost-of-tokens at P50 / P90 / P99 by tenant. | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The buyer's tolerance for variable bills. | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
| The buyer's tier strategy (good / better / best, or persona-based). | Conditional | Buyer, ToR, approved records, or discovery | Mark unavailable, request it, and qualify any affected claim or artefact. |
Stop condition: Stop before asserting scope, compliance, value, acceptance, or readiness when a load-bearing input is missing or contradicted.
Recovery: Record the gap, owner, and next evidence step; then return the narrowest qualified proposal content that remains supportable.
| Artefact | Consumer | Observable acceptance condition |
|---|---|---|
| AI Pricing Proposal subsection of the financial proposal. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| AI Pricing Pattern Decision Memo (for the win-room file). | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Model-by-Tier Matrix. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Fair-Use Clause language. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Price-Increase Clause language. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
| Worked examples for P50 / P90 / P99 tenants. | Proposal evaluator, buyer owner, and delivery team | Content is complete, traceable to named inputs, and usable in its stated proposal section without an unsupported claim. |
For agentic engagements, the pattern library expands from five to six agent-specific patterns: per-resolution, per-outcome, per-step, per-agent, hybrid (base + usage), and success-based (outcome-linked bonus). Two clauses become essential: intervention credit (if intervention rate exceeds the agreed ceiling, the buyer receives a credit) and vendor cost pass-through (agents fan out 10–100 model calls per task; a model-price increase invisible in a copilot can be catastrophic in an agent). Load ../ai-agent-pricing-and-packaging-proposal/SKILL.md for the agent pricing patterns and clauses.
| Evidence | Consumer | Acceptance condition |
|---|---|---|
| Input-and-assumption record | Proposal lead and reviewer | Every load-bearing claim maps to a source, approved assumption, or explicit gap. |
| Decision and review record | Buyer owner and delivery lead | The selected option, rationale, owner, stop condition, and approval status are visible. |
| Section acceptance check | Evaluator-readiness reviewer | Each output meets its stated acceptance condition and unresolved checks are not presented as passed. |
This skill may read supplied tender, discovery, architecture, commercial, security, and operating evidence and draft proposal artefacts within the authorised workspace. It must not publish, send, certify compliance, accept contractual terms, change production systems, spend funds, or disclose confidential evidence without explicit authority. Review and analysis remain read-only by default.
If files, current legal or technical evidence, calculation tools, network access, or reviewers are unavailable, produce the narrowest useful qualified draft. Label assumptions and checks as not assessed, omit unsupported assurances or figures, and state the exact evidence and owner needed to complete the work. An unavailable check never becomes a pass.
| Choice | Action | Failure or risk avoided |
|---|---|---|
| Usage variability | Model P50, P90, and abuse cases before fixing allowance and overage terms | Negative gross margin or buyer bill shock |
| Missing load-bearing evidence | Stop the affected claim, record the gap and owner, and continue only with separable supported content. | Fabricated assurance or hidden dependency |
| Conflicting buyer and supplier evidence | Surface the conflict for decision; do not silently choose the favourable version. | Misaligned scope, price, or acceptance |
| Irreversible, contractual, publishing, or production action | Obtain explicit authority and preserve an approval record before acting. | Unauthorised commitment or mutation |
When inference cost and usage distribution are uncertain, price a bounded allowance with measured true-up and model-tier rules; do not offer an unlimited fixed fee without cost evidence.