Conversion and lifecycle
Technical pricing and packaging
Choose a value metric and package boundaries that fit real technical workloads and predictable customer costs.
Open-source skill · format validated
When this is useful
Design or review pricing, packaging, free tiers, trials, usage meters, and pricing-page explanations for developer tools and data products. Use for value metrics, workload economics, predictability, and upgrade boundaries; not payment integration or financial forecasts without data.
What to bring
User value, buyer and budget owner, usage shape, delivery cost evidence, present packages, evaluation needs, and any customer research or billing records.
What you can work toward
A meter comparison, workload scenarios, proposed package table, cost and predictability risks, customer-facing explanation, and research questions.
Developer-tool version
Compare value alignment for individuals, teams, service accounts, and heavy CI automation. Assess whether per-seat or per-request billing discourages integration or creates surprise usage. Separate open-source license terms from managed-service pricing.
Data-product version
Compare meters against volume, scan/compute behavior, concurrency, refresh frequency, retention, egress, and operating cost. Explain metering semantics, retries, failed jobs, predictability, and spend controls with explicitly observed or illustrative workloads.
How to use it
Choose the version for your product type and follow its repository installation instructions. Keep the skill folder, references and any assets together. Each skill works on its own; reuse a shared brief when helpful rather than repeating a full intake.
The source follows the open Agent Skills format and is MIT licensed. Live research and execution depend on the tools and permissions available in your host. Preparing a plan or draft does not itself authorize publishing, messaging, spending or production changes.
A starting prompt
Use the technical pricing and packaging skill for our developer tool or data product. Our task is [specific task], our supported environment is [environment], and the decision is [decision]. Use these facts and sources: [evidence]. Produce the requested artifact, label unknowns, and do not invent results or perform external actions beyond my authorization.
How to judge the result
Do not copy a competitor's prices without checking workload fit. No universal free tier, trial duration, margin target, or seat-based default.
Check that the product-specific version changes the recommendation, the requested deliverable is complete, and proposed tests are distinguished from observed results. Format validation does not establish how a model will perform on your product.
From input to reviewed output
Put it to work
- Choose the collection for your product type and install the relevant skill with its bundled references and assets.
- Supply the task, supported behavior, existing evidence and constraints that affect the decision. Reuse context already available.
- Ask for the concrete deliverable, distinguishing facts, hypotheses, unknowns and any untested instructions.
- Check the product-specific acceptance criteria, source claims and next steps before using or publishing the output.
Limits and tradeoffs
Do not copy a competitor's prices without checking workload fit. No universal free tier, trial duration, margin target, or seat-based default. No fresh-host model performance is claimed; verify output against your product, evidence and authorized environment.