[johnmark1845]

Before the meeting, give some thought on how your potential employer (in this case healthcare software business owner) would perceive Cost Benefit Analysis when he hires you. He is not just looking to solve problems with the code and to port it to another more developer friendly ecosystem (although this sure will help in the long run), but what benefit / overall value he gets. You sure gotta add more value to the table. Try to analyze how much can he sustain / afford (in terms of time) to port the code to another developer friendly ecosystem. Or is his main priority is to add more features to the software product (If this is the case)? Because porting the code to another framework / language is more of an expense, while on the other hand adding more features / enhancing his product is more sort of a value addition. So, give some thoughts on this, try to figure out his main priorities and discuss with him in meeting discuss how you can bring more value to the business.

[mxmpawn]

Thanks for your opinion. I was thinking about giving all modules a priority based on alternative income sources the module could provide(the app for appointments for example) and also considering how relevant is the module in the system.

This way I could change the "refactor this system in 1 year and then we might see the benefits" to "pick several modules, refactor them and add some features/apps taking advantage of it".