How PageFix came to be: from customer question to product

The question that would not stop

For months I have been getting the same question from my community, just in different disguises. It sounded most honest like this:

“Kirsten, how do I change my page now? I built one with Claude Code, and now I want to change something — but I don’t understand code. I can’t go into the actual code, that doesn’t help me. And every time I restart the chat or change something on the page, the chat automatically sends me new design along with it. Then things change that I never wanted changed.”

This question came so often that at some point I stopped treating it as an isolated case. Because behind it are three problems that have nothing to do with each other — and yet all occur at the same time:

• Code is not an interface. “Just go into the code” is, for most people, not advice but a dead end. If you cannot read code, you cannot fix a typo in it either.
• The new chat no longer knows your page. For one changed price you explain everything again from scratch — and burn tokens on the AI rethinking the entire page.
• The AI changes things unasked. That is the point that frustrates most: you wanted to swap one word — and get a new design delivered on the side. Things shift that were good before — and you often only notice once the page is already live.

On top of that, the fear at your neck: one wrong click, and the page that still worked yesterday is broken.

For a tool where you simply click, change and download the finished file — and where only what you clicked happens —, I would have loved to give my clients a name. There was none.

The decision: build it instead of explaining it for the hundredth time

So I built it. Not as a corporate project with agency, requirements document and six months of lead time — but in dialogue with the AI, alongside the day-to-day business.

The division of roles was clear from the start: I lead, the AI builds. Concept, decisions, quality control — mine. The code, the structure, the execution — Claude. That way a complete product came into being in a good week: the app itself, the payment system, the legal texts, the landing page. Even the demo video emerged in the same dialogue.

That is exactly what I have been preaching for two years: AI is not a toy for prompt collections. It is an execution partner — if you know what you want and keep the lead.

The plot twist: just before launch, the name bursts

And then, a few days before launch, the moment where everything would have tipped over in the old days: I discover a German provider with almost the same name I had intended for my product.

I know the old thinking from 25 years of entrepreneurial life: call the lawyer. Wait weeks. Stew in frustration. Postpone the launch.

The new thinking looked like this: one night. New name, new domain, all copy rewritten, the entire tech moved over, the old address cleanly redirected. In under 24 hours the old working title had become PageFix — and honestly, I like the new name better than the old one. Sometimes the incident is the upgrade.

Launch day: everything in one day — including a mishap

Today, on 15 July, everything a real product needs went live. In a single day: the payment system. The legal texts. The price tiers. A personal welcome video for every customer. The visitor statistics.

And because this is an honest report and not a glossy story: of course something also went wrong. The first email to the first customers went out with the wrong sender name. Saw it, cursed briefly, corrected it, moved on. That is what a real launch looks like — not polished, but on the market.

The moment

In the afternoon I posted a single Instagram story. Reach: around 40 views. Plus a short note in my AI Business Community. There was no more marketing at that point — the official launch post was not even out yet.

Then the phone buzzed. The first real payment. From a simple story with 40 views.

I am not saying this to show off. I am saying it because it confirms the most important insight of the whole project: If the problem is real, the launch needs no fireworks. My clients had been shouting the problem at me for months. I merely listened — and delivered.

What this means for you

I was born in 1972. I am not a developer. A few years ago this product would have needed a team, a budget and half a year — or it would simply never have come into being.

The tools that make something like this possible in a week today are available to you just as they are to me. What most people lack is not the technology. It is someone who shows how to lead the AI: what you decide yourself, what you hand over, and how you recognize whether the result is good. That is exactly the difference between collecting AI and putting AI to work.

If you are thinking right now “I could never do something like that” — a week ago I thought the same about my own payment system.

Something like this rarely emerges on a drawing board. Mostly it emerges because someone has done a task by hand for the third time. That is exactly what we talk about in my free community “KI — aber richtig” — the templates and workflows from my videos live there too. And if you want company instead of doing it alone: the AI Business Community offers monthly live calls, workshops and the MACHZEIT! challenge for exactly that.

Frequently asked questions

What is PageFix?

A browser editor for AI-built HTML pages: you drag your file in, click what you want to change — texts, colors, images, links — and download the finished page again. No code, no new AI chat, no burned tokens.

Why does the AI change things I never wanted changed when editing?

Because a language model does not correct your page point by point; as a rule it regenerates it. It reads what context it has and writes the file out again as a whole — including the parts you never talked about. That is why a requested word change often comes with an unasked-for new design, and sections shift that were good before. An editor that touches individual elements deliberately does not have this problem: there, only what you clicked changes.

How long does it take to build your own product with AI?

From the first version to launch: a good week, alongside the day-to-day business. The rebranding just before launch: under 24 hours. Both in dialogue with the AI — led by me, built by Claude.

Can I build something like this without technical background?

More likely than you think. The tools are made for users, not developers. What you need is a clear problem, the willingness to decide — and someone who shows you how to lead the AI. That is exactly what I help with: in the newsletter and in my community.