Most freelancers’ pipeline notes are a disaster. There’s a paragraph from three weeks ago about a call that went well, a follow-up reminder that got buried, and a vague “waiting to hear back” that could mean anything. When you open that deal on Friday afternoon to figure out what to do next, you spend 10 minutes re-reading your own notes and still can’t remember what the prospect said about their budget.
This isn’t a memory problem. It’s a format problem. The solution isn’t to write more, it’s to write the same five things every time, in the same order, every time you touch a deal. Consistency in notation is what turns a messy pile of notes into a scannable, actionable system.
The 5-line format below works whether you’re using HubSpot, Pipedrive, Folk, Notion, or a plain text file. The tool is secondary. The structure is everything.
The 5-Line Format
Every deal entry, every time you touch a deal, gets exactly five lines. No more. No exceptions for “complex” deals.
Line 1, Contact: Full name, title, company. If you spoke to multiple people, list all of them. “Sarah M., VP Ops + Derek L., CFO, Acme Corp”
Line 2, Date: The date of the last interaction. Not the date you wrote the note, the date of the contact. “Last touch: May 2, 2026 / email reply”
Line 3, Intel: What was said that matters. Not a summary of the conversation, the one or two things that changed your understanding of the deal. “Confirmed $15K budget exists; CFO needs to approve anything over $10K. Team is burned out on manual reporting. They’ve tried fixing this internally twice.”
Line 4, Next step: One specific action, owned by one person, with a due date. “ME: send revised scope by May 5. THEM: schedule scope review call for week of May 11.”
Line 5, Stakes: Budget, timeline, decision-maker, and any known competitors. “Budget: $12–15K confirmed. Timeline: wants to start June 1. Decision-maker: Derek (CFO). Competition: none confirmed, but mentioned Upwork option.”
That’s it. The whole entry fits in ten lines of plain text and takes two to three minutes to write while the call is still fresh.
What Each Line Actually Does
Line 1 (Contact) prevents the invisible mistake of forgetting who you actually spoke with. In complex accounts, you might touch three different people over six weeks. When the deal stalls, you need to know which person has gone quiet, and which one you haven’t reached yet.
Line 2 (Date) is a health indicator. When you scan your pipeline on Friday, every deal with a “last touch” more than 14 days old is flagged. No calculation required, the date tells you the deal is cold.
Line 3 (Intel) is the most valuable line and the one most people skip or write badly. Bad intel line: “Good call, they’re interested.” Good intel line: “Mentioned Q3 budget was approved last week. Main concern is whether we can deliver before August 15 board meeting. They’ve been burned by freelancers missing deadlines.” The difference between these two is everything, one tells you nothing about how to close, the other gives you the exact pressure point and the exact concern to address.
Line 4 (Next step) prevents the most common pipeline failure: both parties thinking the other person is responsible for moving forward. Write both next steps, yours and theirs. If you have a next step and they don’t, that’s fine. If neither party has a next step, the deal is dead regardless of how interested they seem.
Line 5 (Stakes) exists for prioritization. On Friday, you have 12 deals. Which one gets your first call Monday morning? The one with the confirmed $18K budget, a June 1 start date, and a decision-maker who asked for a revised proposal, not the one with vague interest and no timeline.
A pipeline entry that takes 15 minutes to re-read isn’t a pipeline, it’s a journal. The goal of notation is to let you make a decision about a deal in under 30 seconds. If your notes don’t support that, they’re not serving you.
CRM vs. Notion: The Real Decision
The tool question comes up constantly, so here’s the direct answer.
Use a CRM if:
- You manage 10 or more active deals simultaneously
- You need automated follow-up reminders
- You work with a VA or business partner who also touches deals
- You want activity history tracked automatically (email opens, link clicks)
Best free option: HubSpot CRM. Paid options worth it: Pipedrive ($15/month) for pipeline visualization, Folk ($18/month) for relationship intelligence.
Use Notion if:
- You have fewer than 10 active deals
- You want full customization of deal properties
- You already live in Notion for project management
- You prefer keyboard-first, text-heavy workflows
The Notion setup: one database called “Pipeline,” one entry per deal, five properties matching the five lines (Contact, Last Touch Date, Intel, Next Step, Stakes). Add a “Stage” property with six values: Identified, Contacted, Conversation Held, Proposal Sent, Negotiation, Closed/Won, Closed/Lost.
The practical difference between CRM and Notation in Notion is automation. A CRM can remind you that a deal hasn’t been touched in 10 days. Notion won’t, you’ll catch it in your weekly review instead. If you do your weekly review consistently, Notion is fine. If you skip reviews, get a CRM with reminders.
Writing the Intel Line Well
This is where most pipeline notation breaks down. Here are five bad intel lines and their improved versions:
Bad: “Good discovery call. Very interested.” Good: “Problem: onboarding takes 3 weeks because sales-to-ops handoff is manual. Goal: cut it to 5 days. Current workaround: Sarah manually re-enters data from Salesforce into Asana. This is eating 6 hrs/week of a $90K employee.”
Bad: “Waiting for budget approval.” Good: “Budget needs CFO sign-off. CFO is back from vacation May 12. Sarah will bring it to him then. Sarah’s instruction: follow up May 14 if no word.”
Bad: “Sent proposal, no response.” Good: “Proposal sent May 1. Read receipt confirmed open on May 2 at 9 AM. No reply. Sarah mentioned in last call that she was presenting to leadership mid-month, may be waiting for that outcome.”
Bad: “They want a discount.” Good: “Asked for 15% reduction. Reason given: ‘tight budget this quarter.’ Original budget was $14K, now asking for $12K. Scope hasn’t changed. Timeline still June 1. This may be a negotiating position, not a hard constraint.”
Bad: “Seemed hesitant.” Good: “Hesitation is about timeline, they want to start June 1 but their dev team is mid-sprint. Real concern: disruption to in-progress work. May need to propose a June 15 soft start with June 1 prep work only.”
The pattern: bad intel lines describe feelings. Good intel lines capture facts, quotes, constraints, and context that directly inform your next move.
The Weekly Pipeline Scan
Every Friday, 20 minutes. Open your pipeline. For each deal, read the five lines and answer one question: what is the single best thing I can do to move this forward before next Friday?
The output is a list of actions, one per deal. Write them in a separate “This Week” note or task list. Monday morning, you work from that list.
Deals that have no clear next action and haven’t been touched in 21+ days get one of three designations:
- Re-engage: Send a reactivation touch and see if there’s still interest
- Park: Move to “Nurture” category, one touch per quarter
- Close/Lost: Mark it done, tag the loss reason, move on
The scan takes 20 minutes because each deal is five lines, not five paragraphs. That’s the payoff for disciplined notation.
The entire value of a consistent notation system is time compression. You don’t need to remember everything about every deal, you need to be able to reconstruct the situation in 30 seconds and make one decision. Five lines does that. Two paragraphs does not.
When Deals Get Complicated
Some deals involve multiple contacts, multiple proposals, or multiple rounds of negotiation. The five-line format scales: create a new entry for each significant interaction, with all five lines, dated. Don’t edit old entries, append new ones below.
This gives you a timestamped history that shows exactly how a deal evolved. When you look back at a deal that closed six months ago to inform how you handle a similar one today, you’ll have the actual sequence of events, not a jumbled edit history.
For multi-contact deals (which I cover in the multi-deal-same-account piece), add a “Contacts” sub-section above the five lines that maps everyone in the account: name, title, relationship to the decision, and their level of support for the project. That context layer sits above the notation entries and gets updated when the cast changes.
Implementing This Starting Today
You don’t need to rebuild your whole CRM to adopt this. Open your current pipeline tool, whatever it is, and pick your top 5 active deals. For each one, write the five lines right now, from memory. If you can’t fill in all five lines from memory, that’s your gap. You either need to make contact and find out, or the deal is less active than you thought.
From this point forward, every time you touch a deal, every call, every email, every meeting, you add a new five-line entry within 24 hours. Don’t write it from memory two days later. Write it the same day.
After four weeks of consistent notation, your pipeline review will feel fundamentally different. You’ll stop dreading it and start relying on it.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
