skills/cali-product-workflow/skills-domain-libraries/cali-product-pricing/SKILL.md
Pricing strategies and models for product offerings. Covers exchange bases, consumption control, interest alignment, and perception techniques to formalize value exchange agreements.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-product-pricingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Thinking about pricing is thinking about the nature of the relationship we want to build. Price is not just a number; it's the formalization of a value exchange — an agreement on how risk and benefit are shared.
One-Time Payment for Ownership — "Buy It, It's Yours" Definitive transaction. The customer pays once and assumes total ownership and responsibility. Works well for durable goods or digital products where the maintenance cost for the creator is zero after sale.
Payment for Access (Instead of Ownership) The logic is the exchange of permanent ownership for temporary access. Manifests in main forms:
Access by Time Period:
Access per Unit of Outcome: payment is tied to a specific and transactional delivery. Example: AI service that transcribes audios — the customer pays R$ 0.10 per minute of transcribed audio. Pays for output, not for time of use.
⚠️ Don't confuse with "value-generated pricing": in access per unit of outcome, the price is fixed per transaction (X per minute, Y per image). In value-generated pricing, it's a variable percentage of a business impact (Z% of revenue increase).
Pre-Paid Credits Payment The customer buys a package of "credits" in advance, consumed as they use the service. Gives clear control over spending and guarantees upfront revenue for the company. Forces awareness about use — each action has a visible cost that deducts the balance, making consumption more intentional.
Computational Granularity Pricing Driven by variable cost technologies like AI. Price is tied directly to the resource consumed: per seconds/minutes of time that an AI model uses a specialized processor (GPU/TPU), per token of text processed, or per image generated. Reflects the real economy behind the service.
Performance Payment The provider assumes part of the client's risk. Payment is not tied to the product or time of use, but to the concrete result it generates. If the expected result is not achieved, payment is reduced or non-existent. Requires high trust and ability to measure "performance", but creates powerful alignment of interests.
Value-Generated Pricing Evolution of performance payment. Price is tied to a high-level business indicator — percentage of additional revenue or cost savings that the service provided. It's the deepest form of partnership, turning the provider into a partner in the result.
Payment with Data The customer receives a discount or free access in exchange for permission for their data to be used to train and improve the system, especially AI models. Formalizes a value exchange that often happens in a hidden way.
Bundling Instead of selling items separately, group them in a "bundle" with a single price. Increases perceived value (the customer feels they get more for less) and simplifies the pain of purchase decision (a single transaction instead of several micro-transactions).
Hybrid Pricing Combines stability with flexibility. Usually: a fixed subscription fee to guarantee access to the platform and basic set of features, plus a variable component for consumption of more expensive resources (AI credits, advanced features). Seeks balance: revenue predictability for the company and feeling of fairness for the customer.
Stepped Pricing / Tiered Pricing — Pre-Sale/Launch Strategy Turns pricing into a participatory event, directly rewarding the trust and agility of the first adopters. The risk for the buyer is higher at the beginning (little social proof), so the price should be as low as possible at this moment.
Example:
Benefits: creates strong sense of urgency; clear incentive not to "leave for later"; generates quick feedback cycle on demand.
⚠️ Requires transparent communication — the increase rules must be clear to everyone from the beginning.
Subscription Fatigue — Market Response Strategy We are in a phase of "subscription fatigue" — the accumulation of small monthly charges generates constant cognitive and financial burden for consumers. Alternatives:
The way price is presented has a profound impact on how it is perceived.
Monetary Abstraction: when presenting a price as "20" instead of "R$ 20.00", two sources of noise are removed: the dollar sign (explicit reminder of the act of spending) and cents. A clean and direct number tends to be processed more fluently.
Magnitude Perception (Endings 5, 7, and 9): left-digit effect — the brain processes the first digit from the left as an anchor for magnitude perception. That's why 9.99 seems significantly cheaper than 10.00.
Time (Temporal Reframing): fractioning into smaller and more palatable time unit. Software that costs R$ 365 per year can be presented as "just R$ 1 per day". Anchors the cost to a trivial daily expense.
Decoy (The Decoy Effect): introduce a third price option intentionally less attractive, to make one of the others look better in comparison.
Recontextualization (Value Anchoring): instead of anchoring the price on direct competitors, anchor on the value of the solution you replace. Example: an AI agent that performs sales should not be compared to other software, but rather to the cost of a salesperson's salary.
In a saturated market, where customers feel increasingly trapped in services by contracts, inertia, or difficulty migrating data, trust can be the biggest competitive differential.
Building a "trust pact" means designing the commercial relationship in a way that gives power and autonomy to the customer. It rests on three principles:
1. Contractual Freedom (The Right to Exit) The customer can end the relationship whenever they want, without bureaucratic barriers or punitive fines. The message: the customer stays for the quality of the service, not for a contractual obligation.
2. Financial Freedom (Insurance Against Initial Risk) Ensures that if a customer changes their mind — especially in the first few months — they don't lose their entire investment. Mechanics: fair refund with the returned value deducting only the usage period calculated based on the standard price, without discount.
3. Informational Freedom (Data Belongs to the Customer) The exit barrier of a service cannot be the difficulty of taking their data away. An explicit commitment to data portability — exporting information easily, freely, and in an open format — is the recognition that the company offers a tool, but the work and creation belong to the user.
Why Adopting These Principles is Also a Business Strategy: a company that facilitates customer entry and exit is making a bold bet on the quality of its own product, signaling that it intends to retain customers by merit, and not by lock-in.
development
PocketBase v0.39+ development - API rules, auth, collections, SDK, realtime, files, Go/JS extending, deployment, production tuning.
tools
Auto-initialize structured documentation for any project using lat.md (knowledge graph of markdown files with [[wiki links]], // @lat: code refs, and semantic search). Detects cali-product-workflow artifacts (spec-product.md, spec-tech.md, critiques) and uses them as seed material. Falls back to extracting business rules, architecture, and design decisions directly from the codebase. Use when a project lacks structured documentation or when lat.md/ is missing. After seeding, lat.md extension hooks keep documentation alive automatically.
testing
[Cali] Server security audit and hardening for private servers behind Tailscale. Use when: auditing server security, hardening SSH/firewall/Docker, checking for vulnerabilities, setting up fail2ban, reviewing port exposure, or responding to security alerts. Covers 6 layers: CloudFlare, UFW, Tailscale, SSH, Docker, Application. Triggers: "server security", "security audit", "harden server", "SSH hardening", "firewall rules", "UFW config", "fail2ban", "port security", "Docker security", "vulnerability check", "security review".
tools
Run supply chain security scans before installing packages or before releases. Triggers when: user installs a package (npm, pip, go get, brew), user asks to 'scan dependencies', 'check vulnerabilities', 'supply chain', 'security audit', 'run trivy', 'run socket', or before any release/deployment. Also triggers on mentions of: socket.dev, trivy, OSV-scanner, dotenvx, CVE, dependency audit. Covers all four tools with concrete commands.