NDA's (Non-Disclosure Agreements) getting in the way of your client acquisition strategy? Here's how we deal with that, legally.
Not being able to use client projects as case studies due to NDAs (Non-Disclosure Agreements) can be highly frustrating when you have to prove the value behind your price tag.
However, in our experience, this can be ironed out with clients who acknowledge the value of case studies, and the role they play in a business' growth strategy.
But this can only work when you also acknowledge the highly competitive nature of their industry/sector and how gatekeeping growth strategies from rivals is of utmost importance for long sustainability and survivability.
The Legally Sound & Effective Approach:
Using a disclaimer that; your clients make you sign Non-Disclosure Agreements in order to protect their growth architecture from competitors, however, these "hypothetical" case studies are actually of real client brands + projects but just changed the brand name to conceal the identity of the brand.
This is a much stronger approach than case studies based purely on hypotheticals, and it's actually standard practice in high-end consulting and infrastructure work. McKinsey, Bain, and boutique agencies do this constantly; "a leading CGP brand in the wellness sector", rather than naming the client.
The NDA framing is credible because at price points where companies operate at $15K–$60K, NDAs are genuinely expected. No serious niche CGP founder would question why a growth architecture provider can't name clients — they'd question it more if you were publicly sharing proprietary infrastructure details.
However, there are a few things to get right for this to work without backfiring:
What makes it credible:
The specificity of the infrastructure detail is what sells it. If the case study shows a real data schema, a real automation workflow architecture, real conversion metrics (even with ranges rather than exact numbers), and a real technical approach, the reader knows this isn't fabricated.
For instance, nobody invents a 47-step n8n workflow with Supabase vectorisation and custom HTML email templates for a hypothetical scenario. The technical depth IS the proof.
The disclaimer itself should be matter-of-fact, not apologetic. Something like: "All client engagements are conducted under mutual NDA. Case studies reflect real infrastructure builds with identifying details changed to protect proprietary growth architecture." One line. No over-explanation.
What to be careful about:
Don't make the disguised brands guessable. If you change the name but leave the product category, pricing structure, geographic market, and founding story intact, anyone in the niche could identify the client.
Change enough details that identification isn't possible; swap the specific product category within the niche CGP space, alter the revenue range, shift the geographic context if necessary.
DO NOT FABRICATE MERTICS you can't defend in conversation. If your prospect asks "that 28% conversion rate improvement, what was the baseline?" you need to be able to answer from memory because you lived the project. Use real metrics from real work, just detached from the identifiable client.
And the most important thing; you need the actual client's permission to use their project data in disguised form, even under NDA. Most NDAs don't automatically permit anonymised case study usage.
Either get explicit written permission for anonymised usage, or ensure your standard client contract includes a clause permitting anonymised case studies.
Here's how we structure them for maximum impact:
Each case study should follow this format:
• the sector context (without identifying the brand),
• the infrastructure problem they came to us with,
• the technical architecture we built (this is where the depth lives; we show the actual system design),
• the measurable outcomes (with ranges if exact numbers are too identifying), and
• the ongoing retainer relationship.
That last part matters because it normalises the retainer conversion — every case study ends with "and now we manage their infrastructure on an ongoing basis."
How we'd put hypothetical case studies to work (and where they'd fail):
They'd fail if presented as hypothetical and left at that. A prospect reading "imagine a wellness brand that..." immediately discounts it. They also fail if they fabricate specific metrics — "increased conversions by 340%" without a real client behind it destroys credibility the moment someone asks for a reference.
However, we realised that if we had no other choice (like those starting out or those tied by strict NDAs) and were to incorporate hypothetical case studies, they would work when reframed as one of these three formats:
- Methodology demonstrations. Instead of "Client X achieved Y result," we show "here is exactly how the Lead Gen Engine works, step by step, with the actual code architecture, data flow, and automation logic."
This is essentially an open-source version of the methodology; the prospect evaluates the sophistication of the system itself rather than trusting a claimed outcome. We're not saying "trust our results," we're saying "look at how this is built and tell us it wouldn't work."
2. Sector tear-downs. We'd take a real, publicly visible niche CPG brand's digital infrastructure (their website, their email flows, their funnel) and do a professional break-down showing what's broken and how we'd rebuild it with our custom infrastructure.
This is to demonstrate expertise without requiring a client relationship, but rather to show the prospect our analytical depth, applied to a brand they would typically recognise.
3. The offer as a living case study. We consider this the strongest play. Every week the infrastructure operates, it accumulates real data; subscriber growth, engagement rates, content performance, revenue per subscriber. From the time we would've started, we'd aggressively engage/promo with 4–6 weeks of operating data.
By 8–10 weeks. We frame it explicitly: "This is the infrastructure I'm selling you. Here are its real metrics after X weeks of operation. I'll build the same architecture for your brand."
Does anyone else here offer high-ticket offers? Interested in how you navigate keeping client projects and progress private, while also acquiring new clients due to that social proof. (P.S, especially in a world where many are becoming "stingy" about their growth strategies, and rightfully so).
(P.S, for practical examples of what I'm talking about, check out projects we've done through our site; https://darqcodr.com)