And these guys are already experienced in writing this software, know the traps and pitfalls and how they would design it if they got to do it all over again. It's not unrealistic as a startup to not have positive cashflow for the first 2 years.
That's not unreasonable.
But it would be a solid two years, not a year for example.
You also have to be careful with the old "this is how I'd do it if I started again" trap.
If can potentially make you so focused on "doing it right", that you forgot that you may have to swallow your pride and actually shipping something that works but is not "done right yet".
Sometimes "doing it right" takes so damn long, you go out of business before you can ship.
Or you make the classic mistake of having spent so long "doing it right", that you then panic when you finally realise you have to "ship or die", and by then it's too late because the stuff you should have had in place through good planing, is not there, and you ship crap in the ensuing panic. The result is of course death.
So it's not just a matter of knowing what to avoid and what not to avoid in code and system design etc, it's also planning the thing so you can have realistic deliverable objectives. Most developers are quite poor at this.
For a new EDA tool from scratch, there is quite a bit of competition out there at the low end, so you'd have to have something at least as comparable before people decide to give your tool a try. A tough gig.
If I had Nick's millions I'd simply buy an existing tool which can generate income from day one.
Dave.