DEV Community: Igor Gridel

Consistency Is a Multiplier, Not a Strategy

Igor Gridel — Sat, 04 Apr 2026 09:53:16 +0000

I posted consistently for two years. It felt productive. It produced almost nothing.

I showed up. I published. I followed the advice that saturates every founder content thread: just be consistent. Post daily. The algorithm rewards activity. Build the habit and the results will follow.

The results did not follow.

I got impressions. I got some engagement. I did not get the thing I actually needed: people who understood what I do, trusted my judgment, and wanted to work with me or support what I was building.

It took me too long to understand why.

Consistency is a multiplier. The problem is, it multiplies whatever is already there. If your positioning is clear, consistency compounds recognition. If your positioning is vague, consistency compounds noise.

I was compounding noise.

What platforms actually reward now

The old model was simple. Post more, get more reach. The algorithm rewarded activity. Fill the calendar, win the game.

That model is dead.

LinkedIn now uses larger recommender models and LLM support to understand what posts are actually about and how professional interests evolve. The feed is not just counting posts. It is trying to predict what specific people will find relevant.

YouTube recommendations use satisfaction signals, including survey data, not just raw watch time. The platform is asking: did this actually help the viewer? Not just: did they watch?

Instagram ranking is individualized across Feed, Stories, Explore, and Reels. The system is trying to predict what specific people care about, not just what is popular.

Google Search is becoming multimodal, conversational, and AI-assisted. Discovery spans multiple surfaces. The question is not just whether you published, but whether what you published is useful, findable, and trustworthy.

Volume is no longer the bottleneck. Clarity is.

When everyone can publish more, the advantage moves to clarity, credibility, and system design.

The multiplier problem

Here is the trap I fell into.

I was posting regularly, but I had not made the hard choices about positioning. I had not decided what category I wanted to own. I had not clarified who I was trying to reach. I had not built a system that converted attention into anything durable.

I was just showing up.

Output can camouflage strategic vagueness. Daily activity feels productive. It can substitute for the hard work of deciding what you actually want to be known for.

If your content does not teach people what category to place you in, frequency only scales confusion.

The internet does not reward posting. It rewards useful signal.

The four-filter diagnostic

I now run every piece of content through four filters before I publish. If it fails any of them, I either fix it or I do not post it.

Filter 1: Positioning

Does this content teach people what category to place me in?

If someone reads this, will they understand what I do and who I help? Or will they just think I am smart and interesting without knowing what to do with that?

Content without positioning makes it harder for both audiences and algorithms to understand what lane you own. You become a generalist in a world that rewards specialists.

Filter 2: Distribution

Does this content reach the right people, not just any people?

Impressions are not the goal. Reaching people who might actually care is the goal. A thousand views from the wrong audience is worth less than fifty views from the right one.

Distribution is not just about posting. It is about understanding where your people are, what they are searching for, and how they discover new voices.

Filter 3: Authority

Does this content make me more believable, not just more visible?

Visibility without credibility is noise. The question is not whether people saw you. The question is whether they trust you more after seeing you.

The 2025 Edelman/LinkedIn B2B Thought Leadership report found that 95% of hidden decision-makers say strong thought leadership makes them more receptive to sales or marketing outreach. The stat is striking, but the logic is simple: people buy from people they trust. Content that builds trust is more valuable than content that just builds reach.

Founders do not need more content. They need more believable content.

Filter 4: Capture

Does this content build an owned relationship, or is it a temporary performance?

A post that gets attention but builds no owned relationship is a temporary performance, not a strategic asset. The platform owns the reach. You own nothing.

Email is the owned asset. Subscribers are the durable relationship. Content that does not route toward capture is content that evaporates.

A founder content system is only as strong as its weakest filter.

The real job of founder content

I used to think the job of content was to stay visible. Keep showing up. Stay top of mind. Be present.

That is not the job.

The real job of founder content is to reduce uncertainty.

Reduce uncertainty about what you do. Reduce uncertainty about who you help. Reduce uncertainty about whether you are credible.

When someone encounters your content, they should leave with less confusion, not more. They should understand your category better. They should trust your judgment more. They should know what to do next if they want to go deeper.

The post is not the asset. The idea system behind the post is the asset.

What I do differently now

I start with positioning clarity before I touch a content calendar. I ask: what do I want to be known for? What category do I want to own? Who am I trying to reach?

Before I publish anything, I ask: does this piece make my category clearer or fuzzier?

I build for capture, not just reach. Every piece of content should have a path toward an owned relationship. If it does not, I ask why I am publishing it.

I treat consistency as the accelerant, not the strategy. I post regularly, but only after the hard choices are made. Consistency compounds the right thing when the right thing is already in place.

The reframe

The advice to be consistent is not wrong. It is incomplete.

Consistency matters. But it matters after the hard choices are made. It matters after you know what you are trying to be known for. It matters after you have a system that converts attention into trust and trust into something durable.

When everyone can publish more, the advantage moves to clarity, credibility, and system design.

The real job of founder content is to reduce uncertainty.

If you are posting consistently and it is not working, the problem is probably not frequency. The problem is probably one of the four filters.

Fix the filter. Then let consistency do its job.

If this was useful, you can subscribe to get more writing like this. I write about AI workflows, product building, and the operational lessons from building multiple businesses as a solo founder. You can also find more at igorgridel.com.

Originally published on Igor Gridel. Follow me for more on AI workflows and automation.

I Automated My Content Pipeline with Claude Code. Here's Everything.

Igor Gridel — Sat, 04 Apr 2026 09:30:29 +0000

Claude keeps getting confused by Post For Me.

Every time I ask it to schedule something, it forgets the flow. Mixes up steps. Makes the same mistakes on repeat. The API itself is good, the docs are clear, but Claude cannot hold the whole workflow in its head across conversations.

This is the part of AI automation nobody warns you about. The AI works. The tool works. The connection between them doesn't exist, and you have to build it yourself.

So I did.

I wrote a 659-line skill file that teaches Claude the full Post For Me API. How to list accounts, check for duplicates before posting, handle platform differences between X, Threads, and Instagram, verify that posts actually went through, and deal with errors when they don't.

Post For Me is a social media posting API by Matt Roth and Caleb Panza. One SDK that publishes to X, Threads, Instagram, TikTok, LinkedIn, YouTube, and more. The tool is genuinely good and inexpensive. The problem was never the API. It was that Claude had no reliable reference for how to use it correctly.

The skill solved that. Claude reads it before every posting interaction and stopped making mistakes.

But the skill turned out to be just one piece of something bigger.

The automation stack

I now have three agents running on a schedule through Claude Code. None of them auto-post. They suggest, I decide.

An ops sweep runs every four hours. It checks my Obsidian inbox for unprocessed items, flags stale drafts, and spots posting gaps. One suggestion, max 100 words. Quick desk check, nothing more.

A morning briefing runs at 9am. Full daily review: yesterday's posting activity, engagement analytics pulled from Post For Me, inbox status, draft pipeline, platform balance, Patreon status, and one priority for today.

A weekly strategist runs Saturday mornings. Deep review: best and worst posts with pattern analysis, content gaps, video ideas from top performers, project recaps, three priorities for next week.

The pattern is the same for all three. Look at the system, surface what matters, suggest one thing. No auto-posting, no autonomous decisions. I spent time thinking about full automation and realized what I actually wanted wasn't "post for me automatically." It was "review everything and tell me what matters right now."

That turned out to be far more useful.

How it all connects

Everything runs through an Obsidian vault. Ideas get captured in the inbox from voice notes, text dumps, screenshots, conversations. They get processed and routed. Developed into post options. Polished. Humanized if they still sound flat. Run through a quality check. Then Post For Me handles the publishing.

Each stage has its own Claude Code skill. One turns raw ideas into post options. One polishes drafts. One fixes robotic-sounding text. The Post For Me skill handles the final step.

Published posts get tracked. Performance gets reviewed by the agents. Top performers get analyzed and fed back into the system. It loops.

The Obsidian vault is the operating system. The skills are the tools. The agents are the assistants that keep checking the system without being asked.

What I learned building this

Build the skill first. Before the agents, before the pipeline. The skill is what makes the posting step reliable, and that's the step where everything used to break.

A skill isn't code. It's a markdown document that Claude reads before it acts. I was surprised how well that works. You write down the exact steps, the edge cases, the mistakes to avoid, and Claude follows them. No plugin, no extension, just a text file.

The ops sweep is the agent I use most. Every four hours, a quick check on the whole system. That rhythm is what keeps things moving without me having to remember anything.

The full Post For Me skill

The complete 659-line skill file is available for download. If you're using Claude Code, save it as SKILL.md in your .claude/skills/post-for-me/ folder and it works immediately.

Download the Post For Me skill file

If you build something similar or want to talk through the setup, I'm on Patreon. There's also a Discord, but getting access is part of the game. It's not as simple as clicking a link.

Originally published on Igor Gridel. Follow me for more on AI workflows and automation.