Guide
Founder-led sales: a practical CRM setup
Keep the buyer context, next action, and deal evidence clear enough for someone else to use.
What does a founder need in a CRM?
Start with linked companies, contacts, active deals, and dated next actions. Record the buyer's problem, the people involved, and what was agreed. Add fields when they help you make a decision or hand work to someone else.
Start with the records you will use
Keep a person, their company, and a specific buying opportunity separate. One company may have several contacts and more than one project.
Company and contacts
Record the company, current roles, relationship owner, and how you met. Confirm who uses the service, who supports the purchase, and who can approve it. Y Combinator's enterprise-sales guide describes these as distinct roles.
An active deal
Write the buyer's stated problem, proposed scope, amount and currency if known, and any decision date they gave you. Keep unknowns visible instead of filling them with guesses.
A dated next action
Give each action an owner, a due date, and a clear result, such as sending a scope draft or confirming who joins the review. Link it to the relevant contact and deal.
Define stages with evidence
Use a small set of stages that matches your buying process. The example below is a starting point; adjust it after checking real conversations.
Need discussed
The buyer has described a problem and agreed that it is worth exploring. Record their words and the next conversation.
Scope under review
The buyer has a specific scope or proposal to review. Keep the current version, open questions, and review date linked to the deal.
Decision pending
You know the remaining decision or approval steps and who owns them. Record any blocker and the buyer's timing.
Won, lost, or paused
Use a clear team rule for each outcome. Keep the agreed terms for a win, the buyer's stated reason for a loss, or a return date for a pause. A pause should not silently keep moving the expected close date.
Write notes another person can act on
After a conversation, capture what changed and the next action. In a regular review, check overdue actions, missing buyer decisions, and deals whose status no longer matches the evidence.
Fictional handoff note Company: Cedar Studio Buyer need: Support for a new client portal Contact: Jo, operations lead Budget approver: Not yet confirmed Current stage: Scope under review Open question: Include weekend support? Next action: Alex to confirm the approver on Tuesday Linked evidence: Latest call note and proposal version 2
Keep facts and assumptions apart
Label an estimate as an estimate. Record who confirmed a requirement and when. Check an AI-generated summary against the source before saving a commitment.
Try a small handoff
Ask a teammate to prepare the next step from the record. Note what they still need to ask you, then fill those gaps. Agree on which conversations you will join and which they will own.
Check more than one outcome
Review examples of wins, losses, and stalled deals before writing a playbook. Record repeated objections, buying steps, and exceptions without turning one sale into a universal rule.
Test the setup before moving your pipeline
Use a few sample records to run a complete workflow. Check the plan you intend to buy and keep a list of anything that needs manual work.
Capture and retrieval
Add a note and task, link a document, and find them before a sample call. If you need email or calendar sync, test the supported account type, history limits, and failed-sync behavior.
Ownership and access
Reassign a sample deal and confirm that its tasks and shared history remain usable. Check that private notes and unrelated records stay within the intended access rules.
Reporting and exit
Review open deals by stage, overdue actions, and recorded outcomes. Export a sample and check which notes, links, activities, and fields it includes before relying on an exit path.
Frequently asked questions
Sources
Sources checked on 18 September 2026. Examples are fictional; checklists are suggested workflows.