Hackernoon logoIgnore the Internet (and 3 More Lessons Learned Between $10 and $1,100) by@jgreet

Ignore the Internet (and 3 More Lessons Learned Between $10 and $1,100)

Justin Greet Hacker Noon profile picture

@jgreetJustin Greet

Co-founder @ BeamJobs

In July, my brother and I launched our first software product after nearly 2 years of working full-time on our business. We hit a big milestone that month and generated our first $10 in software revenue.

Here are our revenue totals for each month since we launched:

  • July: $60
  • August: $190
  • September: $540
  • October: $1,100

Our product helps people quickly create great resumes. In the last four months we've helped people create or update over 5,000 resumes!

This means we've gotten a lot of user feedback.

One of the biggest challenges these last four months has been prioritization. Our resources are very limited since the "team" is just my brother and I.

This is our first time experiencing any sort of traction and we've made a ton of mistakes the last four months.

The way I like to reflect is through the lens of my mistakes (that's totally normal, well-adjusted behavior. Right?) so every few months I'll share company progress and talk about the biggest mistakes we made over that time frame.

If you want to get alerted whenever these reflections are posted, just leave your email below (these are the only emails you'll get from us).

Lesson 1: SEO is a slog for a while

Back in April when we decided we were going to focus on this resume product we knew (or really, hoped) that our primary acquisition channel would be content.

The thing is neither my brother nor I have ever really written content before at a large scale. Neither of us knew anything about SEO.

So at that time I read way too much about getting started with SEO. If you're anything like me, when you start something new you read way too much before actually doing anything.

If you're doing that right now, reading this article, then stop reading this and get to work!

Through all my reading I knew that it would take a while (3-6+ months) between publishing content and getting search impressions through Google, especially in the beginning.

So for about 3 months I was heads down pumping out resume content with very little to show for it. You can see all the content I created on ourย resume examplesย page.

This was an absolute slog. I was writing a lot of long, detailed blog posts with nothing to show for it.

Still, since my expectation was that I'd have nothing to show for it right away I didn't have much trouble motivating. The only "metric" I cared about was whether I produced the amount of quality content that I set out to produce in a given week.

Then, in July, we started to see the fruits of my labor. We were starting to get ~50 clicks per day from Google.

That continued to grow over the last four months and now we get about 500 clicks per day.

There is a lag between writing content and getting traffic via SEO. But if you double down on this acquisition channel, and it pays off, the return can be exponential.

Lesson 2: QA your primary (read: only) acquisition channel

Just as we were starting to see some return from our efforts in SEO, we hit a snag.

Our search impressions and clicks jumped off a click in mid-July. We went from getting ~5,000 search impressions a day (and growing) to plummeting under 1,000.

This made no sense. It was a precipitous drop that happened overnight.

I don't know why no-one tells this but when you make changes to your website in production, things can break. Who knew?!

What happened?

If you're using a single page application, then not all of the content you want a web crawler (like Google) to see will be available on page load. Since page speed is important in SEO, this can potentially impact your search rankings.

To solve this you can use a pre-rendering service. These services preload all elements on the page in preparation for a web crawler to see it.

This was working for us without issue for a few months.

Then, in July we changed the structure of our blog posts to make them better for the user.

We pushed these changes to production and in a few days our search impressions plummeted.

What we didn't realize was that when we made the change to our blog we also messed with our pre-rendering. Now, instead of reading all of the content on a page web crawlers were only able to see each page's meta title and meta description.


I should have caught this. I could have checked in Google Search Console to see how web crawlers were seeing our pages and I would have immediately identified this problem.

Instead, we went through a week of total panic as our performance tanked.

So, the lesson here is simple. Don't be an idiot. If you make changes that may effect the ONLY channel through which you acquire customers, ensure those changes don't break that channel.

Lesson 3: Don't give weight to random internet comments

The article I linked to on the top of this page did really well on HackerNews and generated over 10,000 visitors to our website.

I very quickly learned that I don't have a thick skin when it comes to random internet comments.

The comments in the HackerNews thread weren't even mean! There were a ton of supportive comments even. We also got really thoughtful feedback from people who I had follow up conversations with.

The critical comments were mostly centered around why it took us so long to build a seemingly basic resume builder and we were likely wasting our time.

These people didn't have the same view of the competitive landscape as I did nor did they know our product vision yet I REALLY let these critical comments get to me.

Our traffic was growing through SEO, we finally had our first taste of success with a software product, and I was in the dumps.

Then, more customers starting trickling in from SEO. I had conversations with customers about the pain points we were solving.

This helped we shake off how I was feeling from, and again let me emphasize this, random internet comments.ย 

In hindsight (and even in the moment I knew), it was completely ridiculous to let these comments get to me. Still, some things are easier said than done.

Interestingly, my brother didn't give two craps about the feedback. I hope next time I can adapt that mindset.

Lesson 4: A smaller range of emotions leads to more productivity

For the first two years of our business when we were pivoting from one thing to the next I regularly felt a sense of existential dread.

I felt like I was wasting my time and my money and had absolutely nothing to show for it.

On the other side of the coin the elation I felt from getting out first paying customer for our resume builder was a high I've never experienced.

The last four months, my range of emotions has narrowed significantly.

If the scale of emotions goes from existential dread (1) to first paying customer (10), I now rarely get outside of the 4-6 range.

This has drastically helped my productivity.

When you're too low, it's hard to motivate. When you're too high, it's easy to rest on your laurels.

The last four months has felt much more like a job than at anytime in the last 2.5 years.

The big difference? I decide what to work on, and of course: I own the upside of what I'm working on.

For me, it's vitally important to my productivity that I maintain a tight range of emotions.ย 

What's next?

Since our last update we've launched some really cool new product features. Mainly, we've built an automated resume grader that gives you actionable feedback on your resume and we've added the ability for your to upload your existing resume.

We're going to continue to talk to customers and uncover other pain points we can help alleviate. I'll also continue to write more and more resume content.

If you want to get an email every 3-4 months when I publish a new company update, reach out!


Join Hacker Noon

Create your free account to unlock your custom reading experience.