Founder-Mode Selling: CRM Habits When the CEO Is Also the Sales Team

You are in fifteen different conversations at once. A warm introduction from a conference two months ago that just replied. A renewal with your second-biggest client. A referral from a happy customer. A cold email that somehow got a response. These are relationships at various temperatures. Some close in six weeks. Some are three years out. Some go nowhere.

• Everything lives in one person's head: Irreplaceable right now and completely inaccessible the moment the founder is unavailable.
• Most CRMs are built for teams: Enterprise setups with required fields and handoff stages were designed for five to ten people.
• Follow-up falls through at the worst moments: The warm lead who said reach back in Q3 is in a notebook from April. Q3 comes and goes.
• Context evaporates between conversations: You spoke to someone four months ago and now work from memory about what they said about their budget.

Mariana researched how early-stage Portuguese tech founders manage client relationships before bringing on a dedicated salesperson. Several told her they had tried a proper CRM, set it up carefully, and abandoned it within six weeks.

One founder running a legal-tech consultancy in Porto had the simplest setup Mariana considered genuinely good: one document per active account, one line per interaction. No stages, no required fields. Just: what happened, what I need to do next.

"The moment she brought in a business developer, it all had to be rebuilt. Not because the information didn't exist - it did. But it existed in a format only she could read."

1. Log the next step, not the full history
2. Keep one running note per account
3. Do a ten-minute weekly scan of open relationships
4. Connect your calendar

What a new salesperson needs for each active relationship:

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.

• Who the contacts are and what role each plays
• What has been discussed and what was left open
• What would actually move the deal forward
• Any context about the relationship itself

• Simple enough to use without a dedicated process owner
• The Feed surfaces which relationships need attention without requiring a pipeline review process
• Lumo helps with pre-call prep and follow-up drafts
• Scales to a team without requiring a migration