Skip to main content
Published in Product Insights

The One Thing to Look At in a Software Development Estimate

The One Thing to Look At in a Software Development Estimate
Table of contents
  1. What Should Software Development Cost Estimates Show?
  2. What Drives the Numbers in Software Development Cost Estimation?
  3. How Do You Work Out How Much of a Software Project Pays for Development?
  4. How Far Off Can Early Software Cost Estimation Be?
  5. What Is the Difference Between a Fixed Price and a Time and Materials Estimate?
  6. How Do You Get a Firm Price for Custom Software Development?

This post is for a buyer holding two or more software development cost estimates. It first ran in April 2025 and compares an offshore estimate with The Gnar Company’s by where the money goes. It also shows how to read the hours, rates and exclusions behind software cost estimation, and how fixed price differs from time and materials. After reading, you can check what share of an estimate funds development and ask for a price written into the contract. That matters because Construx says early estimates “can be inaccurate by a factor of 4x on the high side or 4x on the low side”.

It’s not the hourly rate, it’s where your money actually goes.

When choosing a development partner, most companies compare hourly rates. But the real question isn’t how much per hour? It’s how much of your budget actually goes to development?

It’s a metric we track closely to make sure we’re maximizing value for our clients, so it was shocking when we recently reviewed an actual offshore estimate for a software build with full fidelity Figma designs. While the rates looked low on the surface, only 37% of the budget was going toward actual development. The rest? Extra layers of management, inefficiencies, and hidden overhead.

Bar chart titled Off-shore v. The Gnar, percent of project budget by role: off-shore 63% PM, BA and QA and 37% development; The Gnar 28% PM and 72% development

For Every $100,000 You Spend:

Offshore: Only $37,000 builds your product. Everything else goes elsewhere.

The Gnar: $72,000 goes directly to development, nearly double the value.

Here’s a different way to look at it, breaking down the same estimate by hours per role.

Chart titled Off-shore v. The Gnar, percent of weekly hours by role: off-shore 45% engineering, 23% QA, 14% BA, 9% off-shore PM, 9% US-based PM; The Gnar 83% engineering and 17% US-based PM

Where Your Budget Actually Goes Matters

Here’s why budget allocation impacts your project’s success:

  • More budget for development means faster time-to-market. Delays cost real money.
  • A dedicated team leads to higher quality. Our engineers work on one project at a time. Offshore teams? You’re often paying for teams juggling multiple.
  • You might be paying for their management. The offshore estimate we saw included two project managers for a small scope! We assign one only if needed.
  • Know what’s actually included. Cultural and time zone gaps lead to costly misunderstandings and revisions that you end up paying for. The Gnar stands by its work with a 12-month bug-free warranty.

Before You Sign, Ask Yourself (or them):

  • What percentage of my budget actually funds development work?
  • Will my engineers be fully dedicated to my project?
  • Who’s accountable for quality and meeting deadlines?
  • What’s the hidden cost of inefficiencies and rework?

It’s easy to be tempted by low hourly rates. But in software development, what you pay for matters more than what you pay per hour.

What Should Software Development Cost Estimates Show?#

Good software cost estimation shows the hours and the rate for each role. An accurate estimate lists what the price leaves out. It states how sure the firm is of the number. It says who pays if the work runs over. On the third point, a 2024 post from the Software Engineering Institute (SEI) at Carnegie Mellon says estimators should “document and communicate the uncertainty and risk in the cost estimate”.

  • Hours by role. They let you answer this post’s own question: “What percentage of my budget actually funds development work?”
  • A rate for each role. The Federal Acquisition Regulation (FAR) sets rules for federal government contracts. Its text effective March 13, 2026 says a time-and-materials contract must have “separate fixed hourly rates ... for each category of labor”. The rates “include wages, overhead, general and administrative expenses, and profit”. A rate gives the price of one hour. The hours by role show what those hours build.
  • What the price leaves out. The SEI post limits itself to “the effort and cost of developing software”. It says “Items required to support a software system [i.e., components, external services, supporting hardware, etc.] are not accounted for in software development estimates”. Request a written list of what the firm’s price leaves out.
  • How sure the firm is of the number. Ask how much uncertainty the estimation carries and what could move it. The SEI says estimators “should perform uncertainty and risk analysis”.
  • Who pays if it runs over. Gnar’s How We Work page says: “Ask any software firm two questions before you sign”. They are “Is the price in the contract? Who pays if it runs over?” This post also asks, “Who’s accountable for quality and meeting deadlines?”

The SEI post gives a reason to ask: “Dependable estimates help manage expectations among stakeholders of the project and ensure sufficient time and resources are provided for high-quality work”.

What Drives the Numbers in Software Development Cost Estimation?#

Size and cost drivers set the effort and cost numbers in software development cost estimation, according to the SEI. The SEI post calls the size metric “a major determiner of the cost”. It says size provides “an average effort or cost”. It says “cost drivers can explain variance caused by product, process, personnel, or environmental factors”. Its examples include “reliability requirements” and the “amount of documentation being produced”.

The SEI post notes that “Software doesn’t have physical dimensions”. It adds that, historically, source lines of code (SLOC) “was the first size metric identified and used for software cost estimation”.

The post describes COCOMO II, the Constructive Cost Model II, as a model that takes “size, personnel, product, and environmental attributes as input”. It says the model “returns the estimated effort in person-months (PM) as the output”. It says scale factors “affect the exponent (and thus affect the effort nonlinearly)”. The usual equation form “accounts for the fact that effort grows at a nonlinear rate relative to size”.

Cost estimation models rest on past data. The SEI post says generalizable models are “built on data collected across several organizations and various application domains”. It says trends “can be quite different across different software types and development environments, even within the same organization and team”. It adds that cost drivers help explain the variation, “leading to more accurate effort or cost estimates”.

Cost estimation also helps plan tools and people. The SEI post says estimates “help manage and plan required resources, such as personnel, equipment, and tools”. It says ROI analysis weighs money and time “versus the expected benefits”.

NASA’s Software Engineering Handbook lists methods and tools too. The table quotes the SEI post and the handbook’s version B of the SWE-015 page (last updated August 5, 2021; NASA has published a later version since).

Method or toolWhat the source says
Bottom-up estimateNASA: “the first step is to develop the work breakdown structure (WBS)”.
Analogy and model-based estimatesNASA: “It is highly recommended that model-based and analogy estimates be completed as verification or backup to the primary estimate”.
Parametric modelsNASA: “Model-based estimates are estimates made using parametric cost models”.
SEER-SEMSEI: “allows SLOC and function points as size inputs and cost drivers (such as platform application and complexity) to get the effort estimate”.
TruePlanningSEI: size inputs include “SLOC, function points, predictive object points, or use case conversion points”.
Function pointsNASA: “Other methods that can be used to estimate the software size include function point and use case counting”.

NASA says “Cost models require an estimate of the size of the system”. It adds “a set of inputs describing the system and development environment”. It also says “The accuracy of size estimate is greatly improved when anchored by actual code counts from similar software products or similar software components”. If a project has a cost repository, NASA says it “should be updated with data related to this cost estimate, including software size, effort, and schedule data”. When estimates and the project-imposed budget disagree, NASA says “in most cases, the real solution is to reduce scope or functionality”. The page also lists lessons from the JPL Cost Estimation Handbook, including “When in sales mode, there is tremendous pressure to be optimistic on cost and capability to sell the job”.

On scope, NASA says the work includes “understanding the intended concept of operations and operating environment to fully characterize the complexity of the work”. It lists “software requirements analysis, software design, software implementation, and software integration and testing”.

The SEI post says “While new projects may be similar to existing or previous projects, there will be at least some new functionality”. It warns that “a new project might not be well represented in the data that underlies a given cost estimation model”. It says “Cost drivers can be adjusted to better represent the differences of the new project”.

This post’s own list says, “Know what’s actually included.” For a software project, ask what size of software project the estimation assumed and which cost drivers the firm adjusted.

How Do You Work Out How Much of a Software Project Pays for Development?#

To figure out the share, add up the dollars the cost estimation gives to your developers’ engineering work. Then divide by the total price. The result is the share of your spend that builds the product. In the one offshore estimate this post reviewed, that share was 37%.

  1. List each role and its hours. Together they give the estimate’s team composition. This post’s hours chart shows “off-shore 45% engineering, 23% QA, 14% BA, 9% off-shore PM, 9% US-based PM; The Gnar 83% engineering and 17% US-based PM”.
  2. Price each role. Multiply each role’s hours by that role’s hourly rate. Then add the results to get the total.
  3. Divide the development dollars by the total. This post’s budget chart shows “off-shore 63% PM, BA and QA and 37% development; The Gnar 28% PM and 72% development”. On a $100,000 budget, this post says, “Offshore: Only $37,000 builds your product”.
  4. Ask what each other role does. This post warns, “You might be paying for their management”. Ask the firm for a description of what each role besides engineering does in a week and which deliverables it produces.

How Far Off Can Early Software Cost Estimation Be?#

Estimation at Initial Concept can be four times too high or four times too low. Construx’s page on the Cone of Uncertainty says so. It adds that “The total range from high estimate to low estimate is 4x divided by 0.25x, or 16x”.

Point in the projectWhat Construx’s page says
Initial Concept“Estimates created at Initial Concept time can be inaccurate by a factor of 4x on the high side or 4x on the low side”.
A commitment at Initial Concept or Product Definition time“it has a factor of 2x to 4x error in its estimates”.
About 30% of the way into the project“Meaningful commitments in the early-middle of the project ... are possible and appropriate”.

Construx’s page has no date. This post read it in November 2026. The page says “The Cone represents the error in estimates created by skilled estimators. It’s easily possible to do worse”. It also says “The only way to reduce the variability in the estimate is to reduce the variability in the project itself”.

Construx names decisions that narrow the range. It says defining requirements “eliminates variability further”. It also says “Designing the user interface helps to reduce the risk of variability arising from misunderstood requirements”. The page says “if the Product Definition gets redefined later, then the Cone will get wider”. It says Product Definition “applies equally to web services, internal business systems, and most other kinds of software projects”.

This post asks, “What’s the hidden cost of inefficiencies and rework?” The SEI post gives one example. If past data “suggests that requirements volatility caused about 25 percent rework,” estimators “can apply a 1.25 factor on the size to account for the rework in the estimate”. The SEI post says “As the requirements and specifications for the required software project change, so should the size estimate”. It says requirements change “as customers and users start to better understand how the system needs to work”.

Gnar’s How We Work page says when its price is determined: “the price is set after Discovery, once the work is agreed.”

What Is the Difference Between a Fixed Price and a Time and Materials Estimate?#

A time and materials estimate forecasts hours that you pay for as they are worked, at fixed hourly rates. The Federal Acquisition Regulation describes a firm fixed price as a price “not subject to any adjustment on the basis of the contractor’s cost experience in performing the contract”. The FAR also says “Time-and-materials contracts and labor-hour contracts are not fixed-price contracts”. These are the federal government’s rules for its own contracts.

The FAR describes a time-and-materials contract as one based on “Direct labor hours at specified fixed hourly rates” plus “Actual cost for materials”. It sets a condition. The contract “may be used only when it is not possible at the time of placing the contract to estimate accurately the extent or duration of the work”. The same sentence adds a second case: “to anticipate costs with any reasonable degree of confidence”. The FAR also says this contract type “provides no positive profit incentive to the contractor for cost control or labor efficiency”.

Gnar’s How We Work page says: “At The Gnar Company, Discovery ends with a build plan that splits the work into milestones, each with a fixed price.” The same page says what its fixed price leaves out: “What's not included: a new feature you ask for later. It gets its own price, and you decide whether to add it.”

How Do You Get a Firm Price for Custom Software Development?#

As general advice, pay for the work that defines the product first. Then ask for a fixed price on each milestone and get it written into the contract. Construx says “Effective organizations delay their commitments until they have done the work to force the Cone to narrow”. It names one such step: “defining the product vision (including committing to what you will not do), reduces variability”.

At Gnar, the up-front step is called Gnar Discovery and Design. Its Discovery page says: “Discovery gives your team the research, design, and technical architecture to build the right thing before a dollar is spent on development”. The Discovery FAQ gives the price: “The Gnar Company’s Discovery costs $15,000 to $30,000, depending on the tier. Foundation costs $15,000 for two weeks, Core $20,000 for four and Accelerator $30,000 for six. Each tier ends with a Milestone Project Plan and a fixed price for your build. You get that plan whether or not you build with The Gnar Company.”

The same FAQ says: “The price is guaranteed: if the build costs more than quoted, the overage is on us.” Gnar’s Build page gives Build’s own price: “The Gnar Company’s builds typically run $150K to $300K+.” Gnar’s post What a Software Discovery Phase Should Include covers what a discovery should deliver.

Gnar’s guarantee, in its own words: “Three commitments on every build engagement: a fixed milestone price with any overage on us, a guaranteed outcome meaning the software works as specified or we fix it, and a twelve-month bug-free warranty. It covers Discovery, Build, Forge and Maintain. It does not cover Embed. On Compass, Immerse and Integrate, ask us.” This post said in 2025, “The Gnar stands by its work with a 12-month bug-free warranty.” Gnar’s post Bug-Free Warranty: What a Dev Agency Should Cover covers what a warranty should cover.

Frequently asked questions

Why can a low hourly rate be misleading?

It does not show how much of the total budget pays for development. The offshore estimate Gnar reviewed spent the rest on management, inefficiencies and hidden overhead.

How does Gnar assign engineers and project managers?

Our engineers work on one project at a time. We assign a project manager only if needed.

What warranty does Gnar mention?

Gnar offers a 12-month bug-free warranty.

What should a software development estimate include?

It should show the hours and the rate for each role, what the price leaves out, and how uncertain the number is. A 2024 Software Engineering Institute post says estimators should document and communicate the uncertainty and risk in the cost estimate. It also says items required to support a software system are not accounted for in software development estimates.

What is the difference between a fixed price and a time and materials estimate?

A time and materials estimate forecasts hours you pay for as they are worked, at fixed hourly rates. A firm fixed price is, in the Federal Acquisition Regulation’s words, a price “not subject to any adjustment on the basis of the contractor’s cost experience in performing the contract.” At The Gnar Company, Discovery ends with a build plan that splits the work into milestones, each with a fixed price.

How accurate is an early software estimate?

An early estimate can be off by a factor of four in either direction. Construx says estimates created at Initial Concept time can be inaccurate by a factor of 4x on the high side or 4x on the low side. It also says the only way to reduce the variability in the estimate is to reduce the variability in the project itself.

What is a bottom-up software estimate?

A bottom-up estimate starts with a work breakdown structure, then estimates the size or effort of each element. Version B of NASA’s Software Engineering Handbook says “the first step is to develop the work breakdown structure (WBS).” Its next step is to “Estimate size and/or effort for each element.” It says model-based and analogy estimates should back up the primary estimate, which is “typically a bottom-up estimate.”

Who pays if a fixed-price software build runs over?

In federal government contracts, the Federal Acquisition Regulation says a firm fixed price contract places “full responsibility for all costs and resulting profit or loss” on the contractor. Gnar’s Discovery page answers it for The Gnar Company: “The price is guaranteed: if the build costs more than quoted, the overage is on us.”

Stay In The Loop

Never miss an update. Get the latest blogs, webinars, and expert insights straight to your inbox from The Gnar.