reversa-pricing-estimate

Generates three side-by-side feature pricing scenarios from billing profile and size metrics.

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-pricing-estimate-gleisonoliveira
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: reversa-pricing-estimate
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-pricing-estimate
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-pricing-estimate-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve? Freelancers and agencies struggle to price software features defensibly, often guessing a single number without grounding in effort, client value, or market rates. This Skill combines a billing profile and feature size metrics to produce three comparable pricing scenarios with deterministic calculations. ## Core Features & Use Cases - Three pricing scenarios: Computes Effort (hours, cost, tax reserve, markup), Value (10-30% capture of declared annual value), and Market Range (hourly benchmarks by country and seniority) side by side. - Deterministic formulas: Applies documented v2 formulas for effort hours by T-shirt complexity class, seniority factors, and market benchmark tables covering BR, US, PT, and MX. - Structured outputs: Writes estimate.md and estimate.json following a fixed template and JSON schema, with atomic writes, backup on recalculation, and billing currency conversion. - Use Case: After running the pricing profile and sizing steps for a Pix payment feature, invoke this Skill to get a markdown report showing Effort at 4,800-12,000 BRL, Value at 2,400-7,200 BRL, and Market at 3,200-16,000 BRL, plus guidance on which scenario to anchor the proposal. ## Quick Start Ask the agent to estimate the price of the active feature by combining the existing pricing profile and size metrics into the three scenarios.

Frequently Asked Questions about reversa-pricing-estimate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate a price for a software feature?β–Ό

Run the pricing profile step to capture hourly rate, tax factor, and margin, then the sizing step to assign a complexity class, then invoke this estimator. It produces three scenarios: Effort based on hours and cost, Value based on declared client return, and Market based on hourly benchmarks.

What pricing scenarios does the estimate include?β–Ό

Three scenarios are computed side by side: Effort (hours by complexity class times rate plus tax reserve and markup), Value (10% to 30% capture of declared annual value), and Market Range (benchmark hourly rates by country and seniority multiplied by the same hour range).

Which countries are covered by the market benchmark scenario?β–Ό

The market table covers Brazil, the United States, Portugal, and Mexico with hourly ranges per seniority level. For any other country, the Market scenario is marked unavailable with an explanation, while Effort and Value scenarios still compute normally.

What happens if the pricing profile or size file is missing?β–Ό

The estimator fails with a clear message telling you to run the profile or sizing step first. It never fabricates missing inputs, and if an estimate already exists it asks for confirmation before recalculating and backs up the old files.

Does the value-based pricing scenario validate client-declared returns?β–Ό

No. The declared monthly return and cost of not doing are raw unvalidated inputs. If both are zero, the Value scenario is marked unavailable; otherwise it captures 10% to 30% of the annual value and reports payback months as context only.