Shawn Johnson builds CallJune and writes about helping field sales teams capture customer-meeting insights in their CRM while those details are still fresh.
They are most useful for practical content on capturing field sales meeting insights in CRM.
Best for
B2B sales technology co-marketing webinar or expert content partnership on field sales data capture and forecast credibility.
Not for
A sales-methodology training company seeking paid sponsorship, guaranteed demo bookings, and a fixed rate card.
Key takeaways
79% of what a rep learns in a sales meeting never makes it into the CRM.
A five-step, three-minute post-meeting debrief helps capture meeting context.
A procurement change mistaken for small talk surfaces only after a deal stalls.
Check first: Confirm audience demographics, recent post performance, and independent verification of reported statistics and customer outcomes.
Main ideas
Field meetings are the CRM's blind spot · The hallway debrief holds what the CRM cannot · Deals slip rather than die, and the qualifying questions arrive late
Shawn Johnson builds CallJune and writes about a problem in field sales: useful details from customer meetings often fail to reach the CRM while they are still fresh.
Across their LinkedIn posts, they show what can disappear—a buyer’s concern about implementation, an unexpected procurement stakeholder, or an early warning that a deal is changing—and why that loss can leave managers with a misleading view of the pipeline.
Their posts are useful to sales leaders and RevOps readers looking for concrete ways to capture meeting context, ask existing qualification questions sooner, and spot deal risks earlier.
Johnson makes an abstract data-quality problem tangible by tracing what a rep heard to what a manager or CRM later sees.
One post distinguishes recording that implementation was discussed from preserving that the buyer cared more about implementation than features; another follows a procurement change that is mistaken for small talk and surfaces only after a deal stalls.
They also offer a practical counterpoint to the problem-led stories: a five-step, three-minute post-meeting debrief, and the idea of asking a team’s existing qualification questions on the day of the meeting.
The examples range from rep workload and buyer access to forecast credibility, but return to the same argument: capture the substance of field conversations at the moment it is available.
The posts consistently connect this argument to CallJune, so readers should understand them as both practical sales commentary and a business’s case for its product.
Ask for independent verification of reported statistics and customer outcomes.
Johnson's recurring argument is that field sales is where deals are won or lost, yet it is the one channel that leaves no record: CRM was designed for desk work, where email and video calls log themselves but a handshake does not.
Read more
From that premise, they build a consistent set of priorities: capture what happened in the first minutes after a meeting rather than at 10pm; ask the qualification questions a team already owns on the day of the meeting rather than at the next pipeline review; and, when talking to finance, sell forecast credibility instead of data hygiene.
They also argue that the AI tools sales organizations have bought are only as good as what feeds them, and that the newest reps carry the most after-hours typing and get the least coaching.
Posts usually open with a named or personal field scene, widen it with a cited statistic, reframe the problem ("not a discipline problem, a process problem"), and close with a question to sales leaders.
Johnson cites figures from Gartner, MIT Sloan and Salesforce.
Field meetings are the CRM's blind spot
Johnson argues the gap is not rep discipline but a system built for the wrong person.
Read more
CRM was designed around two monitors, a quiet office and ninety minutes between calls: email and video calls log themselves, while the handshake leaves nothing behind. The information that actually decides deals is gathered in lobbies, on jobsites and in distributors' back offices, and half of it never reaches the record.
One post sets a manager's paid AI summary beside a week in the field: every inside-sales call, objection and next step written up before the coffee is cold, versus one line covering six field reps, 900 miles of territory and fourteen meetings.
Another opens in a rental car outside a customer's office, with four minutes to note that the incumbent missed a deadline; the CRM update came at 10pm in a hotel, after half the day was gone.
Johnson cites reps spending about ten hours a week on CRM, with only 23% of that data accurate, and 79% of what field reps learn in customer meetings never entering the CRM.
The earlier posts in this set tell the story through Johnson's own twenty-five years in field sales: the rental car, the notebook, the late-night update. Later posts hand the scene to named reps, such as Kevin's ninety-minute drive to a Fresno distributor and Marcus typing in a customer's lot, pairing each anecdote with survey figures.
Johnson argues top closers already capture exactly what matters; they just say it in a hallway instead of typing it into a field.
Read more
That's why the debrief works: fast, honest, no typing required. Its weakness is that it only happens when the rep walks past the right person, so the intelligence is real but random.
The post lists six things a closer says in a hallway that never make the CRM: a buyer flinching at a competitor's name, procurement appearing in a meeting unannounced, a buyer pressing on implementation rather than features, a VP of engineering sitting silent through a demo, price being accepted too easily, and a closer sensing the deal is already lost three weeks before anyone writes it off. Johnson's point about the record is specific: "discussed implementation" survives, while the meaning—that the buyer cared about implementation and not features—evaporates.
Deals slip rather than die, and the qualifying questions arrive late
Johnson argues deals rarely die in a moment.
Read more
They slip through a champion changing roles, a new name appearing in the room or budget moving elsewhere; the signal lands first in one rep's head.
They also argue that the qualification questions teams already paid to train on—MEDDIC, SPIN or a homegrown stage gate—are fine.
The break comes when those questions get asked eight days later at a pipeline review, forcing the rep to reconstruct an answer.
A rep leaves a plant in Grand Rapids after a good meeting.
Crossing the lot, his champion mentions procurement is looking at the purchase centrally, then asks about the Lions game.
The rep files the first half under small talk.
Three weeks later, the deal still sits at 80 percent on the board, then goes quiet.
Nobody switched to a competitor; the buyer just stopped deciding.
In another post, a branch manager asks a rep what the buyer said about budget at a meeting eight days and eleven stops earlier, and the room nods at a reconstructed answer.
Johnson's proposed fix is one question asked while the rep can still answer it: what changed today, and what could still kill this.
Posts in this vein narrow the fix to a single question; most others leave the ask broader: the team's own questions, asked sooner.
Johnson's practical argument is that near-perfect recall lasts only three to five minutes after a meeting, before memory starts filling gaps.
Read more
The debrief should be spoken aloud immediately rather than typed at night: replace the end-of-day CRM session with a short call from the parking lot, using the words a rep would naturally use.
The five-step routine: call within five minutes of leaving; say what happened instead of navigating picklists; name the next step and who owns it; flag anything that surprised you; hang up.
The sample wording covers integration timelines, an unexpected procurement lead, and implementation cost rather than license fee as the main concern.
Johnson reports that a Fortune 50 consumer-goods team moved from 30% to 90% CRM completeness in ninety days with the same reps and the same CRM.
Aimed at revenue operations, Johnson argues bad data is a cost with no owner and no invoice, which is why it hides on the P&L and why 60% of companies never measure it.
Read more
Their recommendation is a reframe, not a cleanup campaign: stop selling hygiene, because nobody funds cleanup, and sell forecast credibility, because clean pipeline data lets finance defend the number to the board.
Citing Gartner's figure of roughly $12.9M a year for the average organization and MIT Sloan's tie of 15 to 25 percent of revenue to poor data quality, Johnson lists where the money bleeds: reps chasing dead leads and rebuilding context the CRM should have held; next-step intelligence from a good meeting never reaching the record while the deal quietly slips; and a board-trusted forecast built on numbers that decay.
Johnson argues the AI sales organizations have already bought is only as good as what feeds it: a screen leaves something behind for a model to read; a parking lot does not.
Read more
They count 87% of sales organizations running AI while a third of field teams use none, and conclude the answer is not a better dashboard but getting the field meeting into the same system the AI already reads.
A manager's paid summary captures inside sales completely, logging every call, objection and next step, then covers six field reps and 900 miles of territory in one line from the single rep who typed something. Johnson's stated aim: a rep calls June from the truck on the drive back, gets asked questions in the team's own words, and puts the answers in the CRM the AI already reads.
The newest reps carry the heaviest typing and the lightest coaching
Johnson argues the rep with the thinnest experience does the most after-hours administration and gets the least feedback on the conversations that would build skill—and that the same group is the most willing to leave.
Read more
Marcus, eight months in, parks in the customer's lot at 5:40 and spends most of an hour typing four visits into his phone, least sure which of them mattered.
Johnson cites Salesforce's survey of 4,050 sellers: the average seller spends 40 percent of the week selling, and the youngest group 35, a gap of about two hours a week of typing.
In that group, 46 percent rarely get feedback on their sales conversations and 47 percent get too little practice before customer calls.
Want to understand what Shawn means by sales information getting lost between a meeting and the CRM?
Read more
This post names six examples, from an unexpected procurement stakeholder to a buyer asking about implementation rather than features. It shows how missing information can change the way a deal is interpreted, even when a CRM entry exists.
The post contrasts what a rep notices with what a CRM typically records.
For example, “discussed implementation” preserves the topic but loses the signal that the buyer focused on implementation rather than features.
It calls the hallway debrief fast and honest, then asks how to make that habit happen after every meeting.
For brands planning a campaign
For a field-sales data-capture campaign, use specific examples of lost context—not just missing fields—to frame the problem. A webinar could ask sales leaders which signals their current pipeline reviews miss.
Looking for a practical example of Shawn’s proposed solution, rather than just the problem?
Read more
This post lays out a five-step, three-minute post-meeting debrief: call promptly, describe what happened, name the next step and owner, flag surprises, and hang up. It gives newcomers a concrete routine to assess.
The numbered steps turn the idea of capturing information while it is fresh into an action a team could test.
Example language includes a buyer’s question about integration timelines, an unexpected procurement lead, and implementation cost as the main concern.
The post reports that a Fortune 50 CPG team’s CRM-completeness increased from 30% to 90% in 90 days.
For brands planning a campaign
A partnership could demonstrate the five steps using a realistic field-sales scenario, then invite attendees to adapt the questions to their own CRM and sales process. Ask for evidence supporting the reported result before using it as campaign proof.
Wondering why the timing of sales questions matters?
Read more
This post follows a manager asking about a meeting eight days later, after the rep has visited eleven places. It shows how even a good qualification question can produce a weak answer when asked too late.
Shawn shifts the focus from which questions a team asks to when it asks them.
The post names methods such as MEDDIC and SPIN, and argues that teams need to answer the questions on the day of the meeting.
It connects delayed recall to a specific management moment: a pipeline review where the room accepts an answer the rep still remembers.
For brands planning a campaign
For a forecast-credibility webinar, this is a useful prompt to discuss the gap between sales methodology and timely execution. A co-created exercise could ask attendees to select one existing qualification question and decide how its answer will be captured after each field meeting.
Want an example of how a deal can change before a CRM forecast catches up?
Read more
The post starts with a champion mentioning that procurement is moving centrally, then shows how that warning can be mistaken for small talk and surface only after the deal goes quiet.
The story makes a small detail—the procurement change—matter by tracing its consequence: the deal remains at 80 percent on the board for three weeks, then stalls. Shawn argues that deals often slip through changes in roles, stakeholders, or budgets, and proposes asking after each meeting what changed and what could still kill the deal.
For brands planning a campaign
This piece can help a campaign connect timely meeting capture with earlier risk detection, rather than presenting it as administrative cleanup. A content partnership could use the central-procurement example to explore which questions help managers spot a deal change before the next review.
Deals slip rather than die, and the warning arrives late2
The hallway debrief is the record nobody keeps1
Bad CRM data as a cost a CFO can see1
AI reached inside sales faster than the field1
Newer reps carry the heaviest admin and the lightest coaching1
Field meetings are the blind spot in CRM data
These posts argue that the CRM was built for desk work — two monitors, a quiet office, ninety minutes between calls — so intelligence gathered in person never makes it into the record.
Read more
One post cites reps spending about 10 hours a week on CRM, with only 23% of that data accurate, and 79% of what field reps learn in customer meetings never entering the CRM. Another contrasts an AI summary that captures every inside-sales call with a single line covering six field reps, 900 miles of territory and fourteen meetings.
A short personal or named-rep scene, followed by a statistic block and a direct question to sales leaders.
For brands planning a campaign
A webinar or content partnership can lead with this documented gap, not product features. The numbers provide the headline; a manager can bring the field-versus-desk contrast to life with a week of their own.
One post lists six things a top closer says in a hallway that never reach the CRM: a buyer flinching at a competitor's name, procurement appearing in a meeting unannounced, implementation questions read as a buying signal, a silent VP, price accepted too easily, and a rep's sense that a deal is already lost.
Read more
The argument: reps capture exactly what matters, just in the wrong place. The hallway debrief works because it is fast, honest and requires no typing.
For brands planning a campaign
A strong panel or podcast angle: ask a sales leader which of the six items their own pipeline review would never surface.
Deals slip rather than die, and the warning arrives late
Two posts trace the same pattern.
Read more
A champion mentions on the way out of a plant that procurement is now looking at the purchase centrally; the rep files it as small talk; three weeks later, the deal still sits at 80 percent, then goes quiet.
The qualifying questions were fine — MEDDIC, SPIN or a homegrown stage gate — but they came eight days after the meeting.
The proposed fix is one question asked while the rep can still answer it: what changed today, and what could still kill this?
For a piece focused on the method, ask what question the team should pose sooner.
For brands planning a campaign
Reframes forecast accuracy as a timing problem, a fit for a co-marketing piece on capturing deal signals during the meeting rather than at the next review.
A post aimed at revenue operations recasts data quality as a line item nobody owns: Gartner puts poor data quality at roughly $12.9M a year for the average organization, MIT Sloan ties 15 to 25 percent of revenue to it, and 60 percent of companies never measure it.
Read more
The advice: stop selling hygiene and sell forecast credibility. Clean pipeline data lets finance defend the number to the board.
For brands planning a campaign
Offers a finance-facing hook for a joint webinar: the cost of bad data on one side, board-defensible forecasting on the other.
A post notes that 87 percent of sales organizations now run AI while a third of field teams use none.
Read more
Its argument: the tooling is only as good as what feeds it — a screen leaves something for the AI to read; a parking lot does not. The manager's paid summary covers inside sales completely and reduces a week of field work to one rep's typed note.
For brands planning a campaign
Positions the collaboration as completing an AI stack the buyer has already funded, not replacing it.
Newer reps carry the heaviest admin and the lightest coaching
A post follows Marcus, eight months into the role, typing up four visits on a phone in the customer's lot for most of an hour.
Read more
Against that, Salesforce's survey of 4,050 sellers: the average seller spends 40 percent of the week selling, and the youngest group 35; 46 percent of that group rarely get feedback on their sales conversations, and 47 percent get too little practice before customer calls. The group with the thinnest experience is also the most willing to leave.
For brands planning a campaign
Identifies enablement and frontline managers, not only revenue operations, as a specific audience for a co-marketing piece on onboarding and coaching.
Most posts follow one shape: a named or personal field scene, a statistic that widens the problem beyond the anecdote, a reframe such as "not a discipline problem, a workflow problem," and a closing question that invites readers to answer.
Read more
Product mentions come late and briefly, as when a rep calls a voice assistant from the parking lot after a meeting.
One post breaks the pattern with instructions: a numbered five-step capture routine and a cited result of 30 to 90 percent CRM completeness in ninety days at a Fortune 50 consumer-goods team. The rest ask questions rather than offer steps.
For brands planning a campaign
Sets the shape of a joint piece: lead with a specific field scene and a number, keep product references to the close. The creator writes short posts built for comments rather than long-form reports.
The earlier posts reviewed here frame the problem through the founder’s experience: the rental car, the notebook, the CRM update at 10pm and the six hallway items a closer never logs.
Read more
Later posts name individual reps — Kevin’s ninety-minute drive to a Fresno distributor and Marcus in the customer’s lot — attach the CallJune voice assistant to a specific moment and pair the anecdote with survey data. Product detail becomes more concrete as the series goes on.
The posts have no publication dates; ask for timestamps before treating this as a chronology.
For brands planning a campaign
A partner should expect the account's current voice — short, scenario-led and product-adjacent — rather than its earlier, purely problem-focused framing.
The relationships Shawn Johnson’s posts describe are narrow.
Read more
The one explicit business connection is CallJune, the sales-call capture product they say they built.
Posts refer to its voice assistant as “June,” the same business under a shorter name.
Beyond that, the posts cite third-party research (a Salesforce survey of 4,050 sellers, a Gartner data-quality estimate, MIT Sloan figures) as supporting data.
The posts don’t disclose sponsorships, affiliate arrangements, client engagements, or investments; ask for confirmation of any such relationships.
CallJune
Owned business
Johnson says they built CallJune, a product that lets field reps call in a short spoken debrief after a customer meeting so details reach the CRM while they are fresh.
Read more
Most of their posts focus on the product, describing how reps “call June from the lot” and answer their company’s qualifying questions by voice. The posts explain the problem CallJune addresses—field meetings that go unlogged—and call the assistant June.
Original disclosure
I built CallJune because I lived this for 25 years and I was tired of pretending the answer was “try harder.”
Shawn Johnson writes about the part of B2B selling that leaves no record.
Read more
Start with the field-meeting posts — the rental car, the ninety-minute drive to a Fresno distributor, the rep typing up four visits in a customer's lot — because the argument begins there: email and video calls log themselves; a handshake does not.
From that base, the work branches into CRM data quality, deal slippage and forecast credibility, coaching for the newest reps, and where AI in sales has and has not reached.
Most posts follow one shape: a field scene, a statistic that widens the problem, a reframe, then a question to sales leaders.
Pick the scenario closest to your own pipeline, then read the posts around it for the figures and counter-arguments.
If you want the same territory from other angles, the three creators below approach stalled deals, enterprise buying committees and sales management from different starting points.
Both write about enterprise sales dynamics through short scenarios rather than advice lists, focusing on what people closest to a deal know but never put in the system: a message heard three different ways by three departments, or a deal that stays alive and earnest for months while quietly going nowhere.
Read more
Steinberg tackles the internal side of the same problem: how sales, finance and product misread a leadership memo, and why nobody will say no to a stalled deal.
Their scenes unfold in meetings, memos and email threads; no capture tool or product enters the story.
Johnson's unfold during field visits and in the CRM record, and most posts end with a concrete habit for capturing the meeting.
Both argue that leverage in B2B selling has shifted out of the top of the funnel — where AI has made personalization cheap and everyone runs the same play — and into the middle, where deals stall unnoticed.
Read more
Both point to conversations already in the stack (call recordings, transcripts, pipeline reviews) as underused evidence of why a deal is or isn't moving.
Karuppanan offers tooling: named AI skills for account research, audience targeting and stall diagnosis, wired into HubSpot or Salesforce and run by an ABM program owner. Johnson offers a human habit and a moment — call within five minutes of leaving the meeting, say what happened out loud — and leaves the software as the place the answer lands.
Both teach sales behavior through first-person stories with dialogue and consequence — a rep who reads the room wrong, a champion sent alone into the CFO's office — and push readers toward a specific conversation to handle differently next week.
Read more
Deal-stage discipline and buying-committee coverage are shared ground.
Chan focuses on the manager and the champion: what a leader does to a team in a bad month, and how to equip a champion to sell internally. They write from the perspective of sales leadership and coaching rather than field data capture, and their posts make no product or CRM-record argument.
For a co-marketing webinar or expert content partnership on field sales data capture and forecast credibility, Shawn Johnson's posts support topical alignment more than audience fit.
Read more
They consistently address field sales leaders, sales managers, and revenue operations people—the same group that would decide on CRM capture and forecast credibility—so the subject matter aligns with a campaign aimed at those roles.
The only reader-side number published in the posts here is their LinkedIn follower count: 4,490, observed 8 October 2026.
That figure indicates account reach, not who is in the audience; the posts show who they address, not who actually reads them.
Treat follower count as a reach indicator and content as a topic-fit indicator; neither confirms that the audience holds the buying roles this campaign needs.
Before committing, ask for LinkedIn follower demographics by job function, seniority, industry, company size, and geography, or an audience survey from a comparable campaign, along with recent performance on posts about CRM capture and forecast credibility.
Shawn Johnson's posts document no partnership, sponsorship, or co-marketing format.
Read more
All nine are their own LinkedIn posts promoting CallJune, the field-sales meeting-capture product described in the identity section, and none carries a paid-partnership disclosure or names a partner brand.
The posts follow a consistent pattern: a field-rep scenario, a statistic about CRM accuracy or forecast credibility, and a closing question about how the reader’s team handles the same gap.
Five of the nine end with a rep calling "June" from a parking lot so meeting details reach the CRM the same day, which reads as a product demonstration rather than a disclosed commercial placement.
Cited research from Salesforce, Gartner, and MIT Sloan appears as supporting data, not as sponsorship.
For a proposed co-marketing webinar or expert-content partnership, the posts offer no published format to plan around: no rate card, media kit, sponsorship page, or past paid collaboration appears.
They do establish a repeatable subject for a co-hosted session: field sales data capture, CRM completeness, forecast credibility, and the cost of stale pipeline data.
Approach them directly and ask about available partnership formats, rates, and past paid collaborations.
Brief: a B2B sales technology company wants a co-marketing webinar or expert content partnership on field sales data capture and forecast credibility, aimed at field sales leaders, sales managers, and revenue operations teams.
Read more
The evidence supports this fit most directly because of subject overlap, not reach.
Nearly everything reviewed sits on this exact ground.
The posts argue that CRMs were built for desk work and that intelligence gathered in person never reaches the record, citing reps spending about 10 hours a week on CRM with only 23% of that data accurate and 79% of what field reps learn in meetings never entering the CRM.
They supply finance-facing numbers for a joint session: Gartner's roughly $12.9M annual cost of poor data quality for the average organization, MIT Sloan's 15 to 25% of revenue, and 60% of companies never measuring it.
They also supply a field-versus-desk contrast ready-made for a live opening: an AI summary that captures every inside-sales call set against one typed line covering six field reps, 900 miles and fourteen meetings, with 87% of sales organizations running AI and a third of field teams using none.
The creator has a repeatable, demonstrated position rather than generic enthusiasm for the topic.
Two posts reframe the problem as timing rather than methodology: the qualifying questions were fine—MEDDIC, SPIN or a homegrown stage gate—but they were asked eight days late.
Another traces a deal that slips because a champion's offhand procurement remark is filed as small talk.
That is a viewpoint a co-hosted session can build around, not just a subject area.
The writing format also travels well to a live event.
Most posts run a scene, a statistic that widens the problem beyond the anecdote, a reframe such as "not a discipline problem, a workflow problem," and a closing question to the reader.
That question works as an audience prompt, which a webinar needs.
Product mention lands late and briefly, as a rep calling a voice assistant from the parking lot after the meeting, so a partner should expect to place its own product at the close rather than throughout.
The only reader-side figure is a LinkedIn follower count of 4,490, observed 8 October 2026, with no job function, seniority, industry, or geography breakdown and no engagement metrics.
This is a strong topic-and-format fit with an unverified audience fit.
Treat it as an expert-content conversation with a credible, evidenced point of view, and ask for audience data before committing spend.
When to choose a specialist
A sales-methodology training company selling qualification-course licenses wants a paid multi-post LinkedIn sponsorship plus short-form video, with guaranteed demo bookings and a fixed rate card, targeting enablement leaders.
Read more
This one fails on message, format, and verification.
On message, Shawn Johnson's public position partly contradicts the pitch.
One post says plainly that most teams do not have a question problem: the good questions were written years ago and sit in a deck, while what is broken is when they are asked.
Another makes the same move for stage gates and frameworks by name.
A training vendor would pay to sponsor a message its own product argues against, a weak foundation for a co-marketing piece however well the topic fits on paper.
On format, the posts do not describe a partnership, sponsorship, or co-marketing offering: no rate card, media kit, sponsorship page, disclosed paid collaboration, or named partner brand on any post.
Five of the nine are plainly product demonstrations, with a rep calling June from a parking lot so meeting details reach the CRM the same day.
There is nothing published to plan a sponsorship-shaped buy against, so the only honest route is a direct conversation about whether any paid format exists.
The account is also single-channel and text-first; the posts do not show video production or multi-format output to support a short-form video commitment.
On verification, the posts do not support a guarantee of demo bookings.
The only quantified audience figure is 4,490 followers, with no demographics, engagement, or performance data.
The posts also carry no publication dates, so posting cadence cannot be stated.
A hard conversion target would be an unsupported promise on both sides.
This is a mismatch judgment against this particular sponsorship, not a claim that Shawn Johnson would never take a paid deal or could not contribute to enablement subject matter.
The newer-rep post, which follows someone eight months in typing up four visits on a phone for most of an hour against Salesforce survey data on coaching gaps, would fit an enablement audience well.
The problem is the sponsorship mechanics, the guaranteed-outcome terms, and a message that runs against their own argument.
A worked campaign example
A worked angle for the good fit: a 45-minute co-hosted webinar plus one follow-up asset, hosted with the sales technology company and aimed at field sales leaders, frontline managers, and revenue operations.
Working title: What your pipeline review can't see.
Opening, five minutes.
Use the desk-versus-field split as the shared problem: a paid AI summary that covers every inside-sales call, against one line covering six field reps, fourteen meetings and 900 miles of territory, with the statistic that 87% of sales organizations run AI while a third of field teams use none.
Ask attendees to estimate what share of their own last week's field work is in the CRM by Friday.
That question is Shawn Johnson's own closing move, so it lands in their voice.
Middle, fifteen minutes.
Screen-share the six things a top closer says in the hallway that never reach the CRM, from a buyer flinching at a competitor's name to price accepted too easily to a rep's sense the deal is already lost.
Ask which one their pipeline review would never surface.
This segment does two jobs: it is the engagement moment and becomes the handout.
Reframe, ten minutes.
Move from what is missed to when it is asked for.
Use the Tuesday-morning scene, where a manager asks a rep about a budget conversation from eight days and eleven visits ago, and the Grand Rapids scene, where a champion mentions procurement moving centrally and the warning surfaces only after the deal goes quiet at 80 percent.
State Shawn Johnson's argument: good questions, asked late.
Then run a live exercise.
Each attendee picks one qualification question their team already asks, writes down the moment after the next field meeting when it will be answered, and names who collects it.
The blank worksheet is the deliverable they leave with; show a completed example so the exercise is demonstrated as well as handed out.
Close, five minutes.
Give the five-step three-minute debrief as the takeaway routine: call within a few minutes of leaving, say what happened rather than what the CRM wants, name the next step and its owner, flag anything surprising, hang up.
If the reported result of a Fortune 50 consumer-goods team moving from 30% to 90% CRM completeness in ninety days is used, label it as Shawn Johnson's own reported claim and ask beforehand whether it can be substantiated.
One brief product mention at the very end, framed as a rep calling from the parking lot, matches how the account handles product elsewhere.
Follow-up asset.
One page: the six hallway items on the left, the completed one-question capture example on the right, and space for the attendee's own version.
It should work without the recording.
Buyer next steps.
Approach through a direct conversation, since the posts describe no published partnership format, rate card, or media kit.
Ask for LinkedIn follower breakdown by job function, seniority, industry, and geography, and for any performance on the CRM-capture and forecast-credibility posts specifically.
Ask whether the 30-to-90% result can be substantiated and how it should be attributed.
Confirm Shawn Johnson is comfortable with a partner product placed at the close rather than throughout, since that is the pattern the account already uses.
Keep the same decision — a co-marketing webinar or expert content partnership on field sales data capture and forecast credibility for field sales leaders, sales managers and revenue operations — and choose Daniel Steinberg when the campaign shifts from capturing meetings to exploring why internal change and stalled deals go sideways.
Read more
Both posts address that ground.
One follows a leadership memo through a day as sales hears lost autonomy, finance hears a budget shift and product hears more red tape, closing with the line that implementation follows interpretation.
The other traces an enterprise deal that keeps meeting, gets repeated "strong momentum" updates and circles in a holding pattern for months while nobody says no.
That offers useful material for a session about a forecast that quietly drifts while every logged touch still looks healthy, aimed at the senior leaders who own adoption and alignment rather than frontline reps.
A partnership here would trade a campaign on field sales data capture for one on leadership and change.
Neither post mentions CRM data quality, field-rep capture or forecast mechanics; both build narrative scenes rather than the metrics and field-versus-desk contrast that define the other option.
A co-hosted session built around Steinberg would need the partner to supply the capture details and numbers.
The posts show no partnership format, rate card or disclosed commercial offer, so establish any paid or co-marketing arrangement in a direct conversation.
Given the same field-data-and-forecast need, choose Omprakash Karuppanan when the campaign shifts from capturing what never got logged to diagnosing and reactivating pipeline already in the stack — the same decision, framed as a mid-funnel deal-health conversation.
Read more
One post argues AI made B2B outbound worse by piling personalization onto the top of the funnel, then names four things AI does at scale in the middle: flag likely stall deals early, surface buying-committee gaps, aggregate objections across accounts and replace activity tracking with deal health.
The other lists five AI skills built for ABM, including a stall diagnosis that ranks open deals by single-threaded, champion lost, no compelling event and sequence fatigue.
It cites an audit of 31 stalled accounts where 17 had a trigger in the last 60 days that no one acted on.
Karuppanan's posts also state a commercial offer — ABM execution programs, pilot programs and stalled deal reactivation — with a direct message invitation, giving a partner a concrete opening.
The starting point and audience center differ.
Karuppanan's work assumes the intelligence is already captured — call recordings, transcripts, email threads and webinar logs — and asks what to do with it.
That is the opposite of the field-rep problem of a meeting that never reaches the record.
The audience leans toward enterprise SaaS and ABM programs rather than field sales leaders working a territory.
The posts focus on approaches and numbers rather than a demonstrated rep scene, so the human field-capture moment that anchors the fit would need to come from elsewhere.
Ask for follower count, audience breakdown and engagement data.
For the same field-data-and-forecast need, choose Marcus Chan when the campaign targets frontline sales managers and frames the subject as coaching and enablement rather than data plumbing.
Read more
Both posts focus on manager behavior and deal skills.
One recounts how a first-person account of humiliating a top rep in a team meeting over a missed number led to losing her and making changes: praise publicly, coach privately, seek to understand before being understood.
It closes with the line that great reps quit managers, not companies.
The other focuses on champions who cannot sell internally: reps who assume the champion can handle the CFO, and questions to ask before sending negotiated pricing.
It ends by urging role-play on economic-buyer involvement before price discussions.
For a co-marketing webinar aimed at field sales managers, that is story-led material with clear audience hooks.
The tradeoff is distance from the field-data-capture campaign's core.
Neither post touches field data capture, CRM completeness or forecast credibility; the content focuses on coaching narrative and closing skill, with no field-versus-desk contrast or data-quality details to build a session around.
A data-capture webinar would sit outside the creator's demonstrated subject matter, so the partner would need to supply the capture details and metrics.
The posts show no partnership format or commercial offer; settle any paid or co-marketing arrangement in a direct conversation.
Nine LinkedIn posts on Shawn Johnson's own account cover field-meeting capture, CRM data accuracy, when qualification questions get asked, deal slippage, coaching for newer reps, AI in sales, and forecast data.
The posts carry no publication dates, so no posting frequency is stated.
The account showed 4,490 followers on 8 October 2026; the posts do not state audience demographics, engagement data or performance history.
The posts attribute statistics to Gartner, MIT Sloan and a Salesforce survey of 4,050 sellers, and those statistics were not independently verified; the reported customer result on CRM completeness is likewise the creator's own claim.
Similar-creator comparisons draw on posts from three other sales writers, dated March to September 2026, and focus on their ideas and teaching approach rather than reach or audience size.
One gap stays open: the posts here do not establish books, shows or earlier career work that might explain name searches, so the reason for those searches remains unclear.
