A solo consultant can run a reliable referral pipeline in a spreadsheet. The useful version is a decision ledger: every live opportunity has an evidence-based stage, one owner, one next action, and a date when that action should happen.
Without those rules, a tracker becomes a list of people you hope may hire you someday. Names accumulate, recent conversations feel more promising than they are, and warm introductions disappear under delivery work. A practical ledger answers a narrower question: what has actually happened, and what should I do next?
Separate relationships from opportunities
Referral work has two connected pipelines. The relationship ledger covers former clients, peers, and complementary professionals who may know suitable buyers. The opportunity ledger begins when a specific company or person could plausibly buy a defined piece of work. Keep both in one workbook if that is convenient, but give them separate tabs.
A referral partner does not move through “proposal sent” or “won.” A prospective client does not need a “relationship contribution” score. Combining them in one stage column creates false progress, especially when a pleasant partner meeting gets counted as new business.
Relationship record: Maya, fractional COO; knows post-seed founders; next action is to send the hiring-risk checklist discussed on Tuesday.
Opportunity record: Northwind Labs; introduced by Maya; qualified conversation booked for September 24; possible onboarding redesign.
Build the opportunity ledger around thirteen fields
Start with one row per possible engagement, not one row per contact. The same company may have two genuinely separate opportunities, while three stakeholders may belong to the same engagement. Use these columns:
| Field | What belongs there | Why it matters |
|---|---|---|
| Opportunity | Company plus a short problem label | Prevents vague company-only rows |
| Contact | Current decision contact | Shows who owns the next decision |
| Referral source | Person who made the introduction | Preserves attribution and follow-through |
| Introduced | Date the connection became mutual | Starts the opportunity clock from a real event |
| Stage | One controlled value from the definitions below | Makes rows comparable |
| Evidence | The event that justifies the stage | Stops optimism from becoming data |
| Next action | One concrete action, written as a verb | Turns the record into work |
| Next-action date | The date you will act or review | Exposes neglected opportunities |
| Estimated value | A range or scoped estimate | Supports capacity planning without false precision |
| Last meaningful contact | Date of the latest two-way exchange | Distinguishes dialogue from sent reminders |
| Outcome | Won, lost, nurture, or blank while active | Keeps closed work out of the live queue |
| Outcome reason | Short factual explanation | Reveals patterns worth addressing |
| Notes | Only context needed for the next decision | Avoids turning the sheet into a transcript |
Dropdowns should control stage and outcome values. Dates should remain dates rather than phrases such as “next week.” Conditional formatting can flag a next-action date that has passed, but color never replaces a clear action.
Define stages by evidence
Salesforce's current pipeline guidance recommends adapting stages to the actual sales process and using exit criteria before an opportunity advances. That principle matters even more in a manual tracker because the software will not challenge a hopeful stage change for you.
| Stage | Entry evidence | Normal next move |
|---|---|---|
| Potential fit | A named organization has a plausible problem, but no introduction has been requested | Decide whether a relevant, consent-based introduction is reasonable |
| Introduction requested | A partner agreed to consider or make the introduction | Wait once, then close or return the record to relationship work |
| Introduced | Both sides are connected and the prospect accepted contact | Offer a brief exploratory conversation |
| Qualified conversation | You confirmed a problem, plausible fit, timing, and a real decision path | Agree on the next discovery or scoping step |
| Proposal sent | A scoped offer with price and terms reached the buyer | Book the decision conversation |
| Decision pending | The buyer confirmed the decision process and date | Follow the mutually agreed plan |
| Won | The required agreement is complete | Move delivery to the delivery system |
| Lost | The buyer declined, chose another route, or the need disappeared | Record the reason and close cleanly |
| Nurture | Fit exists, but there is no current buying event | Set a specific, defensible review date |
“Interested” is too elastic to be a stage. “They loved the call” is not evidence of a proposal decision. Write the observable event instead: “VP confirmed budget review on October 3 and asked for a two-option scope.”
Give every active row one next action
A pipeline fails quietly when a row has a stage but no scheduled action. Use a verb, name the recipient or artifact, and pick a date. “Follow up” leaves too much interpretation. “Send revised two-option scope to Lena by Friday” can be completed or missed.
Some next actions belong to the other person. Your row still needs a date for your own decision: “Review whether procurement replied; close if silent.” This prevents an open record from waiting forever while preserving a respectful follow-up boundary.
After a warm introduction, track only meaningful contact. An automated open, a social-media like, or an unanswered message should not reset the last-contact field. The measure exists to tell you when a conversation last moved.
Run a weekly pipeline review in four passes
Put the review on the calendar and use the same order each time. The sequence keeps urgent follow-ups from consuming the entire session.
- Repair the facts. Add missing conversations, correct stages, and remove duplicate opportunities.
- Clear overdue actions. Do the short ones now. Reschedule only when a real reason exists.
- Close or park weak rows. Move absent buying events to nurture. Mark explicit declines as lost.
- Choose relationship work. Review the separate partner tab and select a small number of useful, non-transactional actions.
The final pass protects future pipeline while current work is busy. It may mean thanking a referrer, sending a useful resource, checking on a former client's project, or making an introduction for someone else. Do not convert that tab into a quota for asking favors.
Use three views instead of a dashboard
- Due now: active rows with a next-action date on or before today.
- Decision work: proposal sent and decision pending, sorted by the buyer's date.
- Source review: closed opportunities grouped by referral source and outcome.
These views answer daily operating questions. A collection of charts can wait until you have enough consistent history to interpret them.
Forecast with ranges and capacity checks
A small referral pipeline rarely contains enough comparable opportunities to justify elaborate probability math. One large proposal can distort the total, and a warm introduction can still be a poor fit. Keep full estimated value visible, then build a conservative near-term view from evidence.
For each proposal, record a range and the next decision date. Separately total work that is contractually won. Compare possible start dates with your delivery capacity. This makes the forecast useful for choices such as reserving time, continuing business development, or declining a conflicting project without presenting uncertain revenue as committed.
After several closed opportunities, calculate simple counts by stage: how many qualified conversations reached a proposal, how many proposals closed, and how long each stage took. Treat the early numbers as observations about your own process, not universal conversion benchmarks.
Preserve the referral trail
The referral source field deserves more care than a generic “lead source” label. Record the person who enabled the introduction, whether the introduction was direct, and when you closed the loop with them. Never expose confidential proposal details in that update.
If two people contributed, note both rather than forcing credit into one cell. If fees or reciprocal terms apply, keep the agreement outside the pipeline notes and link to the controlled record. The guide to fair referral fees covers the commercial considerations; the guide on asking for client referrals covers a consent-based introduction process.
Keep personal data deliberately small
A spreadsheet is easy to copy, share, and forget. Store business contact details and the minimum context needed to manage the opportunity. Avoid sensitive personal observations, private information supplied by the referrer, or speculative labels about a person's motives.
The UK's Information Commissioner's Office describes data minimisation as keeping personal data adequate, relevant, and limited to what the stated purpose requires. Its small-organization guidance also recommends periodic review and deletion of data that is no longer needed. Applicable law depends on where you and the people in the tracker are located, so use local advice where required.
Restrict access, enable multifactor authentication on the account that holds the file, and know how the workbook is backed up. NIST's small-business Cybersecurity Framework guide recommends inventorying and classifying business data as a starting point for risk management. Your pipeline is part of that inventory.
Move to a CRM when coordination starts failing
Row count alone should not trigger a migration. A solo consultant with many short, clear opportunities may manage a sheet comfortably. A smaller pipeline with multiple collaborators, long procurement cycles, or permission-sensitive notes may outgrow it quickly.
Consider a CRM when two people need reliable ownership, follow-ups are missed, email history must be reconstructed, access permissions become awkward, recurring reports consume significant time, or the process needs dependable automation. Before migrating, clean the stages and next-action rules in the spreadsheet. New software will reproduce a confused process with more fields.
Use a referral circle to create trackable relationships
A ledger helps you operate the opportunities you have. It cannot create trusted relationships by itself. Referna organizes curated referral circles for independent professionals who want peer relationships that can produce relevant introductions. Members apply, receive AI-ranked match recommendations based on their profiles, and choose whether to proceed with each match. Referna schedules the meeting only after both people opt in.
Track those peer relationships in the relationship tab like any other: what you learned, what useful action you owe, and when you will reconnect. Move a specific company into the opportunity ledger only after there is a real, consent-based introduction.
Sources and further reading
- Salesforce: What is a sales pipeline? for stage ordering, qualification, and exit-criteria concepts.
- Information Commissioner's Office: Data minimisation for collecting and retaining only the personal data needed for a stated purpose.
- NIST Cybersecurity Framework 2.0 for Small Business for inventorying, classifying, and protecting business data.