vendor-estimate-creator

Name: vendor-estimate-creator
Availability: InStock
Author: takusaotome

Create WBS-based effort, cost breakdowns, and ROI justification from software RFQs.

5|4|Updated Nov 9, 2025

Search Tags:#roi #estimate #wbs #npv #rfq #software project costing

Ready to run

npx skills add https://github.com/takusaotome/claude-skills-library --skill vendor-estimate-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vendor-estimate-creator
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/vendor-estimate-creator
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill vendor-estimate-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Software RFQs often lack clear sizing and justification, making it hard to produce accurate WBS-based effort, cost breakdowns, and a persuasive ROI business case for quotations.

Core Features & Use Cases

RFQ-to-Estimate Workflow: Analyze RFQ requirements, extract scope metrics (screens/APIs/DB/etc.), identify gaps, and list assumptions.
WBS + Effort + Cost Breakdown: Generate a phase-based WBS, estimate effort per task using standard references, aggregate labor costs, and include contingency based on risk level.
ROI and Quotation Document Generation: Build an ROI/NPV/business case using ROI guidance and output a professional Markdown estimate document (including ROI, risks, schedule assumptions, and approvals).

Quick Start

Use the vendor-estimate-creator skill to generate a Japanese software development estimate document from your RFQ by pasting the RFQ text and stating the target deliverable should be a complete Markdown quotation with WBS, effort, cost totals, and ROI.

Frequently Asked Questions about vendor-estimate-creator

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

FAQPage Schema

How do I create a software cost estimate and WBS from an RFQ?▼

To create a software cost estimate from an RFQ, analyze the requirements to extract scope metrics, generate a phase-based WBS, estimate effort per task, aggregate labor costs with risk-based contingency, and output a Markdown quotation document.

What is the best way to calculate ROI and NPV for a software project quotation?▼

Calculating ROI and NPV for a software project quotation involves building a business case from the aggregated labor costs and effort estimates derived from the WBS, justifying the investment directly within the generated estimate document.

Can I generate a structured estimate document directly from raw project requirements?▼

Yes, you can generate a structured estimate document directly from raw project requirements by parsing the RFQ text to identify gaps, list assumptions, calculate total costs, and export a professional Markdown quotation with approvals.

How do you handle risk-based contingency and assumptions in software project costing?▼

Handling risk-based contingency in software project costing involves identifying gaps in the RFQ, listing explicit assumptions, and applying a risk level adjustment to the aggregated labor costs before finalizing the estimate.

Does this approach to RFQ estimation support extracting scope metrics like screens and APIs?▼

Yes, RFQ estimation supports extracting scope metrics by analyzing the provided requirements text to quantify items like screens, APIs, and database structures, which form the baseline for the WBS effort calculation.

What are the limitations of using a WBS-based estimate for software quotations?▼

A limitation of WBS-based estimation is its dependency on the clarity of the initial RFQ; vague requirements require extensive assumption listing and gap identification to avoid inaccurate effort and cost breakdowns.