paint-brush
Startup 3: Week 1 — Getting scrappy(er)by@elijahmurray
256 reads

Startup 3: Week 1 — Getting scrappy(er)

by Elijah MurrayApril 13th, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

<em>4 Weeks to </em><a href="https://hackernoon.com/tagged/launch" target="_blank"><em>Launch</em></a><em> is an ongoing series about building passive income across multiple startups — a new </em><a href="https://hackernoon.com/tagged/startup" target="_blank"><em>startup</em></a><em> every 4 weeks. Read the</em><a href="http://4weekstolaunch.com/4-weeks-to-launchlaunch/" target="_blank"><em> first post on 4 Weeks to Launch</em></a><em> to get started, or </em><a href="http://4weekstolaunch.com/newsletter/" target="_blank"><em>subscribe for weekly updates</em></a><em>.</em>

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Startup 3: Week 1 — Getting scrappy(er)
Elijah Murray HackerNoon profile picture

less writing, more doing…

4 Weeks to Launch so far

4 Weeks to Launch is an ongoing series about building passive income across multiple startups — a new startup every 4 weeks. Read the first post on 4 Weeks to Launch to get started, or subscribe for weekly updates.

And we’re back again. It’s been a few weeks since I’ve written and there are lots of updates. Let’s start!

4 Weeks to Launch has been extremely rewarding and a big pain in the ass. I love building businesses, but the amount of time I was putting into my blog posts wasn’t fun. It took ~ 5–10 hours a week, and that’s when I actually did something. Procrastinating always takes longer. All that proofing, editing, and curation. And all I want to do is build projects!

In my few weeks silence I’ve been chugging away at multiple side projects, but just haven’t been writing. That means something’s broken. On top of that what I did write didn’t feel actionable. Sure, I see how it all connects on because I’m the one doing it but it’s not helpful unless I can put it into words (or video?).

Time to shake it up.

4 Weeks to Launch going forward

I will spend less time writing and more time doing. I will spend less time proofing and more time doing. I will spend…you get it.

This is what I enjoy. And I think the content will be more interesting too. I may do a reflection at the end of each startup, but I the weekly updates will be short and sweet. And casual writing. No more crazy proofing (forgive my typoos).

So what happened to the last business?

Startup #2 was a mobile app to make save money fun.

Then it was a game.

Then I it needed to be redesigned.

Then the database schema was bigger.

When we sat down to actually build the thing we had a problem. Instead of a very fast, simple product we started with, we now had a mountain of work. And it was a lot of work.

The point of 4 Weeks to Launch is scrappy and fast. We’re not shooting for perfection, just something. Startup #2 is dead. Come now, let’s not dwell.

Yippee! Startup #3!

Startup #3 is a mobile app that let’s you book last minute rental home deals. Hotel Tonight for week-long rentals.

My friend Nick got access to a list of surplus vacation homes (don’t ask me how). The agency rents the properties, but anything that’s unbooked is wasted inventory. They publish their excess rentals online and offer extreme discounts.

We’re going to scrape the data from the website nightly and offer a simple mobile app for booking. When someone books through our app, we’ll manually go and reserve it for them. We’re still working on the incidental/liability details, but that’s it! Once confirmed we’ll notify our customer.

What happens next:

  1. Design the database
  2. Design the app (and keep it to the MVP!)
  3. Setup hosting
  4. Build the scraper
  5. Build the app (using ionic)
  6. Release to the wild

I’ll send an email out (newsletter link) with the designs when I have them fleshed out.

If you have any questions, let me know!

Now for some actionable advice…

When validating a startup idea, have a system for comparing. I built a spreadsheet that calculates a valuation based on different parameters and weighting. The core criteria is:

  1. Idea quality/value (shit vs brilliance)
  2. My personal ability to execute (don’t know where to start vs I can build this solo)
  3. Market size: (niche, community, industry, global)

Output = Valuation

The valuation doesn’t matter. It’s just a placeholder. What matters is being able to compare ideas to each other. Evaluate each idea you have and you’ll get better at picking good ideas.

By focusing on your own ability to execute, you stay within a knowable world. If it’s a tech product and you have 0 experience/network with technology, you probably should rethink it. However if you’ve managed engineers before then you’re probably around a 4–6 on ability because you know people who can get it done. Always pick a niche idea you know you can build over a billion-dollar, global game changer.

Hacker Noon is how hackers start their afternoons. We’re a part of the @AMIfamily. We are now accepting submissions and happy to discuss advertising & sponsorship opportunities.

To learn more, read our about page, like/message us on Facebook, or simply, tweet/DM @HackerNoon.

If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories. Until next time, don’t take the realities of the world for granted!