The engineering logs of an independent builder.

A collection of technical deep dives, architectural decisions, and the software tools I ship along the way as an independent builder.

Real engineering problems, practical solutions, and honest metrics from building B2B/B2C tools without venture funding or a team. No growth hacks. No fluff. Just code that ships and customers who pay.


What I'm Building

Focused tools that solve specific problems. No subscriptions that expire. No features you don't need. Just software that does one thing well and gets out of your way.

MockClip

Create realistic 60fps app mockup videos without a login.

Visit MockClip

MindLock

AI conversations, distilled into lasting memory.

Visit MindLock

PuzzlePad

Turn your touchpad into a macro pad.

Get PuzzlePad


Behind the Code

I'm Micael. I spent years as an embedded software engineer in the automotive industry, writing safety-critical code where bugs could cost lives. That environment taught me to think differently about software. Every line matters, edge cases are not optional, and shipping broken code is not an acceptable risk, just look at the endless vehicle recalls.

Now, I apply that same rigor to building my own B2B/B2C tools. Invisible Puzzle is where I document the architecture, the mistakes, and my perspective from shipping software on my own into the world.

This is not another "10x productivity hack" blog. These are engineering logs from the trenches. Here you will find what worked, what failed, and what I learned building products people actually pay for. Without venture funding. Without a team. Just code, customers, and honest metrics.

Each tool here started as a problem I faced or saw others struggling with. MockClip exists because creating demo videos was expensive and slow. MindLock exists because AI chat history is a mess and you cannot trust it. PuzzlePad exists because Stream Decks are €150 and AutoHotkey requires endless configuration.

The pattern is simple. I find a specific problem, build a focused solution, charge money, and iterate based on feedback. Some tools will succeed. Some will fail. But all of them teach me something about building products that solve real problems.

If you are building your own tools, shipping side projects, or just curious about the technical decisions behind indie software, you are in the right place. I share the architecture decisions, the performance optimizations, the failed experiments, and the micro-decisions that nobody talks about, the ones that make or break every product.


Stay in the Loop

Get notified when I ship new tools or publish deep dives.

Get notified on new posts

No spam. Unsubscribe anytime.