I’ve been thinking about a new SaaS direction and would love to hear how others see this. Until now, SEO was mostly: keyword → Google results → website click But more and more users are no longer only browsing classic search results. They are asking AI tools or Google AI-style answers things like: “Best restaurant in Berlin?”“Where can I buy Jordan sneakers?”“Compare product X vs product Y.”“Which hotel has parking and allows pets?”“Which option is the cheapest?”“Give me their phone number.”“Who has availability tonight?” The problem I see is that visibility is no longer just about ranking. The answer can change depending on: - the query - the user’s location - the language - the follow-up question - comparison intent - price intent - availability - reviews - attributes like parking, pet-friendly, vegan, open now, etc. For example: A user first asks: “Where can I buy Jordan sneakers in Berlin?” They get a few stores. Then they ask: “Where are they cheapest?” The answer may completely change. Then they ask: “Who has size 43 in stock?” Again, a different set of results may appear. The same applies to hotels, restaurants, SaaS products and local businesses. A brand may appear in the first AI answer, but disappear when the user asks about price, parking, comparison, availability, phone number, reviews, or specific features. That made me think about a possible new category: AI Answer Visibility / AI Decision Journey Tracking Instead of only measuring: “Does my website rank?” you measure: “Does AI keep recommending my brand throughout the user’s decision journey?” Possible visibility layers: - Discovery visibility - Comparison visibility - Price visibility - Availability visibility - Contact accuracy - Attribute coverage - Trust/review visibility - Conversion path visibility In other words: If a user starts with a broad query and then keeps asking more precise follow-up questions, the tool would show where a brand stays in the answer — and where it drops out.

I’m currently building an automation system that started with a very simple problem: Small business owners are drowning in messages. One customer writes on Instagram. Another sends a WhatsApp message.Someone else calls.A few people use the website form.Then there are emails, missed calls, Viber messages, Facebook messages… And the owner is expected to answer everything, remember everything, follow up with everyone, and still run the actual business. That is where most automation projects go wrong. People try to build “an AI chatbot” first. But after working through the system, I realized the real goal is not to replace the business owner. The real goal is to remove communication chaos. So the system I’m building is not a classic CRM. It is more like an invisible communication layer between the customer and the business. The customer can come from any channel: Instagram, Website Chat, WhatsApp, Facebook, Viber, email, SMS or phone. The system takes that message and turns it into something structured: Is this a booking request?Is it a price question? Is it a complaint? Is it urgent? Is the knowledge missing? Does the owner need to approve something? Should a human take over? Instead of giving the AI full freedom, I built the system around control. There is a Business Brain that contains the real information about the business: services, prices, working hours, FAQs, booking rules, payment rules, cancellation rules, forbidden topics and escalation triggers. Then there is a Rules Engine. That part decides what the system is allowed to do. Can it answer automatically?Does the owner need to approve?Should this become a request?Should this become an exception?Is this topic too sensitive for automation? That changed the way I look at AI automation. The value is not in making AI answer everything. The value is in making the system know when not to answer. For the business owner, the interface must stay simple. The owner should not open a complicated dashboard. They should only see clear action cards:

Yesterday I was amazed how internet frauds upgraded..on Linkedin a recruiter contacted me about some job and they gave me the project to do some functionality, to download it from github..and I did it, but Claude Code in VS Code checked all the files and found injected malware in js script..soo another level..so be cautious what websites you run locally 😁

Whoever has it is posting a crypto scam. That is not me. I would never promote anything like that. Do not click any links, send any money, or engage with anything posted from my account right now. I'm working on getting it back. Will let you know when it's secured. Thanks for looking out.

Most people open Claude Code and start building immediately. That is usually where the chaos begins. Random features.Wrong architecture.Extra files.Token waste.A project that slowly turns into something you never asked for. My workflow is different. Before I let Claude touch the code, I lock the project first. 🔒 1. Lock the scopeI define exactly what the project is — and what it is NOT.This prevents Claude from drifting into random ideas. 🧠 2. Write skill. md... This becomes the project brain. It includes architecture, rules, UX direction, forbidden actions, naming rules, design logic, and technical limits. 🧩 3. Split the build into phasesClaude does not build everything at once.Each phase has one goal, one scope, and one clear output. ⚙️ 4. Execute with strict limitsNo unnecessary refactors. No random integrations. No extra pages. No “nice to have” features.Only what the current phase requires. 🧪 5. Test before moving forwardEvery phase must be checked before the next one starts.If something breaks, fix the phase — not the whole project. This is how I reduce token waste, keep Claude focused, and avoid turning a simple build into a messy rebuild. The real secret is not the prompt. It is the system around the prompt. Scope → Skill → Phases → Build → Test → No drift That is how I build with Claude without letting Claude take over the project.