Where should I move this product to?
The mistake almost everyone makes is aiming at where the segment is today. By the time your revision completes, the ideal spot has moved. Enter the segment's current ideal position and its drift rate, and this aims at where it will actually be.
How long will this R&D project take?
Project length rises with the distance you move the product. Long projects tie up the product and push the revision date past the end of the round, which means it does not sell in its new position at all this year.
What will my product's age be after the revision?
A revision does not reset age to zero — it halves it. That is why repeatedly nudging a High End product keeps it young, and why a Low End product left alone drifts to the old age its buyers actually want.
Where will every segment be in a few rounds?
Segments drift apart over the simulation. A product that serves two segments in round two often serves neither by round six. Project the map forward and plan your product line around where the segments are going.
How R&D and the Perceptual Map Work in Capsim
Every product in Capsim sits at a coordinate on a perceptual map defined by performance and size. Every segment has an ideal spot on that map, and buyers score your product partly on how close it sits to that spot. The complication is that the ideal spot moves every year, and your product does not move with it unless you pay for an R&D project.
Why aiming at today's ideal spot is wrong
An R&D revision takes time. If the project completes in the middle of next year, the segment will have drifted for most of a year by the time your product arrives. Aim at where the segment is today and you land behind it, having spent the money and reset half your product's age for nothing. This is the single most common R&D mistake in the simulation, and it repeats every round because the error is invisible until the Courier arrives.
The trade-off nobody explains
Moving a product a long way takes a long project. A long project pushes the revision date late in the year, or past the end of it, which means the product spends most of the round in its old position. Small, frequent moves usually beat one large correction, and they keep the product's age lower, which High End and Performance buyers reward. A weak survey score is often the first sign a product has drifted — the sales forecast calculator shows how much segment share it is costing you.
What a revision does to age
A revision cuts the product's age roughly in half at the moment it completes, then age accrues again for the rest of the year. It never resets to zero. That matters because each segment wants a different age: High End buyers want products close to new, while Low End buyers actively prefer an older, proven product. A Low End product does not need revising for age at all — leaving it alone moves it toward what its buyers want.
Segment Age Preferences and What They Mean for R&D
| Segment | Ideal age | R&D approach |
|---|---|---|
| High End | Around 0 years | Revise every round. The product must stay near new and on the cutting edge of the map. |
| Performance | Around 1 year | Revise most rounds, tracking performance drift closely. |
| Size | Around 1.5 years | Revise most rounds, tracking size drift. |
| Traditional | Around 2 years | Revise every other round. Frequent revisions push age below what buyers want. |
| Low End | Around 7 years | Barely revise at all. Age is an asset here, and R&D spend is largely wasted. |
Check your own Industry Conditions Report — these are the standard Capstone values and instructors can configure them differently.
The automation conflict
High automation cuts labour cost, but it makes repositioning slower and more expensive. That produces a clean rule: automate the products you do not intend to move, and keep automation moderate on the products you revise every round. Teams that automate a High End product to 9 discover they can no longer keep it near the cutting edge, and lose the segment. The automation payback calculator recommends a level for each segment with that penalty built in.