MARKET RESEARCH / COMPETITOR WORKSHEET
Micro-SaaS competitor research: compare the real alternatives
The strongest alternative to your software might be a spreadsheet, an existing suite, or simply tolerating the problem. Research the buyer’s actual options before deciding what makes your idea different.
1. Define the job before searching for competitors
Write the task your buyer needs to complete and the circumstances in which it matters. “AI invoice software” describes a product category. “Following up unpaid invoices without losing client context” describes a job that several different products or manual processes might serve.
Keep the buyer segment explicit. A freelancer and a finance department may both chase invoices while facing very different budgets, approval processes, and integration requirements. Comparing products aimed at different buyers can make a weak difference look like an opportunity.
2. Map direct and indirect alternatives
Start with the tools buyers name in interviews. Add specialist products, features inside broader suites, manual services, spreadsheets, email, and doing nothing. Each alternative competes for the buyer's time or budget even when its feature list looks different.
Search the buyer's language as well as your proposed category. Look for phrases describing the task, mistakes, delays, and workarounds. Record the query and date so you can revisit how an alternative was found. Failure to find a competitor is not evidence that no competitors exist.
Use vendor documentation and pricing pages to establish what a company currently offers. Use independent accounts to understand reported experience. Treat your own hands-on observations as a third type of evidence, with the tested plan, version, and limits noted.
3. Compare the evidence that affects a purchase
| Field | What to record |
|---|---|
| Buyer and job | Who the alternative serves and which workflow it handles. |
| Relevant capability | A documented feature or an observed result, with a source. |
| Price and conditions | Currency, billing period, plan, seats, usage limits, add-ons, and date. |
| Setup and switching | Imports, integrations, training, approvals, and migration work. |
| Strengths and gaps | What works well, reported limitations, and what remains untested. |
| Evidence quality | Vendor claim, firsthand observation, customer report, or inference. |
A low headline price can be misleading if the required feature is on a different plan or billed per seat. Do not manufacture a single “true cost” when you lack the buyer's seat count, volume, or setup needs. Leave unknown values visible and compare like-for-like conditions when possible.
Keep links to the actual evidence. A product homepage may establish positioning without proving a detailed capability. If a vendor changes a price or fixes a limitation, update the claim rather than leaving an old criticism as a permanent selling point.
4. Read complaints without turning them into a market
A complaint is a lead for investigation. Check when it was posted, which plan or version it describes, the reviewer’s role, and whether other independent accounts describe the same issue. One unusual requirement does not establish a broad unmet need.
Look for positive reviews too. Buyers may accept an awkward workflow because the product handles something more important exceptionally well. That tradeoff can explain why people complain and still renew.
Keep the original meaning when summarizing feedback. Do not combine different complaints into a stronger claim no individual source made. If you cannot verify a criticism, label it as a reported experience or an open question.
5. Test whether the difference matters enough to switch
Turn a proposed advantage into a buyer question. Instead of assuming “fewer clicks” creates demand, ask what the current process costs and what would justify changing it. Price, trust, training, data access, and procurement can outweigh a useful feature.
Hypothetical example: a small agency likes a standalone reminder tool, but its accounting suite already sends reminders. The potential opportunity might involve the agency's specific approval workflow, or the existing suite may be sufficient. Interview evidence must distinguish those explanations.
Write the narrow claim your evidence supports: for a particular buyer, under particular conditions, your proposed approach may address a documented limitation. Then test feasibility and a concrete offer. Competitor revenue, customer count, or a high review score does not establish demand for your product.
Copy the competitor research worksheet
Buyer segment and recurring job: Alternative and source URL: Research date / tested version or plan: Direct competitor, suite, service, or workaround: Relevant capabilities and supporting evidence: Price, currency, period, seats, and limits: Setup and switching requirements: What customers value: Reported problem and its original context: Contrary evidence or recent fixes: Unknowns and next verification step: Proposed difference and buyer test:
Killgate's Market Research Studio preview is a separate research path. For deciding whether a venture should move forward, use Idea Validation alongside direct buyer evidence. A competitor table informs the decision; it does not issue a build verdict.
Further reading: the SBA market-research guidance includes indirect competitors and barriers to entry. The comparison worksheet and examples here are Killgate's practical guidance.