About Parbat

Pricing is a trust problem before it is a modeling problem.

A recommendation can look profitable on a dashboard and still fail in production. It can hurt conversion, break a feed, violate a constraint, or simply be based on weak evidence.

See the pitch

Core Belief

The customer should not be the first person to test a pricing idea.

Before a change reaches the storefront, the team should understand the expected upside, the uncertainty, and the operational constraints. After it ships, the projection should be checked against what actually happened — including when it was wrong.

Values

What we refuse to compromise on

Say when we do not know

If the data is not strong enough to support a move, we say so. Confidence is part of the recommendation, not hidden behind it.

Say when we do not know

If the data is not strong enough to support a move, we say so. Confidence is part of the recommendation, not hidden behind it.

The operator stays in control

Nothing ships without approval. No silent changes, surge pricing, or per-customer pricing — and rollback remains available.

The operator stays in control

Nothing ships without approval. No silent changes, surge pricing, or per-customer pricing — and rollback remains available.

Check the work

After an approved change ships, we compare the real result with the projection and show both. That is how trust is earned over time.

Check the work

After an approved change ships, we compare the real result with the projection and show both. That is how trust is earned over time.

Profit over proxy metrics

The decision is judged by incremental gross profit and the quality of the outcome, not activity, recommendation volume, or dashboard engagement.

Profit over proxy metrics

The decision is judged by incremental gross profit and the quality of the outcome, not activity, recommendation volume, or dashboard engagement.

Team

Two people, one product, direct line

Farrukh Zaman

Built production platforms at Cisco and Salesforce. Changing prices on a live store is a systems-trust problem before it’s a modeling problem — rollback, feed sync, failure modes at load — and that’s the work he’s done for years.

Zahara Malik

Comes from Dynata and Ipsos, where measuring how people actually respond to things — rather than what they say they’ll do — was the entire job.

We’re building Parbat because pricing is the highest-leverage decision in commerce and almost nobody has good evidence when they make it.

Have a pricing decision your team keeps postponing? Tell us about it.

Apply for the beta