Why is it so difficult to give someone a single number for developing a new product? Because at the start, the number depends on decisions that have not been made yet, such as the manufacturing process, the materials and the confirmed requirements. One3 Design CEO Clay Martin says an estimate generally becomes reliable after the Discover and Define stages, because “after define, we are estimating a scoped project, not an open concept. That is when the number actually starts to mean something.”
Clay explained this to host Mike Downer in Episode 5 of The Design Orchestrator, the podcast from One3 Design, a product development firm whose industrial design, engineering, prototyping and testing services carry a product from idea to production.
When Does a Product Development Estimate Become Reliable?
According to Clay, a product development estimate generally becomes reliable after the Discover and Define stages, though the level of accuracy depends on how much information is available at the beginning.
For relatively straightforward projects with established requirements, an early estimate may remain accurate throughout development. This is particularly true when a company is modifying an existing product and has historical data to guide its decisions.
More innovative projects present greater uncertainty. Engineers may need to explore unfamiliar technologies, evaluate potential manufacturing processes or determine whether certain features are technically achievable.
After Discover and Define, Clay said, the team goes back to the early estimate, “or even a rough order-of-magnitude estimate,” and tells the client which way the needle is moving. Sometimes discovery reveals opportunities to reduce costs, and other times previously unknown challenges require additional investment.
The important distinction is that, after the definition stage, developers have a clearer understanding of what the finished product should accomplish. Our Episode 4 summary covers what the Define stage locks in to protect the client.
This approach aligns with the U.S. Government Accountability Office’s cost estimating guidance, which lists ground rules and assumptions, a technical baseline description, and sensitivity and risk analysis among the steps of a reliable estimate.
What Changes Between a Rough Estimate and a Locked-In Budget?
Actual decisions change it. Clay said a locked-in number “reflects actual decisions having been made: manufacturing process, materials, and confirmed requirements.”
Early estimates frequently rely on assumptions about materials, production methods and anticipated sales volumes.
Clay highlighted several factors that influence development budgets:
- Manufacturing methods, including injection molding, rotational molding and casting.
- Material selections based on product requirements and performance.
- Expected annual production volumes and long-term sales growth.
- Confirmed design specifications and functional requirements.
- The anticipated number of prototypes and design iterations.
Clay’s example was taking a part “from a fabricated weldment into a die-cast or sand-cast component, based on the ramp-up in volume.”
Once these details are established, engineers can estimate costs based on defined production processes instead of broad assumptions. For a stage-by-stage look at where the money goes, see our guide to product development cost.
How Much Can the Number Still Move After Define?
It can still move, and the main reason is the number of design iterations a product needs, although Clay said the more diligently “done” is defined, the less likely the number is to move much.
Clay explained that engineers might initially expect computer simulations, such as finite element analysis or computational fluid dynamics, to validate a design.
Physical prototypes can also uncover problems that were not obvious in digital models. Engineers may discover that components do not fit correctly or that a product performs differently than expected.
These findings can lead to additional prototypes, engineering revisions and testing expenses.
The NASA Systems Engineering Handbook likewise describes its engineering processes as applied “recursively and iteratively” through design and development.
Clay emphasized that experienced development teams should account for anticipated iterations within their proposals and explain when additional work could increase costs.
How Do You Communicate a Growing Estimate Without Losing Trust?
You communicate it by being upfront about confidence from the very first conversation, Clay said, “so a number moving is not a surprise.”
If a concept involves significant technical uncertainty, the One3 Design team explains which challenges require further investigation.
Clay described working with an innovative client whose project pushed the boundaries of what seemed technically possible. Through discovery, the team identified additional variables and developed a clearer understanding of the underlying problem.
Rather than continuing without direction, they communicated their findings and reconsidered potential solutions. “Do not wait until the end to say, ‘Well, we tried six different things, and we just could not get it to work,'” Clay said.
This reflects broader cost management principles. The U.K. government’s cost estimating guidance says an estimate should present a range of outcomes to show the level of confidence, that the range should narrow as the project matures, and that critical assumptions must be communicated.
For Clay, transparency allows clients to make informed decisions before additional expenses accumulate.
Why Does the Final Number Still Shift?
The biggest reason, Clay said, is that “it takes longer to figure out a complex problem than you anticipated,” and the second is a client choosing to expand the product once they see what the work makes possible.
They may request additional features, expanded capabilities or changes that were not included in the original agreement.
Clay explained that these situations require revisiting the project scope and discussing the financial implications. Even then, he said, a higher number “should not be a surprise,” because the staged process, the requirements document and regular reporting keep the client informed before it arrives.
Ultimately, the challenge behind the question “Why is it so difficult to give someone a single number for developing a new product?” is that development involves decisions that become clearer through research, testing and collaboration.
A reliable budget reflects a defined project, not an idea with unlimited possibilities.
Where Can You Watch Episode 5 of The Design Orchestrator?
Episode 5, “When Do You Actually Get an Accurate Product Development Budget?”, is on YouTube and on podcast platforms under The Design Orchestrator. Watch Episode 5 on YouTube to hear Clay Martin explain budgeting, discovery, design iterations and how One3 Design manages uncertainty with clients.
Frequently Asked Questions
Why is it so difficult to give someone a single number for developing a new product?
Because the number depends on decisions that are not made yet at the start, including the manufacturing process, materials, confirmed requirements and expected volume. One3 Design’s Clay Martin says the estimate becomes reliable after the Discover and Define stages, once the project is scoped and no longer an open concept.
When Does a Product Development Estimate Become Accurate?
Estimates generally become more reliable after the Discover and Define stages, when product requirements, manufacturing methods and project scope are better understood.
Why Do Product Development Costs Change?
Costs can change because of unexpected technical challenges, additional design iterations, material decisions or client-requested changes to project requirements.
Can Product Development Costs Be Estimated Before Design Begins?
Yes. However, early estimates may have greater uncertainty, especially when technical requirements or manufacturing processes remain undefined.
How Does Prototyping Affect Development Costs?
Prototyping helps identify design and performance issues. Additional prototypes or revisions may increase development expenses.
How Can Businesses Avoid Unexpected Development Expenses?
Businesses should establish clear requirements, discuss technical risks early and maintain regular communication with their development teams.
Why Is the Definition Stage Important for Budgeting?
The definition stage establishes the project’s requirements, scope and expected outcomes, allowing engineers to develop more meaningful cost and timeline estimates.
Mike Downer: Hello, everybody, and welcome to The Design Orchestrator. It is a podcast about how products actually get built, from the first idea on a whiteboard to the finished product rolling off the line. This show takes you inside the process that most people never get to see. I’m your host, Mike Downer, and I’m joined once again by Clay Martin, CEO of One Three Design. How are we doing today, Clay?
Clay Martin: Doing great, Mike. It’s always good to see you, brother.
Mike Downer: It’s always fun. We’re making design fun, is what we’re doing.
Clay Martin: Design is always fun. Come on.
Mike Downer: So we’re going to talk about something else fun. We’re going to talk money today.
Clay Martin: I like money, too.
Mike Downer: What we’re going to cover in this one is: when do you actually get an accurate product development budget? I know that is on everybody’s mind who does product development. Money is a strong motivator.
What we’re going to discuss is what has to be true before an estimate stops being a guess and becomes a real number. At what stage in the process does your estimate become genuinely reliable?
Clay Martin: At what stage in the process does our estimate become genuinely reliable? Well, there’s a little bit of a diverse answer here, if you will.
Specifically and generally, it becomes pretty reliable after the define stage, after discover and define. But I would say that is applicable to projects that have more unknowns in them.
On the other side of that is a project that is really well defined, that isn’t maybe as complicated, or if it is complicated, you know all the variables and you have a lot of historical evidence of what has worked in the past. Perhaps it’s a permutation of a mature product. If you have a lot of confident upfront information, the estimate that we provide might be really on point clear through deliver.
But if there are elements yet to be defined, discovered, determined, or unearthed, then after discover and after define, we can go back to what is normally an estimate, or even a rough order-of-magnitude estimate, and communicate to the client that after we spend some time digging in, the needle is going to move this way or that.
Ideally, it gets sharper, and you are able to save money. You have a more accurate assessment of what the finish line looks like. Occasionally, it has to go the other way because that element of discover leads to unearthing things that, once you put them all together and define them, may establish a different light under which the project is being evaluated.
Either way, after define, you should be at a point where you have a much clearer representation of what done looks like. Therefore, the cost and timing get much more dialed in.
Mike Downer: Perfect. That makes sense. So what specifically changes between an early rough estimate and a locked-in budget?
Clay Martin: What specifically changes between an early estimate and a locked-in budget? Usually, that locked-in number reflects actual decisions having been made: manufacturing process, materials, and confirmed requirements.
You have things that might have been theories or unknowns in the early stages of discover that become locked in. A lot of that is discovery with the client. What do you estimate your annual usage to be? What do you think in terms of a five-year progression of sales, if things go as expected? What is the maturation process of your product?
By knowing those sorts of things, you can start applying true knowns. For instance, this is now applicable to the injection-molded plastic process, as opposed to maybe roto molding or blow molding. We are going to take this from a fabricated weldment into a die-cast or sand-cast component, based on the ramp-up in volume.
As the product matures, or as you understand more about what the vision is for the product, you get those assumptions locked in. Therefore, the definition comes in terms of those processes that you can drive cost from and those methods that you can estimate cost on.
Mike Downer: Perfect. So once you get that locked-in budget, how much can that number still move after that point, and why?
Clay Martin: That is a moving target. Ideally, the more diligent you are in defining what done looks like, the less likely that number is to move much.
But that number could move based on the number of needed design iterations. Maybe we estimated in the design stage that building a virtual representation and running through some FEA or CFD should show us what we need to know, and we expect the results to be this, which would then allow us to jump right into build. Maybe that is not the reality, and we find something that sends us back to the drawing board a little bit.
You have to make a design adjustment, run another iteration, or build a 3D-printed additive manufacturing prototype, do a fit-up, or get it in your hands, and it is different than what you expected. So you determine that you need to build another one of these.
Once again, that is communication with the client. You evaluate it. We know what we know. We understand that this may result in further iteration, but most of the time, we have that captured in the proposal.
We are identifying to the client in define and design that, ultimately, as we move forward, this may result in additional work. We will put it in a quote and say anything beyond this will result in an uptick in cost.
Mike Downer: You bet. So is there a point of accuracy you aim for at each stage?
Clay Martin: Well, one hundred percent, of course.
Mike Downer: Obviously.
Clay Martin: Ideally, we try to uncover everything we can. That is a great question because it speaks to the necessity of communicating confidence, or lack thereof, to the client during this process of engagement.
We are very upfront in communicating what you are trying to do. For instance, what you are trying to do is very complicated, and what you are asking for, we are not even sure can be done. So we are telling you now, at these stages, these are the elements we are going to need to know for it to make sense to move forward.
Once again, that is a risk mitigator from a cost and maybe even safety perspective. But you are communicative about the level of confidence at each stage. You are making sure that you are on the same page in terms of both their confidence level and our confidence level, and whether what we are trying to achieve is plausible and possible. When doubt creeps in, we are open and honest about it.
Mike Downer: So now that we have talked about all this, and you have talked all this through with the client, you kind of already have a realistic budget expectation from your customer. What do you do if the real number comes in much higher than the client expected?
Clay Martin: What do we do if the real number comes in higher than the estimate, I guess, or maybe higher than what we have talked about? Well, it should not be a surprise.
Because of the staged approach of the process, nothing is going to be a shock when it is introduced because of everything we have talked about. We have communicated confidence. We have a requirements document that illustrates an agreement on where we are headed and what done looks like. We are communicative during the design process to make everyone aware of the results of evaluations and documented report structure.
So when the real number comes in higher, it is usually an expectation because that real number coming in higher, and this is what really most often happens, is when the client sees the value of the process and the results of our work and the clarity and fidelity that work provides, it gives them this clear image of what their product could be.
Very often, we will have them come back to us and say, “With where we are now and what we have accomplished, we think it would be great if we pushed this a little further or tried maybe a little something else.” That is when we go back and revisit the scope and make sure we understand the ramifications of that.
But if the number is higher, it is usually a situation like that or something caused by discovery. It is not a surprise because we have been very communicative during each stage of the process, and we illustrate what is coming before it bites us.
Mike Downer: So when that does happen, you were talking about being communicative. How do you communicate a growing estimate without losing that client’s trust?
Clay Martin: How do we communicate a growing estimate without losing the client’s trust? I would say to refer back to a comment I made earlier about confidence. It is about being upfront about our confidence level at each stage, starting with the very first conversation. So a number moving is not a surprise.
I have had a few projects recently, one in particular I can think of, where what we are trying to achieve is so revolutionary, if you will, to that particular industry. The client is a very innovative client. They are really pushing the bleeding edge of the envelope. You look at that and say, “This is tough. This is something I do not know is truly achievable in the way that you hope it will be achievable.”
So we spent a lot of time in the discover stage evaluating different hypotheses, understanding where the complexity was, understanding if we were all asking the right questions, and understanding if we really understood the problem. We determined that the problem was a little different than we perceived it to be. New variables came in, and a new line of sight to what might be a solution came into focus.
Communicating where our minds are in terms of that confidence level is probably the most effective way. Be upfront. Do not wait until the end to say, “Well, we tried six different things, and we just could not get it to work.”
If the client is unaware that you were off course and you are burning up budget, and you get to the end and say, “We cannot get there. By the way, you are out of money,” that is a terrible position to be in and a really bad client relationship to establish. Communication is absolutely key.
Mike Downer: Perfect. So maybe you can give us an example of this or where it has happened. What is the biggest reason final numbers still shift even after you have a solid estimate and have done all your due diligence? Maybe you could even give us an example of a time that happened to you.
Clay Martin: Yeah, I think the biggest reason final numbers tend to shift is that, most of the time, it takes longer to figure out a complex problem than you anticipated.
I always go back to the iPhone. I remember the story of Steve Jobs saying, and maybe I have to get permission to use Steve Jobs’ name, I do not know.
Mike Downer: I doubt it.
Clay Martin: He wanted this smooth phone with no visible edges transitioning into the case, without a seam or a line, and everybody told him it could not be done. Well, he was a tenacious guy, and he drove until he figured out how to get it done.
Undoubtedly, there was additional cost in being able to innovate a product at that level. Much of the time, what you are trying to achieve may require additional iterations, and that is usually where additional cost comes from. It is sometimes difficult to predict.
Or, as I mentioned earlier, you find opportunities during the development process to make your product something even more than you imagined it to be. Through that development process, you are willing to take that opportunity to invest in that expansion of your vision of your product.
That is why we say, after define, we are estimating a scoped project, not an open concept. That is when the number actually starts to mean something. So you get really, really definitive as much as possible in that define stage so that you are working toward reality. If you have to return to define to sharpen reality a little bit, you can do it.
But yeah, I think that is a pretty good description of what could generally and potentially cause a project to shift after the get-go.
Mike Downer: That was a perfect answer and a great way to sum this one up for today. I look forward to diving into the next few stages. We have a lot to talk about. The more we talk, the more I look at all these products around me right now, thinking that they had to go through all this, and it is guys like you who did it. So you are a pioneer, and I appreciate it.
Clay Martin: I appreciate you, Mike. Thanks for the talk, man.
Mike Downer: You bet. Anytime. I look forward to our next one, and you have a great afternoon.
Clay Martin: You too. See you.
Mike Downer: All right. Take care.