Regarding the business model: You ever thought of a Franchise model? Perhaps train a few folks (perhaps folks who were incorrectly greasing before) who can then take contracts for the large job sites?
I have seen this practice with diamond coring machines of companies like Hilti in markets like Dubai (building contractors don't need the machine , they just need the holes they cut and they don't need it everyday) where folks but the coring machines and then charge per hole (per Zerk in your case) and Hilti provides training to them.
Regarding the segment: If incorrect greasing leads to machinery failure, then perhaps look at operations where machine failure can be mission critical. Sites like Baffin Island, where large contractors' maintenance plan is "buy 10 of each machine" If one breaks down, they just park it and put the next one into service. OR Offshore Platforms where downtime can mean several millions down the pipe. Example projects offshore in Guyana where replacements are not available onshore too.
Can share what we do at our startup. (8 people, 100 - 200 customers). We create a WhatsApp group for every customer and stay with them right from onboarding onwards.
Beauty of it is they sneeze, we know. Everyone in the team kinda knows what's important what's not. we can confidently say things like "nobody cares about that fancy feature". It super valuable for a startup to get immedeate feedback. Especially valuable has been knowing
- the first things the notice when they start using: where is sort? how do i add team members? do i have to prepay?
- feature requests: it's painful to keep closing windows, need the ability to adjust windows, I also want to do this other thing you guys havent thought of.
- Bugs: why am i seeing double messages.
Disadvantages are that some customers expect immedeate answers, unrealistic expectations. and its cringey to lay down the rules and set expectations every time. no matter how many times you do it.
Our take is its 80% good and 20% bad. As we grow the company, the idea is to keep doing this for a "representative sample of customers" . Customer feedback is gold. If you can setup some kind of process like this, its great.
In those United States, you would be right to think so. Yes, there are other chat apps. A flood? No. A (cess)pool, maybe.
Outside of WhatsApp (2 Billion Monthly Active Users), Messenger (1.4 Billion MAU) and WeChat (1.2 Billion MAU) the others stand little chance of building and benefiting from being a platform.
Setting aside WeChat and China, if you now look at the next billion users who are going to be using the internet for the first time, WhatsApp is the lens through which they see the internet - they communicate, consume news and entertainment, buy and sell things, get medical advice, even fall in love via WhatsApp.
In India, where a significant portion of that #nextbillion are gonna come from, Messenger has ~100M users and WhatsApp has ~500M MAU. Similar multiples play out in "WhatsApp first" markets like Latin America, most parts of Asia.
Case in Point: Even though it had nothing to do with our business, we recently helped hack together a solution to conduct two, 20-question, exams for 100K students in an Indian State. Simply because every family had WhatsApp (and nothing else). Messenger simply doesn't have the reach in the emerging world.
From Businesses - small and large. Using the WhatsApp API. That alone is a multi-billion dollar opportunity.
For example, people like my startup (https://www.zoko.io) provides software that enable folks to run any business on (only) WhatsApp.
WhatsApp would make money by
- charging for certain types of messages sent via the API (already doing it)
- from ads on the WhatsApp, Facebook and Instagram Platform that click directly to WhatsApp.(already doing it)
- enabling payments via WhatsApp Pay and then take a cut of the payments. (coming soon)
I am amazed by the things that my customers do with WhatsApp - like Fintech companies who provide loans to Uber drivers via WhatsApp, OR Fertility Clinics that dole out professional advice on how to make babies, via WhatsApp.
WhatsApp is just getting started! Remember when the internet was free, Google showed up and became a toll collector for doing anything on the internet? Just like that, WhatsApp is the internet of the #nextbillion people. WhatsApp, if they play their cards right, could become the "toll collector of the internet for the #nextbillion". I am literally all in, that it will.
:-) Interesting to read many describe that feeling you get when you read Chekhov. A Russian friend once told me it is тоска (toska) - an unbearable, inescapable anguish - "Really you have to be Russian to understand it. toska is rent for being Russian. More Vodka?"
First of all, good job on launching! Hopefully you inspire many others here to take that all-important step.
Not a native english speaker. So take my advice with a grain of salt. Not sure if you actually meant "eccentric". I initially thought you were addressing a niche segment of folks who wanted eccentric (slightly strange) content on their blogs just to spice things up. For example content like this - https://www.atlasobscura.com/articles/utility-pole-surfaces would fit the description of content I would describe as "eccentric and delightful" content. If that's not what you meant, you can re-evaluate that main tagline.
Maybe put that line "Get Premium content on a budget" front and center. That's a great line!
Don't worry too much about getting the grammar right. Focus on putting it out in front of many people as possible. (like you have done here on Hacker News) Bracket feedback into 2 segments:
1. Feedback from paying customers.
2. Feedback from others.
Address the feedback from group 1 first.
Yes. not necessarily. Once you are able to observe active users, have paying users or even sizeable traffic to test conversions.
You can experiment to find out what that "right" or "best converting" price point would be.
"Free to start" may very well end up being the answer. Here are 2 examples one from pubilshing and one about starting with a price and using data to uncover insights about the "right" price. You will see the 30 cents is not the biggest problem you are going to have in pricing. :-)
Your's is not "a project that gives context to news through history" @$1.00 per month. If the market wants it, it should work at $1(+$0.30 +2.9%)per month also.
So just charge $1.49 per month and move on. Once you have a 1000 users, you can think about optimizing things.
That would be like car dealer asking "should I get a LOI before I let folks drive the new car." For a 7-day trial dont waste your time, or their's, on a LOI. LOI's are not worth the paper its written on.
A no commitment try-before-buy is almost always a great sales strategy for good software. Customers would have a hundred questions when they actually use your product. this is also a good opportunity to learn about how to sell to the next client by improving your sales pitch.
Not sure if your product is amenable to this, but one learning I would share is give a "shared account" for trial. for example the product could be branded in your name, other trialling companies could be using it at the same time etc.
say for example if you were sellling GMAIL, you would give them a 7-day free trial but they have to use an email and password you give them like username: [email protected] , password: test123 and other users will be logging in at the same time - trying sending and receving email, tagging mails, suggested replies etc.
I sell a product that allows customers to send messages via WhatsApp. I give them a shared account to play with as long as they like. but if they want a branded account , they have to pay upfront and only then i set it up.
back to the car analogy. Think of it like a demo car http://bit.ly/2ySHeTc . The client get a feel for the car but pays if they need one, all for themselves.
Not sure where the icons are showing up. I had removed all such links. (forgot to mention its a 3 person team. me, cto and an entry level coder)
>Maybe you can flesh out that scenario on the website to explain the process to a prospect. Putting a video out there so you don't have to do the operation with each client (one video that shows how the product can solve the problem).
Maybe its an Indian thing but folks dont seem to read anything. They prefer to call me directly and then see a demo. I also like the call first, because I can quickly decide who will convert and who will not.
> What's the need for signing the word file? Why do they need to sign it?
Thats the contract. If there's no ink on paper we dont setup dedicated accounts. Most of the work is manual for setting up accounts, linking numbers, setting up template messages etc. So unless its a customer who is ready to commit for a year, the coders dont even hear about them.
> Can I as a prospect directly click on an icon on your website or scan a QR Code and start a WhatsApp/FB messenger with you?
Not self serve right now. Once you sign a contract, you get a demo account (still shared with other clients). you get an email with access information so that you can start playing with a shared demo account and also play with the API, while we setup the accounts.
Thanks for the pointers on the shortcomings of the website. Have added them to my long list of to-do improvements to the website.
> How would you take me from now to paying customer? How do I give you money?
- Customers start an an incoming lead from linkedin ads or facebook ads.
- Then a phone call letting them talk and me asking a lot of questions about the problems they face using WhatsApp for business today.
- Then I show them a screen share demo and touch on their problems and how the product solves it.
- Followed by a signing an order form (word file)
- We then setup their accounts and send a precomposed email with links to the API, API key and access details to the web app.
- Also start a whatsapp group so they can ask and get immideate help in integration.
- Billing starts 7 days after API key receipt. All fees paid upfront and all usage through upfront purchase of credits. We have setup stripe in the billing section of the web app.
Thank you for the pointers. Good point about "Zoko not using Zoko" :-) Will change that before teh end of the month.
>Where is that from? I found a Medium post with dubious "stats". Maybe include testimonials in text and video?
The stat is from a widely quoted Forrester study.
Interestingly the website was built in a day using a free service called WIX. We dont have much difficulty convincing clients. Our paying clients may have actually seen our website in passing. Most of the selling is by getting clients via facebok and linkedin ads and demos scheduled via Skype/hangouts/anydesk/zoom etc.
Probably had 4 people reach out to us by the website in 4 months. its been kind of ignored till now.
> I think sharing a bit of the technical side would help attract the people you're looking for. For example, sharing your technology stack would attract the people familiar with that stack.
Mostly React and NodeJS.
- Web app is MySQL, React, Redux and NodeJS
- Multiple micro services (REST) built on NodeJS and Spring Boot
- Other tech: RabbitMQ, WebSockets
> Also, if you share a block diagram of your process, even without going too much into details in case you're worried to be copied at this stage or something. Something like a box receiving a message, and another box processing the message and sending it to a "partner", that gives an idea on how this machine works might help. Heck it can help people think more abstractly and propose ideas to generalize that solution to address a different vertical than the one you're addressing right now.
Not at all worried about getting copied (lesson learned from YC Videos). A video is show here - https://www.zoko.io/zoko-sales . Question is what's the right business strategy/tactic to get to $100K a month? Continue to sell the product shown in the video or make an API that will enable partners to make the product show in the video.
Work Rules by Lazlo Bock may give you some good insights. It references a rigorous study by Frank Schmidt and John Hunter. The gist of it is that the 3 best indicators of on-the-job performance is a work sample test, general cognitive ability tests and structured interviews.
If leadership quality is something you wanna test for, you just have to design the questions in that manner - for example ask about how she handled professional failure in the past, ask her to give you some tips to motivate subordinates, to teach you something you dont know, even its a fun fact, like turtles breath through their bottoms.
As for your concern that "most people would have read about these sort of questions and come up with some template answers". You could flush their prepared answers by asking the candidate to give you a 10 second summary of their answer first, then ask them to give another example in a 10 second summary. After they have exhausted their "template answers", ask them to take their time to give you an example other than these 2. Give them ample time. Don't bully them or put them under pressure, work with them to elicit another example and dive deep in a collaborative manner. for example with "why did you think at that time, this was the right approach", "I messed up recently by doing xxx, how do you think I could have handled it better". (Don't do this for all your Behavioral Questions. Pick the last question especially if the candidate is performing well)
End of the day most interviews are a waste of time because 99.4 percent of the time is spent trying to confirm whatever impression the interviewer formed in the first ten seconds. (https://www.researchgate.net/publication/313878823_The_impor...). I cant find the reference for my life, but I think it was Google (or Amazon) that found out that given the same structured interview process, some people were better than others in selecting great teammates that performed well on-the-job. The key is to encourage these type of interviewers to do more interviews.
"Expecting the world to be fair with us because we are fair, is like expecting the lion not to eat us because we didn't eat him" - Paul Graham
I am no Paul Graham, but I think you are wasting your time. Let's say you win the case next Tuesday and the judge miraculously orders them to shut shop. They dissapear on Thursday. Then what?
You still wake up next Friday with 99% of the problems (and opportunities) you had, before you "came across Otonomo’s publicly available API documentation" a few days ago.
If there's still a little voice inside your head that's sayin - Paul Graham didn't say that, you are missing the f*ing point. Start over.
The Mississippi would, but doesn't to that scale today, because the Army Core has leveed/dyked in most places.
You can see in the pictures here http://bit.ly/2u7f2ta that there is a lot of "marsh" beyond where the river bank ends. You just have to extend the roadway as far as you like. You can see how the bridge extends beyond the river on both sides.
This particular bridge for example has 18 miles of approach roadways. Only about 1600 feet of that, spans the Mississippi.
In short, if flooding adds 27 miles or 270 miles of width, the engineering is pretty much the same. You just have to know, where to start and finish :-)
Always happy when bridges get discussed here. Having built (a couple of) bridges across the Mississippi, i can attest that it is possible to build a bridge across the Amazon. This headline is appears to be click bait
A river rising 30 feet is no big deal. I think the Amazon rises more than that actually. The Mississippi very often rises to 40 feet.More in some years. Here's a video of a 300yr flood hitting in the middle of bridge construction - https://www.youtube.com/watch?v=Orj6B46PJbY (skip and pause at 0:17)
Regarding the business model: You ever thought of a Franchise model? Perhaps train a few folks (perhaps folks who were incorrectly greasing before) who can then take contracts for the large job sites?
I have seen this practice with diamond coring machines of companies like Hilti in markets like Dubai (building contractors don't need the machine , they just need the holes they cut and they don't need it everyday) where folks but the coring machines and then charge per hole (per Zerk in your case) and Hilti provides training to them.
Regarding the segment: If incorrect greasing leads to machinery failure, then perhaps look at operations where machine failure can be mission critical. Sites like Baffin Island, where large contractors' maintenance plan is "buy 10 of each machine" If one breaks down, they just park it and put the next one into service. OR Offshore Platforms where downtime can mean several millions down the pipe. Example projects offshore in Guyana where replacements are not available onshore too.