[ Use case 05 ] Launches · Roadmap
Pick the launch price before the launch.
For a new product with only a few weeks of sales, Jonbar runs price versions on published ranges today, and says clearly how little of yours it has to learn from.
| World | Value | 80% range |
|---|---|---|
| A | 640 | baseline |
| B | 523 | 468 – 570 |
| C (Winner) | 741 | 681 – 788 |
- A
- Planned price
- B
- Price +10%
- C
- 15% off, weeks 3-4
- ! low-data: BL-1 has 6 weeks of history
- ! prior-based: BL-1 elasticity is a category prior
- ! prior-based, no own campaign history: BL-1
[ 01 ] Scope
What works today
Whose problem: Brands pricing a new product with only a few weeks of sales.
- Price versions for a new product with only a few weeks of sales, run on published category ranges.
- Clear warnings when there is little of yours to learn from.
The warnings on the sample are the point: the engine says what it doesn't know.
[ 02 ] Sample output
The same run, week by week.
Each line is one version of the decision, with its range. The shaded weeks are the campaign window; the weeks after show what it cost or kept.
- A
- Planned price
- B
- Price +10%
- C
- 15% off, weeks 3-4
ABC
[ 03 ] Limits
What it doesn't do yet.
- A proper launch module comes after campaigns and pricing.
[ 04 ] Other use cases
- [ Use case 01 ] PromotionsKnow which campaign still pays after it ends.
- [ Use case 02 ] PricingRaise the price. See the volume you'd lose first.
- [ Use case 03 ] Multi-channelA campaign on one marketplace shouldn't blur the other.
- [ Use case 04 ] Bundles · Partly available"2 for x" or "x/2 each"? Same price, different week.