What it means
The activity itself covers research, design, prototyping, testing and the launch work that gets a product in front of buyers. Finance cares because that spending happens months or years before any related revenue arrives, so it depresses profit now in exchange for an uncertain payoff later.
Businesses that stop developing products eventually watch their margins erode as existing lines age and competitors catch up. The accounting treatment splits the spend into two halves.
Pure research is expensed as it happens, while development costs can sometimes be capitalised as an intangible asset once the product is technically feasible and management intends to complete and sell it. That split matters because capitalising moves cost off this year's profit and spreads it across future years through amortisation.
In practice most teams manage product development through a stage gate process, where a project must clear a checkpoint before it gets the next tranche of budget. The financial discipline is simple: each gate asks whether the remaining spend is still justified by the expected return, treating everything already spent as a sunk cost that cannot be recovered.
The main measures are development cost, time to market and the return the finished product generates. A useful habit is to compare the total cost of a project against the gross profit it produces in its first two or three years, because a product that takes four years to repay its build cost may already be obsolete.
The most common financial error is judging a development project only on its optimistic case. Sensible finance teams model a downside where volumes come in at half the forecast, then ask whether the business could still live with the outcome.
In practice
Real-world examples.
Example
A kitchen appliance brand spends nine months and $850,000 developing a compact blender. Finance tracks the spend against the gate budget each month and flags a $90,000 overrun on tooling early enough for the team to simplify the housing design.
Example
A B2B software firm capitalises $400,000 of development costs once its new reporting module reaches technical feasibility, then amortises it over three years. The chief financial officer explains to investors that this is why the cash outflow is far larger than the expense shown in the profit and loss account.
Example
A snack company kills a plant based bar at its second stage gate after taste testing goes badly, writing off $120,000 already spent. The board treats that write off as cheap information compared with the $1,500,000 a full launch would have cost.
Think of it
“Product development is creating new things to sell to the customers you already have.
Formula
Calculation
Development return on investment = (gross profit generated by the product - development cost) / development cost
A software company puts five people on a new module for eight months at a fully loaded cost of $15,000 per person per month. Development cost = 5 x 8 x $15,000 = $600,000.
The module goes on to generate $2,400,000 of revenue across its first three years at a gross margin of 45%, which is $2,400,000 x 0.45 = $1,080,000 of gross profit. Development return on investment = ($1,080,000 - $600,000) / $600,000 = $480,000 / $600,000 = 0.80, or 80%. With gross profit averaging $1,080,000 / 3 = $360,000 a year, the build cost is repaid in roughly $600,000 / $360,000 = 1.7 years.Case study
Seen in the real world.
The following is an illustrative, fictional scenario. Halberd Instruments, an invented maker of laboratory sensors, had four development projects running at once and a development budget of $2,000,000 a year. Nobody could say which of the four was closest to launch, because progress was reported in engineering language rather than money.
The fictional finance director introduced a simple quarterly gate review in which each project reported spend to date, remaining spend to launch and a three year gross profit forecast. Two projects cleared easily, one was cut after it emerged that reaching launch would cost another $700,000 against a forecast of $500,000 in gross profit, and the fourth was reshaped into a cheaper accessory.
Within eighteen months Halberd was spending the same $2,000,000 but launching three products a year instead of one. In this illustrative case the gain came from stopping weak projects sooner rather than from any change in engineering skill.
Watch out
Common mistakes.
- Continuing a weak project because a large sum has already been spent, when past spending is sunk and only the remaining cost and expected return should drive the decision.
- Counting only external costs such as prototypes and tooling while ignoring the salaries of the internal team, which are usually the largest part of the bill.
- Assuming all development spending can be capitalised, when the rules only allow it once specific technical and commercial conditions are met.
Questions
People also ask.
Is product development the same as research and development?
Development is the later, more concrete half of the pair, and only that half can potentially be capitalised, whereas pure research is always expensed.
How long should a new product take to repay its development cost?
There is no universal answer, though many businesses look for repayment within two to three years so the product still has commercial life left after it breaks even.
Should development spending be cut when profits fall?
Cutting it flatters this year's profit and quietly damages the next three, so most boards trim the weakest projects rather than the whole budget.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%