How to Set Up a Simple Sales Pipeline as a Solo SaaS Founder

A simple sales pipeline is a list of real people you're talking to about buying, the stage each one is in, and the next thing you'll do for them with a date next to it. That's it. For a solo SaaS founder with somewhere between zero and fifty customers, it can live in one spreadsheet tab and take thirty minutes a week to keep honest. In my experience, most early deals don't die because the pitch was bad. They die because nobody followed up. A founder said "I'll send that over Thursday", Thursday turned into a launch week, and the buyer quietly moved on. This guide shows you how to set up a pipeline that stops that from happening: the stages, the fields, where to run it, how to feed it, the weekly review and a forecast that doesn't lie to you.

The short answer

If you only read one section, read this one.

• Every conversation gets a row within 24 hours. DMs, demo requests, trial signups you've spoken to, intros. If it's not in the sheet, it doesn't exist.

• Use five or six stages defined by what the buyer did, not by how hopeful you feel.

• Every open deal has a next step and a date. No date means no deal.

• Start in a spreadsheet. Move to a CRM for solo founders when the sheet starts fighting you, which for most people is somewhere around 30 active deals.

• Review it once a week for 30 minutes, and move deals that have gone silent to Lost with a reason.

Do you actually need a sales pipeline yet?

If you sell a B2B product and any of your customers talked to you before paying, yes. You don't need it because a sales book says so. You need it because your memory is a terrible database and you're also the developer, the support desk and the marketing team.

Here are the signs you needed one last month:

• You've lost track of who you promised what. You told someone you'd check whether the product handles their use case. You can't remember who.

• Trials expire without you noticing. Someone you spoke to signed up, the trial ran out, and you found out when you happened to look at the admin panel.

• "Let's circle back next month" never happens. Nobody circles back. Not them, not you.

• Your deals live in five places. Some in email, some in LinkedIn DMs, a couple in X DMs, one on a sticky note, one in a Slack community thread.

• You can't answer "how many people are close to buying right now?" without scrolling through your inbox for twenty minutes.

If you recognised two or more, block an hour this week. The setup below fits in that hour.

What pipeline stages should a SaaS startup use?

Keep it to five or six. Every stage you add is another place for a deal to sit and look busy. The key rule for pipeline stages is that each one is defined by something the buyer did, not something you felt. "Interested" is a feeling. "Booked a call and described the problem in their own words" is a fact.

Here's a set that works well as a sales pipeline for SaaS startups selling to small teams:

Two notes on this. First, the exit criterion matters more than the name. If you can't say what moved a deal from Conversation to Problem confirmed, it didn't move. Second, if you're nervous about the demo stage itself, there's a separate Aura++ guide on running your first SaaS sales demo call as a founder. This post is about what happens around the call: tracking it, following up and not losing it.

What should you track for each deal?

Fewer fields than you think. Every column you add is a column you'll skip filling in on a busy Tuesday, and a half-filled sheet is worse than a short one because you stop trusting it.

These ten are enough for a deal tracking spreadsheet:

That's it. No "lead score", no "probability" column yet, no twelve-option dropdown for industry. You can add one later if you keep wishing you had it. Freeze the header row, turn Stage into a dropdown so you don't end up with "Trial", "trial" and "In trial" as three different stages, and add a filter view sorted by next-step date.

Should you use a spreadsheet or a CRM?

My opinion: start in a spreadsheet and stay there until roughly 30 active deals, or until you catch yourself copying email threads into the sheet by hand every day. A sheet is fast to change, costs nothing, and forces you to think about your stages instead of a tool's defaults. A CRM starts paying for itself when the manual logging is eating real time or when a second person joins sales.

If you do want a CRM for solo founders, here's what the main options say about themselves on their own pricing and product pages, as of October 2026. Prices change, so check the page before you sign up.

Whatever you pick, the stages and fields above don't change. If you set them up in a sheet first, moving to a CRM later is an import, not a redesign. Most of these tools accept a CSV.

How do deals get into the pipeline?

A pipeline is only as good as what you feed it. For a small SaaS, deals tend to come from a handful of places:

• Inbound trial signups you've actually talked to. Not every signup. A signup becomes a row when there's a person on the other end who replied.

• Demo requests and contact form messages. These go straight in at Conversation.

• DMs. LinkedIn, X, community Slacks and Discords. Copy the link to the thread into the Notes link field.

• Warm intros from customers, friends and other founders.

• Outbound conversations you started yourself. If you're still working out who to reach out to, the Aura++ guide on getting your first 10 paying customers without a launch day covers that part.

• Launch and discovery platform traffic. People who found you through a launch listing and then wrote to you or booked a call.

The one rule I'd keep no matter what: every real conversation gets a row within 24 hours. Not when it feels promising. Within a day. The deals you forget to log are almost always the ones that seemed casual at first, and casual is often where the good ones start.

One trick that helps: make the Source field mandatory and specific. "Twitter" is less useful than "reply to my post about CSV imports". Six months from now, that detail tells you which posts brought buyers.

How do you run a weekly pipeline review?

This is the habit that makes the whole thing work. Pick a fixed 30-minute slot, the same day every week. Monday morning or Friday afternoon both work. Then go through the sheet in this order:

1. Sort by next-step date. Anything overdue gets done today or gets a new, honest date.

2. Find deals with no next step. Give each one a next step and a date, or move it to Lost.

3. Check last touch. Any open deal with no contact in 14 days needs a follow-up this week.

4. Check every stage against its exit criterion. Is that deal really in Proposal, or did you just send a pricing page link in passing? Move it back if it doesn't qualify.

5. Kill stale deals. Pick a cut-off, for example 30 days of silence after your last follow-up, and move those to Lost with the reason "went silent". It feels bad for about a minute. Then your pipeline tells the truth again.

6. Write down one thing you noticed. Maybe three deals stalled at the same point. That's a pattern worth fixing in the product or the pitch.

Questions worth asking yourself each week: Which deal would hurt most to lose, and what's the next thing that moves it? Where are deals piling up? What did the last three buyers who said yes have in common?

How many times should you follow up with a quiet prospect?

Two or three touches, spaced out, then stop politely. Each follow-up should add something: an answer to a question they asked, a short how-to for their case, a note that you shipped the thing they mentioned. "Just checking in" adds nothing. Here's a made-up example of a second follow-up:

Example (made up): "Hi Priya, you mentioned the weekly room report was the painful part. I recorded a two-minute video showing how that report looks with a setup like yours. No pressure either way. If the timing's wrong, tell me and I'll stop nudging."

If there's no reply after the third touch, mark it Lost with "went silent" and move on. Some of those people come back months later, and when they do, you'll have the full history in the row.

I'm keeping the email side short on purpose. Writing cold outreach is its own skill. The point here is that the pipeline tells you who to follow up with and when.

How do you forecast without fooling yourself?

At this stage, forecasting isn't about a revenue number you'd show an investor. It's about knowing whether next month looks thin so you can do something about it now.

Keep it simple:

1. Count open deals by stage.

2. Give each stage a rough odds number. These are your own guesses, not industry benchmarks, and they'll be wrong at first. Adjust them every month or two based on what actually closed.

3. Multiply count by odds by an average deal value, and add it up.

Illustrative example (made up): Mossdesk is a fictional desk-booking app for small coworking spaces, run by one founder. Every number below is invented to show the arithmetic, including the odds.

In deal terms, that's 0.6 + 0.9 + 1.5 + 1.5, so roughly four to five new customers likely from what's open today. That's the useful part. If the Mossdesk founder needs eight, the forecast is telling them, this week, that they need more conversations at the top, not a better proposal at the bottom.

Two warnings. Don't show this number with decimals to anyone, including yourself. And don't let it replace looking at the actual deals. A forecast built on three deals in Proposal is three people. Call them.

What should you do with lost deals?

Fill in the lost reason every single time, even when it's "went silent". After a couple of months, sort the Lost rows by reason. If "missing feature" keeps coming up with the same feature, that's roadmap input. If "timing" dominates, maybe you're reaching people too early in their buying cycle. If most losses are "went silent" right after the demo, look at what happens in the 48 hours after the call.

When a loss surprises you, it's worth asking the buyer directly. IndieHunt has a full guide on running a lost-deal debrief when you only have a handful of customers, with the questions to ask and how not to overreact to three data points. The pipeline's job is simpler: make sure every loss is recorded, so you have something to debrief.

What are the traps that break a simple sales pipeline?

• Too many stages. Ten stages for fifteen deals means everything moves sideways and nothing moves forward. Five or six.

• The pipeline lives in your head. It works until the week you launch, get sick or ship a big release. Then three deals quietly die.

• Logging only wins. If you only add rows once a deal looks likely, your conversion numbers are fiction and you can't learn from losses.

• No next-step date. A deal with "follow up" and no date is a deal you've already half-forgotten.

• Buying a heavy CRM and building automations before 10 customers. You'll spend a weekend on sequences and lead scoring for a pipeline that fits on one screen. Get the habit first, then the tool.

• Mixing users and buyers. On a self-serve product, most signups never talk to you, and that's fine. Don't dump every free signup into the pipeline. Your product analytics track users; your pipeline tracks conversations with people deciding whether to pay. Add a signup to the pipeline only when there's a real two-way conversation, or when the account is big enough that you'd reach out yourself.

• Never killing anything. A pipeline full of zombie deals makes you feel busy and makes your forecast useless. Move them to Lost.

A 7-day plan to set it up this week

By the end of the week you'll know exactly how many people are close to buying, who's waiting on you, and what you're doing next for each of them. For most solo founders, that alone is a change.

FAQ

Do I need a CRM as a solo founder?

Not at first. You need a pipeline, which is a habit plus a list. A spreadsheet does that well until you're juggling roughly 30 active deals or spending real time each day copying emails into it. Then a CRM with email sync starts saving time. HubSpot, Attio and Airtable all list free plans, so you can try one without spending money.

How many stages should a SaaS sales pipeline have?

Five or six is plenty for an early SaaS: something like Conversation, Problem confirmed, Demo or trial active, Proposal or pricing sent, Won and Lost. What matters more is that each stage has a clear entry rule based on what the buyer did.

What's the difference between a sales pipeline and a sales funnel?

A funnel looks at groups: how many visitors became signups, how many signups became paying customers. A pipeline looks at individual deals: this person, this stage, this next step, this date. You use the funnel to understand your numbers and the pipeline to decide what to do on Tuesday.

How often should I review my pipeline?

Once a week, for about 30 minutes, at a fixed time. Glance at the next-step dates daily if you like, but the weekly review is where you fix stages, kill stale deals and notice patterns.

Start with one sheet today

You don't need a tool decision to start. Open a blank spreadsheet, add the ten columns, and put in the last five people who talked to you about buying. Give each one a next step and a date. That's a simple sales pipeline, and it's already better than the one in your head.

And if you want more people at the top of it, Aura++ is a launch and discovery platform where founders and early adopters find new products.