Software Gauge transforms your requirements into an objective cost benchmark in three stages. No consultants. No sales call. No waiting.
Stage 1
Begin by uploading your software requirements document, or paste the requirements text directly. Software Gauge accepts: PDF (formatted specs, RFP drafts, SRS documents), Word documents (.docx, .doc), plain text (.txt), or pasted text.
You do not need a formal Software Requirements Specification. Software Gauge is designed to work with documents you already have: draft requirements notes, user story lists, functional specification drafts, RFP scope sections, or business requirements documents (BRD). Even an early-stage scope description listing 5–10 major features will produce a useful estimate. The more detail your document contains, the more precise the sizing.
Stage 2
After uploading, Software Gauge asks ten structured questions to calibrate the base COSMIC size count for factors not captured in requirements text alone.
| Question Category | What It Captures |
|---|---|
| Integrations | Number and complexity of third-party system connections |
| Data volume | Expected transaction load and performance requirements |
| Compliance | Regulatory, security, or audit requirements |
| Delivery constraints | Timeline pressure and staged delivery requirements |
| Geographic complexity | Multi-country, multi-currency, or multi-language scope |
| Ambiguity level | How complete and specific your requirements are |
Total time for this stage: under 5 minutes.
Stage 3
With your document and context answers, Software Gauge runs a five-step analysis:
Step 1 — Requirement parsing
The requirements document is parsed to identify functional processes — distinct operations the software must perform in response to triggering events.
Step 2 — Data movement identification
For each functional process, the analysis identifies all COSMIC data movements: Entries, Exits, Reads, and Writes.
Step 3 — CFP counting
Each data movement = 1 COSMIC Function Point. The total CFP count is the sum across your entire requirements scope.
Step 4 — Cost driver application
Your context question answers apply calibrated adjustments to the base CFP estimate.
Step 5 — ISBSG benchmarking
Your adjusted CFP count is matched against the ISBSG database to produce three benchmark tiers (P25, P50, P75).
Stage 4
Your report is generated as a branded PDF. It includes: total COSMIC Function Points for your requirements, CFP breakdown by functional area, three cost benchmark tiers (Industry Low / Industry Median / Industry High), your estimated range with cost driver adjustments applied, and methodology reference notes (ISO 19761, ISBSG).
The report is designed to be presented to stakeholders, included in RFP documentation, or used for budget justification to your CFO or board.
Do I need a formally written requirements document?
No. Software Gauge is designed to work with working documents — drafts, notes, BRDs, user story lists. A formal SRS is not required.
How accurate is the estimate?
COSMIC sizing is inherently more consistent than effort-based estimation because it measures functional scope rather than human effort. For a well-documented requirements set, variance between different COSMIC analysts is typically under 15%. The ISBSG benchmark data represents median outcomes from real completed projects globally.
Is my document stored after analysis?
Your requirements document is processed in memory and deleted within 60 seconds of analysis completion. It is never written to a database, indexed, or retained.
Can I use the report in a procurement process?
Yes. The report is designed for that purpose. It cites the ISO 19761 standard and ISBSG benchmark source, making it auditable and defensible in procurement, board, and CFO review contexts.
Upload your document and receive a benchmark in minutes.