All articles
I read 52 community teardowns. The best champion programs pay nothing.
I expected the best community champion programs to run on budgets. Notion's ambassadors are unpaid. Cash attracts mercenaries; access attracts advocates. Here's that finding, and the harder rule I shipped with it: no champion and no partnership leaves my community skill without a revenue tie or an honest exploratory flag.
I thought my sales AI was closing deals. It was guessing.
A prospect said "let me think about it" and my agent moved the deal to Proposal. Nobody had agreed to anything. Here's the rule that fixed it: a deal moves stage only on a logged buyer signal, enforced by a script that fails the board when it can't find one.
Directory backlinks are dead. Directory profiles are what AI reads now.
Every launch checklist still says submit to 100+ directories. That advice inverted, because AI now reads directory profiles to decide what to recommend, and a stale profile makes it recommend the product you no longer sell. Here is the skill I built around submitting to fewer.
An ICP list nobody can fetch isn't targeting. It's a wish list.
I asked an AI for 25 ideal customer profiles and got 25. Then the scraper found almost nobody, and nothing in the system said anything was wrong. Here are the two silent failures that make a pretty ICP list worthless, and the planner I built to catch them before they spend money.
Everyone's launch post sounds like a build log. Your agent writes the other kind.
Ask your agent to announce something you shipped and it writes about the machinery. v1.4.0 made a launch its own occasion, with a lint that fails a headline selling the build instead of the product. v1.5.0 adds the first 3 seconds of a Reel, TikTok or Short.
My voice classifier was 93% confident. It was completely wrong.
My brand-voice classifier read a skincare brand's copy and called it B2B SaaS at 0.93 confidence, because it was measuring sentence length and nothing else. Here's the second signal that fixed it, and why a confident wrong answer is worse than no answer.
I thought every post needed a hook. My best one had none.
I built a skill that enforces hook, structure and CTA on every social post. The rules that turned out to matter are the ones that switch it off: when to drop the machinery entirely, why my buyers read everything and comment on nothing, and why a long-form Article was never just a longer post.
I thought a URL that parsed was a URL that was safe
A URL can pass every parsing rule and still be a phishing domain, a doubly-encoded payload, or a link that silently destroys your ad-cost attribution. Three failures my agents were walking straight past, and the skill I shipped to stop them.
Importing your OpenAPI spec doesn't document your API. It builds a skeleton and stops.
Point a tool at your OpenAPI spec and you get a reference skeleton — thin, and only one of the four docs a developer actually reads. Here's the skill I built to enrich it, enforce the rest with scripts that can't lie, and catch real bugs like a missing servers block before they ship.
Get new posts and release notes in your feed reader