Give Away the Framework. Sell the Execution.

Give Away the Framework. Sell the Execution.

Productized advisory works when the framework is easy to access and the paid work sits in the execution gap it reveals. Giving away the map does not cheapen the work. It lets the right buyer see the constraint clearly enough to value the judgment, decisions, and accountability required to move it.

THE SCARCITY TEST

Why is the framework usually not the thing worth protecting?

The framework is rarely the scarce thing because insight without applied capacity does not change an operating result. In the engagements we run, the free framework does the qualifying: the buyer who applies it and hits the gap arrives pre-sold on execution help. They have stopped asking whether the issue is real. They are asking how to move it without creating a new mess.

A pattern we keep seeing is that hiding the framework to protect it protects nothing. The framework was never the scarce thing. The execution capacity was. A buyer can understand a sequence, a diagnostic, or a planning template and still lack the context to decide where to begin, the authority to align people, or the cadence to follow through when the first attempt meets resistance.

That is why a productized advisory offer should be honest about what it gives away. Give the buyer the language to recognize the constraint, the basic steps to inspect it, and enough structure to make a useful first move. Do not pretend the worksheet itself is transformation. It is a way to expose where the work becomes judgment-heavy and organization-specific.

Vista's Real-Constraint Lens is helpful here. The question is not, "What knowledge can we keep behind a gate?" It is, "What is actually preventing progress now?" If the constraint is a missing decision, a cross-functional tradeoff, a sequencing problem, or no one accountable for the next move, more hidden theory will not solve it. The paid work should meet that real constraint directly.

DRAW THE LINE

What should you give away, and what should you sell?

Give away assets that improve a buyer's understanding and let them test whether the problem matters. Sell the work that requires situated judgment, coordinated action, and sustained ownership. This distinction is not a trick. It protects trust because the buyer can see the boundary before they are asked to cross it.

A framework describes a repeatable pattern. A diagnostic helps name a condition. A template creates a starting point. These are useful public goods because they make the conversation more specific. They also allow a buyer to self-select out when the problem is not urgent, which is better than pulling an unready buyer into a process they will not use.

Implementation is different. It forces decisions about local constraints, sequencing, stakeholders, failure modes, and what must happen this week. Judgment calls become expensive when they are wrong, particularly when a team is trying to change a routine while still serving customers. Accountability is different again. Someone has to hold the calendar, call out drift, clarify the decision owner, and keep the work moving after the first burst of enthusiasm fades.

Offer element	Role for the buyer	Where it belongs
Framework	Names the pattern and the likely constraint	Accessible tier, public guide, or introductory session
Diagnostic	Shows where the buyer's current system breaks down	Accessible tier with a clear interpretation path
Template	Provides a practical first move	Accessible tier, with limits stated plainly
Implementation plan	Adapts the work to the actual operating context	Paid transformation work
Judgment and accountability	Resolves tradeoffs and sustains execution	Paid transformation work

The verdict is simple: do not price a buyer for access to language they need in order to understand the problem. Price the work of helping them act when the language proves insufficient. That is a more durable commercial line and a clearer service promise.

MAKE THE GAP VISIBLE

How does a free framework create demand without turning into unpaid consulting?

It creates demand when it reveals a gap the buyer can recognize but cannot responsibly close alone. The framework needs enough substance to be useful, but it should stop at the point where local conditions determine the correct move. That is not withholding. It is being accurate about the difference between a pattern and an intervention.

For example, a diagnostic can help an owner see that decisions are repeatedly stuck at one handoff. It can name the symptom, show the questions worth asking, and provide a basic template for mapping responsibility. It should not claim that the same handoff redesign will fit every team, or that a template can determine the tradeoff between speed, quality, control, and ownership.

The boundary becomes credible when the accessible work produces a real artifact. A buyer should leave with a clear constraint statement, a view of the current state, or a tested first move. That artifact does qualifying work because it forces a choice. The buyer can implement it internally, accept the consequences of waiting, or decide that the cost of getting it right exceeds the cost of help.

The give-sell line. Give buyers enough structure to name the constraint and make a responsible first move. Sell the local judgment, coordinated execution, and accountability required when the framework reaches its natural limit.

SEQUENCE THE DEMO

Why does showing the broad tier first improve the premium conversation?

Show the accessible tier first because it establishes the base case before the buyer encounters the full transformation option. The demo-order mechanic is real: show the accessible tier first, and the premium reads as natural progression instead of sticker shock. The buyer can understand what they receive immediately, then see what becomes possible when the work includes deeper support.

This is not an invitation to sandbag the broad tier. The accessible offer must stand on its own. It should deliver a clear outcome, honor the buyer's time, and make the next decision easier. When it does, the premium tier can be framed as an upgrade in scope and accountability: more context, more integration with the operating reality, more help resolving decisions, and more follow-through.

Keep the difference concrete. Avoid labels that imply an artificial hierarchy without explaining what changes. State the work, access, decision support, and accountability in each tier. The buyer should be able to say, in their own words, "The broad tier helps us see it and start. The premium helps us change it in our environment." That is a healthy upgrade decision.

PRICE THE GRADUATION

How should the pricing ladder reflect the move from knowing to doing?

The ladder should rise when the work takes on more execution risk, more contextual judgment, and more accountability. It should not rise merely because information feels valuable. Information may create the opening, but transformation work carries a different burden: it has to fit the team, survive competing priorities, and produce a usable new behavior.

That is the logic behind Vista's graduation-pricing philosophy. Each step earns a higher commitment because the buyer is graduating from orientation to application to supported transformation. The premium tier should be meaningfully higher when it truly includes the scarce work. Trying to make it only a slightly more expensive bundle can blur the distinction and make neither tier persuasive.

Avoid setting the ladder by reverse-engineering a discount from the highest number you hope to reach. Define the scope and operating burden of each level first. Then test whether the broad tier is a credible standalone decision and whether the premium has a clear job that cannot be met by the framework alone. If both answers are yes, the price difference tells a coherent story.

The premium can lift close rates on the transformation work it surfaces because the right buyer sees the gap more clearly. This is not a guarantee or a reason to force an upgrade. It is better qualification: the buyer who stays broad has received value, and the buyer who moves up has made an informed execution decision.

MAKE THE SALE CLEAN

How do you sell execution help without making the framework feel like bait?

Make the boundary explicit before the buyer encounters it. Say what the framework can do, what it cannot decide, and what the paid work adds. A clear limitation strengthens the offer because it demonstrates that you understand the difference between a reusable method and a context-specific intervention.

Use the buyer's own application as the bridge. If they completed a diagnostic, discuss the constraint it revealed. If they tried a template, discuss what broke or where the team hesitated. If they attended an introductory session, discuss the decision they could not make from the general guidance. This keeps the conversation centered on real work rather than pressure.

Be equally willing to recommend the broad tier or internal execution when that is the better fit. Productized advisory gets stronger when the offer is not trying to capture every buyer. A team with a clear owner, spare capacity, and an uncomplicated constraint may only need the framework. A team facing cross-cutting decisions or repeated drift may need a partner who can work through the consequences with them.

For an owner deciding whether a constraint needs outside support, an advisory conversation should start with that distinction. And before you make a paid diagnosis the only path to clarity, read why good advisors charge for the diagnosis. The point is not to give everything away. It is to make the value exchange legible.

BUILD THE OFFER

What is a practical way to build this offer from scratch?

Start by listing the components of your existing work and tagging each one as reusable knowledge, local judgment, execution labor, or accountability. Be candid. If a component can be applied responsibly without you knowing the buyer's context, it probably belongs in the accessible layer. If it depends on interpreting competing facts or coordinating action over time, it belongs in the paid layer.

Next, design the broad tier around one honest outcome. It might be a constraint statement, a diagnostic readout, or an initial plan. Give it a beginning and an end. Then design the premium around the work that follows: tailoring the plan, resolving decisions, setting the cadence, and staying involved until the new practice is operating.

Finally, test the demo sequence with real conversations. Show the broad tier, describe its value, then introduce the premium as an answer to the limitations the broad tier has made visible. Listen for confusion. If buyers cannot state the difference without your help, the ladder needs sharper boundaries. If they can state it and still choose the broad tier, the model is working as intended.

COMMON QUESTIONS

COMMON QUESTIONS

Frequently asked questions

Does giving away a framework make an advisory offer easier to copy?

It may make the visible method easier to copy, but the method is not usually the scarce asset. The scarce work is applying judgment to a buyer's conditions, coordinating action, and maintaining accountability. A useful public framework can actually clarify why a copied worksheet is not equivalent to competent execution support.

What belongs in an accessible advisory tier?

An accessible tier should include reusable structure that helps a buyer understand and test the problem: a framework, diagnostic, template, or introductory working session. It needs a real outcome, not a teaser. Keep its limits clear so buyers know where self-directed application ends and context-specific work begins.

What should the premium tier add?

The premium tier should add the scarce parts of transformation: local diagnosis, decision support, implementation planning, coordination, and accountability over time. Its value should not be a larger stack of generic materials. Buyers should be able to identify the additional operating burden that the premium team will help carry.

Why demonstrate the broad tier before the premium tier?

The broad tier creates a credible reference point. When buyers see a useful foundation first, they can understand the premium as a progression into deeper context and execution support. Starting with the highest-commitment offer often leaves them evaluating price before they understand the work or the gap it solves.

Should the broad tier be deliberately limited to drive upgrades?

No. A deliberately weak broad tier damages trust and makes the premium feel like a ransom. Limit the broad tier where general guidance naturally stops being reliable. It should help a buyer make a responsible first move, while the premium should address the judgment and coordination that only emerge in their operating context.

How do we know whether a buyer needs execution help?

They likely need execution help when the framework has named a real constraint but the team cannot agree on a local decision, assign ownership, sequence the work, or sustain the new practice. Those are not knowledge gaps alone. They are operating challenges that benefit from context, judgment, and accountability.