2
8 Comments

I Spent ~$500 Promoting an AI SaaS. It Got 30 Signups and 0 Sales.

Hey IH,

I’m a solo developer building ImagineMyHouse, an AI home design product that lets users redesign rooms, visualize floor plans, remove furniture, stage empty spaces, and experiment with different interior styles.

The product is still very early, but I wanted to share the numbers because the gap between “people used it” and “people paid for it” has been more interesting than the building process itself.

So far, I have spent roughly $500 submitting the product to several paid AI directories and launch platforms.

The approximate results:

  • 100–200 visitors
  • Around 30 registered users
  • A little over 20 users tried the generation tools
  • 0 paying customers

The sample size is still small, so I’m not treating this as a final verdict on the product.

But it is enough to show that several of my original assumptions were wrong.

Usage Is Not the Same as Purchase Intent

Every registered user currently receives three free generations.

One of the most interesting sessions came from a user working with a black-and-white floor plan.

They:

  1. Generated a colored version.
  2. Tried a second variation.
  3. Edited a specific area in a third generation.
  4. Downloaded all three results.
  5. Opened the payment modal more than once.
  6. Left without purchasing.

From a product perspective, this looked like a successful session.

The user understood the tool, completed the workflow, found the results useful enough to download, and reached the paywall.

From a business perspective, it produced nothing.

That session forced me to separate three signals I had previously grouped together:

  • The user can operate the product.
  • The user gets value from the output.
  • The problem is important enough for the user to pay.

The first two may be true without the third.

It is also possible that three free generations were enough to complete the user’s entire one-time task.

Directory Traffic May Not Be Customer Traffic

Most of the first visitors came from AI product directories.

They successfully produced visits and registrations, but I’m increasingly unsure whether that audience matches the people most likely to pay.

A directory visitor may be:

  • Another founder researching competitors
  • Someone casually testing new AI products
  • An AI enthusiast trying every new tool
  • A person with one image and no recurring need

That traffic is not useless. It helped expose bugs, test onboarding, and produce the first real usage sessions.

But I probably made the mistake of treating “AI tool traffic” as equivalent to “home design buyer traffic.”

They are not necessarily the same audience.

Someone remodeling a kitchen, staging a property listing, or producing client presentations has a very different motivation from someone browsing an AI directory.

“AI Home Design” May Be Too Broad

I originally thought of the product as one broad category: AI home design.

Actual usage has been much more specific.

People do not arrive thinking:

I need an AI home design platform.

They arrive with a job:

  • Colorize this floor plan
  • Remove the current furniture
  • Turn this space into a bathroom
  • Preview a kitchen renovation
  • Stage an empty listing
  • Change the lighting without changing the room
  • See how one area looks in a different style

These jobs may share the same underlying image-generation infrastructure, but they have different purchase intent and different definitions of success.

This has changed how I think about the product.

Instead of asking, “How do I market an AI home design platform?”, I am now asking:

Which specific workflow has enough urgency and repeat usage to become a paid product?

More Features Are Not Automatically the Answer

As a developer, my default response to weak conversion is to build more:

  • More room types
  • More styles
  • More editing tools
  • More landing pages
  • More models
  • More languages

That feels productive because I can control it.

But adding another feature does not explain why someone downloaded three outputs and still did not pay.

At this point, I think the higher-value work is understanding the gap between download and purchase.

What I’m Testing Next

My next experiments are less about model quality and more about the funnel:

  1. Track conversion separately for each workflow and traffic source.
  2. Identify which tools lead to downloads, repeated generations, and payment-modal opens.
  3. Test whether a small one-time package fits occasional homeowners better than a subscription.
  4. Focus positioning on specific jobs rather than the broad “AI home design” category.
  5. Localize only workflows that show real demand instead of translating the entire site at once.
  6. Continue improving results, but stop assuming better image quality alone will solve monetization.

The question I’m struggling with is what to test first.

Would you:

  • Reduce the free allowance from three generations?
  • Keep the free allowance but introduce a very small one-time purchase?
  • Stop optimizing the paywall and first acquire a much larger user sample?
  • Narrow the product toward a repeat-use audience such as real estate agents or interior designers?

I’d especially appreciate feedback from people who have built credit-based AI products.

At what point did usage turn into reliable willingness to pay?

P.S. The product is ImagineMyHouse. Brutal feedback on the pricing and free-to-paid funnel is more useful to me than compliments on the UI.

on September 2, 2026
  1. 1

    That floor-plan session is the whole post in miniature, someone who fully completed the job and still walked away from a paid wall twice. That points more toward "three free generations covered my one task" than a pricing problem, which makes the one-time-purchase test seem like the right one to run before touching the paywall itself.
    Have you tried reaching out to any of the users who opened the payment modal and bailed, even a couple of DMs, to hear their actual reasoning?
    (Building gnxsales.com, an AI sales agent for early SaaS founders, happy to compare notes.)

  2. 2

    I’d avoid changing the 3 free generations first.

    Your strongest session may actually be telling you something more important than “the paywall failed”: that user completed their entire job before they needed to buy.

    They generated three versions, edited the area they cared about, downloaded everything, opened the payment modal, and left. If that was a one-off floor-plan task, reducing the free allowance could increase payment - or it could simply reduce completed jobs. You wouldn’t know which.

    I noticed your current pricing page already exposes both one-time and subscription options, so I’d use that to separate two very different businesses rather than change another variable immediately:

    one-off homeowner/project → one-time credits
    recurring agent/designer workflow → subscription

    For the next users, tag the exact job and track:

    first useful output → download → payment-modal open → second real project → purchase.

    I would also stop treating directory traffic as one acquisition cohort. It has already been useful for product validation, but it may be a poor sample for willingness to pay.

    The two numbers I’d want before changing the free allowance: of the 20+ people who generated something, how many came back with a second real project, and which workflows produced the payment-modal opens?

    1. 1

      This is probably the most useful interpretation of that session.

      I was framing it as “the paywall failed,” but you’re right: the user may simply have completed their entire job before the paywall became relevant. Reducing the free allowance now would mix too many variables, and I still wouldn’t know whether conversion improved or fewer users simply reached a useful result.

      I don’t currently have a reliable count for “second real projects.” I mostly track generations, downloads, and payment-modal opens, so retries and genuinely new jobs are currently mixed together. I’m going to add tracking for new source images, return sessions, workflow type, and acquisition source.

      The clearest payment-modal session I have seen so far was floor-plan related, but the sample is still very small.

      I also agree that the one-time vs. subscription split needs to be clearer in the positioning, not just available on the pricing page:

      • homeowner with a one-off project → small one-time credit pack
      • agent or designer with recurring work → subscription

      I’ll leave the three free generations unchanged until I have better data on repeat projects and modal opens by workflow. Thanks — this gives me a much cleaner next experiment.

  3. 1

    The biggest signal is the gap between downloads and payment.

    Which workflow gets the most repeat usage so far?

    1. 1

      So far, the clearest repeat behavior has been around the floor-plan editing and visualization workflows, but the sample is still too small to call it a real winner.

      I also realized that my current tracking does not clearly distinguish between “trying another variation of the same job” and “coming back with a second real project.” Those are probably very different signals.

      I’m adding workflow-level tracking for downloads, payment-modal opens, new source images, and returning sessions. That should help me understand whether the gap is caused by pricing, weak recurring demand, or users simply completing a one-off task within the free allowance.

      1. 1

        That distinction between repeat variations and a genuinely new project is the key signal. I’d be interested in digging into what the workflow data shows as it comes in. Happy to continue privately — what’s the best email to reach you on?

  4. 1

    I would split directory traffic into two buckets: validation traffic and acquisition traffic. For a one-off visual job, three free generations can prove the workflow and also finish the user's whole task, so the paywall is arriving after the urgent moment. I would measure repeat jobs by segment next, not just tool-wide signup-to-paid conversion.

    1. 1

      That distinction between validation traffic and acquisition traffic is very useful.

      I think I was treating directory traffic as customer acquisition traffic, while most of it has actually behaved more like product-validation traffic. It helped me test onboarding, generation quality, and whether people could complete the workflows, but it may be a poor sample for willingness to pay.

      I’m going to segment users by acquisition source, workflow, and whether they return with a genuinely new project. For one-off users, three free generations may be enough to complete the entire task, while recurring agents or designers should show a very different usage pattern.

      I’ll keep the free allowance unchanged until I can separate those two groups more clearly.