Your CRM Should Fit Your Business, Not the Other Way Around
Custom fields, flexible pipelines, and conversational input let you shape your CRM around how you actually sell — not how someone else thinks you should.
Oana ClopotelNot Every Pipeline Looks the Same
A freelance designer tracking project inquiries has nothing in common with a SaaS founder nurturing monthly trials. A consulting firm managing retainer renewals works differently from a cleaning company booking recurring appointments. But most CRMs ship with the same default pipeline: Lead, Qualified, Proposal, Negotiation, Closed Won.
When I tested this standard pipeline against real workflows from different businesses, the mismatch was obvious within minutes. People were either cramming their process into stages that didn't fit, or ignoring the pipeline entirely.
If your CRM's pipeline doesn't reflect how you actually sell, you'll stop using it. Not because you're lazy — because it's useless.
The Freelancer Who Needs Three Fields, Not Thirty
A freelance consultant I watched during testing had a simple sales process: someone reaches out, they have a discovery call, they send a scope document, the client signs. Four stages. Three fields that actually matter: project type, estimated budget, and decision timeline.
The CRM they'd been using had 14 required fields on the deal form. They filled in maybe five honestly and left the rest as defaults. Their pipeline looked "full" but told them nothing real.
With custom fields, you track only what matters to your business. A freelancer needs project type and budget range. A SaaS founder needs trial start date and plan tier. A service company needs service frequency and location. The fields you track should match the decisions you make — nothing more.
Four Businesses, Four Pipelines
Here's what I noticed when testing with different types of businesses. Each one needed a completely different setup.
Freelancers and consultants sell based on relationships and expertise. Their pipeline stages might be: Inquiry, Discovery Call, Scope Sent, Contract Signed. The custom field that matters most? Referral source — because their next client almost always comes from their last one.
Small agencies juggle multiple projects across team members. They need stages like: Brief Received, Proposal Draft, Client Review, Signed Off. And they need a custom field for project lead, so they know who owns each deal without opening it.
SaaS founders track trial conversions. Their pipeline looks like: Trial Started, Activated, Demo Booked, Subscribed. The critical custom field? Days since signup — because a trial that's been sitting for two weeks without activation is already dead.
Service businesses — cleaners, landscapers, contractors — care about recurring revenue. Their pipeline: Estimate Requested, Site Visit, Quote Sent, Booked. Custom fields for service area and frequency tell them more than any deal value ever could.
Same CRM. Four completely different setups. That's the point.
Tell Kit What Happened. Skip the Forms.
Custom fields and flexible pipelines solve the structure problem. But there's still the input problem — who has time to fill out forms after every call?
This is where conversational input changes things. Instead of clicking through dropdowns and date pickers, you tell Kit what happened: "Had a discovery call with Marcus at GreenLeaf, he wants bi-weekly office cleaning for their new location, sending a quote tomorrow."
Kit creates the deal, picks the right pipeline stage, fills in the custom fields, and sets a follow-up. You described a conversation. Kit turned it into structured data. That's the difference between a CRM you maintain and one you actually use.
The fastest way to capture a deal isn't a form. It's a sentence.
Your Workflow Came First
Most CRM advice tells you to map your sales process to the tool's structure. Define your stages. Configure your fields. Build your automations. Then start selling.
That's backwards. You already have a sales process. It might not be written down, but it's there — in your habits, your follow-up timing, your gut sense of which deals are real. A CRM should capture that process, not replace it with a template.
When we tested Founders Kit with founders who'd already abandoned one or two CRMs, the reaction was consistent. They didn't want more features. They wanted fewer assumptions. Let me name my own stages. Let me track what I care about. Let me describe a deal in my own words and have the system figure out the rest.
The CRM that sticks isn't the one with the most features. It's the one that gets out of your way.
Stop Bending Your Business Around Software
If you've ever renamed a deal stage to something that doesn't quite fit, or left a required field blank because it doesn't apply to your business, or avoided your CRM because updating it felt like filing taxes — the tool isn't working for you. You're working for it.
Your business is specific. Your sales process is yours. A CRM should shape itself around how you work — not ask you to reshape how you work around it.