A 10-Minute Notion Setup for Consultants Who Bill Time
Ten minutes, four tables
You bill hours, so the first question your workspace should answer is what the last billable hour actually paid. Most consultant setups answer that from memory, which is why the memory is usually a little flattering. A ten-minute Notion setup for consultants replaces the memory with a number you can sort.
The point is not a beautiful workspace. It is four databases that answer three questions: what is due, who owes you, and whether the work you took actually paid your rate. Answer those, and the decorative layers can arrive later without breaking anything. Everything else can wait until you have spare time, which is to say never.
The 10-minute Notion setup for consultants, minute by minute
| Minutes | Do this | Done looks like |
|---|---|---|
| 0 to 2 | Create four databases: Clients, Projects, Tasks, Finances | Four empty tables with nothing but the title property |
| 2 to 5 | Add three relations: Projects to Clients, Tasks to Projects, Finances to Clients | Every row can point at one parent row |
| 5 to 7 | Add the properties below to Clients and Projects | Rate, Rate Type, Budget, and Hours Logged exist |
| 7 to 9 | Paste the two formulas | Effective Rate shows a currency number, Days to Get Paid shows a count |
| 9 to 10 | Create three views: Overdue, Unpaid, Margin check | You can answer the three questions without scrolling |
The temptation is to spend minute five decorating. Do not. The ten minutes are for structure; the properties are what make the structure answer anything.
The client properties that matter
Keep Clients to seven: Name, Status (Lead, Active, Paused, Archived), Rate Type (Hourly, Fixed, Retainer), Rate, Billing contact, Since, and Notes. The one people skip is Rate Type, and skipping it is why their effective-rate comparisons mislead them later.
An hourly rate, a fixed project fee, and a retainer's monthly value are not comparable numbers. If they all live in one Rate property, then the average of that column means nothing, and you will conclude the retainer is your best client when it is only your most predictable one.
The Budget on a retainer is its monthly value, so its effective rate divides a fixed number by however many hours that month happened to need. The rate therefore moves every month, and the movement is the signal. A retainer that paid $150 an hour in March and $90 in October has quietly turned into a full-time job for one client, and the October row is where you notice.
Projects gets Name, Client, Status, Start, Due, Budget, and Hours Logged. Budget means the quoted fee for fixed work, the monthly value for a retainer, and your honest estimate for hourly work. Hours Logged is filled from your timer or your calendar, not from memory.
The two formulas that pay the setup back
The first is effective hourly rate. With Hours Logged kept reasonably current:
`` if(prop("Hours Logged") == 0, 0, round(prop("Budget") / prop("Hours Logged"))) ``
Format the property as currency. Compare each project's result with that client's Rate. Well above target usually means you scoped the work well or have gotten faster. Below target means unbilled revisions, scope that arrived verbally, or a fixed fee you underpriced. When two projects for the same client sit below target, that client is losing you money, and reading client profitability is more useful than working faster. On the first Friday you run this, some numbers will look wrong. Usually the hours are missing, not the formula.
The second measures invoices, not work:
`` if( prop("Type") == "Income", if( empty(prop("Paid On")), dateBetween(prop("Date"), today(), "days"), dateBetween(prop("Date"), prop("Paid On"), "days") ), 0 ) ``
An unpaid invoice reports its age in days, climbing daily until you fill in Paid On. A paid invoice reports the actual gap between sending and getting paid. Retainers close on a fixed date and fixed-fee projects close on delivery, and one column handles both.
Hours go in somewhere
Neither formula works if Hours Logged is empty, and empty means the effective rate reads zero for every project until you give up on it. Pick one place to record time that is not Notion, or a single Notion page you keep open, and update Hours Logged once a week. Twenty honest minutes on Friday beats perfect tracking that lasts nine days.
What to skip in the first ten minutes
Skip the pipeline beyond the Status property. Skip the time-blocking calendar that duplicates your calendar. Skip the knowledge base and the second brain. Skip the dashboard, because a dashboard of three empty databases is a reminder that you have not filled them yet.
Add a view when the same question has come up twice, not before. A consultant's Notion setup is a billing instrument first. It becomes a personal knowledge system only after the invoices are on time. The exception is one filtered view on Projects with hours logged above zero, sorted by effective rate. That view is the instrument itself.
After the first week
Once the four databases hold a week of real rows, the same workspace supports a twenty-minute review. Running the weekly review in Notion uses the numbers you just built, and the relation setup covers the connecting step if you built the tables in the wrong order.
Do this today
- Create the four databases and the three relations in one sitting, before you open your inbox.
- Add
Rate Typeas a select with exactly three options and set it on every active client. - Paste the effective-rate formula, open the Margin check view, and sort it so the lowest effective rate is on top.