Ok, I'll give you a pass on the small team though I would note you had replied to multiple other posts that came after mine. On the benefit of the doubt though, it's reasonable that you may have simply missed it.

Fixing MTOW and empty weights are a start yes, but as I said these are very simple and quick edits. What about missing sounds, ground vehicle and jetway misalignments, fuel amount (changing the actual tanks is at least slightly more complicated since you rely on the obviously defective asobo 748 code and nobody is holding their breath that Asobo is going to fix it on their own, but you could change their capacities relatively easily I think)...

If you want to use Asobo's code as a base, I personally consider that acceptable and I would have been content with a plane produced to approximately the same standard as the base Asobo crafts (Please note that all the Asobo craft have pretty beautiful exterior and cockpit modelling, and $30 is the price tag for *5* such aircraft from them. A smaller team would potentially need to charge a little higher of course but... 5x higher? And you are using their systems code anyway). I cannot understand your reluctance to invest even what I estimate to be a couple of weeks into at least doing some customization on it though. Making it say 777 on the FMS and fixing the EICAS should not take an experienced developer too long.

Honestly, if you wanted more understanding it might've be easier if you could just hold your hand up and say "Look, sorry guys we don't have the team members and knowledge of the MSFS SDK to get this done right now." My first reaction to the status of the addon was 'Ok, this isn't up to a usable standard for me, but they'll probably fix and update it in a few days'. Then I saw you going around on the forums and Facebook telling everyone that this is a 100% release and you have no intention of changing or fixing any of the Asobo code.

Is it the case that you simply don't have a team member able to do that level of work currently?