
Good morning.
I worked with an agency owner two weeks ago who has run the same pricing for three years.
Three years. The retainer floor, the project rates, and the package structure have not moved. In the same window his team grew from four people to eleven, the offer matured, the case studies stacked up, and his cost base went up roughly forty percent. The price stayed where he'd set it in 2023.
When I asked him why, he gave me the answer most operators give. Behind the not-testing sat the fear of losing a client, the sense that he had no time to design a research project, and the conviction that pricing was the load-bearing wall of the business. Load-bearing walls don't get experimented with.
So he didn't. And he left somewhere between a hundred and four hundred thousand dollars of margin sitting on the floor every year while he focused on the easier-feeling work of running ads and refreshing the website.
The pattern is everywhere. Pricing is the highest-leverage growth lever in the business, and it is the lever most owner-operators never touch.
This issue is the operating infrastructure that makes the lever testable. Four Skills, one Protocol, and a way to measure before you change.
— Sam
IN TODAY’S ISSUE 🤖

Why pricing sits untouched while every other lever gets tested
How the four Skills connect into one stack
Skill #1: pricing-strategy, the structural layer for tiers, anchoring, and packaging
Skill #2: pricing-page-cro, the presentation audit you run before testing numbers
Skill #3: price-sensitivity-research, Van Westendorp and willingness-to-pay for measuring before you change
Skill #4: pricing-experiment, the brief structure that turns a candidate price into a safe test
The Pricing Laboratory Protocol: the six-step sequence from untouched pricing to a designed experiment
Let’s get into it.

1. Why Pricing Sits Untouched
Most owner-operators I work with can walk me through their last six months of marketing experiments. Ads tested, sequences refreshed, landing pages rewritten, hooks tried, partners reached out to. They run tests because the cost of being wrong is low. A bad ad creative gets paused. A weak email gets killed. The downside is bounded and the operator stays insulated from any real risk.
Pricing is different. The cost of being wrong feels unbounded. A bad pricing test sends customers somewhere else. A bad pricing test breaks the load-bearing wall. The downside is lived with rather than paused, and the operator absorbs the consequence directly in revenue and team morale.
So pricing sits untouched while every other lever gets tested. The result is that most owner-operators are running prices set under conditions that no longer exist: an earlier offer, a different market, a smaller team, a different cost base. The pricing is a historical artifact the operator forgot to update.
The asymmetry is brutal. A ten percent change in conversion rate on a landing page is a normal quarterly project. A ten percent change in price drops directly to gross margin and compounds across every customer for as long as you don't change it back. The first lever gets tested every month. The second lever sits there for years.
The fix is to build the operating infrastructure that separates measuring from changing. You measure price sensitivity. You study the page structure. You design experiments with clean controls and kill conditions. The change becomes a downstream output of a Protocol the team can run, with the decision pre-made on the brief, which means there is nothing left to second-guess in the middle of the night.
That's what the four Skills below give you.
2. How The Stack Connects
The four Skills are designed to run in sequence, though each one stands alone if you only need one piece.
pricing-strategy is the structural layer. Before any number gets touched, it audits how many tiers you have, what they anchor, what each one promises, and what each one excludes. Number work is wasted on a broken structure.
pricing-page-cro is the presentation layer. Once the structure is decided, the page that shows the structure needs to do its job. Most pricing pages underperform because of comparison overload, anchor inversion, or outcome absence, and all three are fixable before a single price moves.
price-sensitivity-research is the measurement layer. Before you change a price, you measure what the buyer is telling you about it. Van Westendorp, willingness-to-pay surveys, or qualitative synthesis from your existing conversations, depending on what you have access to.
pricing-experiment is the testing layer. The candidate price from research becomes a brief with a hypothesis, a primary metric, a kill condition, and a decision rule. The brief is what the team executes from. The kill condition is what makes the test safe.
The Protocol at the end of the issue runs all four in order. First time through, expect a focused day on structure and page, a week on research, and an afternoon on experiment design. After that, the loop becomes a standing quarterly motion.
3. All the Pricing Skills
Skill #1: pricing-strategy
The first Skill is the structural layer. Before you touch numbers, you decide on structure: how many tiers, what anchors them, how each segments buyer types, what each one signals about the offer's positioning. Most operators ship pricing without ever making these decisions explicitly, which is why their pricing reads as a vibe instead of a structure.
Save this as pricing-strategy/SKILL.md inside your team's Skills folder.
---
name: pricing-strategy
description: Frameworks for tier structure, anchoring, and packaging. Use when an operator is auditing existing pricing structure, considering a new tier, or redesigning their pricing page architecture before any specific number changes.
---
# Pricing Strategy
## When to Use
Use this Skill before any specific number gets changed. The Skill helps the operator decide structure: how many tiers, what anchors them, how each tier segments buyer types, and what the structure signals about positioning. Number changes are handled by `pricing-experiment`.
## Audit Prompt
If the operator has not provided their current pricing, ask them to share it verbatim, including tier names, prices, what each tier includes, and any discounts or special terms. Then audit against the rest of this Skill.
## The Three-Tier Default
Most online businesses serving owner-operators benefit from three tiers, not two and not four. Two tiers create a binary choice that pushes price-sensitive buyers to the lower option. Four tiers create decision fatigue and dilute the anchor effect. Three tiers let the middle tier carry the recommended-purchase weight while the lower and upper tiers do the structural work of framing it.
If the operator has fewer or more than three tiers, ask one question: "Is the extra tier doing real work, or is it there because you couldn't decide?" Tiers exist to segment real buyer types. They are not decoration.
## Anchoring
The price the buyer sees first sets the reference point for every price after. The first price on the pricing page should be the highest when the operator wants the buyer to evaluate the middle and lower tiers as relatively affordable. The first price should be the lowest when the operator wants the buyer to scroll up into higher tiers from a position of starting small.
For most owner-operators selling to other operators, the high-anchor-first model converts better. The high anchor signals seriousness and frames the middle tier as the practical option.
## Packaging
Each tier should contain a deliberate answer to four questions:
1. Who is this tier for? (A specific buyer type. "Smaller businesses" is not specific.)
2. What is the one outcome this tier guarantees? (The result the buyer gets, expressed as an outcome rather than as an included feature.)
3. What is the one constraint that pushes someone up from this tier? (The real lift to the next tier, named explicitly.)
4. What is the one thing this tier deliberately excludes? (The reason somebody has to pay for the next tier up.)
Audit existing pricing against these four questions. If the operator can't answer for each tier, the tier is doing positioning work the buyer can't parse, which is why the page converts below what it should.
## Output Format
Return the audit as a four-row table per tier (one row per question above) plus a short observation about what the structure currently signals about positioning. Highlight any tier where two or more of the four questions don't have clear answers; those are the tiers where the operator is leaving structural clarity on the table.
## Honesty Rules
- If the operator says they want to add a higher tier to capture enterprise, ask whether they have evidence of enterprise demand. Aspirational tiers rarely work and usually clutter the page.
- If the operator's pricing is below their cost-of-customer-acquisition payback window, name that before any structural recommendation. Structure can't fix a price that doesn't fund the business.
- If the middle tier converts under fifty percent of total purchases, the anchoring is off. Recommend the structure fix before any number test.That's the structural layer.
Running the Skill
The Skill auto-triggers when you ask Claude about pricing structure decisions. The cleanest invocation is to drop your current pricing into the chat and let the description field do its job:
I want to audit my current pricing structure. Here's what I'm running today: [paste your tier names, prices, what's included, and any discounts verbatim].If you want to force the Skill explicitly, name it:
Use the pricing-strategy Skill to audit my pricing. Here's what I'm running: [paste].What to bring
Current pricing in plain text: tier names, prices, what each tier includes, billing cadence, any discounts or special terms
Pricing page URL or screenshot if your structure relies on visual hierarchy
Conversion rate per tier if you have it: which tier wins most, which gets ignored
The buyer types you actually serve, described specifically (not "businesses of all sizes")
Any pricing tests or changes the team has considered in the last twelve months and why they didn't ship
The audit gets sharper when you have at least three of those five. With only the current pricing, Claude can still run a structural review but the recommendations will be directional rather than specific.
Next is the page.
Skill #2: pricing-page-cro
Pricing pages fail in predictable ways, and most operators address the wrong layer when conversion drops. They test new headlines and CTAs while the underlying page architecture is doing the actual harm. This Skill audits the architecture first.
Save as pricing-page-cro/SKILL.md.
---
name: pricing-page-cro
description: Conversion optimization for pricing pages. Use when the operator wants to audit or redesign an existing pricing page for clarity, psychology, and comparison structure before running any price experiments. Pairs with pricing-strategy (run that first if structure is unclear) and feeds into pricing-experiment (testable hypotheses come out of this audit).
---
# Pricing Page CRO
## When to Use
Use after `pricing-strategy` if structure is unclear, or directly if the structure is settled and the operator wants to fix presentation. Most pricing page underperformance comes from presentation problems before it comes from number problems.
## The Three Failure Patterns
Most underperforming pricing pages fail in one of three ways:
1. Comparison overload. The page lists fifteen features per tier and the buyer gives up scanning. The feature list is doing inventory work when it should be doing selling work.
2. Anchor inversion. The page leads with the cheapest tier and forces the buyer to climb upward against psychological gravity.
3. Outcome absence. Each tier lists what's included but never what the buyer gets. "Includes priority support" is inclusion language. "Get a response within four hours" is outcome language. Outcome language converts.
Audit any pricing page against those three first. The number is downstream of all three.
## The Above-The-Fold Test
The buyer should be able to answer four questions without scrolling:
1. How many tiers do I have to choose between?
2. Which tier is the recommended one?
3. What is the headline outcome of the recommended tier?
4. What is the price of the recommended tier?
If any of those four take a scroll or a click to answer, the page is converting below its ceiling. Fix the above-the-fold structure before testing copy or numbers.
## Comparison Table Rules
If the pricing page has a feature comparison table, audit it against three rules:
1. Maximum eight rows. Anything longer reads as a spec sheet.
2. The first row is always the headline outcome per tier (not a feature).
3. Rows that are identical across all tiers should be removed or moved out of the table. They add scan weight without contributing to the comparison.
## Risk Reversal
Every pricing page should include one explicit risk-reversal element near the primary CTA: a guarantee, a free-trial window, a no-credit-card-required signup, a cancel-anytime statement, or a refund window. The element exists to neutralize the buyer's worst-case mental model. If the page has none, recommend the lowest-friction risk-reversal that fits the offer.
## Output Format
Return the audit as a numbered list, ordered by impact. For each item:
- What is broken (specific, with example phrasing where relevant)
- What to change it to (specific, with example phrasing)
- Expected effect (which buyer behavior changes)
- Effort to implement (S/M/L)
Stop at the seven highest-impact fixes. A pricing page audit with twenty recommendations doesn't ship.
## Honesty Rules
- If the operator's pricing page reads cleanly and the structure is sound but conversion is still low, the issue is upstream of the page. Recommend `price-sensitivity-research` before more page changes.
- If the operator has no analytics on the pricing page, flag that the audit is doing scope work, not validation work. Real optimization requires measurement, which the page may not have.The page audit produces a numbered list of seven fixes the operator can ship in an afternoon. The price stays the same the whole time. Only when the page is doing its job is it worth measuring sensitivity.
Running the Skill
The Skill auto-triggers when you ask Claude about pricing page conversion. Drop the page content in and the Skill handles the rest:
Audit my pricing page for conversion issues. Here's the page: [paste the headline, subhead, tier structure, comparison table rows, CTAs, and any risk-reversal copy].For a more focused pass on a specific failure pattern:
Use the pricing-page-cro Skill to check whether my page has the outcome absence pattern. Here's what each tier currently lists: [paste tier inclusions].What to bring
The pricing page content: above-the-fold copy (headline, subhead, recommended-tier marker, primary CTA, price), every tier card or column, the full comparison table if you have one, the risk-reversal copy near the CTA
Pricing page URL if Claude can browse to it, otherwise a screenshot describing visual hierarchy
Conversion rate from page visit to signup or trial start
Heatmap or scroll data if you have it: where do visitors stop scrolling, where do they click
One competitor's pricing page for comparison context
The audit returns seven highest-impact fixes. If you bring only the page copy and no metrics, the fixes will be scoped to structure and presentation rather than the specific buyer behavior you're seeing.
Skill #3: price-sensitivity-research
This is the Skill that removes the fear. Most pricing fear is a fear of unknown buyer response. The remedy is measurement before change.
Three methods are in the Skill, sized to the operator's sample. Van Westendorp's price sensitivity meter for fifty-plus qualified respondents. A willingness-to-pay survey for smaller lists. Qualitative synthesis when the operator has rich notes from a smaller number of conversations.
Save as price-sensitivity-research/SKILL.md.
You can either ask Claude to create a Skill like this for you, or become a Cortex subscriber to unlock the full Skill below.
Running the Skill
The Skill auto-triggers when you ask Claude about measuring buyer sensitivity. The opening question routes you to the right sub-method:
I want to measure price sensitivity before I change my pricing. I have [N qualified prospects who'd take a survey / fewer than fifty / a folder of customer interview transcripts]. What study should I run, and how do I design it?For interpreting existing qualitative data:
Use the price-sensitivity-research Skill to synthesize this customer interview transcript. Code the pricing references and tell me where I sit in the buyer's mental model. Transcript below: [paste].What to bring
The size and source of your respondent pool: qualified prospects, recent customers, both, or the count of available conversations if going qualitative
Your current price and any other pricing the buyer has compared you against
A clear statement of what offer the price is attached to (the Skill will ask if missing, better to lead with it)
For qualitative synthesis: transcripts or detailed notes from at least eight to ten customer conversations, including sales calls, win/loss reviews, churn exits, or onboarding interviews
For Van Westendorp: a delivery channel for the four-question survey (email, in-app, lifecycle tool) and a way to attribute responses to your qualified list
If you don't have any of the above and you're working from instinct, the Skill will still run a directional read on your offer category and price band, but it will flag that the output is hypothesis, not measurement. That's still useful as the starting point for designing a study.
Skill #4: pricing-experiment
The last Skill closes the loop. The candidate price range from research becomes a brief with a hypothesis, a primary metric, a kill condition, and a decision rule for each outcome.
Pricing experiments differ from page experiments in two ways. The downside is asymmetric: a bad pricing test can cost revenue across every buyer exposed during the test, and the conversion-rate impact is only part of the cost. The signal also takes longer, because the buying funnel includes consideration time that page tests don't have.
This Skill respects both.
Save as pricing-experiment/SKILL.md.
You can either ask Claude to create a Skill like this for you, or become a Cortex subscriber to unlock the full Skill below.
Running the Skill
The Skill auto-triggers when you ask Claude to turn a candidate price into a brief. Lead with the band from research and the structure from strategy:
I want to test moving my Pro plan from $49 to $74 based on the band from my Van Westendorp study. Generate the full experiment brief with hypothesis, primary metric, kill condition, and decision rule.If you're working with multiple candidate prices:
Use the pricing-experiment Skill to design briefs for these three candidate prices: $69, $74, $79. My current price is $49. Rank by expected impact.What to bring
The candidate price or price band from
price-sensitivity-researchYour current price, current conversion rate, and current revenue per visitor or signup
Traffic volume to the pricing surface (weekly or monthly visitors) so the Skill can size the test honestly
How long you can let the test run (three to six weeks minimum for trustworthy data)
Your analytics setup: what attribution exists, whether you can tag the price condition the buyer saw at signup
Customer support's current bandwidth and whether the team can answer questions about a visible price difference
Run the pre-test checklist before the brief ships, even if the Skill returns one without asking. Pricing tests cost more to run wrong than to delay by a day.
The stack is in place.
4. The Pricing Laboratory Protocol
The four Skills are infrastructure. The Protocol is how to use them in order. Run it once and the operator moves from an untouched price to a designed experiment with a kill condition and a named owner. Run it quarterly and pricing becomes a tested variable in the business instead of a historical artifact.
Step 1: Structural Audit. Load pricing-strategy against current pricing.
Audit my pricing structure: [paste pricing verbatim].The output is a tier-by-tier read on which tiers are doing real work and which are decoration. Fix the structure before testing numbers. A well-priced bad structure converts worse than a roughly-priced good one.
Step 2: Page Audit. Load pricing-page-cro against the current pricing page.
Audit my pricing page for conversion issues: [paste page content].Take the seven highest-impact fixes and ship them. Do not change any prices yet. The page audit is presentation work; the number work happens later.
Step 3: Research Plan. Load price-sensitivity-research. Pick the method that matches the sample size: Van Westendorp if fifty or more qualified responses are available, willingness-to-pay if fewer, qualitative synthesis if the data is interview-rich rather than survey-large.
I want to measure price sensitivity. I have [respondent context]. Design the study.Run the study. The output is a defensible price band.
Step 4: Experiment Design. Load pricing-experiment. Take the band from Step 3 and the structure from Step 1, and turn the candidate into a brief.
Generate the experiment brief for moving my [tier] from [current price] to [proposed price]. Research band and structural notes below: [paste outputs from Steps 1 and 3].The brief includes a hypothesis with a real mechanism, a primary metric, a kill condition, and a decision rule for each outcome.
Step 5: Pre-Test Checklist. Run the pre-test checks from Skill #4. Customer support knows. Other surfaces are aligned. Existing customers aren't affected. Analytics attributes correctly. If any of these fail, fix them before the test ships.
Step 6: Ship and Monitor. Run the test for the planned duration. Resist the urge to monitor daily without a daily decision rule. Watch only for the kill condition. At the end of the test, apply the decision rule literally.
The first time through the Protocol, expect a focused day on Steps 1 and 2, a separate week on Step 3 (the research takes time to gather and synthesize), and an afternoon on Steps 4 and 5. Step 6 runs in the background while the rest of marketing keeps moving.
After three runs, the Protocol becomes a standing quarterly motion. The fear leaves once the operator has watched a real test resolve cleanly with a kill condition that fired or didn't. The lever stops being a load-bearing wall and starts being a variable the business tests like any other.
Do you want ALL the Skills, ready to deploy?
You got some of the skills above. Plenty to get you started and going.
If you’re a Cortex subscriber, you get them ALL below.
You can either spend 30-60 minutes trying to create your own, or you can snag them all in ~30 seconds as a paying Cortex member—plus get the true value of Cortex, far beyond a bunch of skills.
What is Cortex?
Cortex is the premium monthly membership version of Bionic Business, helping entrepreneurs and business owners grow and scale with AI and Agents.
In addition to 3-4 full, unrestricted regular issues per month, you also get:
1x SIGNALS Strategic Briefing issue (strategic moves you must make now to secure your business revenue, market share, and profits).
1x CIRCUITS Tactical Guide issue (workflows, how-to’s, prompts, very practical implementation inside a self-driving business).
Access to all Skills issues (full details, download files, tutorials).
Claude Cowork as your marketing team special issue (full guide on how to run Cowork as an agent marketing team for your business).
50% OFF workshops on prompt engineering, agent operating systems, and more. Only active Cortex subscribers get any kind of discount, no one else.
Free subscribers get a redacted and summarized version of regular issues but only Cortex subscribers get the full emails loaded with the good stuff.
So, if you’d like to receive full issues and the monthly special Signals and Circuits issues, then you should sign up for Cortex, which is $50/month (and you have full archives of previous regular issues for as long as you’re a member).
One note on Signals and Circuits: You only get these special issues for the months you’re subscribed—which means if you skip a ~30 day period, about a month, you won’t get them for that month. There are no back-issues for past months, so now is your chance to lock-in these upcoming issues while you can.
After you’ve upgraded to Cortex, log in to the website and come back to this issue, and the Skills will be unlocked below.
Ready? Get the Skills, full regular issues, and the upcoming Signals and Circuits issues:
Cortex is a monthly premium version of Bionic Business, helping entrepreneurs grow and scale with AI and Agents. You can cancel at any time. But there are no refunds, for any reason. All sales are final.

Join Cortex to read the rest!
Become a paying subscriber to get access to this post and other subscriber-only issues. Cortex is a monthly premium version of Bionic Business, helping entrepreneurs and business owners grow and scale with AI and Agents—and transform their business into an autonomous business.
Upgrade to Cortex NowEvery month, you get:
- Full regular email issues
- 1x Signals Strategic Briefing
- 1x Circuits Tactical Guide
- Access to all Skills issues
- Claude Cowork as your marketing team
- 50% OFF workshops

