Today I launched a new project: qrviz.com. It is a free QR code generator built for a wide range of real use cases, from business cards and restaurant menus to links, WiFi access, promotions, and more.
For this project, I am relying entirely on SEO. That means there is a very real chance almost nobody will ever find it. That is the strange reality of building small web products today: you can make something genuinely useful and still struggle to get even a tiny amount of attention.
What I actually launched
QRViz is a browser-based static QR code generator, not a campaign platform. It covers URLs, Wi-Fi, vCards, PDFs, menus, events, packaging, and other stable destinations. Users can adjust size, quiet zone, error correction, colors, gradients, eye styles, and logo placement, then export PNG, SVG, or PDF.
Two choices keep the workflow deliberately direct: no account is required to create and export a code, and uploaded logos stay in the browser. QRViz also has localized routes in English, Russian, Spanish, Portuguese, German, French, and Simplified Chinese, with guides and use-case pages around practical QR workflows.
Not becoming a dynamic QR platform is part of the product decision
QRViz intentionally does not provide redirect editing, scan analytics, campaign dashboards, or post-print destination management. A static QR code encodes the final destination directly. That makes the workflow simpler and more predictable, but it creates a real trade-off: if the destination changes after printing, a new code has to be generated and published. I prefer that explicit limitation to hiding a redirect layer behind a tool whose main promise is clarity.
The product is simple. Distribution is the uncertain part
On the surface, it is a simple tool. You enter information, generate a QR code, and use it wherever you need it. But for me, launching a project like this is never only about the feature set. It is also about the process of turning an idea into something real, useful, and public.
Distribution is often harder than development. Building the product is the part I understand best. Getting people to discover it is the part that always feels uncertain. Still, I would rather launch the thing and give it a chance than leave it unfinished because the odds are unclear.
This is a launch-day account, not a success story written after the fact. I cannot yet say whether SEO will bring meaningful traffic, how many people will find qrviz, or whether the project will become anything larger. I have a product that is live. The outcome is still unknown.
What I wanted to measure before calling SEO a success
The important part was deciding the measurement chain before the numbers arrived. A launch is not a distribution result. For this experiment, I wanted to separate search visibility, acquisition, and actual product use instead of celebrating whichever metric moved first.
- Indexing and visibility: can search engines discover the relevant pages, and do those pages begin earning impressions?
- Clicks: do those impressions turn into visits from queries that actually match the product?
- Landing quality: do organic visitors reach the right generator or guide instead of arriving on a mismatched page?
- Product use: do visitors actually create a QR code rather than only reading the landing page?
- Exports: do people reach the point where they download an asset they can actually use?
Those stages diagnose different problems. Impressions without clicks point somewhere different from clicks without product use. Defining the funnel first makes it harder to turn one encouraging number into a success story.
A project does not need a business model on day one
Not every project needs to become a business immediately to be worth making. Sometimes a tool is valuable because it solves a problem cleanly. Sometimes it is valuable because it teaches you something. And sometimes it is valuable simply because it keeps your creative engine running.
If qrviz ends up helping even a small number of people, I will consider that a good result. A free QR code generator does not need a huge story around it to justify its existence. Utility is enough. Honest usefulness is enough.
What I am taking from this launch
- Separate product value from distribution. A useful, finished tool and a tool that people actually discover are two different problems.
- Do not turn uncertainty into a result. On launch day I can say that qrviz is live and that I am relying on SEO; I cannot say that the SEO strategy has worked.
- A project can be worth publishing before it has a monetization model. That is a choice that fits this project, not a universal rule for every product.
- Define what a good outcome means before the numbers arrive. For qrviz, helping even a small number of people would already make the launch worthwhile to me.