Don't wait to add a team plan to your product. Add one now.
Something I regret not doing way earlier is adding a "team plan" to Divjoy at a higher price point.
I had assumed that a team plan would, at the very least, need to have some way for the account owner to invite other team members and for each team member to have their own login. Maybe some way to set member permissions. That's how most quality products with a team plan work right?
A couple weeks ago I watched a video by @patio11 where he talks about pricing. He mentions that he once added a team plan for an info product he was selling. All it did was give permission to share the product with team members (100% on the honor system) and that ended up becoming 20% of his revenue đ€Ż
The same day I watched that video I rolled out a team plan on Divjoy at 2.5x the price of the individual plan. All it does is give you permission to share your login with team members. It's not an info product like @patio11's, but maybe this would work fine for SaaS as well. Only one way to find out..
It's now been two weeks and it's accounted for 18% of my revenue. Wow.
The point isn't that you should forgo adding extra team features. I'm going to be rolling out proper team accounts with inviting and all that good stuff. But by launching earlier, I'm making extra revenue now and getting crucial feedback from teams about what they'd like to see in the future.
This is what it looks like. It took me less than an hour to add.
This also helps with price anchoring!
In 2019 I had tier Unlimited, Team, Individual (all use on unlimited products) and switched to Enterprise, Small Business, Hobby in an effort to push businesses away from individual licensing. The unlimited use was removed from hobby as well.
The switch yielded a 6x increase in âmidâ (small business) tier license sales.
Yeah great point about price anchoring! Thatâs amazing you saw a 6x increase in small business sales. I wonder how much of that was simply due to the name change to âhobbyâ.
I skipped over some name changes to keep the comment short :)
I went with âhobbyâ later on, initially changed it to âunlimitedâ, âcompanyâ, and âindividualâ which yielded the 6x increase then changed to âenterpriseâ, âsmall businessâ, âhobbyâ but that didnât make a big change over previous tiers :) did however get more inquiries of small businesses asking if they couldnât just use Hobby instead of small business. đ€·ââïž
I'm wondering how much additional complexity this added. I know many apps don't offer it because it's just one more feature. And when you start looking into all the things you need to do to continue to support it I can understand why more don't have a good story around shared account data between users.
This is actually one of the whole reasons, I had to write articles like building your own auth and securing multitenant platforms.
The first iteration of this added essentially zero extra complicity. All it does is give the user permission to share their login credentials with teammates.
I really hope that doesn't mean users are using the same username/password are the same user account in a why that you can't distinguish them on your side. I.e. if one of our team members leave the company, how can I block their login?
From my post above:
â The point isn't that you should forgo adding extra team features. I'm going to be rolling out proper team accounts with inviting and all that good stuff. But by launching earlier, I'm making extra revenue now and getting crucial feedback from teams about what they'd like to see in the future.â
No, definitely agreed. Although from our experience, security always seems to be left at the back and rarely gets noticed until there is a critical problem. It's one of those things that users expect and may not get. Additionally many teams don't have the technical capacity nor capabilities in auth/security to support building the necessary features to protect their users.
This is probably the core reason we focus directly on solving the problems created in the space with multiple user account platforms.
(It's my primary focus, so I'm always interested in what teams are building in the space because it helps us to focus our efforts and understand what the users (and potential users) of Authress are thinking about)
Congrats @Gabe. Glad this worked out so well!
@patio11 for the win :)
Thanks for sending me that video in the first place :)
Interesting, so it's just the same plan but labelled as "for a team environment" - smart!
That and they have explicit permission to share their login with team members, which imagine some might feel a little cheap doing if it wasnât officially okayed. Sharing your login isnât ideal.. but itâs good enough for most it turns out.
Gotcha, so this is almost like a test of a feature before you build the full collab feature? i.e. login with @domain.com to be in ur "team" or something like that
Yeah exactly. Good way to see if there is demand from teams and to get their feedback before building all those features.
That's amazing. Never thought about it like this. It's basically just positioning.
Yup! Lot of people out there that aren't super price conscious, especially if it's a product thatâs likely to save them thousands, and just want to know it's meant for them and they're on the right plan.
Crazy stuff.
Would be a cool experiment! Offering the exact same thing, under three plan names: Individual, Team & Enterprise. They probably just want to feel like they fit in tight.
Cool! Let's try! For some suggestions for improvements, add minimalistic top pop-up link to the Roadmap and/or Changelog inside No-Code editor. Highlight the improvments!đ