The Six-Week Problem
For the first 15 years of my career, I was convinced the answer to better sales performance was better training.
I built programs for field teams across manufacturing, medical devices, construction, and enterprise services. I taught SPIN. I taught Challenger. I taught consultative selling, solution selling, and frameworks I developed myself from watching hundreds of reps work in the field.
The workshops went well. Reps engaged. Managers were enthusiastic. Post-training survey scores were excellent. Everyone left feeling good about the investment.
Then six weeks would pass.
I'd come back to audit adoption, and the picture was always the same. The reps remembered the concepts. They could articulate the methodology if you asked them. But the CRM data looked identical to how it looked before the training. The pipeline stages hadn't changed. The deal notes were still sparse or nonexistent. The forecast meetings were still a round-robin of "feeling good about this one" with nothing substantive to back it up.
I called this the Six-Week Problem, and I spent years trying to solve it with more training.
The Wrong Diagnosis
My first instinct was reinforcement. If training didn't stick after one workshop, we needed ongoing coaching. So I designed multi-week programs. Monthly check-ins. Certification tracks. Manager enablement so the frontline leaders could reinforce the methodology after I left.
It helped. A little. The reps who were already disciplined got a bit better. The ones who were struggling stayed pretty much the same.
My second instinct was accountability. Maybe the reps needed clearer expectations. Required fields. Manager reviews. CRM compliance scores on the dashboard.
That actually made things worse. Reps started filling in fields with the minimum viable data to avoid getting flagged. "Next Steps: Follow up." "Notes: Good meeting." The CRM had more data in it, but the data was worthless. We'd added compliance without adding insight.
My third instinct was technology. Better CRM design. Simplified views. Mobile-first interfaces. Fewer required fields.
That helped marginally, but didn't solve the core problem. Because the core problem wasn't the interface. It was the workflow.
Watching a Rep Named Marcus
The moment I finally understood came from watching — not consulting, just watching — a field rep named Marcus work a full day in the field.
Marcus was good. Genuinely good. Great rapport, sharp discovery, natural closer. The kind of rep who makes a sales trainer feel like their work matters.
He had four meetings that day. I rode along for all of them.
After the first meeting — a strong one, great conversation with a VP of Operations — Marcus got in his truck and immediately started driving to the next appointment 45 minutes away. During the drive, he took a call from his manager about a different deal. By the time he arrived at the second meeting, the first one was already fading.
After the second meeting, same thing. Back in the truck. Call from a colleague. Quick lunch in the driver's seat. Third meeting.
By 5:30 PM, Marcus had completed four meetings, driven 180 miles, and fielded a dozen calls. He pulled into his driveway, walked inside, and sat down at the kitchen table with his laptop.
He opened Salesforce. He stared at the screen. And then he started typing.
I watched him try to reconstruct four conversations from memory. The first one — the strong VP meeting from 8:30 that morning — had lost almost all of its detail. He couldn't remember the specific objection the VP raised about implementation timeline. He couldn't remember the name of the CFO the VP had mentioned. He typed "Good discovery, follow up next week" and moved to the next record.
That was the moment I understood. The problem wasn't Marcus. The problem was that we'd designed a system that expected humans to do something humans are terrible at: retain detailed information across 8+ hours of competing inputs and reconstruct it accurately at the end of the day.
The Only Device They Always Have
Once I saw the real problem, I started looking for the real solution. Not a better CRM. Not a better process. A different workflow entirely.
I kept coming back to one observation: field reps have exactly one device they always carry, always use, and always trust. Their phone.
Not their laptop — that's in a bag, usually in the trunk. Not a tablet — most don't carry one. Not a CRM app — the download-to-abandonment cycle on mobile CRM apps is brutal. A phone. The same device they use to call prospects, text their manager, and get directions to the next meeting.
And they have exactly one window when their recall is perfect: the three minutes between the conference room and the car.
What if that was the CRM entry point? Not the laptop at 7 PM. Not the mobile app between bites of a gas station sandwich. The phone call they could make while walking to the parking lot, with the meeting still fresh in their mind.
Building June
I'm not a developer. I'm a sales guy. The idea of building an AI product from scratch was, candidly, intimidating.
But I couldn't un-see what I'd seen with Marcus. And with every field team I worked with afterward, I kept seeing the same pattern. Great reps, great conversations, terrible data. Not because of laziness. Because of workflow.
So I started building. I partnered with people who understood voice AI and natural language processing. We built a system where a rep could call a phone number, talk through what happened in a meeting, and have the AI parse that conversation into structured CRM fields.
The key decisions we made early:
- Phone call, not app. Zero friction. No download, no login, no new behavior to learn. If you can make a phone call, you can use June.
- Works from any phone. Landline, cell, international, doesn't matter. No internet required on the rep's end. This matters for reps in rural territories, on job sites, or in areas with spotty connectivity.
- AI asks follow-up questions. If the rep mentions a budget but doesn't give a number, June asks. If they mention a stakeholder but don't explain their role, June asks. The goal is complete data, not just captured audio.
- Output goes straight to the CRM. Not to a dashboard the rep has to check later. Not to a holding area for manual review. Straight to Salesforce, Zoho, HubSpot — wherever the data belongs.
The first time a test rep called in after a meeting and we watched the CRM populate in real time with structured, detailed, accurate data — better data than any rep had ever typed in manually — I knew we had something.
What I Think About Now
I still think about training. I still believe in sales methodology. I still think SPIN works, Challenger works, and that reps who understand consultative selling outperform those who don't.
But I also know that methodology without capture is theater. If the insight from a great discovery call never makes it into the system, it never influences the forecast. It never informs the coaching conversation. It never transfers when the rep moves on and someone else inherits the account.
The irony is that I spent 20 years trying to fix the output (sales performance) when the real bottleneck was the input (data capture). Better inputs produce better outputs. It's obvious in hindsight. It always is.
Where We Are Now
CallJune is live. Reps are calling in. CRM data is showing up that's more detailed and more accurate than anything their managers have seen from manual entry. And the reps are spending 3 minutes on the phone instead of 15-20 minutes at a laptop.
I don't pretend that one product solves every problem in field sales. It doesn't. You still need good training, good coaching, good leadership, and reps who care about their craft.
But you also need the data. And the data has to be real. Not reconstructed at 7 PM from a fading memory. Not batch-updated on Friday from a week's worth of stacked conversations. Real, accurate, captured in the moment when the rep knows exactly what happened.
That's what I built. And if you're managing a field team and any of this sounds familiar, I'd love to talk about it.
There's a demo line at calljune.ai. Call it yourself. Takes about 3 minutes. You'll see exactly what your reps would see.
Or just grab 15 minutes on my calendar. No pitch. Just a conversation about whether this fits your world.