Guide
Founder-mode selling: CRM habits when the CEO is also the sales team
Most CRM advice is written for sales teams. If you are the team, and also running product, hiring, and operations at the same time, you need a different approach. Here is the minimum CRM setup that works for founders doing their own selling, and what the system needs to look like before you hand that off to someone else.
What founder-led selling actually looks like
You are in fifteen different conversations at once. One is a warm introduction from a conference two months ago that just replied. One is a renewal conversation with your second-biggest client. One is a referral from a happy customer to their former colleague at another company. One is a cold email that somehow got a response and now deserves a thoughtful reply.
These are not deals in the traditional pipeline sense. They are relationships at various temperatures. Some will close in six weeks. Some are three years out. Some will go nowhere and you will not find out until they stop replying. The job is knowing the difference, and not losing track of any of them while you are also doing everything else that comes with running a company.
A CRM built for a five-person sales team is not designed for this. A spreadsheet breaks down the moment you need to find something quickly across thirty relationships. The right setup for a founder-seller sits somewhere in between: structured enough to be reliable, simple enough to actually maintain when you are also managing four other things.
The specific CRM problems founder-sellers face
Everything lives in one person's head
The founder knows which deal is warm, who the right contact is at each account, what was discussed on the last call, and what the next step is. That knowledge is irreplaceable right now and completely inaccessible the moment the founder is unavailable, distracted, or trying to brief someone new.
Most CRMs are built for teams, not solo operators
Enterprise CRM setups with required fields, handoff stages, and approval workflows were designed around a team. If you are the team, you are maintaining infrastructure built for five to ten people and getting almost none of the coordination benefit that makes that infrastructure worth maintaining.
Follow-up falls through at the worst moments
Founder-sellers are often strong on relationship and inconsistent on operational follow-through. The warm lead who said reach back out in Q3 is in a notebook from a conference in April. Q3 comes and goes. The relationship goes cold from neglect, not from a real no.
Context evaporates between conversations
You spoke to someone four months ago, the call went well, and now you are back on a call with them and working from memory about what they said about their budget cycle. The conversation starts from scratch instead of from where you left off. You can feel them noticing.
What Mariana found in Lisbon
Mariana spent time researching how early-stage Portuguese tech founders manage client relationships before they bring on a dedicated salesperson. She expected to find spreadsheet chaos and notebook stacks. She found both, plus something more interesting.
"Several founders told me they had tried a proper CRM, set it up carefully, and abandoned it within six weeks," she says. "But when I asked what they were using instead, it was never nothing. It was the inbox as a search tool, the calendar as a reminder system, and LinkedIn as a contact directory. They had a system. It just was not visible, and it would break the second someone else needed to use it."
One founder she spoke to, running a legal-tech consultancy in Porto, had the simplest setup Mariana considered genuinely good. "She kept one document per active account. Every time something happened, she added a line. No stages, no required fields. Just: what happened, what I need to do next. That was her CRM. It worked beautifully as long as she was the only person who needed to know."
"The moment she brought in a business developer, it all had to be rebuilt," Mariana says. "Not because the information did not exist. It existed. But it existed in a format only she could read. The new person spent their first three weeks having conversations that should have been ten-minute briefings."
"That is the bar," she adds. "Not a perfect CRM setup. Something you will actually use, that someone else could read without your help."
The minimum CRM habits that work for founders
These habits keep a founder-led pipeline from decaying into confusion. None of them require a complex system or more than fifteen minutes a day.
- Log the next step, not the full history. Every deal record needs one thing: what happens next and when. Not ten fields about probability and stage. Just: follow up after their board meeting, third week of September. That single piece of information is what prevents a warm relationship from going cold without anyone noticing.
- Keep one running note per account. Not a form. A running thread of what happened and what it might mean. The kind of thing you would use to brief yourself before a call. Founders who do this consistently are almost always better prepared than those who rely on inbox search before a meeting.
- Do a ten-minute scan of open relationships each week. Not a full pipeline review. Just: which conversations have not moved in three weeks that should have? This is the one habit that catches warm leads before they go cold. At twenty to thirty active relationships, it takes about ten minutes and it will eventually save a deal.
- Connect your calendar. A CRM that syncs calendar events has a record of meetings even when you forget to log them. If the system knows a meeting happened, there is a starting point for the account history even when you have not written a note. Some context is better than none.
When to hand off and what needs to exist first
The moment a founder brings someone in for sales or business development, everything that lives in their head needs to exist somewhere else. This transition is where the absence of a CRM has its most concrete, measurable cost.
What a new salesperson or account manager needs for each active relationship:
- Who the contacts are and what role each plays. The new person needs to know who to call for what, who has decision authority, and who influences decisions without officially being involved. A list of names and titles without context about how they relate to the process is not useful to anyone.
- What has been discussed and what was left open. Not a transcript. The key points: what they have agreed to in principle, what they were uncertain about, what you said you would do next. The three things a new person needs to have a credible continuation conversation.
- What would actually move the deal forward. The founder usually has an opinion on what the real obstacle is and what would unblock it. That opinion should be in the CRM record, not just in memory. A new hire who knows the obstacle is procurement timing handles the next call very differently from one who does not.
- Any context about the relationship itself. How long you have known them. Whether there is history before the current deal. Any sensitivities or dynamics that would affect how someone new should approach them. This is often the most important information and the most absent from CRM records.
If this information has been going into a CRM, the handoff takes an afternoon. If it has not, the new person spends weeks reconstructing context from email threads and asking the founder questions they should not still need to answer three months in. The cost of missing records shows up most clearly at the moment of handoff, not before it.
How Lumenbase handles this
Lumenbase is built to work for a single founder managing their own pipeline, while also scaling cleanly when a team joins.
- Simple enough to use without a dedicated process owner. The account timeline captures emails, meetings, and notes without requiring a structured workflow designed for a team. Add context when it matters, and the history builds over time without a manual process around it.
- The Feed surfaces which relationships need attention. Without building a full pipeline review process, the Feed shows which accounts have gone quiet and which deals have stalled. For a solo founder, this replaces the weekly review meeting you would otherwise skip.
- Lumo helps with pre-call prep and follow-up. When you come back to an account after six weeks, Lumo can summarize where things were, what was discussed, and what the next step was. That is the context a solo founder needs before a call, and the context a new hire needs on their first day.
- Scales to a team without a migration. The records that work for solo founder-selling become the foundation for an account manager or BDR to pick up. The history is already there when they join.
Who this is for
Founders at early-stage B2B service businesses who are doing their own selling and want to stop relying entirely on memory and inbox search. Also useful for anyone preparing to hand off sales to a first dedicated hire and trying to figure out what the CRM needs to look like before that person joins. If you have closed between five and twenty clients primarily through personal relationships and have no system for managing those relationships other than your own attention, this article is for you.