Activity-based costing, almost always shortened to ABC, set out to fix a problem that traditional cost systems had quietly tolerated for decades: overhead was being smeared across products in proportion to labour hours or machine hours, regardless of what actually caused it. The result was costing that looked precise and was systematically wrong. High-volume standard products were made to subsidise low-volume, fiddly, complex ones, and nobody could see it. ABC's answer was to trace overhead the way it is genuinely consumed, through the activities a business performs, and from those activities to the products and customers that demand them.
The method is Anglo-American by origin, born at Harvard Business School in the late 1980s, and it changed the language of management accounting. Words now taken for granted, cost driver, activity cost pool, cost of complexity, entered the vocabulary through ABC. This profile traces where it came from, how the two-stage mechanism actually works, and the well-documented weaknesses that, in time, motivated its own successor, time-driven activity-based costing.
Ten minutes, fourteen questions, the full result on screen, no email required. If you already trust your margin by customer, you do not need it.
Activity-based costing
Quick answer. Activity-based costing, almost always shortened to ABC, set out to fix a problem that traditional cost systems had quietly tolerated for decades: overhead was being smeared across products in proportion to labour hours or machine hours, regardless of what actually caused it.
Activity-based costing (ABC) is a method that assigns overhead to products and customers by first tracing resource costs to the activities that consume them, then tracing activity costs to the products and customers that demand those activities, using cost drivers. It was developed by Robert S. Kaplan and Robin Cooper at Harvard Business School and became prominent from 1988. By replacing crude volume-based allocation with activity-based tracing, it reveals the true cost of complexity, of low-volume products and of demanding customers, information that traditional systems hide. Its strength is far greater accuracy in stable, moderately complex settings; its recognised weaknesses are the cost and effort of collecting and updating the data, the subjectivity of time estimates, and a tendency to assume full capacity, which overstates costs and conceals unused capacity. Those weaknesses are precisely what time-driven activity-based costing was built to address. ---
Activity-based costing was developed by Robert S. Kaplan and Robin Cooper at Harvard Business School, and became prominent from 1988. The foundational article, Cooper and Kaplan's "Measure Costs Right: Make the Right Decisions", appeared in the Harvard Business Review in its September to October 1988 issue and laid out the core argument: that conventional cost systems distorted product costs and that a better assignment of overhead, driven by activities, would change the decisions managers made about pricing, product mix and customers. In parallel, Cooper published his influential series, "The Rise of Activity-Based Costing", in the Journal of Cost Management across 1988 and 1989, which set out the mechanics in detail.
The two authors then consolidated a decade of practice and refinement in their book Cost and Effect: Using Integrated Cost Systems to Drive Profitability and Performance (Harvard Business School Press, 1998), which remains the standard reference. The method did not emerge from a vacuum. The Consortium for Advanced Management-International (CAM-I), a body that brought together manufacturers, consultants and academics, had played a formative role in advanced cost-management thinking through the 1970s and 1980s, a parallel network to the Harvard work. Some accounts also trace earlier conceptual roots to George Staubus and his 1971 book Activity Costing and Input-Output Accounting, though this is a contested, secondary lineage rather than the direct origin: ABC as a named, codified method is the Kaplan and Cooper achievement of the late 1980s.
The defining idea of ABC is two-stage allocation. Costs flow from resources, to activities, to cost objects (the products, services or customers you want to cost). The crude single step of traditional costing, resources straight to products via one volume measure, is replaced by a path that follows how cost is really caused.
Map what the business actually does that consumes resources: setting up machines, handling orders, inspecting batches, processing invoices, serving particular customers. Each becomes an activity with its own cost pool.
Assign the cost of resources, salaries, equipment, energy, space, to the activities that consume them. Each activity now carries a pool of cost.
A cost driver is the factor that causes an activity's cost to rise and fall, and so the basis on which its cost is shared out. Cooper distinguished three types of driver: transaction drivers, which simply count how often an activity occurs (number of setups, number of orders); duration drivers, which measure how long the activity takes (setup hours, inspection time), used when occurrences vary in length; and intensity drivers, which charge the actual resources used on a specific occasion, the most accurate and the most expensive to operate.
Divide each activity cost pool by the total quantity of its cost driver. An order-handling cost pool of, say, EUR 200,000 spread over 8,000 orders gives a rate of EUR 25 per order. This rate is the price, in overhead terms, of one unit of the activity.
Multiply each cost-driver rate by the quantity of the driver that each product or customer consumes, and sum across all activities. A product that triggers many setups, inspections and special orders accumulates a large overhead charge; a simple high-volume one accumulates little. The cost finally reflects the demands each object places on the business.
The pay-off is visibility. Because cost now follows activity rather than volume, ABC surfaces the cost of complexity that volume-based systems average away: the true cost of a short production run, a non-standard variant, or a customer who places many small orders with special delivery terms.
Take an illustrative business we will call CaP Components (the figures are illustrative, used only to show the mechanics). It has identified four activities, each with a cost pool and a cost driver. The first stage has already traced resource costs into these pools.
| Activity | Cost pool (illustrative) | Cost driver | Driver quantity | Cost-driver rate |
|---|---|---|---|---|
| Machine setups | EUR 180,000 | number of setups | 1,200 setups | EUR 150.00 per setup |
| Order handling | EUR 200,000 | number of orders | 8,000 orders | EUR 25.00 per order |
| Quality inspection | EUR 96,000 | inspection hours | 3,200 hours | EUR 30.00 per hour |
| Customer service | EUR 144,000 | number of support calls | 4,800 calls | EUR 30.00 per call |
Now trace these to two illustrative products. Product Standard is a high-volume line; product Bespoke is a low-volume, complex one. Suppose, over the period, the two products consume the drivers as follows.
| Driver consumed | Product Standard | Product Bespoke |
|---|---|---|
| Setups | 40 | 200 |
| Orders | 2,000 | 600 |
| Inspection hours | 200 | 900 |
| Support calls | 300 | 1,500 |
| Overhead assigned | EUR 71,000 | EUR 102,000 |
Product Standard's overhead is (40 x 150) + (2,000 x 25) + (200 x 30) + (300 x 30) = 6,000 + 50,000 + 6,000 + 9,000 = EUR 71,000. Product Bespoke's is (200 x 150) + (600 x 25) + (900 x 30) + (1,500 x 30) = 30,000 + 15,000 + 27,000 + 45,000 = EUR 102,000. A traditional system spreading the same EUR 620,000 of overhead by production volume would have loaded almost all of it onto Standard and almost none onto Bespoke. ABC shows the opposite: the low-volume, demanding product is the heavier consumer of the activities that actually drive overhead. That reversal is the whole point of the method.
The headline strength is accuracy. Against the simple volume-based allocation it replaced, ABC produces product and customer costs that are far closer to economic reality, because cost follows the activities that cause it rather than a single, convenient measure. In businesses with high overhead and a genuine diversity of products or customers, that difference is not cosmetic; it routinely overturns assumptions about which lines and which accounts make money.
Its second strength is visibility into complexity. ABC makes the cost of low-volume products, of proliferating variants, and of demanding customers explicit, where traditional systems average it into invisibility. This is the information that supports better pricing, rationalising a bloated product range, and managing the customers who quietly consume more service than they pay for. In stable, moderately complex manufacturing and service settings, it remains a strong and well-understood tool for product and customer profitability.
The weaknesses of ABC are unusually well documented, not least because they are what its own creators later set out to fix. The first is cost and effort. Building and feeding an ABC model means collecting a great deal of data, classically through employee time surveys in which staff estimate how they split their time across activities. That is slow, intrusive and expensive, and it has to be repeated to keep the model current.
The second is subjectivity. Those time estimates are judgements, not measurements, and they are hard to validate. People round, anchor and report tidy percentages that sum suspiciously to a hundred. The third is that models go stale and are costly to update: as products, processes and customers change, the surveys and allocations drift out of date, yet refreshing them is exactly the laborious exercise nobody wants to repeat. ABC also scales poorly, because adding activities multiplies the cost pools, drivers and survey questions, so a model rich enough to be realistic becomes too complex to maintain.
Finally, and more technically, conventional ABC tends to assume that resources run at close to full capacity. Because cost-driver rates are usually calculated by dividing a cost pool by the actual quantity of the driver, any idle or unused capacity is silently rolled into the rates, which overstates the cost of each transaction and hides the unused capacity that managers most need to see. Taken together, these limitations, expense, subjectivity, staleness, poor scalability and the capacity blind spot, are exactly the problems that time-driven activity-based costing was designed to solve.
ABC earns its place in manufacturing and service businesses that carry high overhead and a real diversity of products or customers, the conditions under which volume-based allocation does the most damage and activity-based tracing reveals the most. It is at its best in settings that are stable enough that a model, once built, stays valid for a reasonable period, and moderately rather than overwhelmingly complex, so that the activity structure can be maintained without collapsing under its own weight.
Geographically and culturally, ABC is the costing method of the Anglo-American and consulting world: the dominant overhead-allocation framework taught in English-language accounting curricula and deployed by management consultancies internationally. Where the central question is customer or channel profitability at large transaction volumes, or where a model has to stay live and cheap to maintain, the method of choice today is usually its successor, time-driven activity-based costing, which keeps ABC's activity logic while removing most of its operating cost.
Activity-based costing is a way of working out what products and customers really cost by following overhead through the activities a business performs. Instead of spreading overhead across products by a single measure such as labour hours, it traces resource costs to activities like setups, order handling and inspections, and then traces those activity costs to whichever products and customers actually demand them. The effect is to reveal the true cost of complexity that simpler systems hide.
Activity-based costing was developed by Robert S. Kaplan and Robin Cooper at Harvard Business School and became prominent from 1988, through Cooper and Kaplan's Harvard Business Review article "Measure Costs Right: Make the Right Decisions" and Cooper's "The Rise of Activity-Based Costing" series. They later consolidated the method in their 1998 book Cost and Effect. Some accounts trace earlier conceptual roots to George Staubus's 1971 work, but ABC as a named, codified method is the Kaplan and Cooper achievement of the late 1980s.
A cost driver is the factor that causes an activity's cost to rise or fall, and therefore the basis on which the activity's cost is shared among products and customers. Robin Cooper distinguished three kinds: transaction drivers, which count how often an activity happens; duration drivers, which measure how long it takes; and intensity drivers, which charge the actual resources used on a particular occasion. The choice of driver trades accuracy against the cost of measurement.
The most cited reasons are that ABC is expensive and slow to build and maintain, relies on subjective employee time estimates that are hard to validate, goes out of date quickly, scales badly as activities multiply, and tends to assume full capacity in a way that overstates costs and hides unused capacity. These practical frustrations led Kaplan, with Steven Anderson, to develop time-driven activity-based costing as a simpler, cheaper and more maintainable alternative.
Classic ABC builds a cost pool and a cost driver for every activity and feeds them with time surveys, which makes it accurate but heavy to run. Time-driven activity-based costing replaces that with just two parameters per resource group, a capacity cost rate and time equations, which makes it faster to build, cheaper to maintain, easier to scale and able to surface unused capacity directly. TDABC keeps the activity logic of ABC while removing most of its operating cost. See the full comparison at /tdabc-vs-abc/.
Wondering which products and customers actually make you money? Start with a Profit Check.
Start a Profit CheckExplore the Profitability LabProof
A distributor in New Zealand. €1.335M of cost-to-serve made visible, then halved, and 830 loss-making customers brought down to 295.
Read the case study →Who you would be talking to
Miguel Guimarães, Founding Partner
Cost and profitability practitioner for 25+ years. Presented the Damco cost-to-serve case at Managing for Profit (Amsterdam RAI, December 2009), on the same programme as Robert S. Kaplan.
Call +351 910 313 731
Workshops
One working profitability model, built from real data, that you take home at the end.
Reserve a seat
Reviewed by
Miguel Guimarães
Founding Partner, Cost and Profitability Consulting
More than 150 Time-Driven ABC engagements across 11 sectors since 2010, working within the Kaplan and Anderson framework.
About the author →Published Updated
Done. There is nothing here to refuse. This site retired advertising on 27 August 2026, and no advertising or tracking tag runs on it for anyone. Your remaining choices, session recording and audience measurement, are under “Cookie settings” at the foot of any page.
We are asking again. Your last answer is more than 12 months old, so it has been cleared. Nothing is switched on until you answer.
This notice has changed. Your previous answer was given to different wording, so it has been cleared and we are asking again. Nothing is switched on until you answer.
Say yes and we learn which pages help. Say no and nothing on this site changes.
Session recording. Microsoft Clarity records how this page is used - mouse movement, clicks and scrolling - so we can improve it. Form fields are always hidden from the recording.
Audience measurement. Google Analytics 4 counts your visit and the path you take through the site, so we can see which pages are useful. It stores two cookies of our own domain, _ga and _ga_L5HNZN655T, holding a randomly generated identifier for your browser - so these statistics are not anonymous. Nothing is loaded until you say yes.