---
title: "How Do I Track Tasks Across Hundreds of Customers? One List"
description: "To track tasks across hundreds of customers, keep one list, let dates and events create the tasks instead of your memory, triage weekly and work by account."
topic: "Playbooks & Operations"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Customer Success Manager, Onboarding Manager"
published: 2026-09-04
modified: 2026-09-04
source: https://gaintrace.com/explore/playbooks/track-tasks-across-hundreds-of-customers
---

# How Do I Track Tasks Across Hundreds of Customers?

*A system, not a better memory*

**Short answer:** To track tasks across hundreds of customers, stop relying on memory and run five rules: one list and nowhere else, tasks created by dates and events rather than by you, a 45-minute weekly triage, a view grouped by account so each customer gets one visit, and a short list of things you no longer track. A CSM with 600 accounts needs the triggers more than the list.

**Key takeaways**

- Keep exactly one list. Every ask that arrives by email, call, chat or Slack gets a line in it within the same sitting, or it does not exist. The list can be a spreadsheet, a CRM task view or a notes app; the rule is that there is only one.
- Let the calendar and the data create tasks. Renewal minus 90 days, onboarding day 7, an invoice 14 days overdue and a usage drop should each add a task without you remembering to add it.
- Triage once a week for 45 minutes: close, delegate, date or delete every open line, then pick the 15 accounts that get a visit this week.
- Work by account, not by task. Open the account, do everything it needs in one sitting, log one note. Ten tasks across ten accounts cost more than ten tasks on one.
- Stop tracking anything that is a habit, a hope or someone else's job. A list of 300 open lines is a list nobody reads.

You need to track tasks across hundreds of customers, and the tasks are small: follow up after the onboarding call, reply about a subscription change, send the quote someone asked for on Tuesday, resend the invite a customer could not see. You are good at the analysis, the problem solving and the conversations. What slips is the little stuff. You read an email, decide to get to it later, and later never arrives. Nothing major has gone wrong yet, but a customer joined a call you had forgotten to confirm, and you can feel the count of missed things going up.
This page is for the CSM or onboarding lead at that point, often the only one covering the book, sometimes with ADHD, always with more customers than any memory can hold. The answer is not a better memory or a better app. It is a system with five rules, a table of where each kind of task should live, a daily and a weekly routine, and a list of things to stop tracking.

## Why can I not track tasks across hundreds of customers from memory?

The CSM whose r/CustomerSuccess thread this page answers covers over 600 customers with a manager and one support person, owns onboarding, implementation, retention conversations and upgrades, and describes the failure precisely.

> "Lately the workload is increasing and I've missed a few things. Nothing major, but e.g. a customer asking for a quote, a customer saying they couldn't see a meeting that we'd booked, so I got on the call just now and realised I hadn't responded to them and sent a new invite. Sometimes I'll read the email and say "I'll get to that later" and then forget."
>
> — r/CustomerSuccess, 2026

Read that as a description of a mechanism rather than a lapse. An email arrives, gets read, and the decision to act is made in the reader's head. At that moment the task exists in one place: memory. Nothing else in the day is designed to bring it back. With 40 accounts, memory gets away with this most days. With 600, the arrival rate of small asks is higher than the rate at which any person can recall them, and the misses are arithmetic, not character.

The review corpus says the same thing from the other side. In our themed sample of 1,386 sentences where reviewers of the three most-reviewed customer success platforms describe the problem they bought the tool for, 114 mention tasks, to-dos or reminders, and the phrase that recurs is "falls through the cracks". In the complaints, 75 sentences mention tasks, and the sharpest one is from a reviewer who still runs a second list beside the platform.

> "I still use task management tool alongside [the platform]. Not enough reminders to have a full to-do list from [the platform]."
>
> — Mid-market SaaS, public G2 review

That reviewer has the problem this page is about: two lists. The rest of the page is how to get to one, and how to make it fill itself. If the book is also too big for the hours, that is a different problem, and the [accounts per CSM coverage model](https://gaintrace.com/explore/playbooks/accounts-per-csm-coverage-model) is the page for it; the system below assumes the hours exist and the tracking is what fails.

## Which five rules replace remembering?

> **The one-list system:** The one-list system: every commitment lands in one list, created by a trigger rather than by memory, with a date and an account attached. Memory scales to about 40 accounts. Past that, the question is not how organised you are but whether the task existed without you thinking of it.

Every task system that survives contact with a large book follows the same five rules, whatever tool it runs in. Each one removes a decision you are currently making in your head.

1. **One list.** A task that is not on the list does not exist. Not in a starred email, not in a Slack thread, not in a sticky note, not in your head. The moment you decide "later", the ask goes on the list with the account name and a date, in the same sitting, before you open the next message. This is the rule the r/CustomerSuccess thread is asking for, and it costs about eight seconds per ask.
2. **Triggered, not remembered.** Anything that recurs on a date or an event is created by the date or the event, never by you. Renewal minus 90 days, onboarding day 7 and day 28, invoice overdue 14 days, usage down 40% in 30 days, a sponsor change in the CRM. A spreadsheet with a renewal column and a formula can do the date-based ones today; the data-based ones are what a platform is for, and the table in the next section shows which is which.
3. **Weekly triage.** Once a week, 45 minutes, every open line gets one of four verbs: close, delegate, date or delete. Nothing stays undated. Then pick the accounts that get a visit this week. Triage is where the list stays short enough to trust.
4. **Account-level, not task-level.** Do not work down a list of 40 tasks across 30 accounts. Group the list by account, open one account, do everything it needs (the reply, the quote, the invite, the note), log once, close. Switching accounts is the expensive move; a task list sorted by due date makes you switch on every line.
5. **Stop tracking some things.** Habits (check the inbox), hopes ("reach out to everyone in the quiet tier") and other people's jobs (support tickets, the AE's renewal paperwork) do not belong on the list. They make it long, and a long list stops being read.

## Where should each kind of task live?

The one-list rule does not mean everything is typed in by hand. It means everything ends up in one view. Most of the tasks in a CSM's week come from seven sources, and each has a natural home and a natural trigger. The table shows what we would set up for a book in the hundreds, with no new tools assumed beyond a CRM or a spreadsheet and a calendar.

| Task source | Examples | Where it lives | Trigger | How it reaches the list |
| --- | --- | --- | --- | --- |
| Customer asks by email or chat | Send a quote, change the subscription, resend an invite, answer a pricing question | The list, with the account name | Manual, at the moment you read it | Eight seconds: account, one line, a date. Then archive the email; the list owns it now |
| Commitments you made on a call | "I'll send the integration guide", "I'll check with product" | The call note, then the list | Manual, within 10 minutes of the call ending | Write the commitments as the last three lines of the note and copy them to the list before the next meeting |
| Onboarding milestones | Kickoff held, day-7 check, day-28 check-in, first integration live | The onboarding tracker (sheet or CRM) | Date, relative to signature | A formula or workflow creates the task on the day; you never add "check on new customer" |
| Renewal dates | Prep at minus 90, outreach at minus 60, paperwork at minus 30 | Billing or the CRM renewal field | Date, relative to renewal | Same formula. Pair it with the [renewal call preparation checklist](/explore/playbooks/renewal-call-preparation-checklist) so the task carries its own steps |
| Risk and usage signals | Logins down 40%, invoice overdue, sponsor left, support ticket escalated | Product analytics, billing, support tool | Event in the data | The one source a spreadsheet cannot do alone; a weekly export and a filter is the manual version, a platform is the automatic one |
| Internal requests | Product wants a customer to interview, finance wants an address, sales wants an intro | The list, tagged internal | Manual | Batch them to one afternoon a week; they are the first thing to delegate at triage |
| Side projects | Segment the book, build the health score, write the onboarding sequence | A separate project doc, one line on the list | Weekly, at triage | The list holds only this week's next step, never the whole project |

Two of the seven sources are manual and they are the ones that were getting missed. Notice that the fix for both is the same small ritual: capture in the same sitting, with the account name. Everything else on the table should already be arriving on its own, and if it is not, that is the first thing to build, because those are the tasks that cost renewals when they slip.

The r/CustomerSuccess thread on requests that are not support tickets puts the failure mode in one line: "If they only live in the CSM's notes or Slack messages they are very easy to miss." Notes and Slack are capture points, not homes.

## How do I set it up in an afternoon?

1. **Pick the one place and empty everything else into it.** A CRM task view if your team already lives there, a spreadsheet if it does not, a notes app only if you work alone. Then spend an hour moving every starred email, open Slack thread and sticky note into it, one line each, with account and date. The relief of that hour is the argument for the system.
2. **Add three columns: account, date, source.** Account so you can group by it. Date so nothing is open-ended. Source (customer, commitment, onboarding, renewal, signal, internal, project) so triage can delete a whole category at once when the week is bad.
3. **Build the date triggers.** From the renewal date column: minus 90, minus 60, minus 30. From the signature date: day 7, day 28. A spreadsheet formula that lists every account whose trigger date is this week is enough. In a CRM, one workflow per trigger. You should never again type "prep for renewal".
4. **Decide the data triggers you can get weekly.** Even without a platform, a weekly export from product analytics and billing filtered to "usage down 40% in 30 days" and "invoice overdue 14 days" gives you the two signals with the most lead time. [Spotting churn risk early across scattered data](https://gaintrace.com/explore/retention/early-warning-signs-of-churn-scattered-data) lists the rest with their lead times.
5. **Book the triage and the daily 15 minutes as recurring meetings with yourself.** Friday 45 minutes for triage, every morning 15 minutes for the day's plan. Decline meetings that land on them. A routine that lives in your intentions is the same as no routine, which is the point of the whole page.
6. **Write the stop list.** Five to ten things you are no longer going to track. The section below has our defaults. Pin it to the top of the list so that triage can check new lines against it.

## What does the daily and weekly routine look like?

The system holds only if two short routines run without fail. Together they cost about two hours a week, which is less than the time currently spent re-reading the inbox to find what was missed.

| When | Length | What you do | What you do not do |
| --- | --- | --- | --- |
| Every morning, before the inbox | 15 minutes | Open the list grouped by account. Pick the accounts you will visit today (usually three to five) and the trigger tasks due today. Block the time for them in the calendar | Read email. The inbox is a capture point; opening it first lets it set the day |
| Every time an ask arrives | 8 seconds | Account, one line, a date. Archive the message | Reply now unless it takes under two minutes and you are not in the middle of an account |
| After every call | 10 minutes | Note with the commitments as the last lines; copy commitments to the list | Move to the next call with the note unwritten |
| Friday | 45 minutes | Every open line: close, delegate, date or delete. Check new lines against the stop list. Choose next week's 15 accounts | Do any of the tasks. Triage that turns into work never finishes |

**The Friday triage, line by line**
- [ ] Is it done? Close it. Be honest about lines that are done in spirit.
- [ ] Is it someone else's job? Delegate it with a date and remove it from your list; a line that tracks another person's work is a line you will nag from.
- [ ] Is it on the stop list? Delete it.
- [ ] Is it older than 30 days with no date? Either it gets a date this week or it gets deleted. There is no third option.
- [ ] Which 15 accounts get a visit next week? Trigger tasks first (renewals, onboarding days, signals), then the accounts with the most open lines, then whoever has waited longest.

## What should I stop tracking?

A list is only trustworthy if everything on it is real. Most CSM lists carry a third of lines that are not tasks at all. These are the ones we would delete on the first triage, with the reason.

- Habits. "Check the inbox", "update the CRM", "review health scores". These are routines with a slot in the calendar, not tasks with an end.
- Hopes. "Reach out to all quiet accounts", "be more proactive with tier three". Turn them into one trigger (usage down 40%) or delete them. A wish with no trigger fires never.
- Other people's work. Support tickets, the AE's paperwork, the engineer's bug. Track the date you need to hear back, not the work itself.
- Whole projects. "Build the health score" lives in a project doc. The list holds this week's next step only.
- Anything with no account or no date after 30 days. If it was not worth dating in a month, it was not a task.
- Reading. Newsletters, product release notes, the thread you meant to get to. They go to a reading folder, and the folder is not the list.

The stop list does more for a book in the hundreds than any of the tools. The CSM in the thread was doing onboarding, implementation, support, account management and strategy; the list that tries to hold all five jobs at task level is unreadable by Wednesday. Half of what makes it unreadable is on the list above.

## Which rules hold up when focus and memory are the constraint?

The thread asked specifically to hear from CSMs with ADHD, and a second r/CustomerSuccess thread, "ADHD and the bottomless workload", describes the shape of the job that makes it hard: no finite set of projects, a book where every account is always due for something.

> "Fellow CSMs with focus and memory issues, I assume we're all hyper-organized with a million reminders set. This is surely true for people with typical retention and ability to concentrate too. But what other personal and professional habits help you keep up and not feel overwhelmed all the time?"
>
> — r/CustomerSuccess, 2026

We are not clinicians and this is not medical advice. What we can say is which parts of the system above do the most work when attention and working memory are the scarce resource, because they are the parts that remove decisions rather than add reminders.

- Capture beats recall, so make capture the shortest possible action. One keyboard shortcut or one always-open tab. If capture takes more than ten seconds, it will be skipped exactly when it matters.
- A million reminders is the problem, not the fix. Reminders interrupt; triggers schedule. Move recurring work to date and event triggers so the list, not a notification, tells you what today holds.
- Grouping by account turns a hundred small context switches into ten large ones. That is the single biggest reduction in load the system offers.
- Time-box the routines and stop when the box ends. A triage that is allowed to run long becomes a dreaded task in its own right and gets skipped.
- Put the routines in the calendar as meetings with yourself. External structure is the point; intention is what the system exists to replace.
- Make "done in the same sitting" the rule for anything under two minutes, and make the list the rule for everything else. The dangerous middle, "I'll remember", is removed as an option.

None of that is specific to ADHD. It is what every CSM with a large book ends up doing, and the CSMs who wrote the two threads had already worked most of it out. The system's job is to make the habits load-bearing rather than heroic.

## What does one Monday with 600 customers look like?

> **The thread's book, run through the system:** Monday, 8:45. The list has 61 open lines after Friday's triage, down from 240 before the system started. Grouped by account, it shows 14 accounts. Five have trigger tasks today: two renewals at minus 90 (the prep checklist runs), two onboarding day-7 checks, one invoice overdue 14 days. The CSM blocks 9:30 to 12:00 for those five accounts, visits each once, does everything it needs, logs one note per account, closes 11 lines. The afternoon inbox brings nine new asks. Each gets an eight-second line with account and date; three are under two minutes and are done on the spot. A post-call note at 3:20 adds two commitments to the list. By 5:00 the list is at 58 lines and 15 accounts, every line dated, and nothing lives in the inbox. The quote request from Tuesday of last week was on Friday's list with a date of today; it went out at 10:10 during the account visit, not when the customer chased.

The number that changed is not the task count. It is the number of places a task can live, which went from five (inbox, Slack, head, notes, calendar) to one, and the number of tasks the CSM had to remember to create, which went from all of them to the two manual sources in the table.

## What if the list is tidy and things still slip?

If the routine runs for a month and customers still catch you out, one of three things is wrong, and the fix for each is different.

1. **The data triggers do not exist.** Renewal and onboarding dates fire, but usage drops, overdue invoices and sponsor changes still reach you only when the customer writes in. This is the limit of a spreadsheet, and the point at which the question becomes [whether to buy customer success software](https://gaintrace.com/explore/customer-success/when-to-buy-customer-success-software). The test: count the misses of the last month; if most were events in the data rather than asks you forgot, the list was never the problem.
2. **The book is over capacity.** The list is right and the hours are not there. Run the book through the [accounts per CSM calculator](https://gaintrace.com/tools/accounts-per-csm-calculator). If the load is over 105%, the system is working and is showing you a staffing problem in writing, which is the most useful thing it can do.
3. **The team shares customers and not the list.** Two people cover the same accounts from two lists, and asks go to whoever the customer emailed last. That is a pooled-team problem, and the fix is a [shared inbox for pooled customer success](https://gaintrace.com/explore/playbooks/shared-inbox-for-pooled-customer-success) with ownership rules, not a longer personal list.

The decision rule we would use: if the misses are asks, fix capture. If the misses are dates, fix triggers. If the misses are events in the data, you have outgrown the spreadsheet. If the misses are everything, count the hours.

**Slip rate**

```
Slip rate = Commitments missed ÷ Commitments made × 100
```

Where:
- Commitment: anything you told a customer you would do, with a date. If it never entered the list it still counts as made
- Track weekly: a rising slip rate is the earliest sign the book has outgrown the coverage model, before anyone reports feeling behind

## How does GainTrace create the tasks so I do not have to?

GainTrace connects billing, CRM, product usage and support data and turns the events in them into tasks with the account context attached, so the fifth row of the table, the one a spreadsheet cannot do, arrives on the same list as everything else. [Product signals](https://gaintrace.com/platform/product-signals) fire the usage and adoption triggers, and [rescue playbooks](https://gaintrace.com/solutions/rescue-playbooks) run the renewal and onboarding sequences as dated steps, without an admin building workflows or a CSM remembering to start them.

## Frequently asked questions

### What is the best way to keep track of tasks as a CSM with hundreds of customers?

One list, and a set of triggers that fill it. Capture every ask in the same sitting with the account name and a date, let renewal and onboarding dates create their own tasks, pull usage and billing signals weekly, and triage every open line on Friday. Work the list grouped by account so each customer gets one visit. The tool matters far less than the rule that there is only one list.

### Should I use my CRM, a spreadsheet or a to-do app to track customer tasks?

Use whichever one your team already opens every day, and use only that one. A CRM task view wins if others need to see your tasks or if handoffs happen. A spreadsheet wins for date formulas and speed when you work alone. A to-do app is fine for a solo CSM but hides tasks from the team and cannot group by account well. Two of them at once is the failure mode.

### How do I stop small customer follow-ups falling through the cracks?

Remove the moment where you decide to remember. When an ask arrives, it gets a line on the list before you open the next message; when a call ends, the commitments go from the note to the list before the next meeting. Then triage weekly so nothing sits undated. Most misses come from asks that were read and deferred, and the eight-second capture is the whole fix for those.

### How often should a CSM review their task list?

Fifteen minutes every morning to plan the day by account, and 45 minutes once a week to prune. The daily review chooses; the weekly review deletes, delegates and dates. Reviewing more often than that turns the list into a place you go to feel busy. Reviewing less often lets it grow past the point where anyone reads it, which for most people is around 100 open lines.

### What tasks should a customer success manager not track?

Habits with a calendar slot (check the inbox), hopes with no trigger (be more proactive), other people's work (support tickets), whole projects (build the health score), reading, and any line that has had no date for 30 days. Those lines make the list long without making it useful. Delete them at the first triage and keep a short stop list pinned to the top so new ones are caught.

### Are there ADHD-friendly ways to manage a customer success workload?

The parts of the system that help most when attention is the constraint are the ones that remove decisions: a capture action under ten seconds, date and event triggers instead of reminders, grouping work by account to cut context switches, time-boxed routines booked as meetings with yourself, and a two-minute rule that removes "I'll remember" as an option. This is organisational practice, not medical advice; a clinician is the right source for the latter.

## How this was researched

We read the r/CustomerSuccess threads on tracking tasks across hundreds of customers, ADHD and the bottomless workload, requests that do not fit support, and inbox management, and quote them here with links. We read 3,628 public G2 reviews of the three most-reviewed customer success platforms, grouped the sentences by theme, and counted the ones that mention tasks, to-dos or reminders in the problem-we-bought-it-for and complaint sets. The five rules, the routine and the worked example are our recommendation and an illustration, not customer data.

## Sources

- [r/CustomerSuccess: How do you keep track of all your tasks in one place? Especially interested to hear from people who have ADHD or hundreds of customers.](https://reddit.com/r/CustomerSuccess/comments/1vh6ikg/how_do_you_keep_track_of_all_your_tasks_in_one/)
- [r/CustomerSuccess: ADHD and the bottomless workload](https://reddit.com/r/CustomerSuccess/comments/1teg644/adhd_and_the_bottomless_workload/)
- [r/CustomerSuccess: AI powered service desk handles support tickets fine but CSM requests fall through every time](https://reddit.com/r/CustomerSuccess/comments/1vrpm9d/ai_powered_service_desk_handles_support_tickets/)
- [r/CustomerSuccess: Whatcha doing with your inbox?](https://reddit.com/r/CustomerSuccess/comments/1tgrrrg/whatcha_doing_with_your_inbox/)

## Next steps

Empty every other place into one list this afternoon, run the Friday triage twice, and then see the data triggers arrive on that list on their own. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).