What Is a "Person-Month"? A Plain-English Guide for Business Owners — Rates and Pitfalls

A person-month is a unit that represents the amount of work one engineer can complete in one month, typically defined as around 20 working days or 160 hours. The notation "X person-months" appears frequently in system development quotes, but many business owners find it hard to intuitively connect to cost or timeline. This article organizes the basic concept of person-months and what to look for when reading a quote.

System development has few processes that can be mass-produced like a factory line; much of design, implementation, and testing depends on human effort, making it a labor-intensive industry. As a result, the common business practice is to estimate project scale in person-months — how many people working for how many months. While this method makes labor hours relatively transparent, it can still be difficult for the client to judge whether the resulting price is reasonable.

One reason person-month estimates are hard to interpret is that the output of "one person-month" can vary significantly depending on the engineer's skill level. The actual effort required also shifts with the complexity of requirements and the amount of communication needed between the client and the vendor. Furthermore, the person-month figure in an estimate is only a projection — it is not unusual for it to change if the scope changes during development.

Person-month rates vary widely based on the engineer's experience and specialization, the vendor's location (metropolitan versus regional), and the size of the development company (major system integrator, mid-size firm, or freelancer). As a general tendency, experienced staff handling upstream processes command higher rates, while those focused on downstream work tend to be more affordable — but actual figures differ by project and vendor, so it is difficult to state a single definitive rate. It is advisable to request quotes from multiple vendors and compare the person-month rates and the breakdown of hours they present.

*The above reflects general tendencies only — always confirm actual rates through quotes from multiple vendors.*

One important caution with person-month math is that doubling the headcount rarely halves the timeline. When a new member joins a project, existing members often need to spend time on onboarding and knowledge transfer, which can temporarily reduce overall productivity. Adding people also increases the coordination and communication overhead among team members. This phenomenon has long been noted in software engineering, and it illustrates that a person-month is not a unit that can simply be divided and multiplied as "headcount × duration."

- Breakdown of total person-months: How many person-months are allocated to each phase (requirements, design, implementation, testing, etc.)
- Skill level of assigned staff: Years of experience for members assigned to upstream and downstream work
- Rate per person-month: Whether the rate for each line item is clearly stated
- Handling of scope changes: The conditions and process for adding person-months or cost if requirements change
- Person-months for maintenance and operations: How much effort is budgeted for post-launch support
- Contract type: Whether it is a fixed-price (ukeoi) or quasi-delegation contract, and the resulting difference in scope of responsibility

The Guide to Reading a Development Quote covers how to read a quote in more detail.

A person-month is a convenient unit for expressing development effort, but it is not something that can be simply multiplied or divided to predict cost or timeline. Carefully reviewing the breakdown and assumptions behind the person-month figures in a quote supports a sound ordering decision. See the Basic Guide to Ordering System Development for the overall process, and the Guide to System Development Cost Ranges for more on pricing.