Engraved alchemical cover artwork for “Big Companies Copying Startup Ideas: The Runlayer vs Rippling Warning”

Big Companies Copying Startup Ideas: The Runlayer vs Rippling Warning

The story that made me wince

TechCrunch reported this week that Runlayer, a small startup building an MCP gateway, is accusing Rippling — a company worth billions — of taking its product idea after what was supposed to be a partnership evaluation. Runlayer says it shared its approach, its pitch, its thinking, in good faith. Then Rippling allegedly built something remarkably similar and moved on without them.

I don't know all the facts of this particular case, and neither do you, and neither does anyone outside the two legal teams currently drafting letters to each other. But the pattern is one I've seen play out for decades, and it's worth talking about honestly rather than just nodding along at the headline.

This isn't new, and it isn't going away

Big companies evaluate small companies constantly. Sometimes it's a genuine acquisition interest. Sometimes it's a partnership that might actually happen. And sometimes — more often than founders want to admit — it's market research wearing a business development badge. The bigger company wants to know what's out there, what the clever approach is, and whether it's worth building in-house instead of buying.

I've built software commercially since 1986 and run tools in a genuinely competitive space with the Masher suite — RSSMasher, MarketMasher, BookMasher, and the rest. Content automation and AI tooling is exactly the kind of category where a well-resourced competitor could watch what smaller players are doing and simply build it themselves, faster, with more marketing spend behind it. It's not paranoia to think about this. It's just how markets with big and small players actually work.

What you can control

You can't stop a company deciding to build something similar to yours. Ideas alone aren't defensible — the market is littered with better-executed copies of good ideas, and always has been. But you can control how much of your actual mechanism, your specific approach, your unreleased roadmap, you hand over before there's a real signed agreement in place.

A few things I've learned the hard way over the years:

NDAs are a filter, not a shield. They won't stop a determined bad actor, but they will filter out the casual ones, and they give you something in writing if things do go wrong. Always have one before a serious conversation, even an informal one.

Show outcomes, not mechanisms. In an early conversation, a potential partner needs to see that your thing works and roughly why it's valuable. They don't need your architecture diagram, your exact prompt engineering, or your unreleased feature list. Save the detail for when there's a term sheet or a signed deal, not a "let's explore this" email.

Watch the tempo of the conversation. Genuine partnership talks tend to move with legal and commercial structure attached fairly early — contracts, terms, exclusivity discussions. If a big company wants long calls, deep technical demos, and roadmap detail but keeps the actual deal terms vague or endlessly delayed, that's worth noticing.

Build the moat that isn't the idea. Your distribution, your customer relationships, your data, your speed of iteration, your brand — these are much harder to copy than a feature set. If your entire value is "we thought of this first," you're exposed regardless of what agreements you sign.

Why founders keep taking the risk anyway

Here's the uncomfortable truth: most founders in Runlayer's position would take the meeting again. A conversation with a company like Rippling is a real chance at an exit, a partnership, or serious distribution — and turning that down because it might go badly is its own kind of failure. You have to weigh genuine opportunity against genuine risk, and sometimes you'll get burned even doing everything right.

What I'd say to anyone building in a crowded space right now is: assume every conversation with a bigger player could go either way, and structure what you share accordingly. Protect the specific, not the general. Get things in writing. And build something that's valuable beyond the idea itself, because ideas travel fast and copies always show up eventually.

Runlayer may or may not win this fight. But the lesson for the rest of us doesn't depend on the verdict — pitch smart, share carefully, and never mistake enthusiasm in a meeting room for a deal.

— Wayne