The CRM Was Built for Checkboxes. AI Rebuilds It for Context.

The CRM was built for checkboxes. It needs to be rebuilt for context.

Every revenue leader has stared at the same Salesforce report. 60% of opportunities have Stage = Qualification and Decision Criteria = Other. The pipeline review is supposed to be a strategy session. Instead it's a guessing game played from a checkbox graveyard.

This isn't a Salesforce problem. It isn't a HubSpot problem. It isn't a "your reps don't care about hygiene" problem, even though every operations team has run that initiative twice and gotten the same outcome both times. The problem is older than that, and more structural. The CRM was designed around what a rep could plausibly enter at 1:58pm between calls. Picklists won not because anyone thought they were the right unit of capture, but because they were the only kind of data structured enough to report on and small enough to fit in the gap between meetings.

That constraint is gone. Reps no longer have to choose between speed and depth, because they're no longer the ones doing the data entry. AI listens to the call, writes the narrative version of the field, and posts it into Salesforce or HubSpot before the rep is back at their desk. Rich-text fields, captured at the depth a real human conversation actually had, finally become viable. And once they're viable, every downstream system that depends on CRM data, including every agentic play that revenue teams are spinning up in 2026, gets meaningfully more powerful.

This is the shift. Not "AI in your CRM." A different CRM, fueled by data that was always present in the conversation but never captured.

Why checkboxes won the first round

The CRM as we know it was designed in the late 1990s, when the canonical sales workflow was a rep finishing a phone call and walking back to a desktop computer. Siebel established the schema. Salesforce moved it to the browser. The fields, the picklists, the stage gates were all shaped by the same design constraint: a human had to fill it out, and that human had between 60 and 120 seconds before the next conversation started.

Picklists are what survived that constraint. Decision criteria is a picklist with five options because nobody at any company in 2003 was going to type three sentences of free text after every call. Stage is a picklist because nobody was going to write a paragraph explaining where the deal sat. Pain point, in the cases where it exists at all, is a picklist because the alternative was worse. A rich-text field that nobody actually filled in produced less useful data than a constrained one filled in shallowly.

The rich-text fields existed all along. They were the ones reps skipped first when running late. The Salesforce State of Sales report tracks this directly: 68% of reps say note-taking and data input is the single most time-consuming part of their job, and reps spend roughly 30% of their working time actually selling, with the remaining hours absorbed by admin, internal meetings, and tool-switching [1]. The reason your Decision Criteria field on closed-won deals from 2024 reads "Other" or is empty isn't that your reps didn't know the answer. It's that the answer was a paragraph, and they had 90 seconds.

That's the design history. Checkboxes won by default, not by merit.

What we lost when we picked checkboxes

The picklist version of Decision Criteria can hold one of five values: Pricing, Features, Integration, Support, Other. The rich-text version of the same field, captured from a real discovery call, looks like this:

They've been burned twice on integration timelines, including a Workday rollout that ran six months over and forced their CIO to issue a directive that no enterprise software project gets approved without a fixed implementation schedule and a CIO-level sponsor. Their evaluation will weight implementation predictability above feature parity, and the CFO has informal veto power on contract length.

The picklist tells you which bucket. The rich-text tells you what to do next. There is no version of an "agentic forecasting workflow" or "automated deal coaching" or "churn early-warning system" that produces useful output from "Other." Every one of those workflows depends on context that a picklist cannot hold.

The cost of having only the picklist version is large and well-documented. Gartner estimates the average organization loses $12.9 million per year specifically to poor data quality, with bad CRM data driving forecasting failures, wasted outreach, and decisions made on incomplete information [2]. Sirius Decisions research, now under Forrester, found that 10 to 25% of B2B records contain critical errors and that data decay accelerated to roughly 30% per year post-pandemic. McKinsey's State of AI work landed on the same point in different language: 70% of the valuable insight in an enterprise is trapped in unstructured data the company has but cannot reach [1].

The thing that connects all of these stats is not a data hygiene problem. It's an interface problem. The data was captured. It was captured in the conversation. The interface for transferring it from the conversation to the system of record was a human typing into a form during a 90-second window between calls, which is exactly the workflow that produced "Other" in your Decision Criteria field.

An AE we spoke with during a recent demo described the dynamic plainly: "Reps hate updating next steps. I just want to know what the next step is in the process. Right now it's a gate, so I either put it in incomplete or once, and then it doesn't evolve over the course of the deal." The AE wasn't being lazy. The AE was responding rationally to a workflow where the cost of detailed entry was their own time and the benefit accrued to a manager looking at a report next week.

What changes when AI fills the field

Attention's CRM auto-fill writes directly to any Salesforce or HubSpot field, including custom objects and rich-text fields, based on what was actually said on a sales call. Each field has a prompt the team configures once, the AI extracts the answer from the call transcript, and the result lands in the CRM within minutes of the call ending. The rep does not have to be involved in the data capture for the data to be captured.

The mechanism is prompt-based, which is the part that matters for rich text. The team configures a field by writing the question in plain language: "List the two most important next steps the customer agreed to, with the owner and timing if mentioned. Maximum 200 characters." Attention's auto-fill runs that prompt against the call transcript and writes the structured output back. The same approach handles picklists ("classify decision criteria as Pricing, Features, Integration, Support, or Other"), multi-select fields ("list every named competitor mentioned"), and free-form narrative ("summarize the economic buyer's specific budget approval timeline").

A revenue leader at a software company evaluating Attention put it this way during a demo: "Ideally, all the fields you're showing here, the AE, as long as they've had the conversation with the customer, wouldn't have to add any of this information." That's the shift. The rep stays in the conversation. The CRM gets the depth it always needed.

An Attention account executive walking a customer through field configuration described the difference: "It's prompt-based. You just tell it, hey, list out two key next steps from the conversation, ensure the total output is no more than 200 characters. So this is really valuable for people because it's prompt-based, it just allows you to get whatever output you want, you're not being boxed into anything."

The control layer matters too. Every field configuration is owned by the team, edited in the platform's CRM settings, and applied consistently across calls. Updates can flow automatically when calls end, or pause for rep approval via Slack before they hit Salesforce. Permissions, audit trails, and team-level scope are configurable. The team that wants the AI fully on the wheel and the team that wants every field reviewed before push are using the same product.

Context is the fuel for every agentic play

The single best summary of why this matters comes from McKinsey's most recent State of AI work: "An agent is only as good as the context you give it. If your data is trapped in silos, spread across collaboration apps, email, and documents, your agents will fail" [1].

Every "agentic CRM" pitch in 2026 ultimately depends on this. The agent's quality is bounded by the quality of the context it can read. A pre-call prep agent that only has access to Stage = Discovery and Last Activity = 4 days ago will produce a generic briefing. The same agent reading a rich-text Discovery Notes field that captures the prospect's actual stated CFO mandate, the integration risk they articulated, and the named competitor they mentioned will produce a meeting brief that changes how the rep walks in.

Three plays that get materially better when CRM fields move from checkbox to context:

Pre-call research and account briefing. An agent that pulls the rich-text decision criteria, last call's stated objections, and the most recent multi-call summary produces a one-page brief that beats anything the rep would prepare manually. With only picklist data, the same agent produces a watered-down version of what the rep already knew. Attention's Super Agent runs this play across the entire account history, not just the most recent touch.

Churn detection and account health. A traditional health score combines product usage, login frequency, and CSM-entered Status = Yellow. A health signal that also reads the rich-text Stakeholder Sentiment field, captured from QBR call transcripts, picks up the moment a champion casually mentions they're interviewing alternative vendors. The structured field never would have caught it. The narrative one does. Customers running this play in production are detecting churn risk weeks earlier than the dashboard-based version.

Forecasting and pipeline review. A forecasting agent reading rich-text Economic Buyer Status notes can tell the difference between "champion confirmed economic buyer is signing this quarter pending budget approval" and "rep heard a name on the call but never confirmed buying authority." The picklist version of this field, usually a binary Identified / Not Identified, flattens both into the same bucket. The narrative version separates the deals that close from the deals that slip.

None of these plays require killing dashboards. The opposite, in fact. Rich-text fields make dashboards smarter, because the same AI that wrote the field can extract structured tags from it on demand. Want to chart how often "integration risk" comes up in late-stage deals across Q1? Five years ago that required a picklist someone had to maintain. In 2026, the rich-text field captures the narrative and the dashboard query extracts the signal at read-time. You get both: depth in the field, structure in the chart.

"Garbage in, garbage out" was a CRM-era axiom. The 2026 equivalent is "rich context in, useful agents out, smarter charts on top." That's what changes.

What revenue leaders should do this quarter

The migration from checkbox CRM to context CRM is not a rip-and-replace project. It's an additive one, and a small one if scoped well.

Start by auditing the CRM fields your team uses most and asking a single question for each: was this field a picklist because the picklist version was the right design, or because the rich-text version was unrealistic for a rep to fill out? The fields that answer "unrealistic" are your migration candidates. Common patterns: Pain Point, Decision Criteria, Next Steps, Champion Profile, Competitive Context, Mutual Action Plan, MEDDIC Summary.

Pick three to start. For each, write the AI prompt that defines what gets captured: the question to answer, the format constraints, the maximum length. Attention's field configuration UI shows you the AI's output on real historical call data so you can iterate before any of it hits Salesforce. When the prompts are good, push them live and let the auto-fill run on new calls.

Leave the picklists you actually use for routing, stage gates, and reportable structure alone. The point isn't to delete the structured layer. The point is to stop using picklists as a workaround for the data-entry tax, and to add a context layer underneath them that fuels every downstream agent and dashboard.

The CRM your team uses in 2027 will be drawn on top of fields that didn't exist in 2024. Fields nobody could have asked a rep to fill. That's the real shift, and it's available now.

If your team is starting to think about how to make CRM data the fuel for agentic plays, we'd be glad to walk you through how Attention handles it.