At the moment, it's mainly just price. We try to offer the same services but with much more affordable plans.
One spot where we do differ greatly though is our bulk email verification. We check for more risk factors and information about an email address compared to other companies.
This companies directory part of our site though is more just a service for easily finding the main contact information and emails for a company, without having to be a member of MailDB. Being a member is free, though! :)
Thank you for your code, I will be definitely be referring to this as I build the base of my current project.
Diving back into Node though, just so I can get my current portfolio up to par and job-ready, it makes me realize how broken this whole process is.
It seems like bi-annually, either Node.js is changing, Webpack is changing, React is changing, or possibly all three have changed. What you learned just a year ago has been modified and 'updated', usually with configuration and API changes. This leads to a whole slew of new articles and tutorials and boilerplate GitHub projects being created, only to be somewhat legacy less than a year down the road.
Then the plugins you have to learn, all of which separately might have configuration and API changes from one version to the next... Then you have to learn server side rendering because all of this is built for the client, so it's time to incorporate some weird page loading query string hacks to get that working...
All of this feels like it's just one hack put on top of another, to try and achieve what browsers have been doing since the 90's, just without reloading the page.
I think the updates to JavaScript in ES6 like arrow functions, classes, the spread operator, etc are great, but even this I could see going down the C++ route of just trying to add every single feature a programmer can think of to the language.
This is why I prefer Go so heavily. The core language keywords and features have not really changed since its inception. I hope one day this can all be condensed and simplified, much like Go is doing for backend languages.
I'm using MailChimp for building the email list, and I'm using the same MailChimp account as I do for my main SaaS, MailDB (https://maildb.io).
This is completely separate and has nothing to do with that site - I thought the settings were different for this specific list.
I'll double check now, thank you! And no worries, you will never be emailed regarding that site - this list is only for SaaScriber and this idea alone.
The way I was looking at it, this is something we want to form a real team around and build in 4-6 months time.
While we could try to leverage our own idea, without having this site known and heavily trafficked, the subscriptions will be minuscule and probably not enough to achieve our goals - look at early Kickstarter. An influx of cash would help get the word out.
Plus, we're hoping to work with SaaS companies who sign up and see which products/ideas want to launch with us.
I do see your point though. Maybe this is something where it needs to start small, using the idea itself as proof.
One spot where we do differ greatly though is our bulk email verification. We check for more risk factors and information about an email address compared to other companies.
This companies directory part of our site though is more just a service for easily finding the main contact information and emails for a company, without having to be a member of MailDB. Being a member is free, though! :)