Cross-posted from noflattery.com/decide — where I ran this exact question through a council of four different frontier models and let them argue it out.

You're a solo founder at ~$8K MRR. You have runway for exactly one full-time hire. Which role unlocks the most growth?

• (A) a second engineer to ship features faster
• (B) a marketer to build a real acquisition channel
• (C) a customer-success / support hire to cut churn and free your time
• (D) a salesperson to chase larger deals

The intuitive answer for most technical founders is A — more shipping velocity. The case below is for C, and it's stronger than it looks. (With one caveat that can flip the whole thing — stick around for it.)

TL;DR: At ~$8K MRR solo, hire customer success first if churn is real or support is eating your week. If voluntary churn is under ~3% and support is light, hire a marketer instead. Engineer and sales come later.

The case for customer success first

1. Churn quietly eats growth before features can add it. At $8K MRR, 5% monthly churn is ~$400/month bleeding out before you grow an inch. Across bootstrapped SaaS in the $5–15K MRR band, the strongest predictor of reaching $50K isn't feature velocity or channel — it's net revenue retention above 90%. That's a customer-success function, not an engineering one.

2. You are the bottleneck, and support is eating you. As a solo founder you're doing product, sales, billing, and support. If support takes ~15 hours a week, that's nearly 40% of your capacity — and it's the cheapest thing to hand off. A CS hire costs less than a senior engineer or an experienced salesperson, and it buys back the hours (and the headspace) you need to think strategically again.

3. It's a research department in disguise. A CS hire generates the highest volume of qualitative signal: why people leave, what they actually use, what they'd pay more for. An engineer builds what you think users want. CS tells you what they actually need — which means the engineer you hire next builds the right thing instead of the wrong thing faster.

4. It's the only hire that makes every later hire better. Lower churn stabilizes runway → you can afford the next hire without sweating. Customer insight → aims your future engineer. Case studies and referrals → arm your future marketer or salesperson. Every other first hire operates in a silo. CS creates a feedback loop.

5. It's the role you can actually manage well right now. A marketer needs strategy and positioning you may not have yet. A salesperson needs a repeatable playbook. An engineer needs a backlog. A CS hire needs your ear and a process doc — and a bad CS hire costs ~2 months to recover from, versus ~6 for a bad engineering hire. Lowest downside, fastest correction.

The caveat that flips it

All of the above rests on one unverified assumption: that churn is your binding constraint.

If your voluntary monthly churn is under ~3% and support isn't consuming your week, you don't have a retention problem — you have an acquisition problem. Hiring CS then is a tourniquet on a paper cut while you bleed out from the top of the funnel. In that case, hire the marketer.

So before you post any job description:

• Calculate your voluntary monthly churn. Above ~3–5% with growth stalling → retention is the constraint → customer success.
• Count your weekly support hours. If it's eating your week → CS.
• Low churn + low support, healthy signups but flat top-of-funnel? → acquisition is the constraint → marketer.

The decision genuinely flips on that one number. Measure it first.

Why I framed it this way

I built NoFlattery so I could run decisions through a council of AI agents that argue instead of agreeing with you — each agent on a different model. All four independently voted C, for different reasons: the numbers, the systems leverage, the founder's bandwidth, and the compounding feedback loop. The full debate, per-model votes, and verdict for this question are here:

👉 Who should a bootstrapped SaaS founder hire first? (full council debate)

What was your actual first hire — and would you make the same call again?