Why pickuma Runs No Sponsored Posts (and How That Shapes Recommendations)

You’ve read the disclosure line at the top of our reviews: pickuma earns affiliate commissions. So it’s fair to ask what that buys. The short answer is nothing a vendor can control. We don’t run sponsored posts, paid placements, “featured partner” slots, or review-for-payment deals. A company cannot pay us to write about their product, to write about it favorably, or to rank it above a competitor.

That distinction gets blurred constantly, partly because affiliate and sponsored revenue both involve money flowing from vendors. But the mechanics point the incentives in opposite directions, and the direction is the whole story.

The two models pull in opposite directions

A sponsored post is paid up front. A vendor hands over a flat fee — anywhere from a few hundred dollars for a small blog to five figures for a large one — in exchange for coverage. The payment lands whether the product is good or bad, whether you buy it or close the tab, whether the review ages well or embarrasses everyone in six months. The publisher’s incentive is to keep the vendor happy enough to buy the next slot. That pressure leans on every editorial choice: which flaws get softened, which competitor goes unmentioned, which “con” gets demoted to a “thing to keep in mind.”

Affiliate revenue works the other way. We get paid only if you read a recommendation, decide it fits your situation, click through, and the product holds up well enough that you keep it past any refund window. Commission rates in the tools we cover typically run 15–30% of the first payment, and most programs claw the commission back if you cancel inside 30 to 60 days. So a recommendation that wins the click but loses you as a happy user is worth roughly nothing to us. A bad recommendation is actively unprofitable.

What “no sponsored posts” changes in practice

The policy is only worth something if it shows up in the work. Four things follow from it directly.

We can name the loser. In a sponsored arrangement, the vendor paying for the post is the implicit winner of any comparison. Without that constraint, our comparison tables can say a tool came third, and the third-place vendor has no recourse — they were never our customer. The reader is.

We can recommend against buying. Some categories are full of tools that solve a problem you might not have. The most useful sentence in a review is sometimes “you probably don’t need this.” That sentence is incompatible with getting paid to promote the thing.

Coverage follows demand, not budgets. We write about tools because developers are searching for honest comparisons, not because a vendor opened a campaign. That’s why you’ll find write-ups of tools with no affiliate program at all — they earn their place by being worth your time.

Negative aging is allowed. When a tool we recommended gets worse — a price hike, a gutted free tier, a quality slide after an acquisition — we update the review and, when it’s warranted, pull the recommendation. A sponsored relationship makes that awkward. An affiliate relationship makes it mandatory, because steering you toward a tool that’s now wrong for you destroys the only thing the model runs on.

None of this makes our recommendations objective. Our scoring weights reflect what we think matters — fast onboarding, transparent pricing, an export path so you’re not locked in — and you might weight things differently. The point of refusing sponsorship isn’t to claim we have no opinions. It’s to make sure the opinions are ours and yours, not a media buyer’s.

A concrete example: how we picked a newsletter platform

When we needed somewhere to publish the pickuma newsletter, we ran the same evaluation we’d run for a review. We weighted deliverability, the cost curve as a list grows, and whether we could export every subscriber on demand. beehiiv won on the export guarantee and a free tier that doesn’t cripple sending, which is why we use it and why we recommend it here — not because of the program, but because it passed the test we’d apply to anything.

For reference, our internal review notes and scoring rubric live in a shared Notion workspace, which is the same kind of tool-on-merit decision — we tried several docs apps before settling there.

If you ever read a pickuma recommendation that feels like it’s protecting a vendor instead of helping you decide, that’s a bug in our process, not a feature of our business model. Tell us, and we’ll re-examine it.