Guide
How to keep a sales pipeline from your meeting notes
For freelancers, solo founders and small studios who sell their own work on Google Meet and Microsoft Teams: how to keep a sales pipeline as a table that fills itself from call notes, using the Sales discovery template's columns, a stage that ends at Won or Lost, budget and timeline changes kept with quotes, and plans from meetings with your manager tracked beside it.
By Sami Kanafani · Updated 4 November 2026 · 7 min read
A sales pipeline built from meeting notes is a table of prospects that updates itself after each call: what hurts, what they use today, the budget they named, who decides, where the deal stands and what happens next. This guide is for freelancers, solo founders and small studios who sell their own work on Google Meet or Microsoft Teams, and for anyone who would rather listen to a prospect than type into a form after the call. It covers the columns, how a deal moves to Won or Lost, and how TrackHeros keeps the table current.
Why keep a pipeline from meeting notes?
Because the pipeline's facts are said in calls and typed in afterwards, if at all. A prospect names a budget on the second call, mentions on the third that their finance director now has to sign, and moves the start date on the fourth. Each of those belongs in the pipeline, and each has faded by Friday.
A pipeline that reads the calls stays current without the typing, and every value comes with the line it came from, so "they said fifteen thousand" can be checked rather than remembered.
Which columns does a sales pipeline need?
The Sales discovery template in TrackHeros is a reasonable start. It is a tracker template, not a way of writing the call's notes: the notes are written as project minutes, as described on the sales calls page, and the tracker reads the meeting alongside them.
| Column | Type | What belongs in it |
|---|---|---|
| Company | Text, names the row | The prospect's company name |
| Contact | Person | The main person speaking for the prospect |
| Pain points | List | Problems the prospect describes and wants solved, one each |
| Current tools | List | Tools, vendors or systems they use today, one each |
| Budget | Money | A budget the prospect states, with its currency |
| Timeline | Text | When they want to decide or start, as said |
| Decision makers | People | People named as making or approving the buying decision |
| Stage | Status | Discovery, Proposal, Negotiation, Won, Lost |
| Next step | Text | The next agreed step, as said |
Each description is what TrackHeros reads when it decides what goes in the column, so edit them to match how you sell. Whether your plan lets you add or change columns is on pricing.
How does a deal move from Discovery to Won or Lost?
When a call says where the deal stands. Stage is a status column with options you can edit, and Won and Lost are marked as final: the two that close a deal. The newest call's stage is the current one, and every earlier stage stays in the cell's history with the line that moved it.
Because a stage change matters, it waits for you by default. New and changed values go to a review queue, grouped by call, where you accept, correct or reject each one, or accept everything from one call. "We'll probably sign next week" may or may not be Negotiation; you decide. A tracker can be set to apply confident values on its own, but removing an item from a list, a value that contradicts a keep-the-first-value column, a change to a cell you edited by hand and a possible duplicate row always wait for a person. Review before a value changes explains why.
What happens when the budget or timeline changes?
The cell changes and its history keeps the old value with the quote. Here is one prospect's budget across two calls:
| Value | Call | Said by | Words |
|---|---|---|---|
| 15,000 GBP | Discovery, Tue 6 Oct | Maya | "We've put aside about fifteen thousand" |
| 12,000 GBP | Proposal walk-through, Tue 20 Oct | Maya | "Finance has cut it to twelve for this year" |
The table shows 12,000 GBP, with both quotes one click away, which is the conversation to have before you send a revised proposal. Each quote links to the moment in the transcript and the recording.
Three rules keep this honest. A value said again is recorded as a confirmation, not a change. A call read late, older than one already in the table, lands in history labelled as older and does not overwrite the newer value. And a budget nobody stated stays empty: every value must point at the transcript lines it came from, and a value with no line is dropped. If you want the first figure kept as an anchor, add a "Budget first stated" column with the keep-the-first-value rule, and a later different figure shows as a conflict for you to decide.
Should each prospect have a workspace of its own?
Either works. Put every prospect in one workspace and the pipeline is one table with a row per company. Or give each prospect a sealed workspace, so that a prospect who signs starts their project with the discovery calls already in it, and use a tracker that covers all your clients.
That second setup is one definition with a separate table for each client. The Trackers page shows them together with a client label on every row, and a client added later gets its table automatically. Rows from two clients are never merged, even when two companies share a name, and the private "No client" space is not included. Whether your plan includes trackers across all clients is on pricing; how the walls work is on client isolation.
Can meetings with my manager feed a tracker too?
Yes, as a second tracker beside the pipeline. If you sell inside a company, the weekly pipeline review with your manager is where plans are made: "I'll get their finance director on a call before the 20th", "I'll send the revised quote on Thursday". Those are plans, not facts about the prospect, so they belong in a table of their own.
Scope a tracker to that recurring meeting and name each row by the deal:
| Column | Type | Rule |
|---|---|---|
| Deal | Text, names the row | One row per deal, updated at every review |
| Plan | Text | Latest value wins |
| Committed close date | Date | Latest value wins, so every slip stays in history |
| Help needed | List | Added when asked for, removed when said to be sorted |
| Last discussed | Automatic | The last review that mentioned the deal |
Next week's review starts from the table: what you said you would do on each deal, and how often its close date has moved. File that meeting under a workspace of its own, such as one for your company's internal meetings, and keep the tracker there, never in a prospect's: a tracker reads only its own workspace's meetings. The one-to-one meeting tracker guide applies the same idea to other one-to-ones.
Can the pipeline sync with my CRM?
No. TrackHeros does not send tracker rows to a CRM or to any other tool. The current table and its full history download as CSV, which opens in Excel or Google Sheets, and pricing says which plans include export.
How does TrackHeros fill the pipeline?
TrackHeros is an AI meeting notetaker that connects every Google and Microsoft calendar you hold, recognises close to 100 spoken languages on its own, writes the notes in nine of them, and keeps every client's notes in a sealed workspace of its own. The notetaker joins the sales call on Google Meet or Microsoft Teams as a visible participant. Once the notes are ready, not during the call, the tracker reads the meeting and proposes values.
A call with a prospect in Spanish, or in French and English, is read through the same transcript as the notes, and text values are written in the notes' language; the languages page lists what is recognised. Each meeting page lists what that call gave the pipeline, and the tracker's creator gets an in-app alert when changes are waiting. The assistant reads the table as well: "which deals are in Negotiation, and what is the next step on each?" is answered from the tracker, with the call each value came from. For the call itself, discovery call notes covers what to ask so the columns have something to fill.
Questions
Frequently asked
Is the Sales discovery template a sales-call summary?
No. It is a table template: it decides which columns a tracker keeps across calls. The call's own notes are still written as project minutes, which cover the problem, decisions, milestones and next steps with owners and dates.
Does the pipeline update during the call?
No. A tracker reads a meeting after its notes are ready. A call held in another language, or in two, is read after the audio pass, so it is read once.
Can I add a deal to the table myself?
Yes. Add a row by hand and edit any cell. A cell you edited is protected: a later change from a call goes to review instead of replacing your value.
Related
Keep reading
- FeaturesTables that fill themselves from your meetingsTrackHeros turns Google Meet and Teams calls into tables that update themselves: candidates, features, requests, each value cited to its meeting.
- Use casesDiscovery and sales call notes for freelancers and solo foundersDiscovery call notes for freelancers and solo founders. The bot joins on Google Meet and Microsoft Teams, records what the prospect said, and cites it.
- GuidesDiscovery calls for solo developers: what to ask, what to write down, what to send afterDiscovery call notes for solo developers: what to ask, what to write down verbatim, how to capture next steps, and what to send the same day.
- GuidesReview what a meeting changes in your table before the change landsHow the TrackHeros review queue works: values from Google Meet and Teams calls wait for you, confident ones can apply on their own, and rejections stick.
Early access
Get in early.
We’re onboarding a small group at a time so we can get it right. Join the list and we’ll reach out.