---
title: "How Do I Start Building a Customer Success Function From Scratch?"
description: "Building a customer success function starts with ownership, not tooling: name who owns renewal and handoff, pick one number, tier the book, run a weekly review."
topic: "Customer Success"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Head of Customer Success, Founder"
published: 2026-09-04
modified: 2026-09-04
source: https://gaintrace.com/explore/customer-success/building-a-customer-success-function-from-scratch
---

# How Do I Start Building a Customer Success Function From Scratch?

*Building a customer success function*

**Short answer:** Building a customer success function starts with ownership, not tooling. In week 1, write down who owns renewal, adoption, the sales handoff and escalations today, and get one number (gross revenue retention or logo churn) the CEO will accept. In month 1, tier the book and put a named owner on every account. In quarter 1, run one weekly risk review and one playbook. Buy nothing until those exist.

**Key takeaways**

- Your first deliverable is an ownership map: for renewal, adoption, handoff, escalation and expansion, name the person who owns it today, even if the answer is nobody.
- Pick one retention number before you pick a health score. Gross revenue retention over a trailing twelve months is the safest first choice because finance can reproduce it.
- Tier the book by ARR and renewal date in month 1, and give the top tier a named owner with a 90-day plan. Everyone else gets a lighter, scheduled touch.
- Run one weekly 30-minute risk review from week 5. It is the habit that turns a group of CSMs into a function.
- Do not buy a customer success platform in the first 90 days. Of 3,628 public reviews of the three most-reviewed platforms, 734 name setup, configuration or admin as the main downside; you are not ready to absorb that yet.

You were handed customer success last month, and building a customer success function from scratch is now your job. There is a team, or at least some people with CSM in their title, and they spend their days reacting to escalations from support and account management. Nobody can tell you who owns the renewal. Usage data exists somewhere in the product database. Sales closes a deal and the customer finds out about it when an invoice arrives.
This is the most common starting position we see, and building a customer success function from it is less about frameworks than about sequencing. The order below is the one that survives contact with a real company: ownership first, then a number, then segments, then rhythm, and tooling last.

## What does 'undefined' mean when you inherit a CS function?

> **The ownership map:** The ownership map is a one-page list of every recurring customer job with exactly one name against it: renewals, escalations, onboarding, expansion, product feedback, billing questions. We use it as the first artefact of a new CS function because an undefined function is rarely missing effort, it is missing single owners. Anything with two names or none is the work.

The phrase people use is that customer success is undefined, but when you read what they describe, it is always the same four gaps. Nobody owns the renewal. Nobody owns adoption after go-live. There is no handoff from sales. And there is no number that says whether any of it is working.

> "I don't think anyone truly owns adoption, outcomes, retention, or the overall customer experience. We also don't have easily accessible metrics or usage data, nor do we have any handoff between Sales and Service. I also don't know who owns the renewal process."
>
> — New head of customer success, mid-size software company, r/CustomerSuccess, 2026

The same shape shows up at 15-person startups. One CSM three months into a new role described it as 'a completely open field. I have the freedom to build it however I want, but there isn't a defined place for me within the organization or a clear set of responsibilities.' That freedom is the trap. Without an ownership map you will build a process for whatever shouted loudest last week.

So the job in the first 90 days is not to design customer success. It is to close those four gaps in a fixed order, and to resist everything else until they are closed.

## What should I define in week 1, month 1 and quarter 1?

Each column below is a deliverable you can show your CEO. If you can only do one thing in each period, do the first row.

|  | Week 1 | Month 1 | Quarter 1 |
| --- | --- | --- | --- |
| Ownership | A one-page map naming who owns renewal, adoption, sales handoff, escalation and expansion today | One name per account for the top tier; a named renewal owner for every contract in the next 180 days | A written RACI that sales, support and finance have signed |
| The number | Trailing 12-month gross revenue retention, computed from billing, agreed with finance | GRR and logo churn split by segment; the list of every account that churned in the last 12 months with a one-line reason | A quarterly target the CEO set with you, and a monthly forecast against it |
| Segments | A list of every account with ARR and renewal date, in one sheet | Three tiers by ARR and renewal proximity, with the touch model for each written in one sentence | Tiers reviewed once against the churn list: did the tiering predict anything? |
| Rhythm | A 30-minute weekly meeting on the calendar for week 5 onward | The weekly risk review running: five accounts, five decisions, owners named | The risk review plus one monthly review with sales on handoffs and one with product on top churn reasons |
| Playbook | None. Write down what CSMs do today, in their words | One playbook, for the most common risk you found in the churn list | Two playbooks running, one of them for the sales-to-CS handoff |
| Tooling | Your CRM and a spreadsheet | The spreadsheet, now with the tier, owner, renewal date and one risk flag per account | A decision on whether to buy, made from the [signs the spreadsheet has stopped working](/explore/customer-success/when-to-buy-customer-success-software) |

## How do I run an ownership audit in the first week?

Spend the first week asking one question of every customer-facing team: who does this today? Not who should. Write the answers down, including 'nobody' and 'it depends', because those are the findings.

**The week-1 ownership audit**
- [ ] Who sends the renewal notice, who negotiates price, and who signs off a discount? Ask sales, finance and the CSMs separately and compare answers.
- [ ] When a deal closes, who tells the customer what happens next, and within how many days? Pull the last five closed deals and check.
- [ ] Who is told when usage drops, and how would they find out? If the answer is 'the customer tells us', write that down.
- [ ] Where does an escalation go, and who decides it is resolved? Follow the last three to their end.
- [ ] Who can see billing, CRM, product usage and support tickets for one account without asking someone else? Usually the answer is nobody, which is the root of most of the rest.
- [ ] Which accounts renew in the next 180 days, and does each one have a person who would notice if it went quiet?

The audit produces your ownership map, and it also produces the churn list: every account lost in the last twelve months with one line on why. Ask for it from finance, not from the CSMs, because finance has the invoices. That list is the most valuable document you will own in the first quarter.

## What does a 90-day plan for building a customer success function look like?

This plan assumes a team of two to eight CSMs and somewhere between 100 and 1,000 accounts. Scale the numbers, not the order.

1. **Days 1 to 5: run the ownership audit and get the churn list.** Interview every customer-facing lead. Ask finance for twelve months of cancellations and downgrades with the revenue attached. Do not propose anything yet.
2. **Days 6 to 10: agree the number.** Compute trailing twelve-month gross revenue retention from billing. Walk it through finance until they accept the definition. Show the CEO the number and the churn list on the same page. This is the moment you get a mandate; the [cost of churn calculator](https://gaintrace.com/tools/cost-of-churn-calculator) turns the churn list into a revenue figure the room will remember.
3. **Days 11 to 20: build the one sheet.** Every account, one row: ARR, renewal date, owner, last meaningful contact, one risk flag. Pull ARR from billing and renewal dates from contracts, not from memory. If this takes more than two weeks, the data problem is your real week-1 finding.
4. **Days 21 to 30: tier the book and name owners.** Three tiers by ARR and renewal proximity. Top tier gets a named owner and a written 90-day account plan. Middle tier gets a scheduled quarterly touch. Bottom tier gets a monthly automated check-in and a human only on a risk flag. The [150-accounts-per-CSM coverage model](https://gaintrace.com/explore/playbooks/accounts-per-csm-coverage-model) has the maths for how many accounts each tier can hold.
5. **Days 31 to 45: start the weekly risk review.** Thirty minutes, same time every week. Each CSM brings the accounts they are worried about. The output is five decisions with owners, written in the sheet. This is the first thing you do that makes customer success a function rather than a set of people.
6. **Days 46 to 60: write the first playbook.** Pick the most common reason in the churn list and write the response to it as a sequence of steps with timings. One playbook, run by hand. If the top reason is 'never adopted', the playbook is the [sales-to-CS handoff](https://gaintrace.com/explore/onboarding/time-to-value-onboarding-complete-but-churned).
7. **Days 61 to 75: fix the handoff.** Agree with sales what CS receives on every closed deal: goals the customer stated, promises made, the stakeholder who signed. Make it a form in the CRM that the deal cannot close without.
8. **Days 76 to 90: report, then decide on tooling.** Show the CEO the number, the tiers, the review cadence, the playbook and the handoff. Only now ask whether the spreadsheet is holding. Most teams at this size find it holds for another quarter or two; the [decision rule for buying](https://gaintrace.com/explore/customer-success/when-to-buy-customer-success-software) tells you when it stops.

## Which number should a new CS function report first?

Gross revenue retention, trailing twelve months. It is the share of last year's recurring revenue you still have from those same customers, before any expansion. It cannot exceed 100%, finance can reproduce it from invoices, and it does not flatter you the way a net figure can.

Report [net revenue retention](https://gaintrace.com/explore/revenue/how-to-calculate-net-revenue-retention-b2b-saas) beside it once expansion is tracked, and compare both against your own segment rather than the whole market; [how much churn is normal](https://gaintrace.com/explore/retention/how-much-churn-is-normal-b2b-saas) depends heavily on contract size. Leave the [customer health score](https://gaintrace.com/blog/customer-health-score) until quarter 2. A health score built before you have a churn list is a weighted average of whatever data was easy to reach.

Most new CS leaders reverse this. They build the score first because it feels like the professional thing to do, then discover six months later that it never predicted the accounts that left.

## What stalls a new customer success function in its first quarter?

By week 6 most new leads have hit one of three walls. Each has a specific unblock.

- **You cannot get the data.** Usage lives with engineering, billing with finance, and nobody has time. Ask for one export, once, of three fields: account, last login date, active seats. Put it in the sheet by hand. A monthly manual export beats an integration that is still in the backlog.
- **Sales and CS disagree about who owns the renewal.** Do not fight it in the first quarter. Take renewal preparation (the account review, the risk flag, the value summary) and leave the commercial close where it is. Ownership of the close follows whoever demonstrably knows the account.
- **The team is fully reactive and cannot free a day for any of this.** Take the bottom tier off them entirely with a scheduled automated check-in. The [coverage model](https://gaintrace.com/explore/playbooks/accounts-per-csm-coverage-model) shows how many hours that returns.

> "Just setting up [the platform] has revealed gaping holes in both our data and CS strategy that we weren't fully cognizant of."
>
> — Director, small business SaaS, public G2 review

That reviewer found the holes during a platform implementation. You can find the same holes in week 1 with a sheet and six interviews, at no cost, and then choose what to fix first.

## What do I do if it is 90 days in and nothing has moved?

Retention is a lagging number; do not expect GRR to move in a quarter. What should have moved is the leading evidence. Check these four before deciding the plan failed.

1. Does every account renewing in the next 180 days have a named owner and a risk flag that was updated in the last 30 days? If not, the sheet became a document instead of a system.
2. Did the weekly review produce decisions that were acted on? Count them. Fewer than three a week means the review is a status meeting.
3. Did the playbook run on real accounts, and did you record the outcome? A playbook that has never been run is a diagram.
4. Has the churn list from month 1 grown by accounts you were not warned about? If yes, the risk flag is measuring the wrong thing, usually a lagging one like login count. [Spotting churn risk early in scattered data](https://gaintrace.com/explore/retention/early-warning-signs-of-churn-scattered-data) covers the earlier signals.

> **What a good day-90 report looks like:** Eight CSMs, 620 accounts, $9.4M ARR. GRR (TTM) 87%, agreed with finance. Churn list: 41 accounts, $1.1M, top reason 'no owner after go-live' (17 accounts). Tiers: 60 / 180 / 380. Weekly review running for seven weeks, 31 decisions logged, 24 closed. One playbook (post-go-live check-in at day 14 and day 45) run on 22 accounts. Handoff form live for three weeks, 9 of 11 deals complete. Tooling decision: spreadsheet holds until Q2; revisit when the second playbook starts.

## Should the first 90 days include buying a platform?

No. We read 3,628 public reviews of the three most-reviewed customer success platforms, and 734 of them (20%) name setup, configuration, implementation or admin effort as the main downside. A function with no ownership map and no churn list is not in a position to absorb that. You will configure the platform around whatever you assumed in week 2 and spend quarter 2 unwinding it.

The exception is when the sheet cannot be built at all because data lives in four systems nobody can join. That is a real reason to look at tooling early, and [what implementing a CS platform takes](https://gaintrace.com/explore/customer-success/customer-success-platform-implementation-what-it-takes) is the honest read on the cost before you do.

## How does GainTrace help a new CS lead start?

[GainTrace](https://gaintrace.com/) is built for the day-90 decision, when the sheet is holding but barely. It connects billing, CRM, product usage and support into one account view without an admin to configure it, so the ownership map, tiers and risk flags you built by hand live in a system the team keeps updated. [Customer success on GainTrace](https://gaintrace.com/solutions/customer-success) covers the operating layer, and [churn prediction](https://gaintrace.com/solutions/churn-prediction) replaces the manual risk flag with one scored from the data.

## Frequently asked questions

### What should a new head of customer success do in the first 30 days?

Run an ownership audit (who owns renewal, adoption, handoff and escalation today), get twelve months of churned accounts from finance with the revenue attached, agree a trailing twelve-month gross revenue retention figure with finance, and build one sheet with every account's ARR, renewal date and owner. Propose nothing until those four exist.

### Do I need a customer success platform to build a CS function?

Not in the first quarter. A CRM plus one well-kept spreadsheet holds a book of a few hundred accounts for a team of two to eight. Of 3,628 public reviews of the three most-reviewed platforms, 734 name setup or admin as the main downside, so buy once ownership, a number and a weekly rhythm exist and the sheet is visibly failing.

### Who should own renewals, sales or customer success?

In the first 90 days, split it: customer success owns renewal preparation (account review, risk flag, value summary, the 180-day watch list) and sales keeps the commercial close. Ownership of the close tends to follow whichever team demonstrably knows the account, so win the preparation first and revisit the close in quarter 2.

### What is the first metric a customer success team should report?

Trailing twelve-month gross revenue retention, computed from billing and agreed with finance. It cannot exceed 100%, it is reproducible from invoices, and it does not hide churn behind expansion the way net retention can. Add net revenue retention and a health score later, once a churn list exists to validate them against.

### How do I tier accounts when I am starting from nothing?

Three tiers by ARR and renewal proximity. The top tier (typically the accounts making up half of ARR) gets a named owner and a written plan. The middle tier gets a scheduled quarterly touch. The bottom tier gets a monthly automated check-in and a human only when a risk flag fires. Review the tiers once a quarter against the accounts that churned.

### How long before a new customer success function shows results?

Retention itself lags by a renewal cycle, so do not judge it inside a quarter. By day 90 you should be able to show leading evidence: every account renewing in 180 days has an owner and a fresh risk flag, the weekly review is producing decisions that get acted on, one playbook has run on real accounts, and no churn arrived that the risk flag had not raised.

## How this was researched

We read 3,628 public G2 reviews of the three most-reviewed customer success platforms and 1,328 threads from r/CustomerSuccess, r/SaaS, r/sales and r/startups, and pulled every thread where someone described being handed customer success without a definition. The 90-day sequence is the order we have seen hold up; the review counts come from grepping the corpus for setup, configuration, implementation and admin language in the 'dislike' text of each review.

## Sources

- [r/CustomerSuccess: Customer Success is undefined, where do I start?](https://reddit.com/r/CustomerSuccess/comments/1th4a7a/customer_success_is_undefined_where_do_i_start/)
- [r/CustomerSuccess: CSM at a startup (no established structure for the role)](https://reddit.com/r/CustomerSuccess/comments/1w6iydf/csm_at_a_startup/)
- [r/CustomerSuccess: What am I missing? Are these problems common?](https://reddit.com/r/CustomerSuccess/comments/1vl48tg/what_am_i_missing_are_these_problems_common/)
- [G2: Customer Success software category (source of the 3,628 public reviews)](https://www.g2.com/categories/customer-success)

## Next steps

Bring the churn list and the one sheet; we will show you the same book with billing, usage and support joined. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).