“What should we charge for this?”
A defensible price for a new product, tier or market — before you launch it.
A founder or Head of Product with a launch date.
There is no historical data to reason from, so the price is usually picked by looking at one competitor and rounding. That number then anchors the category you end up in, the customers you attract, and the margin you live with. It is the most consequential guess in the launch, and the one made with the least evidence.
The evidence, before the recommendation.
Nothing here is a market average or a rule of thumb. Every number is computed from your own data or carries the source it came from.
What the market will bear
Willingness-to-pay by segment from synthetic respondents across Van Westendorp, Gabor-Granger, conjoint and MaxDiff — validated against a real panel when the decision warrants it.
What it is worth
An Economic Value to Customer model per segment: the next-best alternative plus value drivers expressed as formulas, with an explicit capture decision you make.
What the set already charges
Competitive price points for the nearest comparable products, tier by tier, with provenance.
What you get, and what keeps going.
One engagement produces something you decide on. What happens next — and on what rhythm — is the section below.
The work product.
- A price point per segment, with the WTP band and the value model behind it
- The packaging it implies — what is in the tier and what is fenced out
- Where the price sits against the competitive set, and deliberately why
- The launch discount policy, so day-one deals do not reset the anchor
The launch price, the packaging around it, and what you will hold the line on.
Nothing reaches your billing system until you approve it.
A launch price is a hypothesis. We keep testing it.
You priced against a band and a value model. Both move once the product is in the market and someone else launches into it.
These read your own data, so they are current the moment a sync lands — no waiting for a reporting cycle to find out what you charged last week.
- Adjacent-product pivot and customer audit
What your existing customers already pay you, and what that anchors the new price to
For the first two quarters the market read is weighted to new entrants rather than incumbents. New entrants price aggressively to take share, and they do not warn your buyer first.
- Price-level comparison
The number your buyer will hold you against on day one
- Pricing-model comparison
How the category charges, which sets what reads as normal before you say anything
- Total cost at a reference buyer
What a comparable buyer spends today across the whole set
Demand moves with the category, not the week. Simulated respondents are what make a quarterly re-measure affordable at all — a conventional study is priced to be run once.
- Van Westendorp — the opening bandlead
The range that reads as fair before anyone has used the product
- Choice-based conjoint — what to charge for
Which unit buyers accept being metered on
- MaxDiff — what belongs in the launch package
What has to be in v1 for the price to hold
A value model is wrong the day you ship something that changes the offer, not on a date. Quarterly is the floor; any release that moves what the buyer gets pulls it forward.
- Economic value against the next-best alternativelead
What the product is worth against however the buyer solves this today
Baseline is thin by construction — there is no history for a product that does not exist yet, so demand and value carry the argument.
Your own book is live because it is your data — the analyses recompute as soon as a sync lands. The rest are cadences a person keeps, not alerts a dashboard fires: your pricing expert does the refresh and brings you the read. Each one either confirms the price you are charging or turns into a proposal, and nothing changes until you approve it.
Where this question usually comes from.
Judge the method before you buy it.
We run this analysis on public pricing pages and publish what we find — outside-in, every claim bounded. It is the closest thing to watching us work before you hire us.
All teardowns →An $8 AI add-on worth about a dollar a seat — withdrawn, and replaced with a $20 tier boundary worth an estimated $120–165M.
Read the Notion teardownBefore you book a call.
What do you need from us to start?
Read-only access to your billing system, or an export of customers, subscriptions and invoices. Competitive and demand evidence we bring ourselves.
Who does the work?
A senior pricing operator, with Albi's agents doing the continuous groundwork on your data. You review a proposal — you are not being handed software to learn.
What if we disagree with the recommendation?
Then it does not ship. Every number arrives with the evidence behind it, so you can argue with the reasoning rather than the conclusion.
Does this end, or continue?
Either. A scoped engagement ends at a proposal you approve or reject. A standing mandate keeps the willingness-to-pay, value and competitive evidence current, and brings you a move when one is warranted.
The Albi workspace
Your engagement runs in a workspace you log into. Your expert works there on your data; you review the evidence, read the proposal, and approve the move. Approved pricing provisions into Stripe from the same place.
- One workspace per pricing initiative, with the evidence behind every number
- The proposal, the working underneath it, and the approval in one surface
- Nothing reaches your billing system until you approve it
Next: the answer where the question gets asked
Not built yetNobody asks a pricing question in a pricing tool. They ask it in the thread where a deal is being argued, on the record where the opportunity lives, or through an agent already halfway through a task. We are building toward Albi answering in those places, from the same evidence — and none of it changes who approves a price.
- In the deal threadChat, wherever your team argues deals — Slack, Teams, or whatever you actually use.
- In your CRMThe guidance on the opportunity record, where the rep already is.
- To your own agentsAn MCP server, so agents you already run can read your pricing evidence directly.
- Through the APIYour own surfaces, your own workflow, the same evidence behind it.
Approval does not move. However the question reaches us, the answer comes back as a proposal a person signs off.
Not the one you're asking?
"What should we charge for this?"
Bring us the question. A scoping call gets you the shape of the engagement, what your data makes possible, and a number.