Yes. An NDA keeps a disclosure private; it does not give you any rights in the invention, and it does nothing if the counterparty independently develops, or already holds, the same idea. Filing a first application before the pilot fixes a priority date that the pilot cannot disturb, however many of the customer's engineers see the system, and it lets you disclose more freely during the pilot, which usually makes the pilot go better. It also changes the negotiation: a customer will happily sign an IP clause that assigns "all inventions arising from the project" when nothing is filed, and will accept a carve-out for your pre-existing, patent-pending technology when something is.

Pilots create three specific risks that an NDA does not cover. The customer's staff may contribute to an improvement and become joint inventors, giving their employer a claim on the resulting patent. The customer may deploy the system in a way that is visible to the public or to other suppliers, which can be a public disclosure. And the customer's standard contract may contain a work-product clause that assigns everything created during the engagement to them. A filed application answers the first and second and gives you a defined thing to exclude in the third. In practice: file a provisional or priority application covering the core mechanism before kick-off, get the NDA signed before any technical detail is shared, and make sure the pilot agreement identifies your background IP by reference to that application. If the pilot has already started without a filing, file now; disclosures under the NDA are not public, so the position is usually still recoverable. See also Who owns IP created in a pilot or joint development project?

By default, whoever invented it, which in a joint project is often both parties jointly, and joint ownership without an agreement is the worst outcome for everyone. Joint development agreements therefore split IP into three categories. Background IP is what each party brings in, and stays with that party; it is normally listed in a schedule and licensed to the other side only for the project. Foreground IP is what the project creates; the agreement decides who owns it, typically the party whose background it improves, or the party that will commercialise it, with the other receiving a licence. Sideground IP, less often defined, is what a party develops during the project period independently of it, and stays with that party. Patents follow inventorship, not funding: paying for the project does not make a customer an inventor, and an engineer who contributed to a claim is an inventor whichever company pays them.

Where the agreement is silent, the default rules bite. In the United States, joint owners of a patent can each make, use and license it without the other's consent or any duty to share revenue (35 U.S.C. 262), so a customer co-owning your core patent could license it to your competitor. In the UK, under section 36 of the Patents Act 1977, a co-owner can work the invention but needs the others' consent to license or assign, which produces deadlock instead. Either way, a joint patent is hard to enforce and hard to sell. The practical rules: file your own applications on your background before the project starts, so it is identifiable; agree in writing who owns foreground and who gets what licence; require both parties' staff to have assignment agreements with their employers; and keep an invention record during the project so inventorship can be established when it comes to filing. Lightbringer's disclosure workflow produces that record as a by-product of drafting.

Yes, if you sign it. Enterprise customers' standard terms frequently contain a clause assigning to the customer all "work product", "deliverables" or "developments" created under the agreement, sometimes including improvements to the supplier's own platform made during the engagement. Read literally, these clauses can transfer to the customer ownership of features you built for everyone, or of a patentable improvement you made while solving their problem, and a signed contract will be enforced as written. Procurement and legal teams include them by default; most will negotiate them, because they were drafted for bespoke consulting, not for buying a product.

The standard fix is a three-part IP clause. The supplier retains all pre-existing IP, its platform and any improvements to it, and grants the customer a licence to use them as part of the service. The customer owns deliverables that are specific to them, such as their data, configurations and custom integrations that have no use elsewhere. And a feedback clause gives the supplier a perpetual, royalty-free licence to use any suggestions the customer makes, without obligation, so that improvements suggested during the relationship stay yours to build and patent. Where the customer insists on owning a genuine joint development, treat it as a joint development agreement with defined background and foreground IP rather than a sales contract. Having filed applications on your core technology before the negotiation makes all of this easier, because "supplier background IP" can then be defined by reference to specific patent applications instead of by argument. This is general information, not advice on a specific contract; have a lawyer review the clause before you sign.

Ownership follows inventorship, and inventorship follows conception, not payment or suggestion. If a customer says it would be great if the product could also do X and your engineers work out how, your engineers are the inventors and, under their assignment agreements, your company owns it. If the customer's engineer works out how, describing the specific technical means that end up in a claim, that engineer is an inventor, or a joint inventor alongside yours, and their employer will usually own their share under the customer's own employment agreements. Naming only your own staff on the application when a customer's engineer contributed to a claim is an inventorship error that can put the patent's validity at risk (see MPEP 2109), so the question has to be answered honestly at filing.

The way to keep ownership clear is contractual and evidential. A feedback clause in the customer agreement grants you a perpetual, royalty-free, irrevocable licence to use any suggestions, ideas or feedback and, better still, an assignment of any IP in them; most customers accept this because they want the improvement built. An invention record kept as the work happens, showing who proposed the problem and who worked out the solution, settles inventorship questions that would otherwise depend on memory two years later. Where a customer's engineer did genuinely co-invent, the options are an assignment from the customer, a cross-licence, or a joint ownership agreement that fixes who may license and enforce. What not to do is leave it undocumented: a joint inventor discovered in due diligence, whose employer has never assigned their interest, is exactly the kind of chain-of-title gap that stalls a financing. See also Who owns IP created in a pilot or joint development project?