Introducing Dealpuffin

Early products and early adopters are trying to find each other. The product wants people who will actually try it. The person wants a reason to start today, on a tool that is still new. A coupon is that reason, and most indie products already know how to make one. It lives in Stripe.

The hard part was never inventing a discount. It was putting that discount in front of the right people without standing up a second checkout, a lifetime-deal marketplace, or a pile of one-off codes in email.

Dealpuffin is that layer.

Point at the product. Connect Stripe. Choose the coupons.

You submit the product URL. You paste a Stripe restricted key that can read coupons and promotion codes, nothing else. Dealpuffin imports what you already created. Nothing goes public until you publish it. A coupon you made for one customer, or one you are not ready to share, stays in the import.

Someone who wants to try the product claims the code and pastes it at your checkout. Stripe applies your percent or amount, your duration, your expiry, and your redemption cap. Dealpuffin does not take the payment and does not redeem the code. Your checkout stays yours. The only Stripe setting you may still need is the one that accepts promotion codes on the payment page. A read-only key cannot flip that for you.

That is the whole loop. No new billing stack, no application, and no one checking that the product is already big enough. The coupon you were already willing to give an early user has somewhere to be found. The page for an agent running this as go-to-market is A go-to-market channel.

Both sides are early adopters

The products on Dealpuffin are early. The people looking are the ones who try new tools first. Often that is the same person: a founder who wants users this week, and who is also willing to try someone else's product with a real code instead of a vague "let me know."

A code that fails at checkout wastes that attention. So the listing rules follow Stripe. No promotion code, no listing. A code locked to one customer stays off. An inactive, expired, or maxed-out code stays off. Sync imports. Publish is a separate, deliberate step. The details are in the docs.

The same Stripe connection can show monthly recurring revenue as social proof, and only if you opt in. The number is fetched from Stripe. The ordinary choice is a band. The exact figure is a second choice. Hidden is the default, so importing coupons does not publish your revenue. Early adopters get a reading, not a figure typed into a form. That is Showing MRR.

Perk clubs, lifetime-deal shops, and read-only deal directories are doing a different job. The comparisons are in How Dealpuffin is different.

Your agent can do it too

If an agent is implementing go-to-market, it can submit the product, connect Stripe, and publish the coupons. If an agent is looking for a SaaS deal for its user, it can search the same catalog and reveal one code. Either way:

npx skills add dealpuffin/agent -g -y

The skill talks to the remote MCP server. You give it a Dealpuffin API key with only the tools you want, or you approve OAuth. Search does not reveal a code. Revealing one is a claim, and it counts once. The seeker-side write-up is Find a SaaS deal for your user.

The catalog is not public yet

Providers can submit a product now. Seekers can leave an email on the homepage and get a note when the catalog opens. That email is not an account, and it does not reserve a code.

If you have a product and a Stripe coupon you would actually give an early user, submit it. If you are waiting to browse, join the waitlist. The short version of the product is how it works.

Frequently asked questions

What is Dealpuffin?

A marketplace of live Stripe promotion codes. Products publish coupons they already have. Early adopters claim a code and paste it at that product's checkout.

Do I have to switch checkouts?

No. You keep Stripe. Connect a read-only key, publish the coupons you want used, and make sure your payment page accepts promotion codes.

Does Dealpuffin redeem the coupon?

No. The seeker pastes the code. Stripe decides whether it is valid. Dealpuffin never charges a card with the read key.

When can I browse coupons?

The public catalog opens at launch. Until then, leave an email on dealpuffin.com and you will be notified. Providers can prepare a listing now. An agent can already call the MCP server.

Does a small product have to wait until it is bigger?

No. There is no revenue minimum and no manual approval. Connect the Stripe key and publish the coupons you want used.