# 1 month - 3 products launched > Three products in one month, built around a full-time job and family life. My story, the launches, the first feedback, and why I want to build in public. Canonical: https://palasselabs.com/writing/1-month-3-products-launched Published: 2026-10-22 | Updated: 2026-10-22 Tags: Building in Public, Indie Maker, SaaS, AI Coding, VisuMerge, Hexacryon ## Where it all started In 2013, I read [an article by Pieter Levels](https://levels.io/i-love-minimalist-living). I started following him and got inspired by the way he tried things, built products and shared what he learned. I discovered the digital nomad world. I enjoyed reading stories about people who build their own projects, take risks and learn in public. It made me want to try more things too. At that time, I was creating my own startup in the 3D printing sector with a few friends. We wanted to let people create 3D objects and print them with our tool. It was incredible. We learned a lot, and of course we failed to reach our target. I think it was too early for many European customers. After that experience, I worked as a lead developer and CTO for different startups in health, retail and digital products. I continued to learn how to build, ship and scale products with some incredible teams. But building a product for a company and launching your own small product are two different challenges. ## The projects I never shipped For a few years, I have been creating little products in my free time. The problem was almost always the same: I built something, pushed it to GitHub, and moved to the next idea. Going to market wasn't so easy for me. Before Twitter was acquired by Elon Musk, I launched a little tool to find your bookmarked tweets more easily. I got a few users, which was already a great feeling. Then the Twitter API rules and pricing changed. I didn't agree with the new model, especially the lack of a free quota, so I switched my product off to protest! I also created other tools: a pool cleaner task manager, an email unsubscribe tool and a few video games. Sometimes the product worked. Sometimes I lost interest. But too often, the result was the same: another project staying in my GitHub account. I had experience as a developer, CTO and startup founder, but this time things are different. I don't have a team. I have a full-time job and an awesome child to take care of. So I build my own products during the evening and sometimes late at night. I needed a simple rule to stop collecting projects and start launching them. ## One month, three products shipped Here is my new rule: **build, ship, learn and repeat.** At least one little product must be launched every month. Not necessarily perfect. But something real that people can try. This first month, I launched three. ### [VisuMerge](https://visumerge.app) — Stop translating client feedback I'm also a freelancer, and I build projects for clients. Usually the process is clear: we define user stories, validate the design, develop the product, meet during the sprints and finally release it. But guess what? A few days after release, I often receive a WhatsApp message, an email or a screenshot asking for changes. Sometimes the explanation isn't clear. Sometimes the client wants to change a design they already validated. And someone has to translate all of this into developer tasks. So I created VisuMerge. My clients can propose changes directly on the website, and I receive a structured review. I can approve or refuse each change before updating the code. Recently I also added the possibility to move content blocks and export a changelog that an AI coding agent or developer can use. It's a small tool, but it solves a problem I know very well. It changed the way I handle feedback, so I decided to open it to other people. ### [Bannerly](https://bannerly.me) — Banners that can update themselves I'm not a designer. I wanted an easy way to create a banner for my social profiles and keep it updated using information from other tools and accounts. So I built Bannerly. You can create your own banner, edit it and use connected data to update it automatically. I also added an MCP integration so people can use Bannerly from AI tools like ChatGPT or Claude. I love that idea: my product shouldn't only work through its own website. It should also be available inside the tools people already use. And I got my first paying customer! Only one for now, but I'm happy. Someone found my tool useful enough to pay for it. That means a lot to me. ### [Hexacryon](https://hexacryon.com) — My little game experiment I'm a gamer. I love strategy and management games like StarCraft, Prison Architect and Diablo. But now I have less time to play, and I wanted a game with some challenge that I could enjoy with friends. So [Hexacryon](https://hexacryon.com) was born: a multiplayer browser game mixing survival and tower defense in a cyber universe. I opened the first public testing session recently. During the first night, 10 games were launched. It's a small number, but for a first test of my own game, it was exciting! I added logs to understand what players do, where they get confused and which mistakes they make. For me the important question isn't only *how do players defend the base?* It's also *do they understand what they need to defend?* The game is still an experiment. If you try it, please send me feedback on [X](https://x.com/anthonypalasse). ### A different way of building These last weeks, I have also changed my workflow. I use AI coding agents, including Claude Code, to help me develop, test and iterate faster. But AI doesn't decide which problem is worth solving, or whether someone will use the product. I still need to make those decisions, talk to users and ship. I'm also turning an old computer into a small home server for automations and GitHub runners. The goal is to test whether running some of my workflows at home makes sense. I'm measuring the electricity cost before deciding if it's really worth it. I prefer to make that decision with data. One thing I learned: finishing the code is not the end. It's the beginning of distribution, feedback and learning. ## Building in public: the good and the bad I decided to be more transparent about what I build and what happens after launch. I'm experimenting with sharing revenue and product progress on [Indiepa.ge](https://indiepa.ge/snap). No bullshit! I'm not going to pretend that three launches mean three successful businesses. One paying customer is one paying customer. Ten game sessions are ten game sessions. These are small beginnings, but at least they're real. I also started working on **Palasse Labs**, a place to show my products, write about what I learn and share ideas before they become products. I want to keep the useful numbers public when they make sense, without turning everything into a marketing story. And I want to share the less exciting parts too: features that nobody uses, distribution that doesn't work, bugs, experiments and decisions made with real data. My goal isn't only to earn money, even if I hope these little products can generate some revenue one day. I want to keep building useful things, meet other makers and learn along the way. Next month, I'll try to take better notes about what I build, what I ship, what people say and what I would do differently. Then I'll write the next article. If you're also building after work, during the evenings or whenever you find some free time, I'd love to hear what you're working on. See you soon!!!