Testing-Led Sponsorship: How I Evaluate, Accept, and Write About Sponsored Tools
Why I Built This Framework
I work in AI product management. I ship things. I test systems. I distrust demos.
I’ve also seen enough shallow hype reviews to know they’re useless.
So when I collaborate with a sponsor, I use the same structured testing models I’d apply to a product I build myself.
That means:
A sponsorship is accepted after testing, never before
No first-impression sponsorships
No opinions formed based only on consensus sentiment
No “looks promising” endorsements
If I write about your product, it’s because I’ve tested it thoroughly enough to understand its strengths and its limits.
Key Principle
There’s only one:
Run your tests before you run your mouth.
What You Get From This Approach
This framework is not for everyone, and that’s intentional.
The Four Stages of Testing-Led Sponsorship
This framework has four stages. Failing any one of them disqualifies the partnership.
Stage 1: Fit Screening (Before Any Testing)
Goal: Eliminate misaligned products early.
Assessment Phase:
Ethical Baseline ( there no conflicts with my own values)
Any company that lands in my Most Absurd Ethical Product Decisions roundup is permanently excluded from sponsorship consideration
No products that rely on deceptive data practices (i.e. selling user data)
No businesses with a track record of serious ethical breaches that my newsletter advocates against (e.g. user well‑being, consent)
No tools that target or exploit vulnerable groups, like products marketed aggressively to minors or people in crisis
No abusive, discriminatory, or harmful use cases (e.g. harassment, exploitation)
Audience fit (must be a “yes”)
Does this solve a real problem for any of these groups?
Product builders / Product Managers / Vibecoders
Designers / Creatives
Founders / Solopreneurs
AI-curious Practitioners
Substack Writers
Category relevance (must be a “yes”)
Is this something I’d recommend trying without a sponsorship?
Long-term credibility risk (must be a “no”)
Would endorsing this make my future recommendations weaker?
Partnership setup
Am I able to retain full editorial control?
Stage 2: Hands-On, Multi-Session Testing
This stage is intentionally unglamorous.
If a product only shines in a demo, it won’t survive this phase.
Goal:
Observe real experience, not marketing claims.
Ethical Baseline ( = no conflicts with my own values)
No dark patterns, deceptive pricing, or manipulative UX
Test Setup (must mirror real usage scenarios)
test across multiple sessions
test in different contexts
test wearing different hats: beginner user, advanced user
test using real (or close-to-real) workloads
test using messy data
if possible - test on desktop and mobile
comparison against alternatives I’ve tested in the past
record moments of confusion, delight, or annoyance
Stage 3: Decision Gate
Goal:
Decide whether a sponsorship is justified.
Decision:
Rejected - The product didn’t pass stage 1 and/or stage 2. No sponsorship.
Accepted - The product passed stage 1 and stage 2.
Only in case #3 do we discuss sponsorship terms.
Stage 4: Transparent Sponsorship Disclosure
The sponsorship explains why the post exists, not what it says.
Goal:
Maintain reader trust.
Every sponsored post follows a clear rule:
Disclosures are upfront, unambiguous, written in plain language
Typical phrasing looks like:
Sponsored by [X]. Sponsorship accepted after hands-on testing; I’m still a paying user.
I don’t do:
buried disclosures
euphemisms
“partnered with” vagueness
In short
Testing-led sponsorships compound trust. Short-term hype erodes it.
If a product survives testing, I’ll stand behind it — sponsored or not.
Inquiries
As a reader, you know where to find me 🤗
As a sponsor, please contact me via Passionfroot.