Build versus buy
Build, Buy, or Improve What You Already Have?
A framework for deciding between buying a Customer Success platform, building a lightweight internal tool, improving your existing stack, or delaying the decision entirely.
2 min read
Customer Success Architecture
Find the real cause of your retention problem before you spend money fixing the wrong thing.
I help B2B SaaS leadership teams diagnose post-sale constraints, design the right Customer Success operating model, and build a sequenced roadmap for retention and profitable growth - grounded in evidence, not a default assumption about where the problem lives.
Fig. 01 - The Method
Evidence
Structured interviews, retention data, and lifecycle analysis replace assumption with a documented record of what's actually happening.
Diagnosis
Root-cause hypotheses are tested against the evidence and attributed to their actual source - ICP, sales, product, onboarding, support, CS, capacity, or organizational design.
Architecture
The operating model, org design, and systems needed to address the confirmed root causes are designed around your business, not a generic template.
Sequence
Findings and design decisions are ordered into a roadmap that reflects dependencies, not just priority - some fixes have to happen before others can work.
Execution
Your team runs the roadmap, with Transformation Leadership or Fractional CCO support available where the internal team needs additional capacity or authority.
The executive problem
You may have a retention problem. That doesn't mean you have a CSM problem.
Retention outcomes are produced by every function that touches the customer - who you sell to, what sales promises, how mature the product is, how onboarding runs, how support performs, and yes, how Customer Success executes. Treating every retention problem as a CS staffing or skills gap is one of the most common and most expensive misdiagnoses in B2B SaaS.
Symptoms are not root causes
The same symptom can point to several different diagnoses.
Here are common executive assumptions about what's wrong, next to the range of underlying causes the evidence more often supports.
Symptom
Renewals are slipping or coming in flat
Common assumption: "Our CSMs aren't managing renewals well enough."
Possible underlying causes
- Renewal ownership was never clearly assigned between sales and CS
- Deals were sold with promises the product doesn't yet deliver
- Forecasting relies on CSM gut feel instead of usage or engagement data
- CSMs are managing too many accounts to engage meaningfully before renewal
Symptom
Customers churn shortly after onboarding
Common assumption: "Onboarding needs a better playbook."
Possible underlying causes
- Sales sold to accounts outside the actual ICP
- Time-to-value is genuinely long because of product complexity, not process
- Expectations set during the sales cycle didn't match what implementation could deliver
- Handoff from sales to post-sale loses critical context every time
Symptom
Net revenue retention is declining
Common assumption: "We need to invest more in expansion and upsell motions."
Possible underlying causes
- Gross retention is the real problem and expansion is masking it
- Product adoption plateaus below the level needed to justify expansion
- Pricing and packaging don't align with how customers actually get value
- Account coverage is too thin for CSMs to identify expansion signals
Symptom
The CS team feels constantly reactive
Common assumption: "We need more CSMs."
Possible underlying causes
- CSMs own support escalations, onboarding, and renewals with no prioritization framework
- Health scoring doesn't exist or isn't trusted, so everything looks urgent
- Systems and data are fragmented, so CSMs spend hours assembling information instead of acting on it
- Capacity was never modeled against actual account complexity
Symptom
Leadership disagrees about what's wrong
Common assumption: "We just need to align on strategy."
Possible underlying causes
- Different functions are looking at different, disconnected data sets
- Nobody has done a structured, cross-functional root-cause analysis
- The disagreement is really about decision rights, not facts
Symptom
A new CS platform was purchased but adoption is low
Common assumption: "We picked the wrong tool."
Possible underlying causes
- The underlying process and data problems the tool was meant to solve were never fixed first
- Ownership of health scores and workflows inside the tool was never assigned
- The team wasn't resourced to configure and maintain the platform after go-live
Why sequencing matters
Acting on the wrong diagnosis is expensive - and hard to undo.
Every response to a retention problem - hiring, buying software, reorganizing - is a reasonable idea in the right situation and a costly mistake in the wrong one. Getting the sequence right matters as much as getting the individual decisions right.
What the wrong diagnosis tends to produce
- A hire added to an undefined process, which just puts another person inside the same constraint
- A platform purchase that formalizes a broken process into an expensive, well-configured dashboard
- A reorganization that disrupts the team without addressing the actual root cause
- More competing priorities stacked onto a team that was already at capacity, with nothing taken off their plate
Why sequence, not just substance, matters
- Hiring before the process is defined multiplies the cost of a bad structure - now you're paying more people to operate inside it.
- Buying software before data and ownership are clear tends to produce a well-configured mirror of the same broken process.
- Reorganizing before the root cause is confirmed risks solving the wrong problem with the most disruptive tool available.
- Adding priorities without removing any just distributes the same capacity across more competing demands.
The diagnostic approach
Evidence, then diagnosis, then architecture, then sequence, then execution.
The same method underlies every engagement, whether the outcome is a diagnostic roadmap, an operating model redesign, or ongoing fractional leadership.
- 01
Evidence
Structured interviews, retention data, and lifecycle analysis replace assumption with a documented record of what's actually happening.
- 02
Diagnosis
Root-cause hypotheses are tested against the evidence and attributed to their actual source - ICP, sales, product, onboarding, support, CS, capacity, or organizational design.
- 03
Architecture
The operating model, org design, and systems needed to address the confirmed root causes are designed around your business, not a generic template.
- 04
Sequence
Findings and design decisions are ordered into a roadmap that reflects dependencies, not just priority - some fixes have to happen before others can work.
- 05
Execution
Your team runs the roadmap, with Transformation Leadership or Fractional CCO support available where the internal team needs additional capacity or authority.
The flagship engagement
The Post-Sale Operating Blueprint
A fixed-scope diagnostic and roadmap - not a questionnaire, not a generic audit. It combines leadership interviews, retention and churn analysis, lifecycle mapping, and a rigorous build-versus-buy review into a sequenced plan your team can execute.
What leadership receives
- Executive diagnosis summarizing the findings in plain, decision-ready language
- Root-cause hypotheses, each supported by the specific evidence behind it
- A customer lifecycle map showing ownership at every stage from sale to renewal
- An ownership and accountability map across sales, CS, support, and product
- A capacity and workload assessment for the post-sale team
- A revenue-at-risk analysis grounded in your account data
- A systems and data architecture review
- A build-versus-buy recommendation where software is a live question
Who this is for
Built for leadership teams at complex, growing B2B SaaS companies.
Roughly $8M to $75M in ARR, with enough customer and organizational complexity to produce real post-sale operating problems
Retention, NRR, onboarding, capacity, forecasting, or organizational pressure that leadership can feel but hasn't fully diagnosed
A Customer Success leader who recently left or was just hired, creating a natural point to establish an independent baseline
Evaluating Gainsight, ChurnZero, Vitally, a Salesforce build-out, or an AI tool - and wanting a sanity check before signing
Leadership that knows something isn't working, but suspects the internal narrative about why might be incomplete
Typical executive audiences: CEOs, COOs, CFOs, CROs, Chief Customer Officers, Heads or VPs of Customer Success, operating partners, and board members.
Engagement options
Diagnose, design, implement, or lead - start wherever fits.
The Post-Sale Operating Blueprint is the easiest first step and the natural gateway into the others, but each service also stands on its own.
01 - Diagnose
Post-Sale Operating Blueprint
A fixed-scope diagnostic and roadmap that finds the real cause of a retention or post-sale performance problem before you spend money fixing the wrong thing.
Review this service02 - Design
Customer Success Architecture
Design of the post-sale operating model: organizational structure, capacity model, customer journey, renewal ownership, and the systems that support them.
Review this service03 - Design
Build vs. Buy Advisory
A vendor-neutral assessment of whether the right answer is a Customer Success platform, better use of your existing stack, a lightweight internal build, or a delay until process is fixed.
Review this service04 - Implement
Transformation Leadership
Hands-on leadership for the first 90 days of executing a roadmap: standing up processes, reporting, tools, governance, and operating cadence.
Review this service05 - Lead
Fractional Chief Customer Officer
Selective, part-time executive leadership of the post-sale organization - offered only when a company has the alignment and authority to make it work.
Review this serviceVendor-neutral
Considering Gainsight, ChurnZero, or a Salesforce build-out?
Before you buy, it's worth testing whether the constraint is actually a software gap, or a process and data problem software won't fix. The Build vs. Buy Advisory gives you an independent answer - buy, build, improve, hybrid, or delay.
Explore Build vs. BuySelective by design
Fractional CCO leadership, only when it can actually work
This isn't unlimited execution across support, onboarding, CS, renewals, and strategy at once. It's selective executive leadership for companies with an aligned sponsor, clear decision rights, and the resources to execute.
Check fit criteriaThe founder's background
An operator, not an outside observer.
- More than a decade in Customer Success and support leadership roles across B2B SaaS organizations
- Experience building and scaling global Customer Success and support functions from early stage through growth
- Direct experience with retention, renewals, customer operations, executive reporting, AI-enabled workflows, and organizational design
- A career spent as an operator inside the function, not as an outside observer of it
- 20%
- Reduction in churn
- Achieved while leading a Customer Success and support organization at WordStream supporting more than $30M in ARR.
- 120%
- Net revenue retention
- During a measured period leading Customer Success at CorralData.
- 98%
- Enterprise gross revenue retention
- Alongside an NPS of 100, during a measured period leading Customer Success at Localize.
- 100%
- CSAT across 200+ surveys
- Measured across more than 200 customer surveys while leading Customer Success at OutSystems.
Figures reflect team and organizational outcomes achieved with the teams led along the way - not results attributable to one person alone. Full context is available on the About page.
Fit matters
This works best under specific conditions.
- You're a B2B SaaS company, roughly $8M to $75M in ARR, with enough customer and organizational complexity for a post-sale operating problem to exist
- There is an executive sponsor - typically a CEO, COO, CFO, CRO, or CCO - who wants an independent, evidence-based answer
- You're willing to grant access to the data and people needed to do the analysis properly
- You want a diagnosis and roadmap, not a guaranteed number or a pre-decided conclusion
From the practice
Recent insights
Post-sale metrics
How Long Should Customer Success Improvements Take to Affect GRR?
GRR and NRR are lagging metrics. Here's a realistic timeline for when operational changes, leading indicators, and retention metrics should each move - and why treating them the same causes bad decisions.
2 min read
Retention diagnosis
How to Diagnose a SaaS Retention Problem
A structured method for finding the real cause of a B2B SaaS retention problem before committing budget to a hire, a platform, or a reorganization.
3 min read
Common questions
Questions leadership teams ask before reaching out
Why act now instead of waiting to see if things improve?
Retention problems compound. A cohort that churns this quarter reduces the base you're renewing and expanding next quarter, and the operational habits causing it don't fix themselves. Acting doesn't mean rushing a decision - it means getting an accurate diagnosis before the next budget cycle, board meeting, or renewal wave makes the problem more expensive to fix.
Why not just hire another CSM?
Sometimes that's the right answer. Often it isn't - adding headcount to an undefined process or an unclear ownership model just adds another person operating inside the same constraint. The diagnostic tests whether capacity is actually the bottleneck before you commit to a hire.
Why not buy a Customer Success platform immediately?
Software can't fix a process or ownership problem, and a platform implemented on top of bad data usually just makes bad data more visible, faster. The Build vs. Buy Advisory and the diagnostic both test software readiness before recommending a purchase.
Why not have our current Customer Success leader solve this?
Often they should, and often they're the right person to execute the roadmap. But asking someone to diagnose a problem that may originate outside their own function - in sales, product, or onboarding - asks them to investigate territory they don't control and can't objectively assess. An outside diagnosis removes that conflict.
What makes this work independent?
This practice has no software to sell, no staffing bench to fill, and no incentive to recommend a bigger engagement than the evidence supports. The recommendation might be to hire, to buy software, to reorganize, to do nothing differently for now, or some combination - whatever the evidence points to.
What happens after the diagnosis?
You receive a roadmap built to be executed by your own team. Some clients take it from there. Others bring in Transformation Leadership for the first 90 days, pursue a scoped design engagement, or - if the fit criteria are met - discuss fractional CCO leadership.
How will success be measured?
Every roadmap includes leading indicators and success measures specific to your business, not a generic promise. Operational changes are usually visible within 30 to 90 days. Leading customer indicators tend to move within 3 to 9 months. GRR and NRR are lagging outcomes and typically take 12 to 18 months or more to fully reflect the changes, especially in annual-contract businesses.
How long will outcomes take to show up in our numbers?
It depends on your contract structure and sales cycle. Monthly-contract businesses tend to see retention metrics move sooner because the feedback loop is shorter. Annual-contract businesses typically need a full renewal cycle - often 12 to 18 months - before GRR and NRR fully reflect operational changes.
Next step
Ready to find out what's really driving your retention numbers?
A short conversation is enough to know whether the Post-Sale Operating Blueprint is the right next step for your team.