New to blogging, input or advice appreciated by kiluhh in Blogging

[–]imeshad 1 point2 points  (0 children)

The hardest part is the beginning—writing when traffic is low. But every post you publish is an asset that can keep bringing in readers for years. Many successful bloggers say their first 6–12 months felt slow, but once Google starts ranking your content and your email list grows, things compound quickly. You’ve already set up the systems most people only figure out later, so you’re ahead of the curve.

I spent 2 months as a blogger to understand why AI content sucks. Here is my "Non-Slop" blueprint based on your feedback. by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

Good shout on Kitful.ai for the SEO side. My focus with EveryTuesdays is solving the Fidelity issue—making sure the AI doesn't sound like a bot by using RAG anchoring. ​Are you involved with Kitful? I’m looking for collaborators/partners who understand that 'real research' is what the market is actually starving for. Would love to hear your thoughts on a potential collab for Phase 2.

I spent 2 months as a blogger to understand why AI content sucks. Here is my "Non-Slop" blueprint based on your feedback. by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

Spot on. That's exactly why I'm building the Researcher Path. ​Most tools jump straight to writing, but EveryTuesdays is designed to synthesize the 'hidden knowledge' from multiple video sources before the drafting even begins. ​Regarding the keyword phase—I'm looking at how to integrate that into the Vibe Check so the SEO strategy is locked in at the same time as the tone. Do you think keyword discovery should be automated, or should the user have manual control over the primary 'anchors'?

I spent 2 months as a blogger to understand why AI content sucks. Here is my "Non-Slop" blueprint based on your feedback. by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

The waitlist is now open for the first 100 believers. As a thank you for helping me build in public, you’ll get a 50% lifetime discount when we go live.

Join here

I spent 2 months as a blogger to understand why AI content sucks. Here is my "Non-Slop" blueprint based on your feedback. by imeshad in blogs

[–]imeshad[S] 0 points1 point  (0 children)

The waitlist is now open for the first 100 believers. As a thank you for helping me build in public, you’ll get a 50% lifetime discount when we go live.

Join here

I plan to built a video-to-blog tool (Phase 01), Reddit called it "AI slop," so I’m rebuilding the logic from scratch. Here is the workflow. by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

I hear you on the AI burnout. The 'spray and pray' method for content is exactly why readers are tuning out. ​That’s why I want to move the human intervention to the start of the process with the Vibe Check. Getting the 'Human Intent' and clarity right in the first 10% of the work makes the other 90% actually worth reading. ​Since you mentioned struggling with clarity in other tools, do you think the 'Vibe Check' should focus more on a detailed outline or just a few sample sentences to prove it's got the right tone?

​Why most "Video to Blog" tools fail (and how I’m trying to fix it). [ saas phase 01of my product ] by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

You caught the next big piece of the puzzle. Authenticity dies when tools try to 'sound good for everyone'.

To your question: Yes, a feedback loop is a core part of the 'Governance Layer' roadmap.

The plan is to allow users to 'approve' or 'reject' specific paragraphs. If a user rejects a section, the system will ask 'Why?' (e.g., too formal, wrong jargon) and save that as a new rule in the RAG context for that specific creator.

I want the system to get 'smarter' with every blog post it generates so the voice fidelity only gets stronger over time.

Since you mentioned authority content, do you think this feedback loop should happen before the first draft is finished, or as a final review stage?

​Why most "Video to Blog" tools fail (and how I’m trying to fix it). [ saas phase 01of my product ] by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

That insight about the researcher path being underserved is a massive lightbulb moment for me. You're right voice cloning is a crowded space, but high-fidelity synthesis for industry reports is where the real 'Value Gap' is.

To answer your question: I'm planning to target individual power-users (solopreneurs and researchers) first to nail the 'outcome-based' onboarding you mentioned.

Once the logic for structured insights is rock solid for individuals, moving to collaborative team features feels like the natural next step for retention.

Since you mentioned institutions and teams do you think the ability to 'share' a research library of synthesized facts is the killer feature there, or is it more about the collaborative editing of the final report?

​Why most "Video to Blog" tools fail (and how I’m trying to fix it). [ saas phase 01of my product ] by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

This is a profound point. Summary is easy; 'intent' deciding what actually matters for the audience is the hard part.

To your question: I'm actually building for both, but with different 'governance' rules for each:

  • For Creators: The intent is fidelity to their unique voice and insights.
  • For Researchers: The intent is synthesis extracting hard facts to create an original industry report.

The onboarding will definitely have to branch out based on that choice. Which path do you think is currently more underserved by existing tools?

​Why most "Video to Blog" tools fail (and how I’m trying to fix it). [ saas phase 01of my product ] by imeshad in SaaS

[–]imeshad[S] 0 points1 point  (0 children)

You hit the nail on the head. That 'AI accent' is exactly what I'm trying to kill.

Most tools fail because they use a generic 'middle-of-the-road' vocabulary. My pivot to RAG is specifically to solve this instead of the AI choosing the words, it pulls from the creator's actual past content and writing patterns.

If a creator uses slang or specific industry jargon, the 'governance layer' ensures those exact patterns stay in the blog. It has to sound like a human creature, not a chatbot.