Why we're losing $300 per user every month
kudu.io
kudu.io
Isn't the point of MVP to test the idea that people will pay money for the provided service ? The blog post does not seem to mention if they are charging customers a price for their service.
Also, is it possible that the current users , who are being served manually, are viewing kudu as a "consulting" service rather than a SaaS
How do I test without building? How do I know they want Kudu or just the Kudu test?
The best I could do was make it VERY clear on the landing page at http://kudu.io that they were purchasing what is effectively 'early access' to Kudu and what this would involve.
(Note - We've now changed the page content as we've sold out of these early-stage seats.)
..and yes, we're charging just $30 p/m
On a related note, I was looking at patio11's charts last week and noticed that he seems to have dropped AdWords in the past year. For 2012, BCC had $64k in sales and $29k in expenses ($13k of which was for advertising) yielding a net of $35k. In 2013, his sales dropped to $46k, but with little overhead it's almost pure profit.
And thanks for patio11's stats you've encouraged me to have another look at them.
I assume they've some confidence they can create the technology or they'd have started with that side of things. No doubt there is still risk there but there was probably less there than on the market side of things. Good work.
If you have 1000 users and 10 employees This is a bad thing.
If you have 10k users this is a really bad thing.
Most startups in the pre-cashflow positive stage are losing pennies per user, not dollars. Few are losing $3600 per year per user.
It is hard to comeback from those kinds of numbers. It is harder to convince a VC that you will ever be able to turn that around.
Edit: I also don't think that telling a VC that you trained people to do what you think you can build software to do will fly.
If I told you we were going to launch a new search engine, but until we got the formula's worked out we were launching using human edits to the results, you'd laugh me out of the room.
However, in MVP, "viable" is from the customer perspective, not the business perspective. The MVP is viable for the customer to use, not necessarily viable for the business to continue providing in its minimal state.
Our current manual process is for our discovery process only.
We want to create a service for those who can't justify hiring PPC managers or third-party consultants.
When they switch over to the self-service version, they have to put more of their own time in to using your system and lose the expertise of the concierge person, and the value proposition may not be > $30/m anymore.
At the end of the test period (which will be at least 2 months) our users will have early access to the Kudu product.
Digging through links on the site suggests "minimum viable product". That term isn't among the top definitions listed in acronym dictionaries, though having had my memory prodded, I've seen it before on HN.
Articles which can't be arsed to define their acronyms draw flags from me.
The idea behind an MVP is that you build the bare minimum of what it takes to prove their is demand, and then you build out the rest of the features to make it awesome.
If you don't build an MVP you might never ship anything, and that makes VC's unhappy.
Does it really cost $300 a month, in any case? I have a hard time imagining that your company is losing ~$3600 on average per customer a year just for assigning keywords to their $SEO_PHRASE. This is not an informative article. It doesn't make anyone's life better. You're just inflating the value of your unnecessary service and trying to make like you're doing a huge service for everyone, when you're not.
However, if they have someone on their payroll making $100k/yr and that employee spends a day with a customer gathering feedback about the product and what the customer would like to see going forward, that's going to be an opportunity cost of ~$300. It's just an investment. They aren't making money right now- they are spending money paying the (hopefully) right people to determine what they can do to (hopefully) maximize their viability later in the product's life.
I am aware this isn't the point of the post - but the point is lost if the example "quick hack" involves a three-order-of-magnitude increase in CO2 emissions. This shouldn't be a socially acceptable suggestion to make in this day and age.
The actual product wouldn't involve burning a bunch of fossil fuels.