Your product looks really nice.
If you are not profitable yet maybe you should consider increasing the price, you're much cheaper than the competition based on your pricing page.
If you are not profitable yet maybe you should consider increasing the price, you're much cheaper than the competition based on your pricing page.
Then make a plan for say up to 15 or 25 users that is substantially more expensive and finally the unlimited user plan could be even higher.
Because you're able to do so much inside of one application I could easily see companies paying $1k+ for parts of this on a yearly basis especially when they had 20+ users of something like the task management tool.
Personally I'd also suggest modularizing your different pieces (so you can just buy the project management or just buy the invoicing etc.) As teams get larger they may want to do more or do less inside of one application, you dont want to have people feel like they're paying for things they don't need if they arent using them.
Just my $.02 I know all this takes a lot of work, but the product looks great, I hope you can figure it all out!
Best of Luck!
You should definitely split test all of this and pretty much everything you do, honestly.
Price Anchoring:
Use a giant unreasonable number for the unlimited plan with 1 month of phone support, 12 month same business day email support, you will install it for them, all the ACH and Credit Card processing through you (and you through stripe), etc. A HUGE list of features to go along with the $574 price tag.
Then drastically back off of that pricing for the 10-25 team ($249), 5-10 ($199), 2-5 ($149) and solo ($99) plans. You need to also reduce the features, support windows, contact method as you drop the price, not just the number of users.
Additional Revenue Streams:
1) Include your own payment processor and accept payments on their behalf, if you have 500 customers doing a few thousand each month on average, you processing fee will drop a lot. Always default to ACH via Stripe (0.8% fee, and a 25 cent transfer) bill the customer at 2% + $0.30 and you are making money.
2) Annual licensing. Don't give updates away unless it is a bug fix. And make sure to always be improving your product (which it sounds like you are)
3) Cloud hosted. As someone else said take the annual price divided by 12 and add a premium to it (25% or so). Also push updates to this channel regularly and add a few extra premium add-ons to it (like the a custom domain name self hosted has but for an extra $5/mo)
4) Plugins to various other solutions for $49/piece.
I know this is probably a side project, but you could turn this into a viable small business with an additional 1-2 developers.
Conclusion: I'm totally buying it before you potentially take any of my advice ;)
I was a product developer for 8 years. Developing tools in the SEO, Reputation Management and Email Marketing space. Eventually you find little tricks that just work across the board.
Then I left that job for corporate america and I regret it every day.
I now work directly with our marketing team, but they hire out to vendors for the email marketing bits, the retargeting and ad spends. I just provide my 2 cents every now and then and go back to developing in house products.
You might be about staying away from that sort of thing on principle but there's another angle. Being the one making those decisions, you have the ability to reduce the short- and long-term harm they make by picking good strategies. Schemes in marketing and driving profit up are inevitable. What's not inevitable in general is inaccurate information, highly-biased profiling, products that don't work (or do harm), customers getting fewer products than they want, technological lock-in, and so on.
Consider getting with the right companies pushing a collection of useful products or less harmful services vs other garbage on the market. Then all your schemes and optimizations would be benefiting people since the right companies would be benefiting. Companies you can vouch for. Best if they've been in business over a decade with good practices and/or are a non-profit with sustainable revenues. Just a thought.
As a side note, someone else decided that my blog was worth posting on HN, so if you have any questions or comments, you can ask them over there: https://news.ycombinator.com/item?id=12409577
What's the benefit to the customer (and you) of this, vs letting them plug in their own Stripe account credentials (and handle chargebacks etc themselves)?
I have a side project and we've let people enter their own details thinking it would be less hassle for us (customers: 3). Curious what I've missed..?
https://www.atlassian.com/software/jira/pricing?tab=host-on-...
For corporations this isn't big money. They'll worry more about ongoing cost of a sysadmin looking after the installation.
Think of it as being like BaseCamp, but with complete control of the data. It's a feature, and to some people, it should be worth more.
Your pricing plan of 1/2/Unlimited Users doesn't really capture this. The plan before unlimited should probably have 100 users or more. That way, larger customers who want to control their data can pay the right price (and feel more comfortable doing it, as @patio11 has pointed out-- you can be too cheap for people to buy).
Good luck!
No.1 lesson from my dad was "think of a number, then double it, they'll always pay more"