How do I protect my idea when talking to potential co-founders?

Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.

The question: "I'm about to start co-founder conversations and I'm nervous about sharing details. Should I ask people to sign an NDA before serious talks? What actually protects me?"

The answer.

The uncomfortable consensus first: asking a prospective co-founder to sign an NDA before hearing the idea is a known anti-signal in startup circles — experienced builders decline on principle, not because they plan to steal, but because they hear pitches constantly and can't carry a portfolio of overlapping legal obligations for ideas they mostly won't pursue. Investors are the same, but stronger.

Why this is less risky than it feels:

1. Ideas are abundant; yours is probably being attempted. In AI apps especially, whatever you're building, several people are building adjacently right now. Secrecy doesn't change that; speed and depth do.
2. The theft scenario requires a rare person: someone with your domain insight, your motivation, free capacity, and low integrity, who hears one conversation and outruns you in your own domain. Possible; genuinely uncommon.
3. What's actually scarce is everything the conversation doesn't transfer: your customer relationships, validated pricing, proprietary data, and accumulated judgment about what doesn't work.

What deserves real protection, and how:

• Proprietary data and customer lists — don't share in early talks; described at the category level ("2 years of labeled claims data") they impress just as much.
• Code and prompts — walkthrough on a call, not repo access, until a trial agreement exists.
• Trial projects — this is where paper starts. A two-week trial should have a one-page agreement: work product belongs to the venture, confidentiality on materials shared, no solicitation of your users. Reasonable people sign this readily because it's scoped to actual collaboration.
• The partnership itself — IP assignment and founders' terms the moment you commit (see the four-conversations thread).

So: gate documents, not conversations. Talk freely about the problem and the shape of the solution; share the crown jewels only as commitment ratchets.

What's the piece of your project you'd genuinely be hurt by leaking? Name the category (not the secret) and we'll suggest the right gate for it.

AXIS Editorial

Follow-up from maker intake: "Where do NDAs actually make sense, then? This platform publishes a standard NDA at /legal/nda."

Right distinction: NDAs are for diligence, not introductions. Ours exists for auction bidder rooms — a buyer inspecting your financials, code, and customer data has real, specific confidential material in hand, which is exactly what NDAs are built for. Same logic applies to your co-founder search: no NDA to hear the pitch, a scoped confidentiality clause inside the trial-project agreement, full mutual confidentiality inside the founders' agreement. The paper follows the access level.

Jonathan (AXIS Launch)

The strongest protection nobody lists as protection: being publicly, datably first. A listed app with dated screenshots, a build log in Show & Tell, and verified early revenue is an established fact that a copycat has to explain away. Secrecy protects an idea for weeks; a public track record protects a business for years. It's one of the quieter arguments for listing before you feel ready — permanence is provenance.

AXIS Editorial

Follow-up from maker intake: "A prospect I talked to twice just launched something similar. Did I get robbed, and is there anything to do?"

Painful, and — hard truth — usually not what it looks like. Parallel invention in AI apps is the norm; two conversations rarely transfer anything a competent builder couldn't reach alone, and timelines usually show they were already building. Unless they took materials (code, data, docs — where you may have actual recourse, especially with any signed trial paperwork), the productive response is competitive, not legal: you have the domain depth they lack, so out-execute where depth matters. Document the timeline for your own records either way.

AXIS Editorial

Follow-up from maker intake: "What about co-founder matching platforms — is sharing details in their chat different from sharing over coffee?"

Legally, essentially no — platform chats create a record (mildly useful for timeline evidence) but no confidentiality obligation unless the platform's terms say so, and they almost never do. Behave the same as anywhere: problem and approach freely, documents and data behind commitment gates. One platform-specific habit worth having: keep the substantive record in email once talks get serious, so your trail doesn't live inside an app you might stop using.