u/Character_Loss_3548

At 3-4 people, hiring was: find a good person, explain the job, they figure it out alongside you.

At 7+, it's different. The new person works alongside the team, not alongside me. The team has unwritten processes nobody has documented.

Employee #8 took 6 weeks to become productive. Not because she was slow. Because nobody could articulate "how we do things here."

Employee #9 took 3 weeks. Because #8 documented everything she had to figure out herself.

The lesson: hire in pairs. The first hire discovers the gaps. The second benefits from them. Stagger by 4-6 weeks.

At 9 people the company has outgrown "figure it out" and hasn't reached "formal onboarding." The middle is messy and nobody talks about it.

Simple practice since February. Every customer who hits 6 months gets a phone call from me. 10-15 minutes. "How's it going? Anything we could do better?"

14 calls so far. The feedback is consistently different from support tickets.

Tickets are tactical. Feature requests, bugs, billing questions.

Phone calls surface ambient friction. "I'm not sure I'm using it correctly." "There's a section I've never opened." "I almost cancelled 2 months ago but decided to try again."

Three patterns emerged that no ticket ever mentioned:

Customers don't know about features we added after they signed up. They onboarded with version 1. We're on version 3. The changelog exists. Nobody reads it.

Customers are afraid of the settings page. 14 settings. Most use 3. The other 11 create anxiety that never becomes a ticket.

The highest-risk churn signal: "I almost cancelled but stayed." Those customers are one bad week away from leaving and they've already rehearsed the decision.

The phone call is my cheapest retention tool. 10 minutes per customer. The insights are worth more than any survey.

Added a simple practice in February. Every customer who's been with us for 90 days gets a phone call from me. Not an email. A phone call. 10-15 minutes. "How's it going? Anything we could do better?"

12 calls so far. The feedback is consistently different from what our support tickets show.

Support tickets: feature requests, bug reports, billing questions. Tactical. Specific. Addressable.

Phone calls: "I'm not sure I'm using it the way you intended." "There's a section I've never opened because I don't know what it does." "I almost cancelled last month but decided to try one more time."

Three patterns emerged that no ticket had ever surfaced:

Pattern 1: customers are afraid of the settings page. They don't touch it because they worry about breaking something. We have 14 settings. Most customers use 3. The other 11 create confusion that manifests as general anxiety, not as a specific ticket.

Pattern 2: customers don't know about features we added after they signed up. They onboarded with version 1. We're on version 3. The changelog exists. Nobody reads it. They're using a version of the product that's 18 months old inside a product that's current.

Pattern 3: the highest-risk churn signal is "I almost cancelled but decided to stay." These customers are one bad week away from leaving and they've already rehearsed the decision. Without the phone call, we wouldn't know.

None of these patterns appear in support tickets because they're not problems that feel specific enough to report. They're ambient friction. The kind that builds until the customer leaves and cites "didn't get enough value" as the reason.

The phone call is my cheapest retention tool. 10-15 minutes per customer. The insights it produces are worth more than any survey or support ticket analysis.

Ran a profitability analysis by client type last quarter. Not by revenue. By actual margin after accounting for all the time each client consumes, billable and unbillable.

The results contradicted my assumptions.

High-communication clients (weekly calls, frequent emails, detailed reporting): average margin 22%. These clients generate the most revenue but consume the most unbillable support time.

Low-communication clients (monthly check-in, minimal email, standard reporting): average margin 41%. Same service. Lower revenue per client. Dramatically less time consumed.

I had been optimizing for high-revenue clients. The business was actually optimized by low-communication clients who use less of my team's time and generate nearly double the margin.

The uncomfortable discovery: the clients who "love" working with us, who email frequently, who want extra calls, who require custom reports, are the clients who cost us the most to serve. The relationship feels strong. The margin is weak.

The quiet clients who pay the invoice, review the standard report, and call once a month are the ones funding the business. They are also the ones I spend the least time thinking about because they don't demand attention.

I had been pricing based on service scope. I should have been pricing based on communication overhead. Two clients with identical scopes can have dramatically different margins depending on how much of my team's time they consume with questions, requests, and check-ins that fall outside the formal deliverables.

Now I track communication volume as a cost metric. Clients who exceed a threshold of monthly interactions get a conversation about adjusting the engagement terms or adding a communication surcharge. The surcharge has been accepted by 2 of 3 clients I've proposed it to.

The relationship that feels closest is not always the relationship that's most profitable. Sometimes it's the most expensive.