Skip to content
Anvisco

Notes · · Brian Nguyen

Why Anvisco is building small tools

Anvisco started as a website studio for local service businesses: audits, rebuilds and small upgrades, sold as packages. That work taught a lot, but it also made one pattern hard to ignore.

The pattern

The most useful fixes were rarely visual. They were things like a sitemap listing pages that no longer existed, structured data describing the wrong hours, or a site that only made sense once a person clicked through three menus. Each fix was small. Finding it took most of the time.

Those are problems with how a site reads to machines, and machines are now a large share of the audience. Search engines have always read sites this way. Feed readers do too. AI assistants that summarise or recommend businesses add another reader that depends on the same basic signals being right.

Why tools, and why small

A one-off project fixes one site once. A small tool that finds a specific class of problem can help many sites, and keep helping after things change. Keeping each tool small makes it easier to explain, easier to check, and easier to stop building if it turns out not to be useful.

"Small" is also a constraint on promises. A tool that does one thing can be honest about exactly what it checks and what it can't see.

What changes in practice

  • The old audit-and-package offer is retired. The previous site will be kept separately as a record of that work.
  • Ideas are published while still ideas, with a status label. The first is Feed Doctor, which is a concept under evaluation, not a product.
  • Some hands-on work continues, by choice and in small amounts. The services page explains what that covers.

What this note doesn't claim

There are no users, customers or results to report yet. When there are, they'll be written up here with the details that make them checkable.