4 ms·
Hmmmm. It probably depends upon how much money were talking. If the customer is throwing around a couple million dollars of NRE, it's probably worth bolting s
by bsder 10y ago
Hmmmm. It probably depends upon how much money were talking.
If the customer is throwing around a couple million dollars of NRE, it's probably worth bolting something on and pocketing the money. If the customer is only moving a couple hundred thousand, it's probably not.
This seems more like a software-only startup issue. We have hardware and have these hard-nosed discussions all the time--generally about volume.
Customer--"We want X and we want 100,000 units and we're going to put the NRE on this payment schedule."
Us--"No, you're going to put all that NRE up front and it's <2-5 million dollars depending upon change complexity>. And you're going to front the first 10,000 units which is <generally a nice chunk of a million>. After that, we can put you on the royalty schedule. We can't put ourselves in the position of losing the company because your volume never materialized."
Customer--"<choke> <splutter> That's preposterous."
Us--"No. It's the reality of hardware. We know our costs really well."
Side comment: it's always 100,000 units and 100,000 units is generally hardware death--big enough that you have all the volume problems but small enough that your profit sucks.
- cortesoft 10y agoI think the article covers that; they explicitly talk about sometimes choosing to serve the customer who wants something you aren't currently offering.
- ixtli 10y agoThe equivalent definitely exists in a software-only startup with enough users. In practice it's rarely the case that it's _one_ user, but that there are cohorts of users that want a certain thing you don't provide. I still agree with your point, though, that if those cohorts aren't gonna give you enough money you shouldn't let your development process get sidetracked by their desires.
- warfangle 10y agoUnless you're in enterprise software. It's really easy for enterprise companies to get in the trap of making every customer a spacial snowflake, because they need to to get a half mil contract signed. And then the product becomes sorta shapeless, because each customer gets their own product... And you end up a consultancy instead of the platform/SaaS that you originally envisioned.
- calgoo 10y agoAnd then that project half dies because of replacement XY which is sooo much better /s. Now you are stuck on a legacy platform, and if you have great sales people who included this system in the contract worth $10M+ and no replacement exists, you cant get rid off it. So someone has to manage the legacy platform, where all docs where lost and no one has the domain knowledge as everyone has left. Now guess what happens when the company finds out you setup the servers, "Hey, you setup these servers, so you are now responsible for the platform, congratulations!"....
- oz 10y agoNRE = 'Non-recurring engineering', for those as ignorant as I was. https://en.wikipedia.org/wiki/Non-recurring_engineering https://en.wikipedia.org/wiki/Non-recurring_engineering
- bsder 10y agoIt could also be "non-recurring expense". Sometimes things have a "setup charge" that you have to pay once, but then don't have to pay again.
- robbyt 10y agoIn hardware, I know NRE as non reoccurring expense. Manufacturing companies charge setup fees for programming assembly machines, ordering silk screens, tooling, etc.
- bo1024 10y agoIt definitely seems like a software thing because a hidden assumption in the article seems to be: if you build it for one person, you have to offer it to everyone. This makes sense for software where one customer alone will never pay for the investment of building the add-on.
- ozim 10y agoNice today I have learned. I thought you just includ NRE in the price you offer to the customer so it can be amortized by volume. But yeah it makes sense if volume will not be realized and you do not want to make bets on your comapny with someones else customers.