# How to Do a Competitor Teardown Before You Build > A competitor teardown in 2 to 3 days: sign up as a real user, read unhappy reviews, check public signals, then decide what to build and what to skip. --- url: "https://earlyhunt.com/studio/how-to-do-a-competitor-teardown-before-you-build" markdown: "https://earlyhunt.com/studio/how-to-do-a-competitor-teardown-before-you-build.md" type: studio_post title: How to Do a Competitor Teardown Before You Build slug: how-to-do-a-competitor-teardown-before-you-build published: "2026-10-23T04:53:39.405Z" updated: "2026-10-23T04:53:48.870Z" --- ## Summary A competitor teardown in 2 to 3 days: sign up as a real user, read unhappy reviews, check public signals, then decide what to build and what to skip. ## Article A competitor teardown is a short, timeboxed study of the three to five products your future customers already use, done before you write much code. Sign up for each one as a real user and log every step to first value, read their unhappy reviews and tag the complaints into themes, check public signals like changelogs, job posts and old homepages, then put it all in one sheet. The goal is not a feature list to copy. It is three decisions: who you are for, what you will not build, and what to test with real users first. Two to three days is enough for most early founders. This guide is for founders who are pre-launch or in their first few months. The startup and competitors in the examples are made up, and nothing here is legal advice. ## What is a competitor teardown, and what is it not? A teardown is competitor analysis for startups done the cheap, hands-on way. You use the products, read what their customers say when they are annoyed, and look at what each company does in public. You learn where the market is crowded and where people are quietly unhappy. It helps to be clear about what it is not: - **It is not a copy plan.** If you leave with a list of 40 features you "need for parity", the teardown failed. - **It is not a market-size slide.** Nobody decides what to build from a TAM number. You decide from specific complaints. - **It is not a comparison page.** A public "us vs them" page is a different, later job. Why bother? Competitive research before building is the cheapest way to avoid spending three months on the part of the problem nobody complains about. ## Who actually counts as a competitor? Most founders list the two or three companies that look most like their idea and stop. That misses the competitor that usually wins: whatever your buyer does today instead of paying anyone. Type What it looks like Why you study it Direct Products built for the same job and the same buyer Shows the default promise, the default onboarding and the default complaints Indirect Broader tools that cover your job as one feature among many Shows what "good enough" looks like and why some buyers never look for a specialist Do nothing / DIY A spreadsheet, a paper diary, a shared inbox, a group chat, a virtual assistant This is often your real rival. Free, familiar, and already part of their week Hire someone An agency, a freelancer, a part-time admin person Tells you what the job is worth in money and which parts people happily hand off For a first teardown, pick one or two direct competitors, one indirect tool, and the do-nothing option. ## How do you find competitors you have never heard of? The ones you already know are rarely the full list. Spend one focused session on these searches and keep everything in one tab of a sheet: 1. **Search the job, not your product name.** Type the problem the way a buyer would say it: "send appointment reminders to dog grooming clients", not "groomer CRM". 2. **Browse software review site categories.** G2 and Capterra group products by category, which surfaces small tools you would never find by name. 3. **Check launch sites.** Product Hunt and smaller launch boards show who launched in your space recently, including tiny products that may be ahead of you or may have quietly died. 4. **Search "alternatives to [the biggest player]".** Alternatives lists are where smaller competitors fight for attention. 5. **Ask three target users what they use today.** Not "would you use my thing" but "what do you use now, and what did you try before that?" The answers often include the spreadsheet, a WhatsApp group, or a tool you have never heard of. If you are planning those user conversations anyway, the SideHunt guide to [validating an idea with five conversations](https://sidehunt.io/studio/how-to-validate-a-side-project-idea-with-five-conversations) pairs well with this step. Ask about current tools there and you get competitor research for free. Stop when searches only show names you already have, then cut to three to five. ## How do you sign up like a real user and stay honest? Most founders skip this, and it is the most useful part. A homepage tells you what a company wants you to believe. Signing up shows you what being a customer feels like. Open a fresh browser profile, start a timer, and record the following for each product: What to log How Time to first value Minutes from landing on the signup page to the first moment the product did something useful for you Steps Every screen, form and click until that moment, numbered Required fields What they insist on knowing (phone number, company size, card details) before you get in Where you got stuck Any moment you had to guess, search the docs or give up Emails over a week Subject line, day sent, and whether it helped you do the job or just pushed an upgrade Take a screenshot at every step and drop them in a folder per competitor, named with the step number. The email log often ends up the most revealing part: it shows what they think new users need. Keep it honest. Your market is smaller than you think: - **Use your own name and email.** No invented personas. - **Do not book sales demos under false pretences.** If you want a demo, say who you are. - **Do not scrape or automate against their terms.** Manual use of a public free trial is a very different thing from pulling their data. - **Read the terms of service if you are unsure.** Some vendors restrict competitive use. For example, Salesforce's Main Services Agreement, as of Oct 2026, says customers may not access a service to build a competitive product or copy its features or functions. If a clause worries you, skip that product or ask a lawyer. This is general information, not legal advice. ![earlyhunt-2026-10-23-inline-1.jpg](https://txmhk1zrnc.ufs.sh/f/xSkWTCqmKWx9Jcn19fsLgUeyZW5qmHS78OPtbRYcNjE6olG3) ## How do you read their unhappy customers? The useful reviews are in the middle. Two and three star reviews come from people who wanted the product to work and got let down by something specific. That something is your opening. Where to look: - **Review sites and stores.** G2 and Capterra for B2B software, the App Store and Google Play for mobile apps, the Chrome Web Store for extensions. - **Reddit and niche forums.** Search the product name plus words like "frustrated", "switched" or "alternative". People are often more candid there. - **Their own community or forum.** Feature request boards and community threads show what customers have asked for repeatedly and not received. - **Their help centre.** If it lists popular articles, those topics show where the product confuses people. Copy each complaint into a sheet with four columns: competitor, source link, the complaint in the customer's own words, and a theme tag. Keep the tags plain, like "setup too long", "reminders unreliable", "too expensive for one person", "mobile app weak", "support slow". After 30 to 50 complaints, sort by tag. Usually two or three themes carry most of the weight. Watch who is complaining, not just what. "Too complex for a solo operator" from ten small businesses is a segment signal. The product may be fine for teams and wrong for that group. ## What public signals show where a competitor is heading? Spend an hour per competitor on what they do in public: - **Changelog or release notes.** How often do they ship, and what kind of things? A changelog full of enterprise features (single sign-on, audit logs, admin roles) tells you where they are moving. Small customers may be left behind. - **Job posts.** The roles a company hires for show strategy. Several enterprise sales roles suggest a move upmarket. A first hire for a new country or a new platform shows where they plan to grow next. - **Docs and API.** Public docs show what the product really does beyond the marketing copy, and an API tells you whether they expect customers to build on top of them. - **Integrations page.** Which tools they connect to tells you who their customers really are and what else those customers use. - **Old homepages.** Paste a competitor's homepage URL into [the Internet Archive's Wayback Machine](https://web.archive.org/) and pick dates from the calendar. You can watch how their headline and audience changed over the years. If they used to say "for freelancers" and now say "for growing teams", the freelancers may be underserved. Not every site is archived, since some are excluded or blocked from crawling. - **Pricing page, as an input only.** Note how plans are structured and which features they lock behind higher tiers. That shows who they think pays the most. Write down the price anchor and move on. This is research, not your pricing decision. Traffic estimate tools such as Similarweb, and Google Trends for search interest, can give a rough sense of size and direction. Treat them as rough. Similarweb describes its numbers as estimates built from modelled data, and Google says Trends data is a normalised sample, scaled from 0 to 100, where very low-volume terms show as 0 and the data is "not a perfect mirror of search activity" (from the [Google Trends data FAQ](https://support.google.com/trends/answer/4365533?hl=en)). Use them to compare competitors, never to decide on their own. ## What goes in a competitor teardown sheet? All of the above ends up in one sheet, one row per competitor. This is the startup competitor analysis template I would use. Keep each cell short. Here is a made-up example. Haywick is a fictional startup building booking and reminder software for independent mobile dog groomers. The competitors below are invented too, so treat the rows as an illustration of the format, not facts about real products. Competitor (made up) Who it is really for Homepage promise Time to first value Steps Top 3 complaints What they ignore Changelog pace Price anchor Integrations Salon suite A Multi-chair salons with front-desk staff Run your whole salon in one place About 40 min 14 Setup too long; built for teams; mobile app weak People working from a van with no front desk Every 2 weeks, mostly staff and payroll features Per-location monthly plan Payments, accounting, marketing email Groomer app B Small grooming shops Booking made for groomers About 12 min 7 Reminders sometimes late; no route planning; slow support Travel time between appointments Monthly, small fixes Flat monthly fee Payments, calendar sync Booking tool C (general) Any service business Let clients book you online About 8 min 5 No pet details; generic reminders; hard to handle repeat bookings Pet notes, vaccination dates Weekly, broad features Free tier, paid per seat Many calendars and video tools Paper diary + text messages Groomers who have never paid for software None Instant 1 Double bookings; forgetting reminders; no record of past cuts Everything beyond the next appointment None Free None Even with invented data, the gaps jump out: the salon suite ignores people working from a van, the general tool knows nothing about pets, the groomer app ignores driving time, and the paper diary is good enough until a double booking costs a client. ![earlyhunt-2026-10-23-inline-2.jpg](https://txmhk1zrnc.ufs.sh/f/xSkWTCqmKWx99y73EpsSYksFrxbCcIQZtwhXo1HyLjU3f6O7) ## How do you turn the teardown into decisions? A sheet nobody opens again was a waste of three days. Force it into four outputs. ### 1. Find the underserved segment or complaint cluster Look across the complaint tags and the "who it is really for" column together. You are looking for a group of buyers that keeps complaining about the same thing across several products. In the made-up Haywick sheet, that is solo groomers working from vans: too small for the salon suite, poorly served by the general tool, and annoyed by late reminders and no travel planning in the groomer app. ### 2. Write a one-line wedge Use a simple format: "We are for [specific buyer] who are tired of [specific complaint]." For Haywick: "We are for mobile dog groomers who are tired of software built for salons with a front desk." If you cannot write it, go back to the complaints. Turning that into homepage copy is a separate step. The IndieHunt guide to [writing a one-page positioning brief before your homepage](https://indiehunt.io/studio/how-to-write-a-one-page-positioning-brief-before-homepage) covers that, and your teardown sheet gives you most of the inputs. ### 3. Write a "will not build" list This is the most valuable output and the one founders skip. List the things competitors offer that your segment does not care about. For Haywick that might be staff payroll, multi-location reporting, inventory management and a marketing email builder. Writing it down protects you from feature-list envy later. ### 4. Pick three things to test with users before writing code Turn your biggest assumptions into questions you can check in conversations or with a rough prototype. For example: - Do mobile groomers actually lose money to late or missed reminders, or is it just irritating? - Would they pay for travel-time planning, or do they already handle it fine with a maps app? - Will they move off a paper diary at all, and what would make them do it in the first week? If the answers do not hold up, you just saved a build. ## What traps turn a teardown into a waste of time? - **Feature-list envy.** You see what competitors have and feel behind. Their features were built over years for their customers. Your wedge is usually doing less, better, for fewer people. - **Studying only big incumbents.** They are the easiest to find and the least useful to copy. Include at least one small competitor and the do-nothing option. - **Trusting traffic estimates.** Estimates are modelled guesses. Two tools can disagree by a lot. Use them to compare, not to conclude. - **The teardown that never ends.** There is always one more competitor and one more review site. Timebox it to two or three days and stop. - **Copying their onboarding wholesale.** Their onboarding is shaped for their buyer. Take ideas about what confused you, not their exact screens and steps. - **Badmouthing competitors in public.** What you learn is for your decisions. Posting "their product is terrible" makes you look small. If you later write a public comparison, the Aura++ guide to [writing an honest SaaS comparison page](https://auraplusplus.com/studio/how-to-write-a-saas-comparison-page-that-ranks) shows how to stay fair. ## A 5-day competitor teardown plan A few focused hours a day fits this into a working week. Full days compress it to two or three. Day Focus Output Day 1 Find competitors: job searches, review site categories, launch sites, alternatives lists, ask three users what they use Long list cut to 3 to 5, including one indirect and the do-nothing option Day 2 Sign up for each product as yourself, timer running, screenshots at every step Signup log per competitor; email log started Day 3 Read 2 and 3 star reviews, Reddit threads, community boards and help centres 30 to 50 complaints tagged into themes Day 4 Public signals: changelog, job posts, docs, integrations, Wayback Machine, pricing structure Teardown sheet filled in, one row per competitor Day 5 Decisions: segment, wedge line, will-not-build list, three things to test One page of decisions and a list of users to talk to next week Keep the email log going for a few days after Day 5 so you catch the full first-week sequence. ## Competitor teardown FAQ ### How many competitors should I analyze? Three to five is enough for a first pass. Include one indirect tool and whatever people do today without software. More than five usually means you are avoiding the decisions. ### Is it legal to sign up for a competitor's free trial? Signing up for a public free trial under your own name is a normal thing founders do, but the product's terms of service are a contract and some restrict competitive use. Read the terms first, do not misrepresent who you are, and do not scrape or automate against the rules. If a clause concerns you, skip that product or ask a lawyer. This is general information, not legal advice. ### What if I find no competitors? Look harder at the do-nothing option. If people have the problem, they are handling it somehow: a spreadsheet, a notebook, a freelancer, or just living with it. That is your competitor. If you truly find nobody doing anything, check that the problem is painful enough for anyone to pay to fix it before you build. ### How often should I redo a teardown? Do a light refresh when something changes: you are about to launch, a new competitor appears, or you are picking your next big feature. A quick pass over changelogs, new reviews and homepages every few months is plenty early on. New products show up all the time, and plenty of them launch small before anyone writes about them. Browse what other early-stage founders are launching on [EarlyHunt](https://earlyhunt.com/) to spot new entrants in your space early. ## Links - Page (HTML): https://earlyhunt.com/studio/how-to-do-a-competitor-teardown-before-you-build - AI-friendly Markdown: https://earlyhunt.com/studio/how-to-do-a-competitor-teardown-before-you-build.md ## Explore - [Studio](https://earlyhunt.com/studio) - [Blog](https://earlyhunt.com/blog) - [Launch Guide](https://earlyhunt.com/launch-guide) _HTML version: https://earlyhunt.com/studio/how-to-do-a-competitor-teardown-before-you-build_