Both can track the same basic thing (a list of suppliers or customers with a status and a follow-up date), so the real question for a small team is which one holds up as the list grows and the tracking gets a little more complicated.
Where a spreadsheet still wins
For a short list (under about 20-30 active suppliers or accounts), a plain spreadsheet is faster to set up and everyone on a small team already knows how to use it without onboarding. Filtering and sorting a simple list of rows doesn't need anything more than that.
Where Notion pulls ahead
Once you want more than one view of the same data (a table view for data entry, a board view grouped by status for a quick visual check, a calendar view for follow-up dates), Notion keeps all of those in sync automatically, where a spreadsheet would need separate tabs or manual upkeep to fake the same thing. It's also the more natural home once the tracker needs to sit next to related documents (a policy doc, a supplier's spec sheet, meeting notes) that a spreadsheet can't hold inline.
A concrete case: the supplier outreach tracker
In the AI-assisted supplier outreach workflow, automation logs each supplier reply's summary, price, and lead time into a tracker. A spreadsheet handles that log just fine at low volume. Once you want to see, at a glance, which suppliers are in "needs negotiation" versus "waiting on samples" versus "confirmed," a Notion board view built on the same underlying data does that without a second tool.
What doesn't change either way
Neither tool replaces the actual judgment calls in supplier negotiation or customer follow-up; both are just where the tracking lives. Don't over-invest in restructuring a tracker before you actually feel the pain of the simpler version.
What columns should a supplier and customer follow-up tracker have?
Whichever tool you pick, the columns matter more than the software. This layout works for most small teams, in this order:
| Column | What goes in it | Why it matters |
|---|---|---|
| Name | The supplier or customer, written the way you'd search for them | One row per relationship, not one per message |
| Type | Supplier, wholesale customer or retail customer | Lets you filter one list instead of keeping two |
| Owner | The one person responsible for the next step | Shared ownership usually means nobody follows up |
| Status | A short, fixed list of values (see below) | Free-text status can't be filtered or grouped |
| Next action | One sentence, such as "ask for a revised quote at 500 units" | Whoever opens the row knows what to do without rereading the thread |
| Follow-up date | The date the next action is due | The column you sort by every morning |
| Last contact | The date of the last message in either direction | Shows which threads have gone quiet |
| Key terms | For suppliers: MOQ, unit price, lead time, payment terms | Lets you compare suppliers side by side |
| Link | The email thread, chat or document | Saves hunting for the original conversation |
| Notes | Anything that doesn't fit above | Keep it short; long notes belong in a linked doc |
The key terms column mirrors the four things the supplier outreach playbook asks for in every first-contact message (MOQ, unit price at your target quantity, lead time and payment terms), so a reply summary can drop straight into it.
For status, pick five to seven values and stick to them. For suppliers, something like: Contacted, Replied, Needs negotiation, Waiting on samples, Confirmed, Paused. For customers: New enquiry, Quote sent, Waiting on customer, Order placed, Follow up after delivery, Closed. Using the same names as your outreach workflow (for example "needs negotiation") means any automation that writes to the tracker doesn't need a translation step in between.
In a spreadsheet, this is one tab with the columns above, a dropdown on Status and a filter or sort on Follow-up date. In Notion, it's one database with Status as a select property, and the table, board and calendar views described earlier built on top of it. Because the structure is the same in both, outgrowing the spreadsheet later means moving the same columns into a new home, not redesigning the tracker from scratch.
When to switch from a spreadsheet to Notion: a checklist
Run through this once a quarter, or whenever the tracker starts to feel like a chore. If you tick three or more, the switch is probably worth an afternoon:
- You keep copies of the same list on several tabs just to see it grouped or sorted differently.
- You've added a column purely to fake a status board (colour codes, "1-Hot / 2-Warm" prefixes and so on).
- You regularly have to open a separate document (a spec sheet, call notes, a quote) to make sense of a row.
- More than one person updates the tracker and edits have clashed or rows have gone missing.
- Follow-up dates slip because nobody looks at the sheet unless they happen to remember.
- The notes cells have grown so long that nobody reads them.
If you only tick one or two, fix the spreadsheet first: tighten the status list, add a saved filter, move long notes into linked docs. A messy tracker usually stays messy when you move it into a new tool.
AI prompts for keeping a follow-up tracker up to date
This is where the tracker connects to the rest of an AI workflow. Two prompts cover most of it. The first turns a supplier or customer message into one tracker row:
You are helping me keep a follow-up tracker up to date.
Read the message below and return ONE row with exactly these fields:
Name | Type (Supplier / Wholesale customer / Retail customer) | Status (choose only from: [YOUR STATUS LIST]) | Next action (one sentence, starting with a verb) | Follow-up date (suggest one only if the message says something about timing; otherwise write "set manually") | Key terms (MOQ, unit price, lead time, payment terms, only if stated) | Unclear or missing (anything I should ask about)
Rules:
- Only use facts stated in the message. If a field isn't mentioned, write "not stated".
- Don't round or convert prices or quantities.
- Don't decide on my behalf whether to accept any terms.
Message:
[PASTE SUPPLIER OR CUSTOMER MESSAGE]The second turns the tracker into a short list of what needs doing today:
Below is my follow-up tracker as a table. Today is [DATE].
1. List every row where the follow-up date is today or earlier, oldest first.
2. List rows where the last contact was more than [NUMBER] days ago and the status is not Confirmed or Closed.
3. For each row, repeat the "Next action" exactly as written. Do not invent new actions.
Tracker:
[PASTE TABLE OR EXPORTED ROWS]The first prompt works the same with either tool: paste the output into a new row by hand, or let automation do it. The second works on a copied spreadsheet range or a copied Notion table view. Either way, read the result before acting on it. A summary can miss a caveat buried in the original wording, which is the same caution the supplier outreach playbook gives.
Worked example: one supplier from first reply to confirmed
Take a fictional homeware importer, "Larkfield Home", sourcing a ceramic planter from four suppliers, as an example.
- First reply arrives. Supplier B answers the first-contact message with a mix of prices, a pasted spec sheet and a line about samples. The first prompt above returns a row with Status "Replied", Next action "Ask whether the quoted unit price applies at our target quantity", MOQ and lead time filled in, payment terms "not stated", and Unclear or missing: "payment terms; whether the sample cost is refundable".
- A person checks it. Before pasting the row in, the owner rereads the original email and notices the quoted lead time was for a different glaze colour. They correct the Key terms cell, set a follow-up date three working days out and put their own name in Owner.
- Negotiation. The follow-up brings back a price above target, so Status moves to "Needs negotiation". In the spreadsheet that's a dropdown change; in Notion, the card moves to a different column on the board view.
- Samples. Once terms are agreed, Status moves to "Waiting on samples" and the follow-up date becomes a couple of days after the expected delivery.
- Confirmed. The row gets a link to the final quote and moves to "Confirmed". Nothing is deleted, so next season you can see who you worked with and why.
With four suppliers, a spreadsheet handles all of this comfortably. If Larkfield were running the same process for twenty products at once, each with spec sheets and call notes per supplier, that's the point where the Notion board and linked pages start to earn their keep.
Common follow-up tracker mistakes
- Tracking messages instead of relationships. One row per email turns the tracker into a second inbox. Keep one row per supplier or customer and update it as things move.
- No owner. A row everyone can see but nobody owns is the one that slips.
- A follow-up date with no next action. The date tells you when; the next action tells you what. You need both.
- Free-text status. "Waiting?", "waiting on them" and "pending" mean the same thing, but no filter will treat them that way.
- Building before using. Setting up a dozen Notion views before you have twenty rows is busywork. Start with one view and add the next only when you miss it.
- Pasting sensitive details into AI without thinking. Customer addresses, payment details and anything you've agreed to keep confidential don't need to go into a prompt to get a useful summary. Strip them out first.
FAQ
Should a brand-new store start with Notion or a spreadsheet? Start with a spreadsheet. Move to Notion when you notice you're duplicating the same list across multiple tabs to get different views of it. That's usually the actual signal, not a fixed supplier or customer count.
Can Notion replace a real CRM for a growing wholesale business? Eventually, no. Once pipeline complexity or team size grows past what a small team can track in a table, a dedicated CRM will handle reporting and permissions better than either option here.
Is Notion better than a spreadsheet as a simple CRM for a small team? For a short list, no: a spreadsheet is quicker to set up and everyone already knows how to use it. Notion is better once you want several views of the same list, or once the tracker needs to sit next to related documents. Past that, as above, a dedicated CRM is the next step rather than a bigger Notion setup.
How often should a small team update its follow-up tracker? Update a row whenever its next action changes, and look at overdue follow-up dates once a day. A tracker that only gets reviewed weekly tends to turn into a record of what you meant to do.
Can AI update a supplier tracker automatically? Partly. The supplier outreach workflow uses Zapier or Make to log each reply's summary, quoted price and lead time into a shared sheet, and Zapier vs Make for a two-person team covers which tool suits that step. Keep the decisions with a person, though: moving a supplier from "needs negotiation" to "confirmed" should be done by whoever actually agreed the terms.
See Notion directly, or the supplier outreach playbook this tracker example is drawn from.
