Proof points, starting with MRR

A coupon proves the discount. It does not prove that anyone is paying, that the site stays up, or that anyone visits. Those are different facts, and early adopters look for them before they paste a code.

Dealpuffin calls them proof points. A proof point is a reading from a provider, shown on the listing, marked verified by that provider. The founder does not type the number in.

MRR from Stripe is the first

The first provider is Stripe, and the first field is monthly recurring revenue.

The reading is the sum of active subscription prices, normalized to one month, before discounts. Metered prices are left out. A quantity of zero adds nothing. If the account bills in more than one currency, the total that is shown is the currency that adds up to the most. Dealpuffin does not convert it into dollars and pretend that was the reading.

You connect a restricted key with read access to Subscriptions. It is stored separately from the key that imports coupons. Publishing a coupon does not reveal MRR. Connecting MRR does not publish a coupon. The first read happens when you connect. After that you pick daily, weekly, or monthly, and an hourly job reads the connections that are due.

If Stripe returns more than one sync can read, that sync saves nothing. A partial total is not presented as the revenue.

Exact, or a band

For each proof point you turn on, you choose what other people see.

Exact shows the figure. A band shows a range and a color. The range for MRR runs from 0–1k through 1M+. The stored reading is still the exact value, including when the public choice is a band. Seekers and their agents do not receive the number, or how far it moved. They receive the band, the currency, the provider, when it was last read, how often it is read, and whether the trend is up, down, flat, or new.

You still see the latest number on your own product page.

You set the order. A catalog card shows the first three. The product page shows every one. The line on the listing says verified by Stripe, with the Stripe mark. It is a reading, not a rank, and Dealpuffin does not pay anyone a commission for it.

Other people see this only on a verified listing whose URL is https. A pending product stays with its owner.

The same shape, for other facts

MRR is the one that works today. It is not the only fact an early adopter asks about.

Uptime and web traffic are the next ones we expect to add. A status page can say whether the product stays up. An analytics provider can say whether anyone is actually there. Each of those is the same kind of object as MRR: a provider you connect, a field that provider can read, a cadence, and a choice between the exact reading and a band. The founder still does not type the number. The listing still says which provider verified it.

Coupons stay the reason to start. Proof points are the reason to believe the product is already a product. The rules for the reading, the band, and the Stripe key are in Proof points.

Frequently asked questions

Do I have to show MRR?

No. Nothing is shown until you connect Stripe as a proof-point provider and turn MRR on.

Can seekers see the exact dollar figure?

Only if you choose exact. A band shows the range. The number stays on your side of the product page.

Is the coupon key the same as the MRR key?

They are stored as two connections. The restricted key can be the same one if it can read both Coupons and Subscriptions. You paste it in each place.

What comes after MRR?

Uptime and web traffic, from providers that can supply those readings. They are not connected yet. They will use the same proof-point shape.