How to Read a System Development Quote — Line Items, Person-Month Rates, and Overhead Costs to Check

A system development quote isn't just a price tag — it's closer to a blueprint showing how much effort and cost each piece of work requires. In practice, though, quotes often list line items like "requirements definition," "design," and "development" without making clear what's actually included in each. Person-month rates and the phrase "lump sum" in particular can lead buyers to judge a quote purely by its total amount without understanding what's behind it. This article walks through the typical structure of a development quote, how to read person-month rates, what to watch for with "lump sum" line items, and what to compare across quotes from multiple vendors.

Quote formats vary by vendor, but most break costs down by project phase. The common line items are:

- Requirements definition: The phase where what to build and what functionality is needed gets clarified
- Design: Turning requirements into concrete screen layouts, data structures, and system architecture
- Development (implementation): Actually building the software based on the design
- Testing: Verifying that the finished software behaves as specified
- PM fee (project management): The cost of progress tracking, quality management, and coordinating stakeholders
- Overhead / miscellaneous costs: Travel, initial server/tooling costs, documentation costs, and anything else not covered above

Quotes often express effort in "person-months." One person-month is the amount of work one person can complete in a month, working full-time (roughly 20 working days). The basic formula behind a quote's total is "person-month rate × number of person-months." Person-month rates vary depending on an engineer's experience and skill level and on the vendor's structure (e.g., prime contractor versus subcontractor) — rates are commonly said to range from several hundred thousand yen up to over one million yen per month, but this varies significantly by project and vendor, so always confirm the specific level with quotes from multiple companies. Rather than judging a quote as expensive or cheap based on the person-month count alone, it's important to check what work that count actually corresponds to. For a deeper look at the limitations and caveats of person-month-based estimating, see What Is a Person-Month? Things to Watch for in Estimates.

Some quotes bundle multiple tasks into a single line, such as "Development (lump sum): ¥X." While this keeps the document simple, it also makes it hard to tell what is and isn't included. For example, if it's unclear whether a "development lump sum" includes a certain number of design revision rounds, you risk being told later that "this counts as additional work" once the project is underway. If you see a lump-sum item, it's worth asking the vendor to break it down phase by phase before signing. For more on where additional charges tend to arise, see Preventing Additional Cost Disputes.

With only one quote in hand, it's hard to judge whether the price is high, low, or fair for the work involved. Getting quotes from multiple vendors under the same conditions and comparing them along the following axes reveals differences in the proposal itself, not just the total price.

When you receive a quote, asking the following questions — not just checking the total — helps prevent disputes later.

- How are the person-months allocated across each piece of work?
- Can you break down what's included in any "lump sum" line items?
- Under what conditions would a spec change trigger additional charges?
- Is maintenance/operations cost included in this quote, or billed separately?
- Who is involved in testing, and what criteria determine that it's complete?
- How long is this quote valid, and could the price change after that?

For the full picture of the development ordering process — from quote comparison through contracts and acceptance testing — see our System Development Ordering Guide.

A system development quote is made up of several components, from requirements definition through overhead costs. Rather than judging it by the total amount alone, it pays to understand the basis for the person-month rate, what's hiding inside any "lump sum" items, and the axes for comparing multiple vendors. Don't hesitate to ask about the breakdown and conditions once you receive a quote — comparing multiple vendors under the same assumptions is what leads to a sound ordering decision.