GTM Sauce

Visualizee · B2B · AI rendering for architects

Swap a complex editor for a chat assistant that writes the prompt for users

Revenue ~$150/month -> ~$10K/month in 6 months; pricing changed too

Workedproduct-activationonboarding

What they did

V1 was a node-based editor like ComfyUI (upload image -> node, connect nodes, write prompt, many parameters). After users said it was too hard, rebuilt as a ChatGPT-style chat: user uploads sketch/model and types a plain request; an AI assistant ('Vizzy') asks follow-up questions, presents a plan with selectable options (materials, lighting e.g. 'raw concrete', 'blue hour'), builds the prompt, and sends it to image-generation services. Also produces videos.

What happened

Revenue went from ~$150/month to ~$10K/month (8.2K MRR) within ~6 months; before, only a couple of sign-ups, after, users started rendering
Stage
2 years post-launch, stuck at ~$100-150/month

This shipped together with other changes, so the result can't be credited to this alone.

In their words

I was stuck at $100 for 2 years until I made one change. Now my app makes $10K/month

Play from 4:10
4:04

Pat WallsNice. Tell me about the build process. How long did it take you to build this, to get this to launch? Tell me about that build timeline.

4:10

Piotr ObidowskiThe first version took approximately 5 months after hours, obviously, and V1, like we- you probably know, it was node-based system similar to ComfyUI. I had a direct feedback from people, "Okay, it's too hard to understand for us." So I decided to pivot and to simplify the product to chat-based solution with the a- prompt assistant because I know that people have troubles with prompt engineering, so I decided to create a layer of the AI that will help people first understand what they want, ask follow-up questions, and then build the perfect prompt for them. That helped me go from $150 per month to nearly $10,000 per month.

4:50

Pat WallsWhat I think is so cool about Piotr's story is that actually simplifying his product down to essentially a ChatGPT wrapper is what actually created the growth. A lot of developers watching this are wondering, okay, how can I add more features to my product? How can I make it more technical and more complicated? When this story right here is an example of when keeping it simple actually creates growth. So if this idea is interesting to you, well, …

7:25

Pat WallsThat's amazing. What did things start to look like once he made this change and how you knew things were actually working?

7:30

Piotr ObidowskiI looked at the data, right? The data always say the truth. Before, I had like only couple of sign ups, but after this change, people started rendering. So, it made very easy for them. With that pivot, I also decided to test one thing. One-time payments are not bringing repeated revenue. So, we need to change to monthly recurring payments and that worked.

7:52

Pat WallsThat's awesome. Looking back on this multi-year experience and finally figuring out the unlock, what would be your like big lessons and takeaways next time you go and build a product, or if you're going to give advice to another founder, what are your big lessons here?

8:05

Piotr ObidowskiYeah, sure. So, friction in your product is killing your conversion. For 2 years, I blamed slow growth on marketing when the real problem was that my product was too hard to use. The fix was removing the thing standing between a visitor and there's first success. And the second lesson is charge subscriptions from day one. Subscriptions are the thing that drive the growth. You need to start charging from day one and don't be afraid that someone will not pay. If the product is valuable, then they will pay.

8:35

Pat WallsAbsolutely. What kept you going with this idea specifically? How did you know that it might work out 2 years later?

Get tactics like this every Monday

New tactics from the week's founder interviews, each linked to where it was said.

More from this episode

Tags: ux-simplification, chat-interface, prompt-assistant, ai-wrapper