The Pattern I Couldn't Unsee
I spent 20 years training salespeople.
Good training. Real frameworks. Workshops that got standing ovations. Managers who shook my hand afterward and said, "This is going to change everything."
And then I'd check back six weeks later.
The reps were doing the same things they always did. The CRM still looked the same. The pipeline was still managed by gut feel. The forecast meetings were still theater.
For years, I blamed retention. I thought we needed better reinforcement, better coaching, better follow-up. So I'd design more elaborate training programs. More role-plays. More certifications. More check-ins.
Nothing changed. Not really.
It took me an embarrassingly long time to see what was actually happening.
The Realization
The training wasn't the problem. The reps actually understood the methodology. They could run a solid discovery call. They could identify pain, quantify impact, map the buying committee.
But none of that mattered if it never made it into the CRM.
And it almost never made it into the CRM. At least not accurately. Not with the detail that makes data useful.
The reps I worked with were mostly field sellers. Manufacturing. Med device. Construction. Services. People who spent their days in trucks, on job sites, in conference rooms 200 miles from the office. They didn't have a laptop open after every meeting. They didn't have 15 minutes to sit in a parking lot and update 17 CRM fields.
They had a phone. And a drive to the next appointment.
I was building a great second floor on a cracked foundation. It didn't matter how good the sales methodology was if the system that was supposed to capture it was fundamentally broken.
The Cracked Foundation
Think about what we ask field reps to do.
We invest in CRM platforms. We invest in pipeline management tools. We invest in analytics and forecasting. And then we tell the people who generate the raw material for all of those systems — the reps who are actually in the room with prospects — to manually type everything in. At the end of the day. From memory.
Reps spend roughly 25% of their workweek on CRM data entry. That's 10-11 hours. For a team of 10 reps earning $100K in total compensation, that's $250,000 a year in salary going toward data entry instead of selling. And the data they enter is degraded by hours of delay, multiple meetings stacking on top of each other, and the natural human tendency to simplify and optimize when the real goal is just to make the field go away.
We weren't getting bad data because reps were lazy. We were getting bad data because we designed a workflow that made good data nearly impossible.
The Phone Was Always the Answer
Once I saw the problem clearly, the solution seemed obvious. Maybe too obvious.
Field reps have exactly one device they always carry, always use, and always trust: their phone. Not a laptop. Not a tablet. Not an app they need to log into. A phone.
And they have exactly one window where their meeting recall is perfect: the walk from the conference room to the car. Three minutes. Maybe five.
What if a rep could just call a number after a meeting — while walking to the car, while the information is fresh — and talk through what happened? What if that call was parsed by AI into structured CRM data? No typing. No screen. No end-of-day guilt.
That's CallJune. That's the whole idea.
A rep calls in. They say what happened. The AI asks follow-up questions if needed. The conversation becomes structured data — next steps, objections, budget, timeline, stakeholders — and it's written to the CRM automatically.
It works from any phone. It doesn't require internet. It doesn't require being logged into an app. It works on the drive between meetings, on a job site, in a parking lot. Everywhere field reps actually are.
Why Not an App?
People ask me this all the time. Why not build a mobile app? Why a phone call?
Because I've watched what happens with apps.
A new app gets introduced. There's a rollout. There's training. Reps download it. Maybe they use it for a week or two. Then it joins the graveyard of tools on their phone that they opened once and never touched again. The resistance to adding another tool, another login, another screen to a field rep's day is enormous — and justified. Every additional platform is friction. And friction kills adoption.
A phone call has zero friction. Reps already know how to make a phone call. They're already holding their phone. There's nothing to download, nothing to learn, nothing to navigate. It's the one workflow that requires no behavior change at all.
That's what "call-to-CRM" means to me. Not a technology play. A workflow match.
What I Learned from 20 Years of Getting It Wrong
I don't say that lightly. I spent two decades focused on the wrong layer of the problem. I was teaching reps what to do in the meeting, when the real bottleneck was what happened after the meeting.
The best sales methodology in the world is worthless if it lives only in the rep's head. If it doesn't make it into the system, it doesn't exist for anyone else — not the manager, not the forecast, not the next rep who takes over the account.
The gap between what happened in the room and what's in the CRM shouldn't exist. And with voice AI and a simple phone call, it doesn't have to.
That's why I built June. Not because I'm a technologist. Because I'm a sales guy who finally saw where the real problem was.
Try It Yourself
If any of this sounds familiar — if you've watched good training fail to stick, if your forecast meetings feel like fiction, if your CRM data doesn't match what your reps are actually hearing in the field — you can try CallJune right now.
There's a demo line oncalljune.ai. Call it. Talk through a mock meeting. See what comes back as structured data.
No demo request form. No SDR call. Just a phone number and a conversation. The way field sales should work.