Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Literally

Literally

The Book on Customer Success for MSPs
Turn quiet accounts into visible business value, without making customer success depend on heroics.
by Marnie Stockman 2021 123 pages
4.08
13 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Sell business progress, not merely trouble-free technology.

Quiet accounts can still leave. Kerrie assumed a client was satisfied because it had no recent tickets or downtime. Then its CEO called to cancel. The problem was not necessarily bad technical service. Kerrie had not made clear how the MSP was helping the business meet its goals. The book distinguishes a pleasant customer experience from customer success: good service matters, but it is not proof that the customer is getting business value.

Connect service to outcomes. The book cites figures that 80% of customers consider their experience as important as the product, and 76% expect a provider to understand their needs. These figures are attributed to Salesforce. For an MSP, the practical test is whether the client can see how technology supports its plans, manages risk, or improves operations.

Analysis

The distinction between a smooth service experience and a useful business outcome is central to recurring-revenue relationships. Clients may tolerate reliable infrastructure for years without noticing its value until a competitor offers a lower price. Translating technical work into business consequences makes that value legible. It also requires asking what the client actually prioritizes, rather than assuming security, uptime, or efficiency has equal weight for every organization. Outcome conversations are not a substitute for competent support, though. A strategic narrative cannot compensate for unresolved service failures, so MSPs need both dependable execution and credible evidence of impact.

Build a repeatable success system before personal heroics become a bottleneck.

Good intentions can break at scale. Paul, an MSP owner, built loyalty by responding personally and giving clients his cell number. As the business grew, the constant calls overwhelmed him, response times slipped, and some customers left. His strength had become a fragile operating model because service depended on one person remembering and doing everything.

Document what works. The author describes entering a Customer Success role and inheriting 20 accounts that had gone 18 months without communication. Her experience eventually included a reported retention rate above 95% across a customer base with more than $20 million in annual recurring revenue. The book argues for practices that can be repeated, documented, and measured, so a customer's experience does not collapse when a particular employee is absent or overloaded.

Analysis

This is an operations problem disguised as a relationship problem. A business that relies on personal memory has a single point of failure, much like an IT system with no backup. Documentation does not make service cold; it preserves the useful parts of individual expertise and gives teammates a way to act consistently. The caution is that a process can become a substitute for judgment if employees follow it mechanically. Good documentation should clarify what must happen and where human discretion is needed, especially when a customer's circumstances depart from the standard case.

Automate routine work, but preserve human judgment where trust is built.

Efficiency needs a human boundary. MSPs are skilled at automating technical work, and the book applies the same instinct to business reviews. Automating data collection and report preparation can save time. Automating every interaction, however, risks making managed services feel interchangeable. If clients experience only impersonal transactions, price may become the main basis for comparison.

Use technology to make people more useful. The intended balance is to automate repeatable analysis and surface signals that call for action, while keeping meaningful conversations between people. The book's example of a customer who disliked needless weekly calls shows that human contact is not automatically valuable. Engagement should be useful and appropriate to the client, not a ritual imposed because a calendar says so.

Analysis

Automation is most valuable when it removes clerical friction without removing accountability. A report assembled quickly can give an advisor more time to interpret what matters and discuss trade-offs with a client. This resembles the distinction between decision support and decision replacement: software can organize evidence, but people remain responsible for context, explanation, and consequences. The limitation is that human contact can itself become a costly default. The relevant measure is not the number of calls, but whether the interaction helps the client make a better decision or feel meaningfully understood.

Segment by client value and complexity, then match the contact cadence.

Equal treatment is not always fair service. Customer segmentation means dividing clients into groups so that communication and support can reflect their different needs. The book recommends assessing two dimensions: value to the MSP, often measured by monthly recurring revenue, and complexity, such as regulatory obligations or technology needs. Plotting clients against these dimensions helps distinguish accounts that need frequent strategic attention from those better served through lighter, more automated contact.

Choose a cadence deliberately. One customer in the book disliked weekly calls and preferred brief, responsive exchanges. Another type of client may need frequent reviews because of high risk or complex operations. There is no universal meeting schedule. The point is to decide what level of engagement creates value for each group, document it, and revise the approach when the evidence shows it is poorly matched.

Analysis

Segmentation is a practical way to allocate scarce attention, but it should not become a ranking of whose problems matter. Revenue and complexity are useful proxies for workload and business exposure, not complete measures of a client's importance. A small account can still face a severe security or continuity risk. Combining economic value with service need helps avoid that blind spot. Periodic review is also essential: company size, leadership, and regulatory exposure change, so a segment assignment should be treated as a current hypothesis rather than a permanent identity.

Treat customer health as measurable warning signals, not a gut feeling.

Look for trouble before cancellation. A customer health score is a structured estimate of an account's condition, built from signals such as sentiment, adoption of the MSP's services, leadership engagement, review attendance, responsiveness, and customer feedback. The book also flags events such as a leadership change, merger discussions, or repeated unresolved concerns. A sudden request for key system passwords may also deserve attention.

Define the scoring rules. The team should decide what counts as healthy, concerning, or at risk, then test the rules against real accounts and adjust them until the results are credible. The book warns against trusting a single variable. A score should prompt investigation and action, not pretend to predict the future precisely. Healthy customers need attention too, because preserving a strong relationship is easier than rebuilding one after it deteriorates.

Analysis

A health score makes vague concern easier to discuss across a team. It can reveal patterns that memory misses, especially when one person manages many accounts. Yet a numerical score can create false confidence: subjective ratings may vary between employees, and a simple average can hide one severe warning sign. A practical model should allow critical events to override an otherwise healthy total and should record the evidence behind ratings. The score is best understood as an early-warning instrument, not an objective diagnosis or a substitute for asking the customer directly.

Use stack alignment to reveal both risk and profitable next steps.

Know what clients actually use. Stack alignment describes how fully a customer's technology matches the MSP's preferred products and services. The book treats the MSP's stack as the set of tools it knows how to support, secure, and troubleshoot. A client using only part of it may be harder to support or exposed to gaps. The same information can reveal services the client has not adopted and may genuinely need.

Make expansion relevant. The goal is not to sell every available tool. It is to connect a missing service to a business risk or goal, making the recommendation useful to the customer and sustainable for the MSP. The book cites a 2020 Datto report finding that MSPs grew more than twice as fast as peers when they focused on increasing recurring-revenue sales and setting growth targets. That finding supports disciplined growth planning, not indiscriminate upselling.

Analysis

This idea links operational standardization to commercial strategy. A consistent technology stack can make support more predictable, while its gaps offer a structured prompt for discovery. The ethical hinge is whether a recommendation solves a real customer problem or merely improves the provider's margins. Trust depends on making that distinction visible, including explaining when an existing solution is adequate. Stack fit also cannot be treated as a proxy for customer health by itself: a client may use every recommended service and still feel ignored, poorly advised, or misaligned with the MSP's priorities.

Make each business review a strategic working session, not a ticket report.

Lead with the client's business. A Quality Business Review, often called a QBR, is a planned conversation about the customer's goals, risks, technology direction, and next steps. The book advises sending an agenda and questions in advance, then using the meeting to discuss a risk assessment, technology budgets, recommendations, and a concise executive summary. Ticket counts, spam totals, and other routine service statistics may support the conversation, but they should not dominate it.

Prepare systematically. Reviews should end with clear decisions and follow-up tasks, and the next meeting can be scheduled before everyone leaves. One MSP owner quoted in the book reduced budget preparation from more than 12 hours of manual work to about 90 minutes after automating the process. The review's purpose is not simply to create an upsell opportunity; it is to give the client a useful view of choices, costs, and business implications.

Analysis

The QBR works best as a decision forum rather than a performance recital. A forward-looking budget can reduce surprise, while a short summary helps busy executives remember what was agreed. This is a form of shared sense-making: provider and client interpret risks together before choosing action. The discipline is valuable, but the meeting must earn its time. A standardized agenda should still adapt to the client's priorities, and a polished report is not evidence of strategic value unless it improves understanding, clarifies ownership, or changes a decision.

Protect your standards with clear boundaries, even when a client is valuable.

A large contract is not a blank check. The author describes supporting a client with a $1.4 million contract whose expanding requests were repeatedly pulling engineers away from core work. She finally told the client's project manager that the company needed to make full use of what it had purchased before adding custom demands. The client accepted the boundary, later became an advocate, and paid for additional services as its needs grew.

Do not confuse care with compliance. A separate story describes a landscaping client demanding a burn during a state fire ban. The business owner refused, despite the revenue at stake, and ended the relationship. For MSPs, the equivalent may be a request that violates security practices, contractual scope, or the support model. Consistent boundaries protect the customer, the team, and the provider's ability to deliver reliable work.

Analysis

Boundaries are a form of service design. They prevent one client's exceptions from silently consuming the capacity promised to everyone else, and they make the provider's responsibilities legible. The strongest boundary is paired with an explanation and a viable alternative, rather than a reflexive refusal. Still, the book's principle should not become a license to dismiss legitimate customer feedback. Repeated demands may expose a genuine gap in the offer. Providers need to distinguish an unsafe or unsustainable exception from a signal that their standard service should change.

Build explicit playbooks for both account recovery and customer advocacy.

Prepare for both red flags and rave reviews. A recovery playbook tells a CSM what to do when a client's health deteriorates: investigate the cause, involve the right people, agree on corrective steps, and track whether the relationship improves. The book notes that MSPs use labels such as escalation or recovery process, but the name matters less than having repeatable actions.

Make advocacy easy to act on. A referral process identifies satisfied customers and gives employees a respectful way to ask for introductions. One example in the book has an MSP owner ask a happy client to connect him with someone who might benefit from a similar business review. The author recommends asking raving fans periodically, while making clear that declining is acceptable. Referrals should follow genuine value, not replace it.

Analysis

Recovery and advocacy are two different moments in a customer relationship, so they benefit from different scripts, owners, and measures. A recovery plan limits improvisation under pressure, while a referral path turns goodwill into a low-friction next step. Neither should be reduced to a scorecard target. If employees are rewarded only for saving accounts or collecting introductions, they may pressure customers or hide structural service problems. A healthy process tracks whether the underlying issue was resolved and whether the customer freely chose to advocate.

Give Customer Success its own data, dashboard, and weekly operating rhythm.

Make the work visible. The book argues that Customer Success should not have to force its work into sales or support software. A fit-for-purpose system should connect to the MSP's professional services automation platform, track segmentation, health, and opportunity, manage goals and tasks, and provide useful reporting with appropriate user permissions. The aim is to make information available for action, not to collect dashboards for their own sake.

Start small and improve. A weekly review can surface at-risk high-value accounts, upcoming business reviews, renewals, preparation work, and overdue tasks. The book's proposed sequence is to set business goals, segment clients, define contact cadences, score health, and track opportunities. A one-person MSP can begin with a spreadsheet and a few documented practices. The first useful improvement matters more than waiting for a perfect program or buying software before the process is clear.

Analysis

The most important claim here is not that every MSP needs a particular platform, but that customer work needs an operational home. When measures, tasks, and account context are scattered, handoffs become fragile and leadership cannot see emerging risk. A dashboard can strengthen coordination if it leads to specific decisions. It can also become another administrative burden if indicators are poorly chosen or disconnected from customer outcomes. The sequence matters: define the work and its meaning first, then automate what is stable enough to scale.

Analysis

The book's argument is a shift in what an MSP sells. Technical reliability remains necessary, but it no longer distinguishes a provider when clients can compare similar tools and services. The durable difference is an organized relationship that helps a customer understand risk, plan technology spending, and connect IT decisions to business aims. The narrative gives this shift a human face: Kerrie is blindsided because quiet service activity is mistaken for customer health, while Paul discovers that personal attention without a process eventually exhausts the person providing it.

The practical architecture is strong because it moves from diagnosis to operating design. Providers first decide which accounts need which level of attention, then define health signals and opportunities, and finally build repeatable reviews, recovery actions, and referral practices. The approach treats Customer Success as a cross-functional responsibility rather than a job title. This makes it usable in a small MSP where one person wears several hats, as well as in a larger company where teams must coordinate.

There are limits to the evidence. Several statistics are attributed to Salesforce, Datto, or industry consultants, but the text does not provide methods sufficient to judge how broadly they apply. The reported retention and growth figures are useful prompts, not guarantees that adopting the process causes those outcomes. Health scores also rely partly on human judgments, so they need calibration and should never replace conversation with a customer.

The book's commercial context deserves attention too: its author co-founded a company selling MSP software, and it argues for a dedicated Customer Success platform. The operational case for connected data is persuasive, but software cannot make an unclear service model strategic. The most transferable lesson is to design the cadence, measures, boundaries, and decision process first. Then use a tool to make that work easier to repeat. The underlying discipline is not more meetings or more metrics. It is making customer value visible before silence turns into a cancellation call.

Summary in 30 Seconds
Reliable technical service is necessary, but customers also need to see how IT supports their business goals. Segment accounts by value and complexity, then tailor contact to their needs. Track health through multiple signals and use warning signs to trigger investigation. Make reviews strategic, set clear service boundaries, and systematize recovery and referrals. Review account risks and follow-up tasks weekly; begin with simple tools before investing in software.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

Customer Success

Proactive customer outcomes

A business function focused on helping customers realize value from the services they buy. In an MSP, it involves understanding the customer's business, monitoring account health, coordinating proactive communication, supporting renewal, and identifying relevant opportunities. It is distinct from reactive technical support, though the two functions need to work together.

Quality Business Review (QBR)

Strategic customer review

A scheduled discussion between an MSP and its customer about business goals, technology risks, budgets, recommendations, and next steps. The book reframes the familiar QBR label as a quality business review rather than assuming that meetings must happen quarterly. The cadence should reflect the customer's needs, and the conversation should focus on decisions rather than routine ticket statistics.

Customer segmentation

Grouping clients by need

The process of dividing customers into groups so communication and service can be matched to their circumstances. The book uses client value, often represented by recurring revenue, and complexity, such as regulatory demands or technology needs, as useful dimensions. Segmentation helps an MSP decide which accounts need high-touch engagement and which can be served efficiently with lighter contact.

Customer health score

Structured account health estimate

A score built from defined indicators that helps an MSP assess whether a customer relationship is healthy, needs attention, or is at risk. Possible inputs include sentiment, service adoption, leadership engagement, review participation, and responsiveness. The score is intended to support earlier investigation and action, not to guarantee that an account will renew or replace direct communication.

stack alignment

Fit with MSP's service stack

The degree to which a customer's technology and services match the MSP's preferred stack, meaning the tools it is prepared to support, secure, and troubleshoot. Greater alignment may simplify service delivery and expose missing capabilities relevant to the customer's needs. It is both an operational indicator and a prompt for discussing risk or a potential service opportunity.

People, Process, and Product

Three operating requirements

The book's way of examining what a Customer Success program needs to work. People provide attention and judgment, process makes the work repeatable and proactive, and product or software helps organize information and surface actions. A weakness in any part can undermine the others, so an MSP can use the three areas to identify where improvement should begin.

tech-touch

Technology-led client contact

A lower-intensity engagement model that uses automated or standardized communication for accounts whose needs do not justify frequent personalized meetings. In the book's segmentation approach, tech-touch may suit lower-value or lower-complexity customers, while still keeping the MSP visible and giving clients a way to raise new needs. It should not mean abandoning the customer.

Download PDF

To save this Literally summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.34 MB     Pages: 15

Download EPUB

To read this Literally summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.43 MB     Pages: 19
Want to read the full book?
Follow
Listen2 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
600,000+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...