The Client with a Strict NDA Whose App Turned Out to Be a Facebook Group

We have a favorite genre of emails. A message arrives with "CONFIDENTIAL" in the subject line and a single sentence in the body: "I have an app idea, but I need to sign an NDA before I tell you anything."
We understand that. People worry about their ideas. And that's fine — that's why we have an NDA built right into our consultation booking. But this story is about a client who took it to an entirely new level.
Triple NDA and Absolute Silence
Mr. Smith (name changed, of course, because — NDA) contacted us in January. He booked a consultation and immediately after confirmation sent us three emails in rapid succession:
- Whether our NDA covers subcontractors and their family members
- If we could sign his own NDA in addition to ours
- Whether the consultation is conducted over an encrypted channel
We answered that our NDA covers our company and its employees. That we'd be happy to review his NDA. And that Google Meet uses end-to-end encryption.
Two days later, his NDA arrived. Sixteen pages. Legal clauses about jurisdiction in the Cayman Islands. A contractual penalty of EUR 500,000 for breach.
We started to suspect this was either a groundbreaking technology or something entirely different.
The Big Reveal
During the consultation, Mr. Smith spent the first fifteen minutes explaining how unique his idea was and how anyone could copy it. We nodded and waited.
Then came the big reveal: "I want to create an app where people with shared interests can connect, share posts, comment, like, and organize meetups."
Pause.
"So... a social network?" I asked carefully.
"No, no, no! This is different! It will only be for people interested in historical model trains."
When the Solution Already Exists
We won't laugh. Community apps for niche groups make sense. There are successful apps for fishermen, gardeners, and coin collectors. But you need to ask a fundamental question: Does this community need its own app, or is there a better solution?
And that's where we had an honest conversation with Mr. Smith.
We went through his requirements one by one:
- Sharing posts with photos and videos — Facebook does this
- Comments and reactions — Facebook does this
- Organizing meetups and events — Facebook Events does this
- Private group for members only — Facebook Groups does this
- Notifications about new posts — Facebook does this
- Works on iOS and Android — Facebook works everywhere
With each point, Mr. Smith lost a little more enthusiasm. But we kept going, because our job isn't to sell the client the most expensive solution — our job is to find the right solution.
- ✗Sixteen-page NDA with exotic jurisdiction
- ✗NDA before sharing any information
- ✗Requiring NDA for family members
- ✗Secrecy around a common concept
- ✗Fear of sharing the idea with developers
- ✓Standard NDA signed before consultation
- ✓Clearly defined scope of confidential information
- ✓Reasonable contract terms and penalties
- ✓Trust between client and vendor
- ✓Open communication about the project
The Math Speaks Clearly
A custom social network — even the simplest one — would cost Mr. Smith tens of thousands per month in a CORE or UNICORN tier. Let's count:
- User profiles and authentication
- News feed with sorting algorithm
- Real-time notifications
- Chat or messaging system
- Content moderation
- Media management (photos, videos)
- Push notifications
- Admin panel
That's at least 4–6 months of development. And then ongoing maintenance, hosting, moderation, and security updates.
Compared to a Facebook group: free. Done in an afternoon. And on top of that — users already have Facebook installed. You don't have to convince anyone to download another app.
When a Custom App Does Make Sense
To be clear — we're not preaching that nobody ever needs a custom community app. There are situations where a Facebook group isn't enough:
- You need monetization — paid content, subscriptions, in-app purchases
- You need specific functionality — 3D model viewer, AR features, hardware integration
- You have thousands of active users and need to scale
- Regulatory requirements — healthcare, finance, sensitive data handling
- You don't want platform dependency — Facebook can change its rules at any time
Mr. Smith had a community of 47 people. Forty-seven. With all due respect — a Facebook group is more than sufficient for that.
How It Ended
Mr. Smith left the consultation a bit disappointed, but he returned to reality fairly quickly. A week later, he wrote to tell us he'd created a Facebook group, added his 47 fellow model train club members, and that it was working great.
And then he added the sentence that pleased us the most: "You saved me a lot of money and time. If you had sold me that app, I probably would have realized after a year that nobody was using it."
Exactly. And that's what we're about.
Establish clear confidentiality rules from day one. A standard NDA within the consultation covers 99% of cases. Instead of sixteen-page contracts, invest your energy in clearly describing what is and is not confidential — and focus on whether your idea has a real market.
Lessons for Everyone Who Wants Their Own App
Before you dive into development, ask yourself three questions:
- Does a ready-made solution exist? Facebook groups, Discord servers, Slack workspaces, Mighty Networks — there are plenty of community platforms out there.
- Do you have enough users? A custom app makes sense from hundreds of active users and up. Below that, it's unnecessarily expensive.
- Do you need something a ready-made solution can't do? If yes, then yes — let's build. If not, save your money.
And that NDA? With sixteen pages and the Cayman Islands? We didn't end up signing it. Our standard NDA was more than enough. Even for a Facebook group about historical model trains.
Have an app idea and want honest feedback? Book a consultation — we'll tell you straight whether it makes sense.


