Marketing context under NDA
In marketing an engineering firm under NDA, demonstrate your approach rather than what you built for a client.
A typical NDA protects the customer’s name, their product, the specs and the production numbers.
It usually doesn’t own your judgment. It covers how you scope a job and what you check first on a site you’ve never seen.
You can discuss which trade-offs you’d make and why.
That judgment is what a technical buyer is trying to size up anyway.
I’m a chemical engineer with an MBA, and I’ve spent the last 15 years marketing to technical buyers. The problem is real. It’s also more solvable than most founders think.
One note before we start: I’m not a lawyer. Read your actual agreements, and when a contract is unclear, ask your attorney or the client. Everything below assumes you stay inside what you signed.
Why does staying quiet cost more than it used to?
Integrators have been stuck on this for a long time. Back in 2008, ASSEMBLY magazine’s John Sprovieri wrote that NDAs prevent integrators from revealing the customer’s identity, the nature of the assembly, design specifications and production rates, and that some are enforced for 3 to 10 years after a project is completed. His line: “Keeping mum also means integrators can’t always crow about their successes.”
Additionally, marketing an engineering firm under NDA changes how buyers shop. The 2026 State of Marketing to Engineers research from TREW Marketing and GlobalSpec, with Elektor, shows engineers rely on research. The same research found that 70% of technical buyers choose a well-known brand when comparing similar solutions.
Put those together. Your buyer forms an opinion before calling anyone, they lean toward names they recognize, and your best evidence is locked in a filing cabinet. When they look you up and find nothing, they don’t conclude you’re discreet. They conclude you’re small, or you’re not there. Then they build the shortlist without you.
What does an NDA usually cover, and what’s still yours?
Agreements vary, so check yours. In general, here’s how it tends to split.
Usually off-limits:
- The customer’s name, and often the fact that you worked with them at all
- What they make, and anything that hints at a product before it launches
- Drawings, specs, cycle times, production rates and pricing
- Site photos, layouts and anything from inside a secure area
Usually still yours:
- General engineering methods. Sprovieri noted that an NDA doesn’t necessarily extend to the mechanisms an integrator creates to assemble the product, and that integrators can reuse their own part-handling methods in any system.
- How you approach a type of problem
- What tends to go wrong on a certain kind of project, and how you catch it early
- Your opinions on standards, technologies and industry practice
- Ranges and the factors that drive them, as opposed to one client’s numbers
Most founders look at the first list and stop. The second list is where your marketing lives.
Why the anonymous case study usually falls flat
The standard advice is to write the case study anyway and swap the client’s name for “a leading manufacturer.” I think that’s the weakest option on the table.
Strip out the name, the product, the specs and the numbers, and you’re left with “we solved a challenging problem for a major client on time and on budget.” Every competitor’s website says that. A senior engineer reads it and learns nothing. Worse, it looks like you’re hiding something, which is the opposite of what you want.
Anonymous case studies can work when you keep the engineering in. Most of them get sanded down until nothing’s left. If you’re going to write one, spend your words on the decisions, not the client.
Four formats that hold up under an NDA
These all work because they show judgment without exposing a customer.
The decision write-up
Pick a call you’ve made more than once. Retrofit or replace. Phase the cutover or take the shutdown. Spec the premium component or the standard one. Walk through how you decide, what would change your mind, and where people usually get it wrong. A buyer facing that exact decision will remember who explained it clearly.
[Joe: add a real example of a decision a client founder explained this way, generalized so nobody can be identified.]
“What I’d check first”
Write the list you carry in your head when you walk into a plant or a control room. A bid package you’ve never seen also matters. This is pure expertise, and no client owns it. It also gives a younger engineer something useful to forward to their boss, with your name on it. This is marketing an engineering firm under NDA.
The lesson from a job that went sideways
Generalize it hard. No industry, no region, no timeline that points anywhere. Keep the mistake and what you’d do differently. Engineers trust people who admit what went wrong more than people who claim nothing ever does.
Ranges and what drives them
Buyers want to know what a project like theirs costs and how long it takes. You can’t share one client’s invoice. You can say what pushes a migration from weeks to months, or which three factors swing the price most. Use ranges from your own experience, and label them as yours.
How do you screen a piece before it goes out?
Run every draft through the same short check before anyone else sees it.
- Could the client recognize themselves? If yes, generalize more or ask them first.
- Could a competitor figure out who it was? Watch for combinations: a region plus an industry plus a project size can identify a client even when no single detail does.
- Does anything touch controlled technology or technical data? If you’re not sure, assume export rules apply and ask before publishing.
- Would you be comfortable if that client’s engineer read it out loud at an industry event? This one catches tone, too.
- Is there an opinion in it? If not, it isn’t worth the risk or the time.
The last test matters as much as the first four. A piece that’s perfectly safe and says nothing doesn’t help you.
Who should write it?
The founder’s thinking has to be in it. That doesn’t mean you write every word. It means the ideas, the opinions and the examples come from you, and whoever drafts it understands the work well enough not to embarrass you in front of peers.
A lot of firms have tried handing this to a generalist agency and gotten back posts that no engineer would take seriously. That’s a real risk, and it can push a founder to give up and go quiet. The fix is a process where your words are the raw material, someone who speaks engineering does the drafting, and nothing goes out until you approve it.
If you want more on what buyers see when they look you up, I covered that in The Essential Red Flags That Undermine Your Executive Profile.
Start with one decision
Don’t start with a content calendar. Start with one decision you’ve explained to a client more than three times. Write down how you make it, where people get it wrong, and what would change your answer. Run it through the five checks. That’s your first piece, and it’s safer than almost anything on your website now.
If you’d like help turning what’s locked inside your projects into something your market can see, that’s the work I do with founder-CEOs of industrial and engineering firms. Book a 45-minute fit call, or start with the diagnostic to see how your market sees you today.
Sources
- John Sprovieri, “Loose Lips Sink Assembly Systems,” ASSEMBLY magazine, May 16, 2008. Long-standing context, not current data.
- TREW Marketing, GlobalSpec and Elektor, 2026 State of Marketing to Engineers; summary also at eeNews Europe.