Rebuilding customer communication at scale
How we rebuilt the customer communication system for a scaling YC-backed FinTech.
The challenge
As this YC-backed FinTech grew, communication became one of the first things to break.
Students, partner schools, and employer partners were all receiving information through different channels, at different times, with different levels of clarity. Answers lived in inboxes, Slack threads, support tickets, and one-off documents. The same questions kept coming up - not because customers weren’t paying attention, but because the system itself was fragmented.
Internally, the team felt it too. Support volume was climbing, clarifying questions were constant, and time that should have gone into improving the product was being spent re-explaining how things worked. Nothing was “on fire,” but everything felt harder than it needed to be.
The issue wasn’t effort or care - it was the absence of a clear, shared communication system that could scale with the business.
What we did
We treated communication like an operational system, not a messaging problem.
First, we reviewed support tickets, inboxes, and internal threads to identify the questions customers asked most often - and where confusion consistently appeared across the lifecycle. That gave us a concrete map of what information mattered, when it was needed, and who needed to own it.
From there, we consolidated fragmented instructions, FAQs, and guidance into a single, reliable source of truth that both customers and internal teams could reference confidently. This wasn’t about writing more documentation - it was about making existing knowledge usable.
We then redesigned lifecycle communication around proactive messaging. Instead of waiting for questions to come in, we created clear, timed communications that answered predictable questions before they became support requests. Common friction points were addressed upfront through structured emails, onboarding materials, and partner-facing resources.
Finally, we defined ownership and feedback loops. Each major communication stream had a clear owner, and incoming questions were tracked to continuously refine messaging rather than handled as isolated incidents.
Impact
- Reduced inbound customer support volume by approximately 50%
- Maintained consistently high CSAT scores (>90%) across customer segments
- Decreased internal clarification requests by establishing standardized, reusable responses
- Improved customer onboarding and engagement through clearer expectations and guidance.
What happened next
With communication stabilized, the business started to feel lighter.
Customers spent less time searching for answers and more time moving forward confidently. Partner schools and employers had clearer expectations, which reduced back-and-forth and sped up coordination. Internally, teams were able to focus on product improvements and growth initiatives instead of answering the same questions repeatedly.
Just as importantly, communication stopped being reactive. Instead of responding to confusion, the team could anticipate it - which made scaling feel deliberate rather than chaotic.
This work didn’t just reduce noise. It created trust, alignment, and momentum across the entire ecosystem - all without adding complexity or headcount.
Dealing with something similar?
If growth has made your systems harder to manage instead of easier to run, we can help you bring clarity, structure, and momentum back into the work. Let's talk!