12
5 Comments

[BuildInPublic]: We are entering a very important product phase!

What I've noticed is that people are wanting fewer cards, tables, etc. With frequent use of AI chats, they're very used to that environment—an AI chat where they can ask for anything and have everything right there in the chat. This is very important; noticing these points early on is what makes your product truly useful for your audience! So, based on my analysis, people barely read information on the platform. It's no use putting a banner on the website anymore (This won't work because you need X,Y)—they don't read it! I'm a bit worried about this and so on, but I decided to cater to this audience that has this difficulty, and so we decided to create an Agent (That's right, an AI agent and not a normal chat with API calls; I believe 2026 will be the year of Agents). This agent will have all the necessary tools and will be able to instruct people on its own. This will make them comfortable and follow the industry standard for AI Agents. However, this agent will not change the app; it will improve it, and we will keep everything as it is. We will just have a new tab so you can chat with the Agent. The AI, with our web engine, will have an arsenal of tools to use!

posted toAvatar for product Multify
Multify
  1. 1

    What you’re describing (intent > volume) also ties into a broader UX shift I’ve been noticing.

    People are increasingly conditioned by AI chat interfaces to expect information in an abstracted, on-demand format. Instead of scanning dashboards, cards, and tables, they want to ask a question and get a distilled answer.

    It’s similar to why fewer people read full documentation when they can ask an AI to summarize exactly what they need.

    That said, I’d be careful about fully replacing structure with chat. The challenge isn’t “people don’t read,” it’s that they don’t want to parse unnecessary structure when they have a clear intent.

    If you introduce an agent, the key question becomes:
    Does it reduce cognitive load, or just add another layer?

    The most powerful version might be:
    Structured data underneath + conversational interface on top.

    Curious how you’re thinking about:

    • When users should use the agent vs. dashboards

    • Whether the agent is assistive or primary

    That balance feels like the real differentiator going into 2026.

    1. 1

      Great! We won't replace everything with chat! The pages will still remain, but the user can use the functionalities within the chat! They don't literally need to go to the page to use the functionality! This way we cater to both audiences.

  2. 1

    You’re right that chat is becoming a default behavior.

    At the same time, I don’t think people have stopped reading they’ve just stopped reading things that don’t clearly help them move forward.

    Agents can be powerful for: getting unstuck, fFinding things quickly, reducing friction for new users

    For more complex or repetitive workflows, structured UI still tends to offer clarity and control.

    If the agent meaningfully reduces time-to-value, that’s a strong move.

    If it’s mainly following the AI trend, the impact may be limited.

    UI isn’t going away.
    Thoughtful UX still matters most.

    1. 1

      Excellent points! I wanted to mention that people don't read; I wanted to relate this to the fact that they want everything handed to them and are becoming too complacent! And AI makes this dopamine release very effective in people.

      And I also agree that the UI should be well thought out.

  3. 1

    Hi John Alex, I saw your recent milestone, congrats! I’m a Virtual Assistant who supports founders with Customer Support VA, Executive VA. Let me know if you will be needing some support right now!

    Congratulation, once again