Our fundraising learning post-YC

They had 250+ meetings over ~3 months to raise only $1.5M? Wow. That&#x27;s a lot of time that could have been spent building a product. Is this what YC money is supposed to be for? You get a few months of runway that you need to turn into a higher raise to have a longer runway on someone else&#x27;s dime?<p>Are there any hacker&#x2F;entrepreneur communities that focus on revenue-funded efforts instead of the self-perpetuating financing cycles?

@matijash what was the content of the follow up email you sent, was it updates on WASP, more data on traction, fundraising, ect? What did you say to prompt people to act? And did you ever pre-empt by just sending a SAFE (assuming the round is not priced) on a follow up email?

I&#x27;m surprised to see the founder describing their company as Deep-Tech, and I wonder if that description hindered their ability to raise. Not saying it isn&#x27;t a technical product, but as per Wikipedia, deep tech is &quot;based on substantial scientific or engineering challenges&quot;.

Good on you guys for being so transparent about your fundraise process! Amazing persistence, glad it worked out

really great article, so rare to not simply say what everyone knows but in your own voice.<p>What I got out of it (which is known) is that founder+CEO is like politician. Most of your job is fundraising.

Can the op comment on this: &quot;We compared ourselves to big, successful companies&quot;. How did you phrase it?

@matijash congrats on successfully raising. Your blog post is super useful. I am a founder and at an early stage now. I am trying to raise and facing the similar situation. I would like to learn more from you. I sent contact invite to you on LinkedIn. I hope you do not mind connecting.

I am getting a 404 when I visit <a href="https:&#x2F;&#x2F;wasp-lang.github.io&#x2F;blog&#x2F;2021&#x2F;11&#x2F;22&#x2F;fundraising-learnings" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.github.io&#x2F;blog&#x2F;2021&#x2F;11&#x2F;22&#x2F;fundraising-lear...</a>. Could you double check the permissions&#x2F;link to make sure everything looks correct?