Most attorneys will listen for 15-30 minutes in a free phone meeting, enough to tell you in general terms how likely you will need their expertise; that is, how much hot water you are getting yourself into. Your braintrust (incubator, mentors, advisers, board) would at least have known about that; that is basic business knowledge. Either communications has broken down badly between your braintrust and you/your team, or I'm missing critical pieces of the picture.

Your public persona is a resource to be husbanded and crafted as carefully as your codebase and/or finances. If you plan on open sourcing your code, exiting the entire sector you are operating in and never intending to come back, then there isn't much Big Name can do to you even if they felt like it, as long as your wording was careful. Go ahead in that case, and burn down that persona for that space. But never is a long, long time. And this industry is still really, really small when you look at those you want to work with in a specialty.

If you intend to continue in your specialty, then I would take some time off, decompress, and figure out what is really important to yourself. The fact that this style of arguably unethical behavior is abundant and a regular feature of the corporate landscape is already out there now, via this thread and meta-discussions reverberating out there; while it can be emotionally satisfying to divulge details, make no mistake, there will always be a cost attached. Just be certain you are willing to pay that cost.

If you have any direct competitors in your space, and your space is very small, you can mention to them that Big Name is fishing for both technical and market intelligence details by posing as potential acquirers, and to be careful what is said around them. You don't need to mention your gaffe. If the space is small enough, then that will have the effect of freezing out Big Name on any future fishing expeditions. That is likely to have a bigger, more focused effect that has direct beneficial bearing upon your activities than trying to generally name and shame them out in the open.

Thanks, so we feel based upon that meeting and all the subsequent large companies (Fortune 50 to 500) who then reached out after we have created something extremely special.

Basically it's BlueTooth/BlueTooth Audio on Steroids via the web. Sync 100s to 1000s of IP devices together via a URL to play/control audio, video & or any media in unison on all devices.

Tons of software & hardware innovation will happen in this space, we've already created a few apps using our sync technology.

We just need the right people... their networks and money behind us! We have yet to been to accomplish such and we have shouted and waved our hands telling this story to those who can help, but it falls on deaf ears.

Once and if we open source this tech, we think doing such and then the community further developing will have a big impact on any company that currently uses BlueTooth and or has their own syncing standard.

ALL I WANT TO DO IS INNOVATE AND BE FAIRLY COMPENSATED FOR IT. I feel I have a knack for it based upon my history and all noted here.

If you go the open source route, then you will likely derive revenue from consulting and support activities. Modifying the open source code for specific requirements and applications, fixing bugs for paying customers, that sort of task.

If you are more into the tech than the business angles, then you could keep it closed source, create various platforms around it, and license the platforms. The F50-500 companies have already told you their likely use cases, even big wig himself probably revealed what they want to use it for. Instead of packaging the technology unto itself, create the interface to the use case, then license that integration package as a whole unit.

If they want to sync under a WebSphere stack, hold your nose if you aren't into the enterprisey stuff, dive into J2EE, build out as complete an integration to your tech as you can, then license that entire solution. You could do an end-run around big wig's team by making it feasible to get to a solution faster than his team could by themselves, since you only have to create the integration, and they have to build and refine the tech from the ground up and then do the integration. By the time they finish (if they finish at all), you are onto the next use case, and the next integration.

If you aren't relying upon this tech to put food on the table today, then you have nothing to lose by doing much of the integration work for your customers, and bridging the gap in the business case to adopt your tech much closer to reality for the business decision makers.

Thanks, but I am not the logic coder of my team. I'm the designer & design coder only.

We could use some more dev/manpower. Everything is written in the latest javascript frameworks like Web Audio API, Node.js and other similar frameworks.

If interested or know anyone who is interested in working on what we feel is game changing, we'd love to chat.

I am not a lawyer, but sounds like you don't have much to loose. It's your calculation to make, but you are probably in a position where calling them out publicly could bring you more benefits than harm (when that NDA expires, obviously), in term of visibility and respect.

The net for society of doing that is most likely positive as you are forcing them and others to reconsider their behaviors and warning other entrepreneurs of this behavior.

There is a risk they would try to sue your startup out of existence (ie. even if they don't have cause they can attempt to drown you in legal costs), but this would bring even greater attention to the matter.