Ideas become
something useful.

Meta launched Muse, an AI agent that shops on people's behalf, and Shopify stores were inside it from day one with no setup. That sounds like free distribution, but it only works if the agent can read your store. Muse never sees your photos, your theme or your brand story, and neither does ChatGPT. They read data.

Over the last six weeks, merchants kept showing our StoreSEO team how fragile that data is. One stray space made "in stock" invalid to Google. Product images went out as 115px thumbnails and failed Merchant Center. A review app's stray comma broke the entire product markup. Shipping and return policies were on the site but never reached Merchant Center. None of it is visible on the storefront, and all of it makes a product invisible to a machine. A large part of our last seven StoreSEO releases went into fixing exactly this.

The result is an agent-readable product checklist: availability that validates, full-size images rather than thumbnails, barcode (GTIN) and product condition, a Google product category, shipping and return policy in structured data, sale dates so agents can see the discount, and revenue tracking for traffic from ChatGPT and other AI assistants. Your storefront was built for people who browse. The next layer is for agents that decide.

Having my initials on a two-character .bd domain is part of the appeal, I admit. The bigger reason for the rebuild was another chance to work closely with AI. I used it throughout: design, code, content structure, SEO, testing and deployment. I stayed in the decisions, we went through revisions, checked the live results, and simplified whenever the design got more complicated than it needed to be.

The site brings together my companies, my writing and the AI projects I am working on. You can explore the project map, read my notes, or ask my AI about my work.

There is also a layer built for AI agents: structured public content and an MCP endpoint for finding projects, searching my writing and reading published notes. That felt right for a personal website at this point in my journey, a place people can explore, with information their AI tools can reach as well. masifrahman.com and asif.im now bring you to the same site.

When AIScan crossed 3,400 scans, the number that interested me was not the total. It was where the scans came from. Most arrived through the API, the MCP server and the command line rather than the website. I had built one scanner and then kept adding ways to reach it, because the people who care about this problem do not all work in the same place.

Today there are seven ways in: the website, a CLI that runs with npx in about 20 seconds, an MCP server with 13 tools so Claude or Cursor can scan a site and act on the failing checks, a Telegram bot, a REST API, a Chrome extension and a Claude Code skill. The same engine sits behind all of them.

The reason this matters is that an AI agent reads a website nothing like a person does. It never sees the design or the hero image. It looks for a handful of small files, and most sites have never shipped a single one of them. That is how a good website ends up invisible to ChatGPT. The free scan stays free; I only charge for daily monitoring, because that is the part that costs money to run.

I noticed a Level 5 Master Builder badge on my Replit profile, placing me in the top 1% of Replit Agent users. The description focused on deployed applications serving real people. That was the part that mattered to me.

Across Replit, Claude Code and Lovable, I’ve built hundreds of small tools and apps. Most started with something in my own work or life that needed fixing. Visa4.Travel is one example: I wanted an easier way to check visa eligibility before a trip, so I built it and made it available to others.

I don’t build at that pace anymore, but many of those tools are still running. My advice is simple: take one problem of your own to AI and try making something useful.

The community tools I tried were built for an older Umami API. They could return plausible answers while pointing at the wrong data. That was a good reason to build something I could check myself.

I released the result as an open-source tool. It connects agents to Umami reports, keeps reads as the default, and makes writes an explicit choice. The useful part is being able to follow a question beyond the dashboard.

The usual response was another plugin to install, scan and maintain. Our team wanted the hosting platform to handle more of that work, with the site, server and DNS already in view.

In this release, we brought broken-link scans, scheduled checks, redirects and exportable reports into the dashboard. It reflects a direction I care about: making everyday site maintenance simpler for the people responsible for it.

The ideas start with investing in a strong skill and choosing a market deliberately. A first job can become a starting point for building a business, a trading relationship or a community.

My central question is how success abroad can create more opportunity at home: connections between makers and buyers, stronger communities, and a wider horizon for the next generation.

AI can help draft code, tests and documentation. The engineer still has to decide what is worth making, check whether the output is correct, and understand what happens when real users arrive.

A convincing demo is only a beginning. Product sense and engineering fundamentals help turn it into something people can rely on. I wanted the next generation of builders in Bangladesh to see that opportunity clearly.

Using AI is becoming part of everyday work. But two people with the same tools can produce very different results. The ability to structure a thought, describe a problem and explain what you want still matters.

I encouraged the students to develop a practical skill, use AI regularly, and keep practising writing and speaking. The summit was also a reminder of the talent and energy that exists beyond Dhaka.

The demo brings together a citizen portal, a pump-station terminal and an administration view. I added Bangla and English, vehicle-verification flows, quota tracking and digital receipts as the idea developed.

It is an independent demonstration of what could be built, not an operating government service. The feedback is part of the work: it helps make the next version more useful.

I described agents handling different parts of a founder’s work, from research and analytics to drafting content. As the number of agents grows, keeping track of their tasks and costs becomes a job of its own.

We built MissionDeck around a shared task board, agent conversations, coordination and cost visibility. My suggestion was to start with one agent doing one useful thing, understand the work, and build from there.

With the StoreSEO 3.9.8 release, merchants could open product-editing screens within the app and act on SEO recommendations without repeatedly switching back to Shopify Admin.

We also added Loox review-schema integration and made improvements informed by Microsoft Clarity. I was proud of how quickly the team turned a platform capability into a more convenient everyday experience.

In this reflection on different generations at work, I was especially interested in people who learn by making a first project: a store, a prototype or a small business.

For founders and leaders, guidance includes showing people where useful tools, resources and communities live. Onboarding should help them take that first practical step, as well as explain what the job requires.