THE METHOD

The Conflict of Interest We Almost Didn't Disclose

2026-09-19

While building out the automation tools on this site, we came across Blotato, a genuinely useful tool for repurposing one piece of content into scheduled posts across platforms. The first draft of its listing said exactly that: useful, well-built, solves a real problem for solo creators.

What that first draft left out was where we'd heard about it. Blotato is most heavily promoted by its own founder's very popular AI newsletter. That's not disqualifying. Founders promote their own products; that's normal. But leaving it out of the listing meant presenting the tool as a neutral recommendation when the loudest voice behind it has a direct financial stake in you signing up.

It's a small thing, and it's exactly the kind of small thing that erodes trust when it's missed often enough. Every best-tools list online has some version of this problem: an affiliate link, a sponsor relationship, a founder's own promotional reach, quietly doing the work of a recommendation without being labeled as one.

The habit of catching this comes from a specific place. Two decades managing vendor partnerships behind resold enterprise software meant sitting on both sides of exactly this table: sometimes as the person promoting a partner's product because the relationship benefited us, and sometimes as the person evaluating whether a competitor's glowing case study was actually independent or quietly self-sourced. Once you've seen how often the second kind gets dressed up as the first, you start reflexively asking who benefits before you finish reading a recommendation.

That habit is what caught this one before it went live, not any special virtue. The listing draft read fine on its own. It was only reading it back a second time, with the where did I hear about this question in mind, that surfaced the gap. Which is itself a useful process note: the first draft of almost anything skips the uncomfortable disclosure, because disclosure isn't the instinct, completeness is, and those aren't the same thing until you specifically check for the second one.

So the listing got a line added: worth knowing it's most heavily promoted by its own founder's newsletter, cross-check independent reviews before committing. That's the whole fix. Not removing the tool, not pretending the conflict doesn't exist, just naming it so you can weigh it yourself.

This is also why every tool listing on this site now gets one extra pass before publishing, specifically asking where did we first hear about this and does that source have a stake in the answer. It's a five-minute check, and it would have taken five minutes to add before the Blotato listing went up too, if we'd thought to ask the question the first time.

We're going to keep making this kind of mistake in the first draft. The commitment isn't to catch everything before you see it. It's to go back and fix it out loud when we don't, and to build the kind of second-pass habit that catches more of them before they ship in the first place.

There's a broader industry pattern worth naming here too, since this isn't unique to Blotato or to us. As more creators build tools alongside their content platforms, the line between recommendation and promotion is going to keep blurring, and readers are going to need to do more of this cross-checking themselves rather than assuming any single source has already done it. That's not a reason to distrust every recommendation. It's a reason to ask the same question we now ask ourselves before publishing one: who benefits, and did they say so. It's a small enough habit that there's no excuse not to apply it consistently, and it costs nothing but the willingness to ask an uncomfortable question about your own sources before you publish, rather than after a reader points it out to you.