For four years, I worked as a consultant helping B2B SaaS companies with their email marketing. I had clients, stability, and a decent income.

    But I was solving the same problems again and again, manually.
    At some point, I realized that if I wanted to scale what I was doing, I'd have to build a tool that could do it better, even if that meant replacing myself.

    So I decided to go all in.
    I'm not technical, so I hired engineers to help me build it.
    Since June, I've spent around €35,000 (my own savings) on development. I've got about €25,000 left, and I'm still not sure if it will work. There are no paid users yet, just some early testers.

    Still, I'm convinced this is the right path. I've spent years deep in this problem, and I know the pain points better than anyone. If founder-market fit exists, this is it for me.

    In two weeks, I'm launching publicly on LinkedIn and in a few communities. After that, I'll start raising a pre-seed round.

    If it works, amazing.
    If it doesn't, I'll be out of savings and back to square one, but at least I'll know I tried.

    Curious how others here handled this phase:
    Would you ever bet your savings on your startup before validation?

    The risk I took when I left consulting to build my own SaaS
    byu/jonathanbrnd inEntrepreneur



    Posted by jonathanbrnd

    4 Comments

    1. Hiring agencies to develop your tool is one of the worst things you could do.

      1) The code will be sloppy and a mess, no future engineer will want to take it over

      2) You will need to make more updates than what was originally scoped out, and that will cost more money. A product is never launched bug-free

      The best route to go is either: higher a technical founder, hire actual employees, or code it yourself. Speaking from experience.

    2. Good luck and fingers crossed it all works out! If it doesn’t then at least there’ll be no regrets on not trying at all

    Leave A Reply
    Share via