1
15 Comments

The stupid simple validation trick that saved me 6 months of building the wrong product

I almost wasted $15,000 and 6 months building something nobody wanted.

Then I discovered this validation method that costs $0 and takes 2 days.

So what happened next:

My mistake: I was building a complex project management tool for agencies. Spent 3 months coding features I thought they needed.

The wake-up call: Talked to 5 agency owners. None of them wanted what I was building.

The simple trick: I started selling before building.

Here's my exact process:

  • Created a landing page describing the product (2 hours)
  • Posted in 10 Facebook groups where my target audience hangs out

Asked: "Would you pay $49/month for this?"

Collected emails from interested people

Results in 48 hours:

  • 3 genuine "yes, I'd buy this" responses
  • 37 email signups
  • 12 detailed conversations about what they actually need

The plot twist: They wanted something completely different. A simple client portal, not complex project management.

What I learned:
Your assumptions about what people want are usually wrong. Test demand before you build anything.

My new rule: Get 50 people to say "I'll pay for this" before writing a single line of code.

What I am doing now:
Building the client portal ( https://www.teamcamp.app/product/client-portal ) they actually asked for.

What is one feature you're building that you haven't validated yet?

on September 4, 2025
  1. 2

    “sell it before you build it” is one off the most basic way to test your market, but you get golden feedback, and your ego learn to accept "I don't care" or "not interested".

    1. 1

      Absolutely. Pre-selling is like holding up a mirror. you see instantly if people actually care. The “I don’t care” response may bruise the ego, but it’s way better than wasting six months building something no one wants.

      When I was working on Teamcamp (an all-in-one project management app), we followed the same approach. Instead of coding endless features, we first validated whether agencies and teams would pay for a simpler way to manage projects without juggling 7–8 different tools.

      The early “not interested” replies actually shaped the product into something people rely on today.

      Curious when you test your market this way, do you just validate demand, or do you also try to capture upfront payments to really prove intent?

      1. 1

        I'll be direct if someone tells me "I'm interested, sounds good..." but nothing more, I immediately ask "what prevents you to buy now". There again it is a simple way to understand the remaining blockers to perfect the pitch or maybe the timing is not good for the customer. As an entrepreneur I recommend to ask for proven intents, it is free to ask :), it can be translated into: "Always seek the shortest path to get the cash" and this is one.

        1. 1

          That’s a solid approach. Cutting straight to the blocker saves time and gives you clarity fast. Asking directly not only sharpens your pitch but also filters out tire-kickers, definitely aligns with the “shortest path to cash” mindset.

  2. 2

    Great post, Pratham. That “sell it before you build it” idea—it stings a little, but in the best way.

    To your question: the feature I keep circling (and honestly haven’t validated at all) is something I call an “automated evidence pack.” My project deals with impersonation accounts hitting creators and brands, and my hunch is the real pain isn’t finding them—it’s the slog afterward. Endless screenshots, copying links, dumping files into a folder just to file one takedown. Feels like doing taxes. The feature would turn that into a single click.

    But maybe I’m completely off. Maybe the deeper pain is somewhere else I haven’t looked yet. Your story reminds me to pause before I disappear into building mode.

    Also—loved that you leaned on Facebook groups. How’d you pick the ten? Every group I peek into is either tumbleweeds or spammy chaos. Separating signal from noise is half the battle. Any trick you used would be helpful.

    1. 1

      That “automated evidence pack” idea actually sounds sharp. You’re right, detection is only half the battle, the real grind is in the repetitive admin work that follows. If you can turn that “doing taxes” feeling into a one-click workflow, you probably be solving for real emotional pain, not just technical friction.

      On the Facebook groups side: I wish I could say there was a secret trick, but it was mostly trial and error. I looked for
      (1) groups where people were actively posting questions daily,
      (2) engagement in comments rather than just likes, and
      (3) admins who were present and curating.

      Most groups failed on one of those three, which is why I only stuck with about ten. The rest really were the tumbleweed/spam mix you mentioned.

      Curious about it have you tested your idea with creators yet, even just by walking them through the “before and after” of what that one-click pack might look like? Sometimes even a rough storyboard lands harder than a finished feature.

      1. 1

        Pratham—thanks for the detailed reply, really helps.

        Hearing that the “automated evidence pack” idea actually resonates—it’s a bit of a relief, honestly. I wasn’t sure if the pain I’m seeing is real or just me overthinking. Knowing you see the emotional drag it solves—that’s exactly the kind of check I needed.

        And your framework for qualifying Facebook groups? Super practical. I’ve wandered into plenty of dead or chaotic ones, so having a filter like that makes sense.

        As for the storyboard—haven’t done it yet. Been sticking to these first community convos, trying to make sure the problem is real before drafting anything. But yeah, even a rough, messy storyboard sounds like the right next step. That’s the nudge I needed—thanks again.

        1. 1

          Glad it clicked for you! Validating the pain before investing time in solutions is exactly the right move. Even a rough storyboard will help you test assumptions faster and spark more useful feedback. You’re on the right track keep the momentum going.

  3. 1

    This is gold. So many founders fall into the trap of building in isolation and only later realizing nobody asked for it. Your approach of selling before building is one of the most practical validation hacks out there — fast, cheap, and brutally honest.

    I love how you pivoted from “complex project management” to the much simpler client portal your audience actually wanted. It’s a perfect reminder that value comes from solving their problem, not the one we imagine.

    It’s kind of like working with a qurantajweedteacher.com: you might think your recitation is already perfect, but only through feedback and correction do you discover what really needs adjusting. Same with products — real users shape the truth.

    1. 1

      That’s a really thoughtful take. Selling before building really does cut through assumptions and puts you in front of reality fast. I like your analogy with the teacher, it nails the idea that outside feedback is what keeps us from getting stuck in our own bubble.

  4. 1

    Love this approach. I have been stuck at building phase before launching. Tracking interest and talk to real users helped me from wasting time and frustration. How did you pick 10 fb group to post in?

    1. 1

      I explore your profile you are notion creator thats great we have some offer for you in Teamcamp. our product is perfect fit for notion creators so if you want to explore it this is my product link: https://www.teamcamp.app/

    2. 1

      I do some research to find Facebook groups i which my ICP is present and also i use perplexity , create connections throw discord and slack than i talk with multiple peoples to find this accurate groups

      1. 1

        It makes sense. Finding right group is key. I have found small niche community give most honest feedback.

        1. 1

          Yes as a Market who work on digital platform to understand where our target audience is present is very important