I’m an entrepreneur and its great. I get super doper excited when I find a new good niche, and I seem to find them all the time. Right now I know of 5 great niches that will make a ton of money.
The last 2 years I have been in a great niche that has been really fun, during that time I built my own ecommerce backend that works great for what I do. Every month I have been putting funds towards making the backend better, and I think I finnaly have it to were I want it. Right now it works just like any normal ecom backend, but mine is different because the drop shipping part is automated, every day at 1pm my time a excel script is emailed to the warehouse people so they can send out the orders. Then they send an excel page back with the tracking numbers and my drop shipper puts the tracking codes in manually (that will change I am upgrading that right meow). Also the email marketing is also automated on my backend, which saves a ton of time.
Now I only have about 3k worth of investments I need to do to the backend to get it exactly the way I want it…. then I can get into any niches pretty easily because I will have the bad ass ecom backend along with developerhut.com (automated seo hehe). But before I spend the funds I need to decide what way i want to head with the databases part, ill explain;
Ok so if you dont know by now, I am obsessed with hayneedle. I love how they set up there business model and I want to do something like that with drop shipping. They use a central products database and then when they start a new ecommerce website they simply buy the top level domain for the niche and then hook there backend onto the domain. It makes total sense because they can easily get into or out of niches easily. Now I have been trying to decide on if I want that style of a backend or not. I can do it 2 ways;
Option 1: make the current backend into a main backend just like how hayneedle does it
or
Option 2: pimp out the current backend to make it so I can get into new niches easier.
Both options would utilize the current backend, I would upgrade the current one to do either option 1 or 2. I think I am kind of leaning towards option 1, the only problem is that I know I will run into a lot more problems that I would with option 2. Because option 2 is just upgrading the backend to make it better, but option 1 is doing something I have never done before.
So I have a question for you guys, if you were to invest 3k into a backend which option would you do?
Follow me on my journey of success and failures, it should be a fun ride.... Again, here is the link for the RSS feed.
Comments are Dofollow! My thanks to you for contributing to the discussion
6 Comments
Sorry, the comment form is closed at this time.
Crazy amounts of niches that hayneedle is in… check out the list here:
http://www.hayneedle.com/all-stores.cfm
How do you know that’s what HN is doing?
They do have a badd ass setup, god only know what their daily rev is.
I would go with option 1 and I think you’ve already decided that’s what you want to do. Your post is uber suggestive that you want us to agree with you. But, regardless of that, I think that’s a good call. It’s obviously a technique that works.
Option two FTW, here’s why:
You ALWAYS get trolls (pessimistic idiots) who will NEVER be happy with your product/services, w.e.
If you just so happen to get one of these unhappy customers, they will tell everyone and their mom about how bad JonWaraas network.com is. You can expect loads of negative forum reviews, blog post, etc. which can dampen the image of not only the website they purchased from, but from your entire network of sites.
Keep your shit separate, it’s better in the long run IMO.
Management wise a central back-end that you can just pop in a domain and a list of products and boom have a niche site up and running will be a lot better in the long term.
But negatively if you ever want to sell off that site you’re gonna have more problems separating it from your central hub.
Don’t over invent something that already exist. The Magento commerce platform allows you to have the same back end and processes but multiple store fronts and even a shared cart between them.