The Question and Where It Applies
You manage a B2B collaboration SaaS product. A direct competitor announces a free version for teams of up to 20 members. It includes an automation capability that your company offers in a plan priced at $18 per user per month. During the next two weeks, sales records 12 qualified opportunities that mention the competitor. Existing-customer churn, downgrades, trial conversion, and expansion have not shown a confirmed change. Leadership wants a decision this week: match the free version, cut prices, accelerate a differentiating feature, or leave the roadmap unchanged for now.
The product, member limit, price, opportunity count, and time periods above are interview-case assumptions, not market facts or industry benchmarks. In a real interview, replace them with the product, segment, cost, and competitive evidence supplied by the interviewer.
This is a product strategy question for product managers, growth PMs, monetization PMs, and leaders who influence roadmap decisions. A product management question set published in June 2026 directly asks how to respond when a competitor launches a free version. Another preparation guide updated in December 2025 includes a question about responding when a competitor launches a similar feature. Those sources support the question's current relevance. They do not establish that a particular company routinely asks it, and they do not justify claims about interview frequency.
The challenge is to separate the competitor's announcement from actual customer behavior. The launch deserves investigation, but the announcement alone does not prove that the target segment will switch, that the free model is sustainable, or that a permanent price change is the best response. A strong candidate creates an executable path between speed and evidence: verify the facts and exposure first, then choose an action that is proportionate, testable, and as reversible as possible.
What the Interviewer Is Evaluating
First, can the candidate begin with customers and company objectives? Amazon's published leadership principles articulate a useful stance: pay attention to competitors while starting with the customer and working from customer needs. A strong answer does not copy a feature merely because a rival launched it. It asks whose job the feature solves and whether it gives the company's core customers a materially better outcome.
Second, can the candidate distinguish evidence strength? A competitor's marketing page, a salesperson's account, a loss interview, hands-on product use, a customer downgrade, and cohort behavior are not equivalent evidence. Twelve opportunities mentioning the competitor are a reason to investigate. To assess impact, the team still needs to know whether those opportunities were otherwise likely to close, why the competitor came up, what the buyer ultimately chose, and what value was actually at risk.
Third, can the candidate define the real competitive boundary? The free version may cover only small teams, omit administration and security, or monetize elsewhere. Different target users, constraints, buyers, substitute jobs, and switching costs can mean that two apparently identical features are not competing solutions. Conversely, if the free capability has become a basic entry criterion, continuing to call it a differentiator would also be inaccurate.
Fourth, can the candidate offer responses of different intensity and explain their costs? Competitive analysis should inform a roadmap, not take it over. Monitoring, updating sales positioning, fixing the current experience, running a limited packaging test, accelerating a validated capability, and permanently cutting prices each require different evidence and carry different risks.
Finally, can the candidate make a current recommendation with conditions for changing it? “Collect more data” is not a decision. “Make it free immediately” puts an irreversible action on top of weak evidence. The candidate should state what happens this week, who owns it, how long the evidence window lasts, which metrics matter, and what result would trigger a stronger response.
Clarifying Questions Before Answering
- What company objective and outcome are we protecting? Is this quarter about new-logo growth, enterprise expansion, margin, retention, or positioning? This case assumes the goal is to protect small-business acquisition without damaging existing customer value or unit economics.
- What did the competitor actually launch? Is it generally available, a waitlist, a limited promotion, or only an announcement? Beyond the 20-member limit, what are the automation quotas, integrations, retention limits, support levels, security controls, and administrative capabilities?
- Who truly overlaps? Does the free version serve individuals, micro-teams, or the same businesses that buy our paid plan? Are the users, buyers, and administrators the same? Only an overlapping segment belongs in the denominator for direct exposure.
- Is the customer job equivalent? Does the competitor merely expose a control, or can it complete the same critical workflow with comparable reliability and governance? Matching feature names cannot replace a job-level comparison.
- What do the 12 opportunities represent? What share of qualified opportunities do they comprise, which segments and stages are involved, what were the outcomes, and did price or capability cause them? Sales notes should be checked against recordings, loss reasons, and customer interviews.
- What are the current baselines? What are the baselines and maturity windows for trial-to-paid conversion, sales win rate, downgrade, churn, expansion, margin, and support cost? Without a baseline, a change cannot be identified.
- How reversible is a pricing change? Would a new discount cause existing customers to renegotiate, create channel conflict, or establish a lasting price anchor? A time-boxed test, a segment-specific package, and a permanent free tier have very different reversibility.
- Is related differentiation already on the roadmap? If customer evidence supported the work before the announcement, the launch may change its timing. If the announcement is the only reason for the work, the evidence threshold should be higher.
- Why is a decision required this week? A major renewal or near-term deal may require a temporary field response. Without immediate customer loss, a short evidence window may produce a better decision.
A 30-Second Answer Framework
“I would not copy the free version or permanently cut prices based on the announcement. I would first verify the competitor's real capabilities, constraints, and target segment, then assess our exposure across segment overlap, job substitution, switching friction, behavior change, and value at risk. Twelve opportunities mentioning the competitor are a signal to investigate, not evidence that we lost them. This week I would publish a verified field brief, interview the opportunities and recent losses that mentioned the competitor, build an exposed cohort, and run a reversible packaging or extended-trial test for the target small-team segment. If the exposed segment shows an incremental loss in win rate, conversion, or retention above a precommitted threshold, the free capability is confirmed as the cause, and the test passes its guardrails, I would escalate to a limited free tier, a pricing change, or accelerated differentiation. Otherwise, I would keep the customer-supported roadmap.”
This framework contains a current choice, immediate actions, and escalation criteria. A deeper answer can then explain the evidence ladder, risk estimate, response matrix, and validation plan.
Step-by-Step Deep Dive
Step 1: Turn the announcement into a verified fact sheet
Assign one owner to sign up where legally permitted, read the public terms, and complete the critical workflow. Record the version, date, and limits. At minimum, verify target users, member limits, automation quotas, integrations, collaboration and administrative permissions, import and export, security, support, and the conditions for moving from free to paid.
A competitor's website represents its positioning, not necessarily the outcome a customer can achieve. Do not stop after copying sales screenshots into a feature matrix. Compare both products using the same customer job, such as: “Can a 20-person team run a weekly approval automatically, without administrator intervention, and recover when it fails?” This exposes the difference between a visible feature and a complete outcome.
Also distinguish direct competitors, indirect substitutes, and doing nothing. If target customers currently use spreadsheets and manual reminders, the free competitor may expand the category rather than only take existing share. The response may then shift from defending the installed base to proving the value of adoption.
Step 2: Build an evidence ladder instead of treating attention as behavior
Evidence can be ordered by how close it is to an actual choice:
- Announcement evidence: published features, constraints, pricing, and terms; it verifies facts but does not prove adoption.
- Stated evidence: sales notes, support tickets, surveys, and interviews; it reveals concerns but remains sensitive to wording and sample bias.
- Choice evidence: qualified deal outcomes, trial exits, downgrades, and renewal negotiations; it is closer to a real tradeoff.
- Behavioral evidence: sustained changes in activation, conversion, retention, expansion, and migration paths for the target segment; it quantifies impact.
- Economic evidence: incremental loss, acquisition cost, service cost, discounts, and contribution after cannibalization; it determines whether a response is worthwhile.
The 12 opportunities are at the second level. For each one, capture stage, segment, prior purchase intent, whether the competitor reached the final consideration set, the blocker, and the outcome. If only two of the 12 belong to the directly overlapping segment, the exposure is very different from assuming that all 12 will be lost.
Step 3: Assess the threat across five dimensions
Build a threat table for the directly overlapping segment:
| Dimension | Core question | Evidence that raises the threat | |---|---|---| | Segment overlap | Does the competitor serve the same users, buyers, and company size? | Core customers can adopt it without a material compromise | | Job substitution | Does the free capability complete the same critical job? | Customers validate that the critical workflow is good enough | | Switching friction | What are the data, integration, training, and contract migration costs? | New buyers have no migration burden and existing customers have a low-cost path | | Behavior change | Are customers actually changing trials, purchases, or renewals? | The exposed segment consistently deteriorates versus a comparable baseline | | Economic exposure | How much value is affected, and what would a response cost? | Incremental loss exceeds the full cost of a proportionate response |
A transparent interview formula for value at risk is: exposed opportunities × incremental probability of loss caused by the competitor × expected value per opportunity. Use ranges for every term; do not count the entire pipeline as certain loss. For existing customers, separately estimate exposed revenue, true downgrade or churn probability, and migration timing without double-counting new-business opportunities.
Time boundaries matter. New-business competition may appear in win rate within weeks, while churn on annual contracts cannot appear until renewal. “Churn has not changed” may mean no impact, or it may mean the metric is not mature. A strong answer identifies the maturity window rather than selecting the interpretation that supports a preferred action.
Step 4: Match the response to the threat instead of choosing only “match” or “ignore”
| Response | When it fits | Main risk | |---|---|---| | Monitor and update the field brief | Weak signal, low overlap, and no behavior change | Slow monitoring may miss a real shift | | Strengthen positioning and the existing experience | The customer job is already superior, but the value is not understood or activated | Copy changes cannot fix a real capability gap | | Run a limited packaging or trial experiment | Price sensitivity is concentrated in a defined segment and the action is reversible | Discounts may attract low-intent users and cannibalize paid demand | | Accelerate already validated differentiation | Customer evidence supported the need before the competitor launch | Competitive pressure may compress quality or scope | | Create a free tier or permanently reprice | Sustained behavior and economic evidence indicate a structural change | Price anchors, renegotiation, cost, and brand effects are hard to reverse | | Take no product action | The target segment differs or the competitor cannot substitute for the critical job | The team may confuse confidence with evidence and stop monitoring |
For this scenario, I would combine monitoring and a verified field response with a limited experiment. I would not immediately make a permanent price cut. The current evidence is stated interest; conversion, churn, and expansion have not shown a confirmed shift. A permanent price action can reset the reference point for every customer, while a target-segment test can establish whether price is actually blocking choice.
If the problem is value communication, improve onboarding, the trial path, comparison material, and the sales demonstration. If customers validate that the competitor is better at the critical job, address product capability. Marketing cannot repair a real workflow gap, and a large development project should not answer an unverified sales narrative.
Step 5: Run a competitive-response sprint with a deadline
The case can use a four-week interview evidence window. Four weeks is a case assumption, not a universal duration:
- The product owner verifies the competitor's scope and maintains the dated fact sheet.
- Sales operations adds competitor exposure, reason, and outcome fields to every qualified opportunity.
- Product and research interview competitor-mentioned prospects, recent losses, and successful buyers so the sample is not limited to lost deals.
- Data builds comparable baselines by small-team segment, industry, region, channel, and new versus existing customer.
- Monetization tests one reversible offer only within a preselected small-team segment, such as a longer full trial or an entry package with a limited automation quota.
- Sales and support receive a verified capability boundary, fit guidance, and escalation path without unsupported attacks on the competitor.
The experiment must address selection bias. If only deals that look likely to lose receive the offer, the offer group cannot be compared directly with the normal group. Randomize within the eligible segment when possible. Otherwise, predefine eligibility, use a same-period comparison cohort, and state the observational limitation.
Step 6: Precommit metrics, guardrails, and decision triggers
Primary decision metrics should be close to actual choice: the win-rate difference between competitor-exposed and comparable opportunities in the target segment, the difference in trial-to-paid conversion, and incremental downgrade or churn among mature renewals. Diagnostic metrics include competitor mention rate, specific blockers, critical-job completion, migration attempts, and sales-cycle length. Economic metrics include net revenue, average discount, service cost, and gross margin.
Guardrails prevent low-quality growth from looking like success: the share of existing paid customers seeking renegotiation, cannibalization as customers who would have paid move to a lower-priced offer, support load, abuse, automation run cost, and brand or channel conflict. More free registrations do not prove the strategy worked. They may add cost without creating durable value for the target customer.
Decision triggers must be written before seeing the result. An interview example could be: “After four weeks, expand the segment-specific offer only if the directly exposed target opportunities lose at least 8 percentage points of win rate versus a comparable baseline, loss interviews confirm the free capability as the primary cause, and the limited packaging test improves conversion while passing guardrails.” The four weeks and 8 percentage points are replaceable case thresholds. A real threshold should reflect the baseline, sample uncertainty, opportunity value, cost, and decision deadline.
If win rate is unchanged but the sales cycle grows longer, improve proof material first. If registrations rise without an improvement in paid conversion or critical-job completion, do not expand the free offer. If existing customers begin downgrading in volume because of the competitor, elevate renewal risk into a separate workstream instead of waiting for the new-business experiment to finish.
Step 7: Close the cycle with a decision record rather than monitoring forever
The record should contain verified facts, unknowns, affected segments, the current choice, rejected options, owners, evidence window, metrics, guardrails, and the next decision date. Leadership, field teams, product, and engineering should use the same version. Otherwise, sales may promise free access while product follows the old roadmap and finance models a different revenue assumption.
At the end of four weeks, select an outcome: keep the roadmap, strengthen the current value, expand the limited offer, change packaging and pricing, or accelerate a capability already supported by customer evidence. If the data is still immature, name the missing evidence, the cost of continued observation, and a new final deadline. “Wait and see” cannot become a permanent default.
High-Quality Sample Answer
“I would treat the competitor's launch as a signal to investigate, not as proof that a price war has started. The free version in the case supports up to 20 people, but I still need to verify whether its automation quota, administration, security, integrations, and support can complete our core customer's job. Twelve opportunities mentioning it within two weeks means the field needs immediate support. It does not yet justify a permanent price cut because trial conversion, churn, and expansion have not shown a confirmed change.
I would first define the objective as protecting small-business acquisition while preserving existing customer value and unit economics. I would then focus on the directly overlapping segment: the same users and buyers, the same critical job, and an acceptable migration cost. Sales operations would complete the stage, segment, competitor role, blocker, and final outcome for each of the 12 opportunities. Product would complete the competitor's workflow and interview competitor-mentioned prospects, recent losses, and successful buyers.
This week, sales and support would receive a verified positioning and capability brief so individuals do not make their own pricing promises. In parallel, I would open a four-week case evidence window. For eligible small teams, I would randomly test one reversible option, such as a longer full trial or an entry package with a limited automation quota, rather than giving every customer a permanent free plan. If the current roadmap already contains differentiation backed by customer evidence, I would revisit its timing, but I would not create a large unvalidated project because of the announcement.
I would compare win rate, trial conversion, and mature renewals between exposed and comparable cohorts, then check the stated loss reasons. Guardrails would cover paid cannibalization, existing-customer renegotiation, average discount, support cost, and automation run cost. For example, the team might precommit to expanding the segment offer only if the exposed segment loses at least 8 percentage points of win rate, the free capability is confirmed as the reason, and the limited offer improves conversion while passing guardrails. That is an interview threshold; the real value must follow the baseline and economics.
After four weeks, if customer behavior has not changed, I would keep the customer-supported roadmap and continue light monitoring. If price has become an entry requirement for the target small-team segment, I would expand the limited package. If customers choose the competitor because it completes the critical workflow better, I would fix or differentiate the product instead of only lowering price. This supports the field quickly without allowing a weak signal to trigger a global pricing decision that is hard to reverse.”
The answer converts “What did the competitor do?” into “Which customers changed which choices?” The response then intensifies only as the evidence does. The recommendation is not permanent; its decision triggers are part of the answer.
Common Mistakes
- Cutting prices across the board when the word “free” appears → The announcement has not established segment overlap, switching behavior, or sustainable economics → Verify the customer job and behavior, then test price friction in a limited segment.
- Stopping at a feature comparison → Feature names do not establish a complete job, reliability, or a purchase reason → Test the same customer task and interview real decision-makers.
- Ignoring the competitor completely → Customers and field teams may already face a new alternative → Provide a verified fact sheet and monitoring system immediately, then let evidence determine response intensity.
- Listening only to salespeople on lost deals → Memory, incentives, and the sample can amplify a few cases → Examine wins, losses, product behavior, and comparable cohorts together.
- Counting every opportunity as lost value → A mention does not mean the competitor reached the final set, and the opportunity may not be in the overlapping segment → Estimate incremental loss probability and a value range.
- Using registrations to declare a free strategy successful → Free users may fail to activate or retain while adding support and run costs → Measure the critical job, sustained use, payment, and economic guardrails.
- Using positioning to hide a real capability gap → Messaging cannot fix a failed customer job → Determine whether the issue is value communication, experience friction, or a product gap before choosing the response.
- Reordering the entire roadmap after a competitor announcement → The team abandons prior customer evidence and enters a copying loop → Keep competitive intelligence as an input, constrained by objectives, customer value, and decision triggers.
- Saying “keep monitoring” without a deadline → Without an owner, metrics, and a decision date, a weak signal remains unresolved indefinitely → Create a time-boxed sprint and decision record.
Follow-Up Questions and Responses
Follow-up 1: The largest opportunity says it will choose the competitor unless we match the free price this week. What do you do?
Verify whether this is the actual final condition, the opportunity value, target-segment fit, and whether the competitor can satisfy the critical job. If the strategic value is sufficient, offer a time-limited exception or pilot with explicit scope and renewal terms, then record the discount cost and success criteria. Do not turn one negotiation into market-wide pricing. The exception also cannot allow sales to promise capabilities the product does not support.
Follow-up 2: The competitor's free product is weaker, but it is growing quickly. Can you still ignore it?
Feature depth is not enough to decide. Determine whether growth comes from the target segment, subsidized acquisition, migration of existing users, or education of a new market, then inspect activation, sustained use, and the paid path. If it lowers the category's trial barrier, improve import, value proof, and migration. If the target segment changes its choices, increase the response. A growth number without a denominator, segment, and behavior should not directly drive the roadmap.
Follow-up 3: A limited free tier increases registrations but reduces paid conversion. How do you decide?
Calculate incremental activation value and paid cannibalization by segment rather than looking at total registrations. Check whether free users complete the critical job, show a future upgrade signal, and include people who otherwise would have paid. If net revenue, margin, or target-customer value falls below a precommitted guardrail, tighten quotas, change eligibility, or stop the test. Top-of-funnel growth cannot conceal downstream loss.
Follow-up 4: Sales says deals are lost on price, but customer interviews identify an integration gap. Which source do you trust?
Return to the evidence for each opportunity. Price may be an easy label to record, while integration may also be a superficial reason. Review decision participants, trial behavior, procurement communication, and the selected alternative. Use an independent, structured loss interview where necessary. Allow multiple reason dimensions with confidence levels instead of forcing every case into one category. Product action should target a repeatable cause that actually changes customer choice.
Follow-up 5: If the competitor copied our strongest differentiator, should we accelerate the next feature?
First determine whether the original capability has become a category requirement and whether customers actually value the feature, data, workflow, service, or ecosystem. If the differentiator has become commoditized, the value proposition does need to evolve, but the next response does not have to be another feature. The company might deepen the outcome, reduce switching friction, strengthen distribution or service, or accept the capability as a baseline. Customer evidence, defensibility, and economics still determine the choice.
Follow-up 6: When should the company create a permanent free tier?
Consider permanent design only when target-segment behavior consistently shows that free access is a primary entry requirement, free users have a validated activation and distribution path, upgrades or another business model can cover service costs, and limited tests have passed cannibalization, support, abuse, and brand guardrails. Define quotas, eligibility, upgrade triggers, existing-customer migration, and exit rules. A permanent free tier is a business-model decision, not a promotional switch.