“We keep losing at proposal. It must be pricing.”

I’ve heard that line in more steering meetings than I can count. Then we open the last three proposals and see the same pattern: the quote was correct, the content was pretty, but the offer didn’t match the real problem. We optimized presentation on top of a vague brief. The price wasn’t the issue. The structure was.

If this feels familiar, you’re not alone. Most teams try to fix this by adding more fields, more dashboards, more KPIs in CRM. Visibility improves. Outcomes don’t.

Tracking Isn’t Structuring

CRM is a tracking layer. It logs accounts, contacts, activities, stages, and amounts. That’s necessary. You need ownership and reporting. But tracking answers “what’s happening?” It doesn’t define “what are we building?”

According to McKinsey research, about 70% of digital transformation initiatives fail to hit their stated objectives (cited by Andre F. Moye on LinkedIn: https://www.linkedin.com/pulse/why-organizations-move-slower-than-tech-buy-velocity-andre-fmoye). At the same time, Gartner has noted that global technology spending reached $4.5 trillion in 2022 and is projected to surpass $5 trillion by 2024 (also cited by Moye in the same article). That’s the paradox: massive spend, mediocre outcomes.

Moye calls this the digital transformation gap - the difference between what technology can do and what organizations actually realize. He puts it plainly: “The disconnect between technological potential and organizational realization creates what scholars have termed the 'digital transformation gap'” (https://www.linkedin.com/pulse/why-organizations-move-slower-than-tech-buy-velocity-andre-fmoye). In sales, that gap shows up when we track deals better but still can’t shape them into wins.

Visibility tells you where the deal is; structure decides where it goes.

When a team says “pricing is the problem,” I usually find a different root cause: the problem wasn’t defined, the product was exposed in the wrong way, and the proposal tried to rescue a fuzzy direction with nicer formatting. CRM saw all the motions. It just couldn’t prevent the miss.

The Missing Layer in CRM

Over time, I’ve come to separate two layers:

  • Tracking layer - Customer, Opportunity, Activities, Stages
  • Structuring layer - Profile, Problem, Personality, Product, Price, Proposal, Prediction

Tracking is for accountability. Structuring is for execution. CRM gives you the first. Complex sales require the second.

Think about a live opportunity. CRM knows there’s a budget, a sponsor, a close date. But does it encode why the buyer is acting now? Does it suggest which version of the product should be shown first to this buyer type? Does it apply pricing logic that can explain itself? Does it warn you when the third proposal revision drifted away from the original problem? That’s what a structuring layer does.

Here’s the heartbeat of that layer:

  • Profile - Context before action. Industry, commercial model, constraints that actually affect how you sell.
  • Problem - Direction before configuration. Why this deal exists, stated plainly enough to guide trade-offs.
  • Personality - Guidance before exposure. How to reveal options to this buyer without creating friction or doubt.
  • Product - Clarity over completeness. The minimal, relevant solution space for this Profile and Problem.
  • Price - Credibility over math theatrics. Logic that can explain itself, or it will get overridden.
  • Proposal - Decision support, not paperwork. Helps the buyer make an internal decision, not just see a number.
  • Prediction - Signal over optimism. Read behavior and changes across versions, not gut feel on stage labels.

In my work with complex products, CPQ sits right in the middle of this layer. Not as a quoting machine, but as the system that encodes what a valid, explainable solution looks like for a given context. When the logic is explicit and testable, your team spends less time debating and more time shaping.

If the system can’t explain itself, sales won’t trust it.

This is why adding another dashboard rarely fixes margin erosion or late-stage losses. Dashboards report on the absence of structure. They don’t create it.

Practical Rules to Shape Deals Early

The shift sounds big, but it starts with a few simple rules of thumb. I use these in every engagement.

Rule 1: Name the problem in one sentence before you configure anything.
If you can’t write a clear problem statement, you’re not ready to show options. Example: “Replace manual changeovers to cut line downtime by 20%” is workable. “Upgrade project” is not. Every time I skip this, I pay for it in the proposal.

Rule 2: Guide by personality, not catalog.
Decide how you’ll expose the product for this buyer type. Analytical buyer? Start with constraints, trade-offs, and a comparison view. Executive buyer? Start with outcomes, risk, and a single recommended path. Same product, different reveal. The wrong reveal creates either overwhelm or doubt.

Rule 3: Price must be explainable on one slide.
If your pricing logic can’t be explained quickly, it will be treated as arbitrary. Add structured reasons: capacity tiers, service levels, boundary conditions. When price movements are anchored in explainable logic, discounting stops being the only lever.

Rule 4: Block invalid choices early.
Don’t let reps assemble combinations that engineering will reject later. Every invalid selection that survives to proposal becomes sunk time and credibility loss. Use CPQ to constrain and guide - not to clean up errors at the end.

Rule 5: Version diffs are a signal, not a history.
Every change between V2 and V3 tells you something about buyer priorities. Did we add complexity to chase a stakeholder comment, or did we simplify around the real problem? Read those diffs, not just the stage.

Named anti-patterns help teams spot trouble fast. My favorites:

  • Stage Theater - The deal moves forward in CRM, but nothing structural changed. It looks healthy. It isn’t.
  • Option Dump - You show the full catalog to prove thoroughness. The buyer sees confusion and risk.
  • Pricing Mirage - Discounts move faster than the problem definition. Margin drops, trust drops, velocity drops.

Dashboards don’t remove friction. Structure does.

Make the Shift This Week

You don’t need a massive program to start shaping. Do a few small things, consistently.

Action 1: Add three fields that force direction.
In your opportunity intake, make room for a one-sentence Problem, a Buyer Personality picklist, and a Primary Outcome target. If the field is blank, the deal isn’t ready for a product walkthrough. This is guardrail, not bureaucracy.

Action 2: Teach the first 10 minutes.
Standardize how you open discovery: confirm Profile, state the Problem, align on Outcome, then choose the Product reveal for that Personality. Record and share one good example. Everyone learns faster when the start is consistent.

Action 3: Make pricing logic visible.
Publish a short, internal “why price changes” page. Tier definitions, scope boundaries, and hard constraints. Put it in your CPQ help text. If reps can point to logic, buyers stop treating price as a guess.

Action 4: Review proposal diffs, not just wins and losses.
Once a week, pick one active deal and compare proposal versions side by side. Ask: what changed, why, and did it move us closer to the stated problem? This turns prediction into pattern reading, not optimism.

Action 5: Remove one workaround per week.
List the top three “we do it outside the system” moves. Pick one and design it into your structuring layer or CPQ logic. Small removals compound into speed and trust.

This is the core message I give to leaders staring at more spend and flat results: the path out isn’t more visibility. It’s better structure. The good news is you can build it incrementally and watch adoption climb because the system starts helping people think, not just click.

We’re spending trillions on technology but still losing to process drag and vague execution. That’s not a software failure. It’s an architecture choice. When you put a structuring layer next to your tracking layer, deals stop wobbling. Reps stop guessing. Proposals start landing.

The next posts in this series go deeper into each structuring element and how they connect to CPQ in the real world. For now, try the rules above on one live deal and see what changes.

The quiet truth is simple: better dashboards won’t save a poorly structured deal.