nozle
    nozle

    Pricing engine | Nozle

    Pricing should change as fast as your product.
    Today it can't.

    It's locked in your codebase, gated by your slowest team. Nozle moves it onto a surface the people who own the number can ship from — backtested, cohort-rolled, reversible. No deploy.

    Five steps your team already does. Measured in minutes.

    Author, pressure-test, ship, watch, undo. The same loop your release train runs — without the release train.

    Loopidea → live → learning
    1. 01
      Draft
      Whoever has the idea — PM, founder, finance — drafts the new plan. No spec doc. No handoff.
    2. 02
      Pressure-test
      Replay 30 days of real usage through the draft. See revenue, margin, and which customers move tiers — before anyone is affected.
    3. 03
      Ship
      Apply to new signups, a cohort, or a percentage rollout. Live as a versioned, signed artifact, not a deploy.
    4. 04
      Watch
      Revenue, margin, and conversion against the previous version, in real time. Not at month-end.
    5. 05
      Undo
      If it isn't working, revert in one click. Customers who signed on the new plan stay; everyone else snaps back.

    Pricing isn't code you deploy. It's a surface you ship.

    When pricing lives in code, every change waits on your slowest team. When it lives in its own surface, the person with the insight on Tuesday morning ships it by Tuesday afternoon.

    Pricing as codeengineering owns the lever
    Mon
    −12%
    +6 wks
    ship
    Margin
    lost
    MON → +6w
    Spec → ticket → PR → QA → release · margin already gone
    —
    What you missed
    six weeks of margin you'll never get back.
    Pricing as a surfacethe PM owns the lever
    Idea
    2pm
    Backtest
    3pm
    Live
    4pm
    TUE · 4PM
    PM ships v17 — backtested, cohort-rolled, reversible
    v17
    What you protect
    the margin, the moment, the optionality.
    v17

    Four parts. One pricing change shipped without a deploy.

    The builder that authors the plan, the diff that reviews it, the backtest that pressure-tests it, the rollout that ships it — and a one-click revert behind all of them.

    Prefer the schema?Read the plan docs
    Plan · plan_pro · draft v17
    draft · saved · 2 reviewers required
    Plan revenue · plan_pro · projected
    $182k / mo$224k / mo+23%
    Author
    sara@acme.com
    Meters
    input_tokens · output_tokens · seats
    Tiers
    free · pro · enterprise
    Surface
    builder · no deploy

    Same plan: 3 meters, 3 tiers, 1 annual discount, 1 grandfather rule — all as configuration. Engineering sees the artifact, not a PR.

    Step 01 of 04

    When pricing moves at product speed, the business does too.

    Not new features — things every team already wants to do, and quietly gives up on because the cost of trying is a sprint nobody can spare.

    01 · Margin defence Same week, not next quarter

    Costs moved Monday. Prices move by Friday.

    Provider hikes, model swaps, FX drift — respond the week you notice, not the quarter you reconcile.

    before → after
    react time: 6 weeks → 60 min
    owner: engineering → PM / finance
    rollback: revert PR → one click
    02 · Experiments One a month, not one a year

    Test pricing the way you test product.

    Cohort a plan to 10% of signups for two weeks. Promote the winner, kill the loser, move on.

    experiments.live
    exp_24a: annual prepay · +$18k MRR · promoted
    exp_24b: raised free tier · +14% conv · running
    exp_24c: usage-only tier · −9% margin · killed
    03 · Bespoke deals Yes, without the hangover

    Say yes to the deal. Without it haunting your codebase.

    Custom terms become their own plan version, scoped to the customer who signed — not an `if` statement someone has to remember in 2027.

    live versions
    v17: public · 78% of new signups
    v14: annual contracts · locked through 2027
    v22: Acme · custom · NDA carve-outs
    Every change ·versiondiffbacktestrolloutauditrollback_to
    Composes with

    The same event, three layers later.

    Nozle is seven layers on one ledger. The events you send here are the events every other layer reads.

    Your next price change. This week.
    Not next quarter.

    Stop shipping prices through your release train. Draft a plan, replay 30 days of real usage against it, roll it out to a cohort — and revert in one click if it doesn't land.

    Walk through a real change
    Start free
    Time to live
    60 min
    Owner
    PM, not eng
    Backtest
    real 30 days
    Undo
    one click