The churn driver is almost certainly happening before renewal, not during product use — start with the renewal conversation itself.

Your three symptoms together point in one direction: support is quiet, people are using the product normally, but they are choosing not to renew. That pattern means the product isn't broken and customers aren't angry — they're just deciding it's not worth keeping. The exit decision is happening at the moment of renewal, which means something changed in that moment or in the weeks leading up to it.

---

Root-Cause Chain (Five Whys)

Step	Question	Most likely answer given your symptoms
1	Why are renewals dropping?	Customers are saying no at the renewal point
2	Why are they saying no if usage is flat?	Flat usage often means customers stopped getting new value — the product still works, but it stopped mattering
3	Why would that change in the last two months?	Something shifted: their budget, their priorities, a competitor offer, or the perceived ROI of your product
4	Why wouldn't that show up in support tickets?	Support tickets reflect problems with the product. A value or ROI problem is silent — customers just quietly disengage and leave
5	What is the fixable root cause?	You don't yet know which of the three triggers (budget, value drift, or competitive pressure) is driving it — that is the investigation

---

Where to Look First — Ordered by Likelihood

1. Talk to the accounts that churned (this week, not next month) This is the single highest-value action. With a small customer base, you can call or email every churned account from the last two months personally. Ask one open question: "What was the main reason you decided not to renew?" Don't offer a discount yet. Just listen. You need the pattern before you can fix anything.

2. Check what happened at the renewal conversation Did your renewal process change? Did pricing change? Did the person who handled renewals change? Did you stop doing check-in calls before renewals were due? A process change two months ago would produce exactly this timing. Pull your renewal records and compare what you did in months where churn was low versus the last two months.

3. Look at flat usage more carefully Flat overall usage can hide a warning sign: customers who stopped using the features that matter most. Log in to your analytics and check whether churned customers were using your core features in the 60 days before they left, or whether they had quietly drifted to surface-level use. A customer who logs in but doesn't do the thing your product is built for is already halfway out the door.

4. Check for a shared characteristic in churned accounts With a small base, patterns are visible. Were the churned accounts all from one industry? One company size? One acquisition channel? One sales rep? One pricing tier? One contract length? If they share something, that something is a clue.

5. Look outside your product for a market-level trigger Two months ago: did a competitor launch or cut prices? Did something shift in the economy that would tighten budgets for your typical buyer? Did a regulation change affect your customers' industry? You won't find this in your own data — you need to search for it. Ask churned customers directly whether they switched to something else, and if so, what.

---

What You Can Rule Out (Based on What You Said)

• Product bugs or reliability issues — support tickets are normal, so this is unlikely the primary driver.
• Onboarding failure — renewals involve existing customers, not new ones.
• Sudden mass dissatisfaction — that would show in support volume.

---

The Single First Action

Contact every account that churned in the last two months. Personal outreach — not a survey form. Aim to speak to at least half of them by the end of this week. The answer to your churn problem almost certainly lives in those conversations, and right now you're guessing without that data. Everything else can wait until you've done this.

---

What to Watch For

Warning signal	What it would mean
Multiple churned customers mention the same competitor	Competitive pressure — you need a response
Customers say they "just didn't need it anymore"	Value drift — your product stopped solving their problem actively enough
Customers mention budget cuts or cost reviews	External economic pressure — pricing or packaging change may help retention
Customers say they never heard from you before renewal	Relationship gap — proactive success outreach is the fix
No clear pattern across churned accounts	The cause may be idiosyncratic — keep investigating per account

Pricing Decision: Friday Board Recommendation

The Contradiction You Must Resolve First

Before the CFO vs. sales argument can be decided, the math has to be read correctly.

Your stated figures do not reconcile cleanly. 200 customers × $49 = $9,800 MRR. You have reported $60,000 MRR. That implies an average revenue per account of $300 — roughly 6× the $49 list price. This matters enormously: if your actual ARPA is ~$300, you are not competing on the same price axis as a $19/month rival at all. You are selling a higher-commitment product to a different buyer profile, and the three accounts you lost were likely anomalously large anchors pulling the average up.

Assumption used to proceed: The $60k MRR figure is treated as correct. The 200-customer count and $49 price are assumed to reflect a mix of plan tiers, annual contracts billed monthly, or add-ons that inflate ARPA beyond the base price. The analysis below holds regardless — but the board must see the reconciled numbers before Friday, because the right pricing move looks completely different if ARPA is $300 vs. $49.

---

What the Current Numbers Actually Say

Metric	Value	Implication
MRR	$60,000
Customers	200	ARPA = $300/mo (not $49)
Monthly churn rate	12%	24 customers lost per month
Implied monthly revenue churn	~$7,200	12% of $60k
Annual revenue at risk from churn	~$86,400	If churn holds flat
Months to halve customer base	~5.4	At 12% monthly, compounding

12% monthly churn is the emergency, not the price gap. At this rate, you lose half your customer base in roughly five months. No pricing decision — up or down — fixes a 12% monthly churn. A company cutting from $49 to $19 with 12% monthly churn just loses money faster. A company raising prices with 12% monthly churn accelerates the departure of marginal accounts. Both moves are cosmetic without diagnosing why customers are leaving.

---

Why the CFO and Sales Are Both Wrong As Stated

The CFO's "raise prices" case rests on the logic that you serve a premium segment willing to pay more. If your ARPA is $300, that may be partially true — but raising list price when churn is 12% monthly signals desperation to the market, removes fence-sitters, and does nothing about the retention problem. The three accounts you just lost did not leave because the price was too low.

The sales team's "cut to $19" case is a race to the floor against a competitor who has already anchored that number. Matching $19 requires roughly 2.6× your current customer count just to hold $60k MRR — from a base that is actively shrinking. It also permanently repositions the brand at the low end, makes the unit economics of your current customer acquisition cost almost certainly negative, and gives away the margin needed to fix the product gaps driving churn.

---

The Actual Decision: Three Options

Option A — Defend the Premium Tier, Attack Churn Directly (Recommended)

Price: Hold at $49 base / defend current ARPA. Do not raise, do not cut the headline number. Instead:

1. This week: Conduct exit interviews with the three lost accounts. Get the real reason — price is the stated reason in 80% of exits; it is the actual reason in roughly 20%. You need to know if this is a value gap, a feature gap, or a sales execution problem before Friday.
2. This week: Pull churn cohort data. Is the 12% concentrated in accounts under 90 days old (onboarding failure), accounts on the $49 base plan (price-sensitive segment that should never have been sold to), or accounts above $300 ARPA (a product-fit problem at scale)?
3. For the board Friday: Present a 90-day churn reduction target. 12% → 6% monthly doubles your effective customer lifetime from ~8 months to ~17 months. At $300 ARPA, that is the difference between a $2,400 LTV and a $5,100 LTV — it dwarfs any pricing move.
4. Structural price move (30 days): Introduce a $19/month entry tier that is genuinely limited (no API, no integrations, 1 user seat) — not to compete with the $19 rival directly, but to stop losing price-sensitive prospects before they evaluate you, while protecting the premium tier's positioning.

Risk: Board wants a decisive pricing answer; "hold and fix churn" reads as indecision. Frame it correctly: the pricing decision IS the churn decision.

---

Option B — Controlled Price Reduction to $29

Price: Cut from $49 to $29. This is a meaningful signal without hitting the floor.

• Narrows the gap to the $19 competitor to $10 (from $30), reducing the "obvious" switch narrative.
• Reduces MRR by up to ~$4,000/month on new business if ARPA assumptions hold — manageable if churn improves.
• Does NOT recover the three lost accounts unless you proactively reach back with the new price.
• Still leaves you with a 12% monthly churn problem that will consume the benefit within two months.

Risk: Signals price sensitivity to your installed base, triggering renegotiation requests from existing customers. Must be paired with a churn intervention or it accelerates the revenue decline.

---

Option C — Raise to $79 (CFO's Direction, Stress-Tested)

Price: Raise to $79. This only works if:

• ARPA is genuinely $300+ (suggesting annual plans or bundles already price the product correctly and $49 is only the floor)
• Churn is concentrated in low-ARPA accounts you are willing to lose
• You have a differentiated feature or outcome that the $19 competitor cannot match and that you can articulate in one sentence

At 12% monthly churn, a price increase will accelerate churn among price-sensitive accounts in months 1–2 before any quality-of-remaining-base benefit materialises. This option is only viable if you simultaneously launch an aggressive retention program and have the runway to absorb 2–3 months of elevated churn.

---

What to Put in Front of the Board Friday

Item	Content
Decision required	Pricing tier structure — not just a single number
Non-negotiable prior action	Reconcile the MRR/customer/price discrepancy before the meeting
The real problem to name	12% monthly churn; pricing is downstream of this
Recommended motion	Hold headline price; launch $19 entry tier; commit to 90-day churn target of ≤6%
Alternative motion	Cut to $29 with explicit 60-day churn intervention attached
What not to present	A unilateral raise without a retention plan — it will not survive the first churn report after the decision

---

Immediate Actions Before Friday (Ranked)

1. Today: Reconcile $60k MRR against 200 customers and $49 price — produce the real ARPA breakdown by plan tier.
2. Today/Tomorrow: Get one live call with each of the three churned accounts. One sentence from a churned customer outweighs any internal pricing model.
3. Wednesday: Pull churn cohort segmentation — where in the customer lifecycle is the 12% concentrated?
4. Thursday: Draft two board slides: (a) the churn math showing what churn reduction is worth vs. what a price cut is worth, (b) the recommended tier structure.
5. Friday: Present Option A as the recommendation with Option B as the conservative alternative. Do not present Option C without the churn data to support it.

---

This analysis treats financial and strategic content as informational; it is not a substitute for advice from your finance or legal counsel on contract and pricing obligations to existing customers.