A software company's sales team inherited a working CRM and instructions
I moved deals out of Notion and left my notes with written procedures and a knowledge base.
A 13-person company's deals were going cold in hundreds of chats. I moved them into one CRM and left it, with my notes, a set of SOPs and a knowledge base, for the next person to run.

Context
I worked at a venture-funded software company as it finished its first year with about 13 people. Notion had started as a few pages for company values and hiring, and grew to hold the leads, the deal notes, product work, tech support and the ticketing system. Most deals ran through chat apps, and the team sat in hundreds of group chats with prospects and partners.
Problem
Notion has no funnel analytics, so nobody could see how many deals moved from one stage to the next. Deal conversations sat in chat threads only one person might see. A prospect would reach out, the right person would miss it, and the thread went cold. My estimate at the time was that visibility on those chats alone would have put the company three to five deals further ahead over the previous two months.
Approach
The first option on the table was building an app on top of Notion. CRMs already exist, so I tested them instead, against the company's real deal data. One colleague wanted the biggest-name CRM, and I told the team it tries to do everything and isn't the best at any of it. I ran trials of ClickUp and two newer CRMs, exported everything from Notion and built the first version of the pipeline in ClickUp. I set the rollout for one quarter: sales and business development first, then marketing, then the product team if it held up. I gave myself a target of 30 leads in the new system to show the team the switch worked. And I structured every contact, deal and note so the same data could feed reporting and automation later.
Tools used
- Notion export to CSV
- ClickUp pipeline, first version
- CRM trials on real deal data
- SOPs and a team knowledge base
Result
The company's leads and deal notes came out of Notion as an export and into one CRM. I left the entire CRM with all my notes in it, a set of SOPs and a knowledge base when I moved on later that year, in much better shape than I found it.
Impact
Whoever took over sales started from a working pipeline, written steps for running it and my notes inside it.
Lessons
Get the reasons behind each deal into the CRM before the person who knows them leaves. Those reasons lived in my notes, so I wrote the SOPs and the knowledge base before I left.
Who this is for
For companies running sales out of docs and chat apps with no view of their funnel, and for founders hiring someone to set up a CRM that keeps working after that person moves on.
Get a quoteThe method behind this result
- Workflow DesignWorkflow design helps sales and onboarding teams agree who accepts a customer. Missing information needs a return path and someone responsible for resolving it.
- State Machine EverythingA change compiles, passes code review and gets merged. The page it was meant to fix is still wrong. Each person completed the job they were given, but nobody checked the result the customer would receive. A useful workflow has to name the evidence that permits work to move, who evaluates it and where the work goes when that evidence is missing.