← All frameworks
Framework

Sales

This framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to B2B sales for mid-market deals.

Built with the Framework Builder methodology

Download markdown

This framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to B2B sales for mid-market deals.

Layer 1: Principles Foundation

Principle 1: No demo without discovery. Require a minimum discovery conversation before showing the product, so the demo answers a stated need and does not become a feature dump that makes the product look like every other.

Principle 2: Large deals need more than one voice. Above a set deal size, two stakeholder contacts must be in place before a proposal goes out.

Principle 3: A discount is a strategic tool, not a closing crutch. Past a set percentage, it needs approval and a documented competitive reason.

Principle 4: Sell to the buyer's process. Buyers recognize a need, evaluate options, build consensus, secure budget and decide. Your stages must fit that sequence, not your internal one.

Principle 5: An objection is data. A price objection may mean the value was not communicated, the timing is wrong or a rival is being compared. Categorize before you respond.

Layer 2: Systematic Approach

Step 1: Qualify. Fifteen minutes, scored against five criteria. A deal advances at three of five.

Step 2: Discover. Thirty to sixty minutes depending on deal size. Branch on the buyer: for a technical buyer focus on integration and security, for a business buyer focus on return and workflow impact.

Step 3: Propose. A standard template for smaller deals, a custom one for larger deals.

Step 4: Negotiate. With a single decision-maker, present and close in one meeting. With a committee, hand the internal champion a decision-support document they can circulate.

Step 5: Review the deal. After every close, win or loss, record whether the steps were followed and where deviations lined up with the result.

Layer 3: Force Multipliers

Multiplier 1: A mutual action plan. After discovery, share a short document listing what each side must do before the decision date. It creates commitment and brings hidden objections out early.

Multiplier 2: A competitive cheat sheet. Group your top five rivals by weakness type: price, feature gap, integration limit, support quality. Reps stop researching mid-conversation.

Multiplier 3: Coach from recorded calls. A fifteen-minute weekly session on one recorded call beats general advice.

Multiplier 4: Build it with your top performers. Watch them work and ask why they made each choice. Their embedded judgment is what the framework should capture.

Multiplier 5: Set rules by deal size. Thresholds, such as two contacts above a deal size or approval above a discount level, give reps a clear rule to point to and give managers an easy exception to review.

Layer 4: Success Metrics

Positive indicators:

Failure signals:

Run a monthly win/loss review on the last ten closed deals. Look at whether the framework was followed and where deviations lined up with outcomes. That evidence tells you what to change.

Layer 5: Implementation Guidance

Roll out in three phases over about nine weeks. Weeks 1 to 3: discovery and qualification only, with each rep recording their next five discovery calls. Weeks 4 to 6: add the mutual action plan and proposal standards. Weeks 7 to 9: add competitive positioning and negotiation. Expect full adoption around week twelve.

Review quarterly. Compare framework assumptions against the last ten closed deals and update the qualification criteria and rival notes.

Common mistake: too prescriptive for senior reps. Keep the decision logic and stage criteria identical for everyone. Leave the execution style flexible.

Edge case: a deal with one champion and a hidden decision-maker. Make the second contact a condition of the proposal, and explain it as protecting their decision.

Edge case: the buyer asks for a demo on the first call. Offer a short discovery first and promise the demo will be built around the answers.

Common mistake: building it without top performers. A framework written by leadership describes how selling should work. Watch your best sellers, ask why they made each choice and capture that.

Common mistake: following your process instead of the buyer's. Your stages describe your steps. Buyers recognize a need, evaluate, build consensus, secure budget and decide. If your stages do not map to that, they create friction.

Common mistake: handling objections as problems. Treat each as information. A price objection may be a value-communication failure, a budget timing issue or a rival comparison, and each needs a different response.

Common mistake: never updating. A framework built for the market of twelve months ago drifts. If win rates fall on deals that followed it, change the framework, not the reps.

How it was built: the full guide on howtoframework.com.
Built with the Framework Builder methodology. Get the skill →