Live data from Hacker News

How we built a $1M ARR SaaS startup

canny.io

41–50 of 125 posts

Re: How we built a $1M ARR SaaS startup

#42
Yet again, not a single person over 40+ (probably even 35) in that happy-go-lucky clique team photo. Happy for you all, sad for the ageism that is rife in our industry.

For all the talk about representation matters, and tech workers champion social issues, this just seems like a really frustrating and curious massive blind spot.

Anyway, again, not to detract from the success, but I just see examples of this weekly here.

Re: How we built a $1M ARR SaaS startup

#43
post #22
post #16

The key learning: Get your product used by the React.js team for hyper growth.

I sure hope that wasn't the key learning from our post! It's not a very repeatable/helpful learning :) Luck can definitely play a big role in building a successful company. I think what a lot of people don't realize is how you can increase your exposure to luck. For example, if you have a bigger/better network, you're more likely to get lucky from that. If you talk to more people about your company, you're more likel…

I didn't mean to imply luck... just that marketing is key and given two amazing products the one that reaches more eyeballs wins.

Re: How we built a $1M ARR SaaS startup

#45

Yet again, not a single person over 40+ (probably even 35) in that happy-go-lucky clique team photo. Happy for you all, sad for the ageism that is rife in our industry. For all the talk about representation matters, and tech workers champion social issues, this just seems like a really frustrating and curious massive blind spot. Anyway, again, not to detract from the success, but I just see examples of this weekly he…

Ageism? Generally speaking older people are:

- more risk averse, less likely to join a small startup and prefer the security of a 9 to 5 job at a larger company.

- more experienced, and more experienced people require higher salaries, which a smaller company might not be able to afford.

Don't look for opression when there's none.

Re: How we built a $1M ARR SaaS startup

#47

Cool read! Very inspiring. Just curious, what kind of metrics are you running for the sales part? Or some new strategies learned from hiring a sales position?

Hmm, we're still pretty new to sales.

Inbound: VIP trial sign-ups, demos booked, demos given, opportunities created, opportunities lost/won

Outbound: Emails sent, emails opened, reply rate, calls made, calls answered, conversions to trial/demo

We use SFDC for our CRM, and Apollo for outbound activities.

Re: How we built a $1M ARR SaaS startup

#48
post #31
post #18

Earlier quoted context omitted.

Uh, how do you “bootstrap” a team of 9 at $1m ARR? I thought bootstrapping means your revenues cover your costs.

$1m ARR is enough to support a team of 9. Especially when they're remote, some offshore, and 2 are founders.

maybe with a SW company where salaries are by far the biggest cost, but $1M revenue isn't $110K per person like a previous post suggests

Re: How we built a $1M ARR SaaS startup

#49

Yet again, not a single person over 40+ (probably even 35) in that happy-go-lucky clique team photo. Happy for you all, sad for the ageism that is rife in our industry. For all the talk about representation matters, and tech workers champion social issues, this just seems like a really frustrating and curious massive blind spot. Anyway, again, not to detract from the success, but I just see examples of this weekly he…

I'll bite. I'm 37, a tech startup founder. I'm wary of ageism and I've long believed that not being ageist would allow us to hire smarter than competitors.

However:

- The amount of programmers grows exponentially. I've seen stats claiming it doubles every 5 years.

- This means that at any time, 50% of the available workforce has - It also means there are simply way more programmers under 40 than over. If you randomly hire 9 programmers there's a fair chance they're all under 30.

- Anecdotally, less than 5% of the job applicants we got was over 40.

- Young programmers haven't had time yet to make the mistake to "repeat the same year of experience 10 years in a row". If you hire a young, junior programmer, you know they're junior - what you see is what you get. If you hire an older programmer they might be great or they might be that same junior programmer but more stubborn and with higher salary expectations.

As an avid anti-ageist, in fact I'm rather disappointed about that last point. I've met many programmers at around or above my age that have gotten completely stuck into a tiny niche of experience and, even there, seem to not really have progressed much in terms of depth. Why do people let this happen to themselves? I mean I met people who spent the last 10 years developing just-not-the-same custom Magento webshop plugin over and over again, each time with a slightly different twist for a different customer. Not hiring someone like that isn't ageist, it's common sense. Once Magento is out of fashion these people have a pretty serious problem.

The reason I don't understand this is because with each new technology you learn, there's a diminishing effort to learning the next because there's so many similarities to a thing you already known. There's a reason most people complaining about "javascript fatigue" are young.

As an example, when React/Flux/Redux first came to the scene, old farts like me could recognize that its "unidirectional data flow" wasn't fundamentally different from the good old desktop MVC UI pattern (before Rails hijacked the name and gave it a different meaning). I imagine that this made learning React and architecting decent apps on it easier for me than for people who'd never seen data "flow" in circles before.

Age definitely can be an advantage. But it isn't by definition. Keep learning new stuff folks! And if that ever stops being fun, you can always become a manager.

Re: How we built a $1M ARR SaaS startup

#50
post #10

Earlier quoted context omitted.

Thanks so much for being a customer! And yeah, it always feels bad to write that "we got lucky", as it isn't really that repeatable/helpful. But it's true.

What do you think you did that helped make that happen? I guess you guys worked hard but did you try a lot of things that didn't work before this hit?

The reason the React.js team started using Canny was because before Canny I worked on the React team at Facebook.

I didn't plan it this way. My ex-colleague, @vjeux, messaged me and asked about my new startup. I told him it was a user feedback tool, for tracking feature requests. He said React Native had that problem, and they just started using it.

So I think working at FB on React is what exposed me to getting lucky here. I think a lot of luck in startups is about increasing your exposure to getting lucky.

Post reply on HN