Ask a sales rep how they feel about their CRM and you'll get a very specific kind of sigh. Not anger. Not even frustration anymore. More like the resigned look a delivery driver gets when you ask them about their routing software. It's a thing that exists. It's mostly in the way. You work around it.
This is wild when you think about it. CRM is a category that's been mature for two decades. There are public companies worth hundreds of billions of dollars built on the premise of helping sales teams. And the people the software is supposedly for actively dislike using it. That gap is the opportunity.
We've spent the last year building Station CRM and working on the next iteration internally called Basic CRM. Here are the things that became really obvious once we started talking to reps instead of pricing pages.
Why every CRM ends up as a data graveyard
The standard CRM data model is built around pipeline reporting. Sales managers want to know what's in the funnel, what stage each deal is at, what the forecast looks like. To produce that report, every deal needs a bunch of structured fields. Amount. Stage. Close date. Probability. Next step.
The natural conclusion, if you're building a CRM in 2010, is that you make those fields required. If reps don't fill them in, the report breaks. So you put little asterisks next to them and you fight political battles inside companies about which fields are mandatory.
This is the core mistake. You've optimized for the manager's report. The rep, the person who actually generates the data, now has to do unpaid data entry between every call. They don't want to. They have a phone and a quota. So they do the absolute minimum. They fill in "Stage 3" without much thought. They put a placeholder close date because the field is required. They skip the "next step" field because there's no next step yet, they just had a good conversation.
Six months later the data is full of placeholders. The pipeline report still runs. It's just completely meaningless. Everyone knows. Nobody can fix it because the whole org has built on top of the bad data.
What reps actually do
If you watch how a real sales rep operates, the CRM is almost never the system of record. Their actual system of record is:
- Notes in their phone
- Voice memos after calls
- Emails to themselves
- Their head
- One messy Google Doc per major account
The CRM gets updated, in batches, the night before the pipeline review. The information is days out of date and stripped of everything that made it useful. The texture of the conversation. The personal details. The fact that the buyer just had a kid, that procurement is the actual blocker not the champion, that the budget is approved but they're waiting on a security review.
None of that fits in a required field. So none of that ends up in the CRM. So the CRM is useless for actually selling, and now you understand why reps quietly hate it.
What changes when you build AI-native
This is the part that makes us bullish on the next generation of CRM. The required-fields problem was always the wrong solution to the right problem. Pipeline reporting genuinely matters. You do need to know what's in the funnel.
But you don't need to make the rep do the work of structuring the data. You can let them dump whatever they have, in whatever form they have it, and have the system do the structuring for them.
Voice memo after a call? The system transcribes it, extracts the deal stage, updates the next step, and surfaces a one-line summary to the manager. The rep doesn't open the CRM. They drove home and talked into their phone.
Email thread with a prospect? The system reads it, updates the deal, attaches the relevant context to the account record. The rep doesn't have to log anything.
Calendar invite for a follow-up? That's the next step. The system adds it. No one filled out a "next step" field.
This is what we mean when we talk about AI-native software. The data model is inverted. Raw mess in, structured data out, automatically. The rep does the job they were hired for. The structured data exists because the system is doing the structuring work.
The five non-obvious things we learned
1. Reps trust voice more than typing
When we gave reps the option to type or talk, they talked. Almost universally. Voice is faster, lower friction, and crucially it preserves the texture they want to remember. Tone, hesitation, what got asked twice. That texture is gold for the model when it's later trying to draft a follow-up.
2. The undo button matters more than the AI
The single biggest objection we get from reps is "what if the AI gets it wrong and updates the deal incorrectly?" Reasonable concern. The answer is not a better model. The answer is an undo log that shows every change the system made, attributed clearly, with a one-click revert. We make that surface a first-class part of the UI, not an audit log buried in settings.
3. Managers want narrative, not just numbers
Pipeline reports have been numerical for so long that we forgot they don't have to be. Sales managers, the good ones, actually want to know what's going on in a deal. A short paragraph that says "Champion is excited, procurement is the blocker, expected to close Q3 if we get past security review by end of June" is way more useful than $250K, Stage 4, 60% probability. The AI can produce the paragraph cheaply.
4. Mobile-first changes everything
Reps live on their phones. The traditional CRM is a desktop SaaS app with a mobile afterthought. If you flip that and design for the phone first, you start making different decisions. Quick voice capture. Push notifications for what matters. A genuinely fast deal-search experience. Most of the desktop features you thought were core turn out to be manager features that should live somewhere else.
5. Integrations are the product
The thing the CRM does is sit between the email, the calendar, the call recorder, the prospecting tool, and the proposal generator. If the CRM is bad at being in the middle of those things, it doesn't matter how good the UI is. We spent more engineering time on integration plumbing than on UI in the first year. That ratio felt wrong at the time. It was right.
Where this goes
The honest take is that the entrenched CRMs are unlikely to be displaced by being faster or prettier. They'll be displaced by being a different shape. AI-native, voice-first, undo-everywhere, narrative-output. A CRM that reps actually open because it makes their job easier rather than harder.
That's the bet we're making. It's a bet a lot of other smart teams are making at the same time, so we don't think we're alone in seeing it. But we do think the people who get it right will be the ones who took the rep experience seriously from day one, instead of treating reps as data input devices.
If you're working on sales tooling and want to compare notes, hit us at [email protected]. And if you want to read more on the design philosophy, see Why Most Sales Software Treats Reps Like Robots for the longer argument.