Your Business Data is the Battleground: What This Lawsuit Tells You
Imagine spending almost a year working hand-in-hand with a big, well-funded company. They love your product. They test it thoroughly. They ask detailed questions about how it works. Then, at the end of the trial, they say “thanks, but no thanks” — and quietly build the same thing themselves, turning your idea into a product that competes with you directly. Then they sue you for good measure.
That’s not a paranoid fantasy. It’s exactly what happened between Rippling, a major HR software firm, and Runlayer, a startup that builds AI connection software. The two are now locked in dueling lawsuits — Runlayer accusing Rippling of breach of contract and stealing its product ideas, and Rippling firing back with a patent infringement claim. It’s a messy, expensive spectacle that should make every Malaysian SME owner stop and think about how exposed you are when you share your ideas, processes, and data with others.
TL;DR: Rippling tested Runlayer’s product for nearly a year without a paid deal, then built a competing version of its own. The fallout: two lawsuits, two damaged reputations. The lessons for you: protect your intellectual property before any long trial, read every vendor agreement carefully, and never concentrate your business around one big client or platform.
What This Means: The “Test Then Take” Trap
Runlayer sells an MCP gateway — software that lets AI agents connect to the data and systems they need to work on their own. MCP (Model Context Protocol) is an open standard, so anyone can build tools for it. Runlayer launched its product about a year ago and attracted substantial venture backing. Rippling became one of its earliest potential customers and spent months evaluating the software.
But the trial never became a paid contract. Instead, Rippling built its own MCP server — using the insights it gained from Runlayer’s product — and plans to launch it as a competing offering. (Rippling regularly turns internal tools into products, like its recently released AI Spend Console.) Runlayer sued first, claiming breach of contract and misappropriation. Rippling responded by filing a counter-suit over three patents.
Here’s the uncomfortable part for you: this isn’t only about patents and legal technicalities. It’s about the power imbalance between a customer and a supplier. Rippling spent a year getting deep access to Runlayer’s architecture, its roadmap, its strengths and weaknesses. Whether or not either side wins in court, that knowledge can’t be un-lived. This is the “evaluate then replicate” risk, at full volume.
When a bigger company tests your product for a year without a signed contract, you’re not giving them a demo. You’re handing them your blueprint — with a tour.
How This Applies to Malaysian SMEs
You might be thinking, “I run a bakery, a logistics company, a hardware supplier — what does a Silicon Valley legal fight have to do with me?” More than you’d guess. Every Malaysian SME today uses some form of software: cloud accounting, inventory systems, HR platforms, AI chatbots. Whenever you trial a new tool, you’re handing over your data, your customer list, and your internal processes to a third party. And whenever a larger client asks for a detailed proposal, you’re exposing your methodology and your workflow.
Consider the service provider scenario. A big corporate client asks you to pitch a project. You spend weeks preparing, sharing your approach, your supplier contacts, your process. They thank you warmly — then hand the job to an internal team that suddenly knows exactly how you operate. That’s the Rippling-Runlayer dynamic at Malaysian scale. The smaller player loses the contract, loses the ideas, and has no realistic path to sue a company ten times their size. The only defence is prevention.
There’s a second angle that matters even more for the next twelve months: AI adoption. Malaysian SMEs are increasingly being offered “AI agents” that can handle customer queries, generate invoices, or update your inventory. The MCP standard that Runlayer builds on is the plumbing that lets these agents reach into your systems. That’s genuinely useful — but it means your business data is flowing through infrastructure you don’t control. If your vendor decides to build a competing service from what they learn across their customer base, what recourse do you have? Read the terms before you click “agree.”
Finally, think about concentration risk. Runlayer bet its early momentum on winning Rippling as a customer, and that bet backfired. For Malaysian SMEs, the equivalent is depending on one client for half your revenue, or keeping all your data in a single platform with no export path. When the other side’s priorities change — and they will — you want options. The Rippling-Runlayer saga shows that even a startup with a strong product and solid backing can be backed into a corner. A small business in Malaysia has even less margin for error.
Practical Takeaways: Act Before the Problem Hits
- Get an NDA signed before you share anything sensitive. Not after the first meeting. Before. If the other party hesitates, that tells you something.
- Put time limits on free trials. Define the trial period, what’s being evaluated, and what rights the evaluator does (and doesn’t) get.
- Document everything you disclose. Keep records of what you showed, when, and to whom. You cannot prove misappropriation if you can’t show what was shared.
- Read your vendor contracts like your business depends on it. It does. Check what rights you’re granting over your data, and whether you can extract your data when you leave.
- Diversify clients and tools. No single client, platform, or vendor should hold the keys to your business.
The Two Lawsuits at a Glance
| Runlayer’s claim vs Rippling | Rippling’s counter-claim vs Runlayer | |
|---|---|---|
| Filing date | July 2026 | August 2026 |
| Core accusation | Breach of contract; stealing product ideas | Infringement of three patents |
| Backstory | Rippling tested Runlayer’s MCP product for nearly a year; no paid deal resulted; Rippling then built its own competing server | |
| Key detail | A Rippling employee reportedly warned Runlayer’s founder that Rippling was building a “copy” of the product (source) | |
The Bigger Picture: AI Compresses the Timeline
Here’s the deeper shift. AI has made it faster and cheaper to build software than ever before. Ten years ago, a big company that trialled a startup’s product would often decide, “it’s not worth building our own.” Today, that calculation has flipped. If a larger firm can see how a product works — and has the engineering talent in-house — they can build an acceptable version in weeks. The Rippling-Runlayer case is one of the first public blow-ups of this dynamic, but it won’t be the last.
What does that mean for you? If your business sells a product or service that a larger partner could plausibly replicate with AI tools, your moat is no longer your process. It’s your relationships, your speed of service, your local knowledge, and your reputation. Those are much harder to copy than a workflow.
There’s also an upside. The MCP standard that started this fight is quietly opening doors for small businesses in Malaysia. AI agents that can connect to your accounting, your inventory, and your customer records are becoming accessible to businesses of every size — not just enterprise giants. Use them. But use them with the same wariness you’d bring to any relationship where the other party holds more power than you do.
Remember the rule this case teaches: treat every business relationship as if the other side might one day become a competitor. In the AI era, that day arrives faster than you think.
Ready to Streamline Your Operations?
Your business should run itself. AutoRunBiz deploys AI agents to automate your daily operations — WhatsApp orders, invoicing, customer follow-ups, and accounting. Book a free 15-min ops audit to see where automation fits your business →