Live data from Hacker News

Launching a product in just 3652 days

medium.com

31–40 of 60 posts

Re: Launching a product in just 3652 days

#31
post #27

Earlier quoted context omitted.

Do you do your own design, do you work with someone or do your customers work with a designer?

Yes :) I do some of the design on my own (like the UI), work with a designer (the marketing website) and my customers usually work with a designer for their website design.

Care to elaborate more? Does the CMS has things like /news, /bio, /photos etc and then the designers/front-end work on top of that?

Great project btw! I am a fan of these bands as well

Re: Launching a product in just 3652 days

#32
Thanks for sharing this!

I checked out your pricing plans and the way you differentiate plans based on visitors / day jumped out at me since it goes against advice I read recently from the UserVoice team. They used to price based on number of users who can vote but (in their own words)...

"This was a huge failure. It created what I call a success penalty: the more successful you were in activating your users to give you feedback the more expensive the product became. On some level this made sense but since no one knew how to estimate this future usage it just created uncertainty about committing to a product without knowing the future cost of it. It was especially problematic because we were often working with young companies who didn’t know or were very optimistic about their future active user levels (and equally optimistic about what % of them would engage on UserVoice and give them feedback). It put us in the awkward position of tempering a customer’s enthusiasm about their use of our product (aka “There’s no way you’ll have 300K people on your site in 60 days time”). When we removed the usage limits, which were designed to drive upgrades, we actually saw that upgrades increased 33%!"

Link: http://500.co/the-data-behind-purchasing-behavior-at-uservoi...

Re: Launching a product in just 3652 days

#33

Earlier quoted context omitted.

Yes :) I do some of the design on my own (like the UI), work with a designer (the marketing website) and my customers usually work with a designer for their website design.

Care to elaborate more? Does the CMS has things like /news, /bio, /photos etc and then the designers/front-end work on top of that? Great project btw! I am a fan of these bands as well

The websites don't have a fixed structure. As a front-end developer/designer you're able to define templates with a set of elements (text, image, datetime, concerts, twitter integration, collection of other templates, …). The schema of the templates define the forms in the content management section of the CMS.

I hope this screenshot helps to clarify things a bit http://drif.tt/1KfpfoI :)

Re: Launching a product in just 3652 days

#34
Just a quick question about some copy on your website, you might be unaware this is even on there but the text for your VAT stuff (pricing related) is a little hard to understand.

    .... Additional VAT charges are added to purchases made by customers from the European Union, except for customers from the European Union, but outside of Germany, who provide a valid VAT ID. Businesses from outside the European Union are not charged with VAT.

Re: Launching a product in just 3652 days

#35

Thanks for sharing this! I checked out your pricing plans and the way you differentiate plans based on visitors / day jumped out at me since it goes against advice I read recently from the UserVoice team. They used to price based on number of users who can vote but (in their own words)... "This was a huge failure. It created what I call a success penalty: the more successful you were in activating your users to give…

Thanks for the feedback! I agree that the pricing isn't perfect, yet.

I'm currently segmenting by visitors/day as it seems to be the only way to separate bands into the different plans based on their popularity and success. It's also directly bound to the costs on my side (more traffic -> more server resources).

I'm happy to hear suggestions on how to make sure a band making tons of money doesn't end up on the smallest plan, as well as costs for infrastructure not bankrupting me. :)

Re: Launching a product in just 3652 days

#36
post #34

Just a quick question about some copy on your website, you might be unaware this is even on there but the text for your VAT stuff (pricing related) is a little hard to understand. .... Additional VAT charges are added to purchases made by customers from the European Union, except for customers from the European Union, but outside of Germany, who provide a valid VAT ID. Businesses from outside the European Union are n…

Yeah, it is hard to understand. The regulations for VAT on SaaS products got insanely complicated a few months ago.

Thanks for the feedback, though! I'll try to rephrase it without losing the gist of it :)

Re: Launching a product in just 3652 days

#37
post #20

Urgh. I really need more motivation to finish my current project! Always just one or two more features from finishing, then some bug comes up that throws me back and i get disheartened. Worst part, i have alpha testers, and damn their patient for a new version, i sometimes wish they would complain to make me get into that 'i gotta get this part updated asap' mood again. Edit: Hmm after reading the article, i really n…

What product are you making? Couldn't find it via your profile.

Huh i should update that! Its a voice command and control system with a few extra bells and whistles that works with starcitizen.

Www.casibymarak.com

Thanks ill update my profile haha.

Re: Launching a product in just 3652 days

#38
post #30

Product makes great impression. Still I have a slight problem with pricing scheme. If for a band 5GB is not enough, and needs e.g. 10GB instead, it needs to put out 120€ per month more. That sounds hostile. It would be probably better if pricing scheme is more modular, and pure hosting capacity aspects are priced reasonably. Additionally option of yearly licenses with hosting on side of a client would be a big plus

Thank a lot for your feedback on this!

Based on my past experience the storage limits are well over the actual needs. It usually only grows when bands have a lot of photos on their website. At the moment I'm implying that a band with a lot of photos has been around for quite some time and is probably also somewhat successful by then, so they'd have to choose a larger plan anyways (because of increased traffic).

Yearly plans is definitely a thing I'm going to add in the future. :)

Post reply on HN