clone test
clone test
Asking whether a well funded team could rebuild your entire product in 90 days and still lose to you.
IN PLAIN LANGUAGE
The clone test is a single blunt question: could a team of ten competent engineers with two million dollars in funding rebuild your entire product in 90 days and beat you? If yes, you do not have a business yet. You have a prototype with good marketing.
This is not a hypothetical exercise. It happens constantly. Yik Yak, an anonymous campus messaging app, raised $73 million and was cloned repeatedly by smaller apps offering nearly identical functionality within months, because there was nothing underneath the feature set that took time to replicate. Yik Yak shut down in 2017.
Contrast that with Figma. A well funded team could rebuild Figma's canvas rendering engine in 90 days, that part is genuinely cloneable with enough engineering talent. What they could not rebuild in 90 days is the thousands of teams who already have their design systems, comments, and workflows living inside Figma's files. The clone test fails for Figma not because the software is unclonable but because the accumulated customer data and habits are not.
Running the clone test honestly requires separating what is hard to build from what is hard to accumulate. Most technical moats are actually build time moats, six months to eighteen months of engineering lead. Most accumulation moats, like Figma's stored files or LinkedIn's connection graph, take years regardless of budget, because time itself is the input, not money.
Founders resist this test because the answer is often uncomfortable. If your product would fail the clone test today, the honest move is not to panic, it's to identify which specific asset, data, relationships, or switching cost, you need to accumulate before a well funded copier shows up. Speed to that asset matters more than speed to launch.
A note taking app with a clean interface and AI summarization gets cloned by three competitors within four months of its product launching. None of the clones fail on quality. The original loses two thirds of its early user base within a year because nothing it built took time or trust to replicate.
Most seed stage startups fail the clone test the day they launch,and that's normal, the test matters more at series A when the money for cloning actually exists.
QUESTIONS
- Does every startup need to pass the clone test on day one?
- No. Early on, speed and distribution matter more than defensibility. The clone test becomes urgent once you're raising real money or a well capitalized competitor enters your space, not before.
- What's the difference between the clone test and a moat?
- The clone test is the diagnostic question. A moat is the answer, if you have one, that lets you pass it. Ask the clone test first, then figure out which moat, if any, gets you a passing grade.
- Can marketing alone help you pass the clone test?
- Brand recognition helps but rarely wins alone against a well funded copier with aggressive pricing. It buys time, not immunity, unless the brand itself took a decade to build, which most startups have not had.
RELATED TERMS
A structural reason a competitor with more money still cannot take your customers.
Building your product so the incumbent's own business model stops it from copying you.
Value that only accumulates through actual use over time, and cannot be captured in a screenshot or a competitor's demo video.
Reading about moats is cheap. Testing one takes six stages.