5 ms·

I noticed the "Try Jetstrap free today!" then I saw you mention "Our first thought was $10/mo for 100 screens"[1] which I think is not only underpriced but the

I noticed the "Try Jetstrap free today!" then I saw you mention "Our first thought was $10/mo for 100 screens"[1] which I think is not only underpriced but the wrong pricing structure. You should implement something like this: - User signs up - gets 5 - 10 FREE Screens. - Once they've used up their FREE screens take them to a page to purchase more screens. - When they have 1-2 FREE Screens remaining you should have a popup which says they've nearly used their free screens up and to buy more (with one option offering to go to payment page & the other leting the user continue what they were doing). - On the page where the users can purchase more screens, I wouldn't bother with a monthly subscription plan because that's not what your target audience is interested in. I'd offer the following options: 100 Screens - $39 ($0.39/Screen) 250 Screens - $95 ($0.38/Screen) 500 Screens - $180 ($0.36/Screen) [1] http://news.ycombinator.com/item?id=4572125 http://news.ycombinator.com/item?id=4572125

yesimahuman 14y ago
Thank you so much for the feedback. I was hesitant to throw out pricing thoughts just yet, but I'm really glad we did.
- fatbat 14y ago
  Saw this from a few HN threads down. May be helpful? http://blog.keen.io/post/32269955563/pricing-is-hard-we-need-your-help http://blog.keen.io/post/32269955563/pricing-is-hard-we-need... Personally I like the "Utility Pricing" (per article) for something like Jetstrap but maybe on a per project basis instead of per screen?
ebzlo 14y ago
The problem with this is that there is no incentive to keep one account. GoMockingbird (http://gomockingbird.com http://gomockingbird.com) is an example of an application I probably have 4 accounts for-- not on purpose, I just couldn't figure out which email, twitter, facebook I used to sign up for it. I didn't realize that only the first project was free until later, because I generally stop using it after one project. I could totally foresee a user signing up for 5-10 free screens then forgetting about the tool for later. When they come back, those original 5-10 screens may or may not be related to what they're working on now, and I can guarantee most people won't shell out the $39 when they realize they could just create a new account. The proper way to monetize this (IMO) is through a freemium model. Don't limit them with what you have now. Figure out something that's truly a solid bell or whistle and sell them that. Give users the ability to create HTML/CSS for free, but maybe scroll-fixed javascript headers cost $10 for 10 pages (scroll here: https://www.kiteedu.com https://www.kiteedu.com).
- asdfaoeu 14y ago
  Right idea I think but I would go with something that makes it more useful for not just prototyping like api export / import and direct editing of template formats like interpreting ruby's erb just enough to display some placeholder text.
- tripzilch 14y ago
  I, for one, completely support this $10 tax on scroll-fixed javascript headers! Make it $100, it's the BLINK tag of 2012.

yesimahuman 14y ago

Thank you so much for the feedback. I was hesitant to throw out pricing thoughts just yet, but I'm really glad we did.

fatbat 14y ago
Saw this from a few HN threads down. May be helpful? http://blog.keen.io/post/32269955563/pricing-is-hard-we-need-your-help http://blog.keen.io/post/32269955563/pricing-is-hard-we-need... Personally I like the "Utility Pricing" (per article) for something like Jetstrap but maybe on a per project basis instead of per screen?

ebzlo 14y ago

The problem with this is that there is no incentive to keep one account. GoMockingbird (http://gomockingbird.com http://gomockingbird.com) is an example of an application I probably have 4 accounts for-- not on purpose, I just couldn't figure out which email, twitter, facebook I used to sign up for it. I didn't realize that only the first project was free until later, because I generally stop using it after one project. I could totally foresee a user signing up for 5-10 free screens then forgetting about the tool for later. When they come back, those original 5-10 screens may or may not be related to what they're working on now, and I can guarantee most people won't shell out the $39 when they realize they could just create a new account. The proper way to monetize this (IMO) is through a freemium model. Don't limit them with what you have now. Figure out something that's truly a solid bell or whistle and sell them that. Give users the ability to create HTML/CSS for free, but maybe scroll-fixed javascript headers cost $10 for 10 pages (scroll here: https://www.kiteedu.com https://www.kiteedu.com).

asdfaoeu 14y ago
Right idea I think but I would go with something that makes it more useful for not just prototyping like api export / import and direct editing of template formats like interpreting ruby's erb just enough to display some placeholder text.
tripzilch 14y ago
I, for one, completely support this $10 tax on scroll-fixed javascript headers! Make it $100, it's the BLINK tag of 2012.