agentsclimarketplace

Conceptual agreement

Skill peterod99/consultant-skills/conceptual-agreement

20 methodology playbooks for B2B consultants. Niche selection, value-based pricing, discovery calls, LinkedIn outbound, account expansion, and more. Installable as Claude Code skills or readable as a standalone playbook.

Install
npx -y skills add peterod99/consultant-skills --skill conceptual-agreement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use before writing any proposal. The alignment ritual with the economic buyer that determines whether a proposal gets accepted.

SKILL.md

4.4 KB, as published. Nobody here has run it

Conceptual Agreement

When to use

Before you write any proposal. You've had initial contact with a prospect, they've described a problem, and you're tempted to jump straight to your solution and a price. Stop. Use this ritual to confirm mutual understanding of objectives, measures, and value with the economic buyer. This is the most critical moment in the sales process, it determines whether the proposal gets accepted or rejected.

The framework

  1. Schedule a dedicated discovery meeting: Not a casual call. Block 60-90 minutes with the economic buyer and relevant stakeholders (champion, budget holder, end-user if applicable).
  2. Open with situation appraisal: Mirror back what you understand about their current state and the gap to their desired future. Invite correction. "Is this accurate, or am I missing something?"
  3. Agree on three to five specific business objectives: Not tactics or deliverables. Objectives answer: What does success look like? Examples: "Reduce time-to-hire from 90 days to 45 days," "Increase customer lifetime value by 30%," "Eliminate the manual compliance audit process."
  4. Define measures of success: Metrics that prove you delivered. "How will we know we succeeded? What number proves it worked?" Get the buyer to name the measure.
  5. Establish joint accountability: Clarify roles. "You'll provide access to the team and weekly check-ins. I'll deliver strategy and coaching. Together, we'll track progress monthly. If we miss the mark, we adjust."
  6. Confirm budget exists and authority is real: Ask: "If this works, is funding already approved? Who signs off?" Don't assume the person in the room can actually commit the money.

How to apply it

A sales strategist is introduced to the VP of Sales at a mid-market B2B firm. The VP says, "Our reps close too few deals. Can you help?"

Instead of pitching immediately, the strategist books a 90-minute session with the VP and the CFO. During the call:

Situation appraisal: "I'm hearing that your team closes 15% of qualified leads, and the industry average for your segment is 22%. You're also burning 6 months to replace reps who leave. Is that picture accurate?"

VP: "Yes, and it's costing us roughly $2M in lost annual revenue."

Objectives: "So success looks like... what? Close rate improvement? Tenure extension? Both?"

VP: "Both. We want reps to stay 3+ years and close 22% like our competitors."

Measures: "How do we know we've hit it? What are we tracking?"

CFO: "Sales rep tenure on average (currently 18 months, target 36+ months) and close rate (currently 15%, target 22%)."

Joint accountability: "You'll give me access to CRM data, weekly calls with top performers, and quarterly reviews. I'll build a new sales process, do coaching, and measure results monthly."

CFO: "What does this cost and timeline?"

(The strategist now proposes with full alignment on value, not guesswork.)

Common traps

  • Skipping the economic buyer: You align with the champion (VP of Sales) but the CFO never agreed the $25K fee is justified. Always get the money person in the room.
  • Proposing before agreement: You assume you understand their problem and write a proposal. They read it and say, "That's not what we meant." The proposal is dead. Align first, write second.
  • Setting vague objectives: "Improve sales" is not an objective. "Close rate from 15% to 22% in 90 days" is. Without specifics, there's no way to prove success.
  • Not confirming budget and authority: You do beautiful work and the prospect says, "This is great, but we need to wait for Q3 budget approval." You've wasted weeks. Ask upfront: "Is funding approved?" If it's not, you either help them secure it or you move on.
  • Treating conceptual agreement as a formality: Some consultants rush through it, thinking they already know the answers. That's how you end up defending a proposal that doesn't match the buyer's real goals.

Source credits

  • In the Buyer's Office (Alan Weiss): Multi-stakeholder alignment, joint accountability, confirmed objectives before proposal
  • Value-Based Fees (Alan Weiss): Conceptual agreement as the foundation for value-based pricing
  • How to Sell New Business (Alan Weiss): Economic buyer qualification, the small-yeses framework

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.