Non-recurring engineering is work a customer pays for once to design, build, adapt or qualify something specific to them. It is common at the hardware and deep tech frontier, where the first deployments require bespoke engineering before any standard product exists. NRE is genuine revenue and genuine validation (someone paid real money), but it has 2 properties that change how it should be read: it does not repeat by itself, and it often consumes the scarce engineering capacity that would otherwise build the scalable product.
In diligence, NRE is separated from recurring revenue and rarely earns the same multiple. The questions that matter: does each NRE engagement move the company toward a repeatable offering, or does it just pay this quarter’s bills; does the work productize (the bespoke build becomes a reusable module) or does every customer need a fresh from-scratch effort; and critically, who owns the IP created during the NRE. A contract that funds development but assigns the resulting IP to the customer can leave the company poorer in the only asset that matters.
The strategic read is whether NRE is a ladder or a treadmill. Used well, early NRE is customer-funded R&D that de-risks the roadmap and seeds the first product, and the company deliberately reuses what it builds. Used badly, it becomes high-touch consulting with a deep tech logo, growing headcount linearly with revenue and never reaching a scalable product. A credible plan states how much NRE there is, what fraction is productizing, and when the recurring product revenue is expected to overtake it.