How to track budgets and rates across clients from your meetings

Money gets agreed in calls. "We can do phase two for forty thousand." "Finance approved the day rate." "Hosting is on us until launch." Then the figure lives in somebody's memory until the invoice, or the dispute. This guide is for freelancers, consultants and fractional CTOs who discuss rates, budgets and quotes with several clients on Google Meet and Microsoft Teams. It shows how to build a table of those figures that fills itself, keeps each client's numbers apart, and keeps the words behind every change.

Why track rates and budgets from meetings?

Because the meeting is where the number was said, and the meeting is the record nobody rereads. A figure agreed on a call and never written down turns into your memory against the client's. A figure written down without its source is barely better.

A table built from the meetings holds the figure, who said it, when, and the words they used, for every client you work with.

What columns does a budget and rate tracker need?

A column naming what the money is for, the amount, the first amount quoted, who said it, and whether it was agreed. Six or seven columns is enough; anything more and the table turns into the minutes.

Column	Type	Rule	Description
Item	Text	Names the row	What the money is for: a phase, a rate, a licence, a piece of work. Short name.
Amount	Money	Latest value wins	The figure most recently stated for this item, with its currency.
First quoted	Money	Keep the first value	The first figure stated for this item, with its currency.
Stated by	Person	Latest value wins	Who stated the current figure.
Status	Status	Latest value wins	Proposed, agreed or rejected, only when someone says so.
Conditions	List	Lists	Conditions attached to the figure, such as "if scope stays as agreed".
Estimate as said	Text	Latest value wins	A range or rough figure, in the words used, when no single amount was given.

"Estimate as said" is there because people rarely quote one number early on. A money column holds one figure, so "somewhere between five and six thousand" belongs in text; forcing it into one would mean inventing a figure. A "last discussed" column, which fills itself, shows which figures have gone quiet.

The descriptions decide what lands in each cell. How to design the columns of a meeting tracker covers writing them, and a scope change tracker covers the change requests that usually come with a new figure.

How does a money column handle currencies?

A money column holds an amount and a currency, together. A figure said with its currency is stored in that currency, and TrackHeros does not convert it.

You can set a currency on the column. For a client who always pays in euros, set EUR, and a figure that comes without a currency takes it. With no currency on the column, such a figure is never applied on its own; it waits for a person to decide. That is the right failure: a figure with no currency is one nobody can add up later.

A tracker across clients often spans currencies: pounds for a UK client, euros for one in Dublin, dollars for a US one. Each table keeps each figure in its own currency. Meetings held in Spanish, German or Hindi are read through the same transcript as the notes, and the figure is a figure whatever language it was said in; see languages.

How does one tracker cover every client without mixing them?

Scope it to all your clients. TrackHeros keeps one definition and a separate table for each client, and the Trackers page shows them together with a client label on every row.

Rows from two clients are never merged, even when they have the same name. "Day rate" for Client A and "Day rate" for a fintech client are two rows in two tables, each with its own history. A client added later gets its table automatically. Meetings in your private "No client" space are not included.

This is the same rule that runs through the rest of TrackHeros: every client's meetings live in a sealed workspace, and the views that read across clients label every row rather than blending them. Whether your plan includes all-clients trackers, and designing your own columns as above, is on pricing; more in can I track across all my clients? and on client isolation.

What happens when a figure changes?

The newest figure becomes current and every earlier one stays in the cell's history, with the meeting, the speaker and the words. In a "keep the first value" column, a later, different figure is shown as a conflict for you to settle instead.

Take a phase-two budget with a fintech client:

Meeting	What was said	Amount	First quoted
Monday 5 October 2026	"Our budget for phase two is forty thousand pounds."	40,000 GBP	40,000 GBP
Tuesday 13 October 2026	"The forty thousand pounds still stands."	40,000 GBP	40,000 GBP
Monday 26 October 2026	"Finance came back at thirty-six thousand pounds."	36,000 GBP	40,000 GBP, with a conflict

The second meeting is recorded as a confirmation, not a change. The third changes the amount, and if it also gives "First quoted" a new figure, that shows as a conflict: the column keeps 40,000 GBP until you decide whether the new figure replaces it. If an older meeting is read after a newer one, its figure goes into history labelled as older, and the table keeps the newer one. Each line in the history links to the transcript at the moment it was said.

Should the AI fill money columns on its own?

Keep review first for money. By default, new and changed values wait in a review queue grouped by meeting, and you accept, edit then accept, or reject each one. A rejected value does not come back when the same meeting is read again.

A tracker can be set to apply confident values on its own. Even then, some changes always wait for a person: removing an item from a list, a value that contradicts a "keep the first value" column, a change to a cell somebody edited by hand, and a possible duplicate row. Later AI changes to a cell you edited wait for review, and any applied change can be undone. Details in review before a value changes.

Who can see the figures?

The person who made the tracker, and account admins on a company account, until it is shared. It can be shared only with colleagues already assigned to the client whose table it is, and it reads only meetings its creator could open.

The assistant chat reads trackers as well. "What day rate did each client agree?" is answered from the tables, with the meeting each figure came from, and when the question covers several clients each figure is labelled with its client. More on asking your meetings. Deleting a tracker deletes its tables and every value and quote, and deleting a client deletes its trackers; how backups are handled is in the privacy statements.

How does TrackHeros read the figures?

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. After each meeting in a tracker's scope is summarised, it reads that meeting against your columns. Nothing is filled during the call.

Every figure must point at the transcript lines it came from, and a figure with no line behind it is dropped. The quote shown is rebuilt from the stored transcript, never written by the model. TrackHeros is told to fill only what the meeting actually says, so a budget nobody mentioned stays empty. The feature is on Trackers, and one view of every client's projects is in project status across all clients.