Ever since I decided to create a product, I have been unable to put it out of my mind. I have to say, this part is very exciting. Much like any new project, possibilities feel endless, not backed into any corners or misguided assumptions, and tons of ideas.

I know that this feeling will be short. The lifecycle of this project should only be 30 days, so I imagine this honeymoon phase will be even shorter than usual.

But to hell with future me’s inevitable fading enthusiasm. I preemptively made a couple moves before I technically start. I’m not sure if this is against my own rules, but here’s what I’ve done so far.

  • Picked a name for my product
  • Bought the domain
  • Put up a ridiculously simple coming soon page and pointed it to the blog for more info
  • Thinking of different ways to structure the product

Picked a name

The name of the product is Weekendr. I felt this name kind of perfectly fits without too much overthinking. I believe it highlights my target audience (weekend travelers) in a quick and recognizable way. Although it does have a bit of a cheesy, trendy use of the r at the end without the e, I think it fits without trying too hard.

Bought the domain

I bought the domain Weekendr.io, which I think is perfect. I bought it from Godaddy since I already had an account and they had a sale, so I only spent $45 on the domain instead of the usual $60. I like this domain because:

  • Same name as the product (most important for me)
  • io TLD is common for digital products
  • Easy to spell or explain

Coming soon

Ok, so I wanted to put up a better landing page, but felt that would be some serious overstepping. Buying the domain before someone else buys it is one thing, but to spend time working on a landing page, possibly looking at vendors or products to expedite the process, feels like work that should be reserved for the 30 days.

I also didn’t want a dead parked page, so I literally just pointed it to my personal server that my portfolio site lives on and just put up the most basic of HTML pages. I think it was about 5 lines of code including break tags on their own lines.

Product Structure

This is really where most of my thinking has been going. I want to keep this product as simple and goal oriented as possible. In order to properly structure options, I need to outline the experience of the user.

  • Signs up for service
  • Receives notifications on round trip weekend flights for very cheap
  • View information about a flight
  • Directed to purchase tickets

So far my thinking has been restricted to the first two points. What is required at sign up and what is the best vehicle for notifications.

I think regarding notifications, email list will be the simplest and most effective and least invasive model. No one has to download anything, Scott’s cheap flights proved it works for flight deals, and it’s very quick and easy to setup. The downfalls of email list, is it essentially allows for zero user input. This means I either restrict all user interaction to signup or create a website that coincides with the email account for any user engagement.

The reason I’m thinking about user engagement is because “cheap” is a subjective term. The purchasing power in San Fransisco is vastly different than in Raleigh, so the concept of cheap for tickets becomes relative. This brings me to the idea of a user inputting a threshold of how cheap the tickets have to be (under $100, $150, $200, etc.). This could be restricted to signup only, but am kicking around the idea of making it adjustable. A workaround would be to cancel and resubscribe, so it isn’t mission critical, but if I introduce paid plans, it can get tricky.

This point also then brings me to sign up. Do I even ask for a threshold or just start with a simple fixed price. Is the assumption that purchasing power is as significant as I am making it out to be? Could this be a level of complexity that is just not necessary for launch. It could be faster to start with a fixed price like $150/round trip and then if I get feedback, I can implement. Or better add it to the paid plan only after launch.

Right now these are all thoughts that are getting me excited about building this thing. Can’t wait to get started.