u/Late-Development-543

Around when we hit 18 people, we lost a client we thought was solid. They'd been with us two years. Renewal conversation was scheduled. Then a week before the call, they emailed saying they'd been having conversations with another vendor for three months and were moving the engagement.

The work was good. They told us as much in the offboarding call. The actual reason was that we'd been doing a thing they couldn't see for a thing they did see.

What we couldn't see: their internal contact had taken on a new manager who started asking "what is this vendor actually delivering for us." We never knew that conversation was happening because nothing on our side prompted it to come up.

What they saw: long stretches between visible artifacts. We were heads-down working, but from their angle they couldn't distinguish "working" from "stopped working." Three to four weeks of silence between deliverables, repeated across months, started to look like indifference. The other vendor showed up with weekly check-ins and a roadmap document and "looked engaged" in a way we didn't.

The mistake wasn't quality. The mistake was thinking that good work speaks for itself. It does, but only to people who can see the work. Internal contacts are not the only people who matter. Their managers, their new managers, their finance team, the random VP who asks "what are we paying these people for" all matter, and they only see what your client tells them about you.

What we changed. Weekly status note to the main contact, two sentences, what we did and what's next. Quarterly recorded video to the contact's manager, 5 to 10 minutes, here is what your team is getting from us. Monthly invoice has a one-line summary of the work it's billing for, in language someone non-technical could read.

None of that is brilliant. None of it changed the work. It changed the conversations the client was having when we weren't in the room.

Three years later we have only lost one more client to the silence problem (different kind of silence, different fix). For small business owners running client work, the question is not "am I doing good work" but "can the people who decide whether we keep getting hired see the work without asking us."

What did your version of this look like? Did you find the cadence before or after you lost someone?

Around when we hit 18 people, we lost a client we thought was solid. They'd been with us for two years. Renewal conversation was scheduled. Then a week before the call, they sent an email saying they'd been having conversations with another vendor for three months and were moving the engagement.

The work was good. They told us as much in the offboarding call. The actual reason was that we'd been doing a thing they couldn't see for a thing they did see.

What we couldn't see: their internal champion had taken on a new manager who started asking "what is this team actually delivering for us." We never knew that conversation was happening because nothing on our side prompted it to come up.

What they saw: long stretches between visible artifacts. We were heads-down working, but from their angle they couldn't distinguish "working" from "stopped working." Three to four weeks of silence between deliverables, repeated across months, started to look like indifference. The other vendor showed up with weekly check-ins and a roadmap document and "looked engaged" in a way we didn't.

The mistake wasn't quality. The mistake was thinking that good work speaks for itself. It does, but only to people who can see the work. Internal champions are not the only people who matter. Their managers, their new managers, their finance team, the random VP who asks "what are we paying these people for" all matter, and they only see what your client tells them about you.

What we changed. Weekly status note to the champion, two sentences, what we did and what's next. Quarterly recorded video to the champion's manager, 5 to 10 minutes, here is what your team is getting from us. Monthly invoice has a one-line summary of the work it's billing for, in language someone non-technical could read.

None of that is brilliant. None of it changed the work. It changed the conversations the client was having when we weren't in the room.

Three years later we have only lost one more client to the silence problem (different kind of silence, different fix). For founders running services businesses, the question is not "am I doing good work" but "can the people who decide whether we keep getting hired see the work without asking us."

What did your version of this look like? Did you find the cadence before or after you lost someone?

When we hit about 12 people, my co-founder and I sat down and decided we were going to be a "documented company." We blocked time. We wrote SOPs. We argued about format. We standardized in Notion with templates and tags and an index page. Two years later we have 73 SOPs, every one of them written by someone who actually does the work.

Here's the part that's stupid. I just ran a spot check across our team. Out of the 14 people whose work touches our customers, six told me they hadn't opened the relevant SOP in the last 90 days. Two told me they didn't know the SOP existed. Three said they used to read it but stopped because "I know the steps now." Only three out of fourteen follow the documented process consistently.

This isn't a documentation problem. We have great documentation. It's a problem of the documentation being inert. The Notion page sits there. Nobody's forced to open it before they do the work. Nobody captures evidence of having done it. The completion of one step doesn't trigger the next. The page is a reference. The work is something else entirely.

The thing that surprised me is that the SOPs were not written by ops people writing policy. They were written by the people who actually do the work. They're accurate. The team isn't ignoring them out of disagreement. The team is ignoring them because there's no friction between "I know what I'm doing" and "I'm doing it the way we said we would."

A few specific failure modes. New hire onboarding has a 47-step Notion doc. New hires get the link, they skim, get pulled into work, and nobody knows which steps got done. We've had two people miss security training because there's no system that gates work behind the training.

Quarterly access reviews are documented. Everyone has "completed access review" on a Notion page. We just had an auditor sample-test and find that two roles hadn't had a real review in eight months. The page was confidently checked off. The review didn't happen.

Customer kickoff has a five-page Notion runbook. Every kickoff goes off the runbook in the first 20 minutes because the lead thinks they remember it. The runbook gets a new section added every quarter that nobody reads.

I don't think the answer is more documentation. I think the answer is that documentation and execution are different problems and we've been treating them like the same one. A Notion page is not a process. It's a description of a process. The actual process is what happens when work meets people, and the page has no power to make that consistent.

What I'm curious about. For the SaaS folks who got out of this, what did the next thing look like. Did you put guardrails inside another tool. Did you train differently. Did you give up on enforcement and hire people who already do it right. I genuinely don't know what the right answer is, but the "more docs" answer has failed us twice now.

We're 20 people now and still finding places where the lack of early documentation is costing us. Hindsight: we should've documented our quoting process before we hired our second salesperson. Each rep developed their own quoting style, and now the price/scope mismatch on the same service is genuinely bad. Took us 18 months to undo it.

The first SOP we DID document was client onboarding because it was bleeding revenue. That paid off fast. Wish I'd doubled down on documentation earlier and on more processes.

Curious what others would have documented first if they could go back. The patterns I keep hearing: sales/quoting (mine), client onboarding, hiring and new-employee onboarding, quality control or delivery review, cash flow and invoicing.

What's yours, and what did the lack of it cost you specifically?

We ran QBRs for years like it was gospel. Big quarterly meeting with the customer's exec sponsor, agenda built two weeks ahead, slide deck with usage data, success metrics, roadmap previews. Took our CSMs roughly 6-8 hours per QBR including prep, the meeting itself, and follow-up.

We were doing this for 40 accounts. Do the math: ~80 hours of CS effort per quarter just on QBR mechanics. Bigger than the deliverable work in some weeks.

Two things kept nagging.

Customers rescheduled QBRs constantly. About a third moved or got cut short. The execs we wanted in the room often sent a delegate. Felt like we were the only ones who thought the meeting mattered.

And our renewal rate wasn't actually correlating with QBR quality. Customers who had stellar QBRs churned. Customers who skipped half their QBRs renewed. The relationship looked random.

So we tested. Stopped scheduling QBRs for Q3 last year. Replaced them with two things: a bi-weekly 15-minute async health update (Loom video + 2-paragraph email, no meeting), and on-demand exec syncs the customer could request when they wanted one.

Result: zero customers complained. Two customers asked for an exec sync, both renewed and expanded. Quarterly renewal rate went from 87% to 91%. NPS in the customer base went up 8 points.

The hard learning: "strategic" QBRs were mostly status updates the customer didn't want and we didn't need. The actual strategic conversations happened in onboarding, mid-cycle problems, and renewal negotiation. The quarterly cadence forced a fake-strategic meeting that fooled everyone.

What we kept:

• Onboarding kickoff (genuine strategic moment)
• Mid-cycle problem reviews (when something is off, we deep-dive)
• Renewal conversation (real commitment moment)
• On-demand exec syncs (customer-driven, not calendar-driven)

What we dropped:

• The quarterly cadence
• The slide deck
• "Stakeholder alignment" agenda items that didn't actually align anything

Curious if anyone else has run this experiment. Not arguing QBRs are universally wrong, for very large enterprise accounts they may genuinely matter. But for B2B SaaS at our scale (~40 accounts, mostly mid-market), the QBR was theater.

We're a 20-person B2B company. Every closed deal hands off from sales to our customer success / delivery side, and our onboarding metrics were ugly. New customers took an average of 23 days to their first meaningful outcome. Renewal conversations 11 months later were brutal because half the customers couldn't articulate what they'd actually achieved.

We tried the obvious things first. Better onboarding documentation, kickoff call template, and video walkthrough library. Real onboarding checklist with timed tasks. None of it moved the needle on time-to-value.

The real problem was upstream of onboarding. Sales would close a deal on a specific outcome the prospect cared about, that signal would not survive the handoff, and CS would start onboarding from scratch with a generic plan. The customer would feel like the second meeting was the first meeting all over again. "I told sales all this last week."

The fix was a one-page handoff brief, mandatory, written by sales before the deal closed. Five fields:

• Specific outcome the customer wants in 90 days, in their own words
• The internal champion's name and what they're being measured on
• The two or three things they tried before talking to us
• Anything they explicitly told us NOT to do (like "don't replace our existing tool")
• The deadline they care about and why

CS reads the brief before the kickoff call. First meeting opens with "you told sales you want X by Y date because of Z, here's how the next 30 days deliver against that." Customer feels seen. We start from week one with a real plan, not a discovery loop.

Time-to-value dropped from 23 days to 12. NPS in the first 30 days went from 41 to 67. The hardest part was getting sales to fill in the brief consistently. We made it a hard gate in our CRM. Deal can't move to closed-won without it. That part took two months of friction.

The lesson for us was that customer success doesn't start at onboarding. It starts at the handoff before onboarding. Most of what looks like onboarding failure is information loss between teams.

Curious what others are doing here. Has anyone built something similar that works without becoming bureaucratic? The brief itself is fine; the bigger problem was making it a non-negotiable in our deal flow.

Quick context: small services business, mostly financial planning and consulting work, regulated industry. Our compliance load was eating about 3 weeks per audit cycle and we were running 4 cycles a year. That's 12 weeks of compliance prep before client work even gets touched.

We weren't drowning because we lacked SOPs. We had SOPs. We had a Notion page. We had a Google Drive folder organized by year. The problem was nobody actually ran the SOPs, they reviewed them once, signed off, and the work happened separately. So when audit time came, we were reconstructing what we did from email, Slack, and memory. Every time.

The change that actually moved the needle was treating each compliance control as a recurring workflow with an owner and a deadline, where the evidence got captured at the time of the work, not assembled later. So when we did a quarterly access review, the actual review steps were assigned to me or our ops lead, with deadlines, and the evidence was the workflow run itself. No separate write-up. No reconstruction.

After about 6 months: audit prep dropped from 3 weeks to about 3 days. We hit zero compliance findings for the first time. We didn't add headcount, we just stopped doing the same work twice (once for the work, once to "evidence" the work).

The mental shift was realizing audit prep felt hard because we were doing it twice. The first time was the actual work. The second time was reconstructing the work for the auditor. Once the workflow captured the work and the evidence in the same step, the second pass disappeared.

For anyone running compliance at a similar size: what part of your audit cycle is reconstruction, and what part is genuinely new work? The reconstruction part is usually 60-70% of the time. That's where to attack first.

For about a year our biggest churn driver was not product issues or pricing. It was onboarding. Customers would sign, get onboarded, and within 60 days a chunk of them were already disengaged. By month 3 they were gone.

We kept blaming CS. The team is not proactive enough. The kickoff calls are not good enough. The training is not thorough enough. We tried fixing all of that. Better playbooks, more touchpoints, faster response times. None of it moved the number.

Then someone on our team asked a simple question during a churn review: "did we actually know what this customer expected when we onboarded them?"

The answer was no. Not really. CS was walking into kickoff calls with a name, a contract value, and maybe a sentence from the CRM about the use case. Everything else they had to discover on the call. Which meant the first 2-3 weeks of onboarding were spent figuring out what the customer actually needed instead of delivering it.

The fix was one structural change. Sales fills out a handoff brief before the deal is marked closed-won. Four fields:

What does the customer expect to achieve in the first 30 days

What was specifically promised during the sales cycle

Who is the internal champion and who is the decision maker

Any known risks or concerns raised during the sales process

CS reviews the brief before the kickoff call. If something does not match what we can deliver, it gets flagged and addressed before the customer is involved. Not after.

That one change cut our "week 2 confusion" problem in half. CS stopped discovering mismatches during onboarding and started resolving them before onboarding began.

The second thing we changed was smaller but also mattered. We stopped treating onboarding as a series of meetings and started treating it as a checklist with milestones and owners. Account setup by day 2. Integration live by day 5. Training complete by day 10. First value milestone by day 20. Each step has one person responsible and if it stalls everyone knows before the customer has to ask.

Our 90-day retention improved by about 15 points over two quarters. Not because we changed the product or the pricing. Because we fixed the handoff.

For CS teams dealing with early churn, how much visibility do you actually have into what sales promised before the deal hits your desk?

Heard this story from someone I know who works in IP licensing at a large research university. Thought it was worth sharing because the lesson applies to any business running on spreadsheets and manual tracking.

Their team of 22 people managed $10M in annual licensing revenue across hundreds of active license agreements. Some of these agreements were 20+ years old. Everything was tracked in spreadsheets and email.

The problem was not that people were lazy or incompetent. The problem was that with hundreds of active licenses, things slipped through the cracks. Billing schedules got missed. Industry IP fees were not charged at the correct rate. Nobody caught it because there was no system making those steps mandatory and visible.

They eventually moved to a system where every licensing process ran as a structured workflow. Each step had an owner, a deadline, and a completion log. If a step was not completed, it did not just sit in a spreadsheet waiting for someone to notice. It escalated.

What happened next was not planned. A team member was running through his standard billing workflow and noticed that several inventions were not being billed correctly. The workflow surfaced the discrepancy because it forced him to verify the billing details as a required step. He investigated and they recovered roughly $200,000 in missed industry IP fees.

That is not an efficiency story. That is an enforcement story. The billing step existed before. But in the spreadsheet world, it was optional in practice. In the workflow, it was mandatory. The process caught what the spreadsheet could not.

A few other things that changed once they moved to enforced workflows:

Federal utilization reporting went from taking days per report to hours. They file 400+ of these per year.

20+ year old license agreements finally had full audit trails showing who did what and when.

Compliance with federal Bayh-Dole requirements went from manual tracking to systematic enforcement.

The takeaway for me was simple. If your business depends on someone remembering to check a spreadsheet, you are carrying risk you cannot see. The spreadsheet does not tell you what was missed. The workflow does, because missing a step is not an option.

Curious how others here manage processes that involve money or compliance. Are you still running on spreadsheets and docs or have you moved to something more structured?