What is a SWOT analysis?
A SWOT analysis is a structured look at Strengths, Weaknesses, Opportunities, and Threats. It helps a team discuss its position before choosing an action. Strengths and weaknesses concern internal conditions, while opportunities and threats concern the outside environment. Asana's guide explains this general four-part structure.
The useful output is a better decision with visible reasoning. A matrix full of broad adjectives can feel complete while saying little about what to do. Start with a bounded question, such as whether a small SaaS should offer an assisted pilot to agencies during the next month.
This article uses an original fictional SaaS example called BriefRelay. Every customer note, product constraint, and external scenario below is invented teaching material. None is evidence about the real SaaS market or ShowMeYourSaaS performance.
Download the matrix and evidence register
The text template includes a completed fictional matrix, a blank matrix, and a decision log. The editable CSV holds the example observations, their evidence status, and a next check. Download both without registration and replace the fictional entries with information you can trace.
Use a consistent ID to connect each matrix statement to its supporting record. Preserve the distinction between an observation, an interpretation, and an untested possibility. When the underlying source changes, you can find the decisions that depended on it.
The files contain no automatic market research or calculated business score. Their purpose is to make your own reasoning reviewable. Add dates, owners, and source locations that fit your information-handling practices; avoid putting private customer material in a broadly shared planning file.
Set the question and the boundary first
BriefRelay collects project briefs and files for small agencies. Its fictional founder is deciding whether to run a two-week assisted onboarding pilot for agencies already using its basic intake form. The analysis concerns that offer, that audience, and the next month. It is not an attempt to assess every possible expansion.
Specify what success would teach you. In this example, the founder wants to learn whether an agency can complete a real intake with the existing product when setup help is available. A pilot can answer that narrower question without proving long-term retention or demand from every agency segment.
State constraints before listing attractive opportunities. The fictional founder has three support hours available each week and cannot change the document-storage system during the pilot. Those boundaries affect which actions are feasible even if the market opportunity sounds appealing.
Build the four quadrants with traceable statements
The example strength is an existing reusable intake form, linked to a fictional product walkthrough record. The weakness is limited support capacity, linked to the founder's planning assumption. Calling both facts would hide their different foundations: one is an observed capability in the exercise, the other is an estimate of future availability.
The opportunity is a possible introduction through an agency community organizer. It is external because access depends on another party, and it remains unconfirmed. The threat is a buyer's possible preference for a bundled intake feature elsewhere. The example note records that concern; it does not establish a broad competitor trend.
Use concrete wording that connects to the decision. Product is easy to use is difficult to evaluate. Existing form can be duplicated in the demonstration is narrower, but it gives the team something to inspect and a reason the pilot may be feasible.
| Quadrant | Statement | Status and implication |
|---|---|---|
| Strength | Reusable intake form already exists (S1) | Fictional walkthrough observation; use existing flow |
| Weakness | Three support hours per week are available (W1) | Planning assumption; cap the pilot |
| Opportunity | Organizer may introduce two agencies (O1) | Unconfirmed possibility; ask before allocating effort |
| Threat | Buyer may prefer a bundled alternative (T1) | Fictional interview concern; test the decision context |
Separate evidence from interpretation
A customer saying they already use a bundled form is an observation from a particular conversation. Interpreting it as a reason your offer will lose is a hypothesis. Record both, but do not turn one interview into a market-size claim.
Ask whether each statement is still relevant to the chosen audience and period. An old performance issue in an abandoned feature may not constrain the current pilot. An external pricing page may change. Keep the observation date and the next review trigger beside consequential claims.
An item can have different implications at different scopes. An integration you do not control is an external dependency; a missing integration capability in your current product is an internal limitation. Choose the framing that helps explain the present decision, and avoid counting the same underlying issue twice as independent evidence.
The customer interview guide helps gather concrete examples before filling the matrix. Do not write a fictional customer quote into a real evidence register simply because it makes a quadrant look balanced.
Turn the matrix into one bounded action
Combine the existing form with the potential community introduction, while respecting support capacity. A proposed action is to ask the organizer whether two relevant agencies want an assisted pilot using the current intake flow. Only offer dates after checking that the founder can support both within the available hours.
The decision log should name the proposal, the observations it depends on, the owner, the limit, and the stop or review condition. In this example, the founder records that the pilot pauses if setup requires a storage change or support demand exceeds the agreed capacity.
Keep the learning question observable: can each participating agency complete one genuine intake with its own permitted material? Record help required, failures, and the customer's next decision. Do not convert two completed intakes into a claim that the product has validated a whole market.
If the organizer cannot make an introduction, the analysis still produced useful information. Update O1 and choose the next investigation instead of quietly leaving an expired opportunity in the matrix.
Know what SWOT does not answer
A business model canvas describes assumptions about how the business creates, delivers, and captures value. SWOT assesses conditions relevant to a decision. The tools can share evidence, but repeating the same statements in both is not additional validation.
Competitor research can inform a threat or an opportunity, but the matrix does not replace checking actual product behavior, current terms, or buyer alternatives. A threat should explain a plausible effect on your audience rather than merely naming a large company.
Review the analysis when a critical assumption changes or before the next commitment. Keep resolved items in the dated history and refresh the current decision. The downloadable example and blank fields were checked for matching IDs, consistent fictional labels, and an action connected to the stated constraints. Framework source checked October 27, 2026.