Skip to content
Peak Atlas

Peak Command / Pricing decisions

The price should go up.How many customers stay?

Feldberg Tee (fictional) is considering raising its subscription by 8%. The calculation further down shows locally what changes in revenue and contribution at the same volume. Nobody knows beforehand how many customers really stay; that number stays open and is not estimated.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
Run the price example

Local calculation · nothing is stored or changed.

Plus eight percent. And then?

Price / Volume / Unknown

01Computed02Threshold03Open
Example / Price calculation

What is computed, what stays open.

Computed
Revenue and contribution at the same volume.
Threshold
How much volume you could lose before it stops paying off.
Open
The actual demand effect: unknown.
Example with a fictional company · not the product interface
For shops and service firmsPrice increase → Discount → New package

Your pricing question in the example

Change, assumption, review.

Frame your pricing decision in three answers. The calculation is further down; nothing is stored.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Command / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three answers. One pricing question.

Draft · not yet put together

Change
Still open
Assumption
Still open
Review
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

Two typical situations

Which pricing question is on the table?

Pick the situation. Assumption, calculation and open question follow from it.

Subscription at Feldberg Tee (fictional)

Purchase prices have risen; the subscription has cost €24 for two years.

The action
The local calculation shows the effect of +8% at the same volume and the volume at which it stops paying off.
The intent
A decision with a clear assumption and review date.
Working example / Price increase

The price calculation

Price
€24 → €26 (example)
Same volume
More revenue per subscription, computed
Demand
Unknown, not estimated
Editorial structure sketch · not a customer reference

The example shows the structure with a fictional company. In Peak Command you read the same question from your own products.

To the next step

Is this for you?

A clear job. Clear limits.

A company that
justifies its prices.

This is where the example helps.

  • You're considering a price increase, a discount or a new package.
  • You want to separate what is computed from what is assumed.
  • You want to be able to review the decision later.
Local calculationPeak Command

Demand unknown

What this page doesn't do.

  • The calculation runs only in your browser and stores nothing.
  • It doesn't estimate a demand effect and changes no price.
  • A price lever is not a scenario slider of its own in Peak Command.

From the calculation to Peak Command

See how Command computes scenarios.

Today Peak Command computes federated scenarios from Peak Finance and Peak Year, such as a changed revenue assumption, and records decisions in Peak Log.

See scenarios in Peak Command

Peak Command / Your next step

A price is an assumption with a review date.

Run your price change below. Then record the decision.

Run the price example
Local working example

A price you can justify.

The actual demand effect: unknown.

Example · Price scenario

What if you changed your prices?

Base and two variants side by side. Nobody knows in advance how demand will change: without your assumption that part stays open, and you only see how many sales you need to keep.

Base

Price
€490
Contribution per sale
€350
Contribution per month
€14,000
Result after fixed costs
€5,000

Price +10%

Price
€539
Contribution per sale
€399
Sales needed to keep the base contribution
35.1 · That is a change in sales of −12.3 %
Contribution per month
unknown, no assumption
Result after fixed costs
unknown, no assumption

Price −10%

Price
€441
Contribution per sale
€301
Sales needed to keep the base contribution
46.5 · That is a change in sales of +16.3 %
Contribution per month
unknown, no assumption
Result after fixed costs
unknown, no assumption

Formulas: contribution per sale = price − variable cost. Sales to keep = base contribution ÷ new contribution per sale. Result = contribution × sales × (1 + assumption) − fixed costs.

In Peak One, Peak Command calculates scenarios from Peak Finance and Peak Year. A scenario changes nothing until it is applied in the owning app.

Example Runs in this browser only · nothing is saved or sent · fictional values

Frequently asked questions

Does the demo change a price?

No. The demo only calculates in your browser. It saves, sends and changes nothing.

Does the demo predict demand?

No. You set the demand effect yourself as an assumption. Without one it stays unknown.

What can Command do here inside Peak One?

Scenarios on revenue, ad spend, delays and skipped initiatives. A scenario changes nothing until you apply it in the owning product.

Are the companies on this page real?

No. The companies and numbers are fictional examples. They show the flow, they prove no effect.

More in Peak Command

All pages in Solutions