I get this question a lot from experts and others who are using Glide as a platform to service clients & customers. Here are the most common ways to use Glide as a service for your customers/clients:
Preferred Way: Client (or affiliate) creates their team and invites you to their team.
This method is eligible for revenue sharing
Client/Customer creates their own Glide Team and purchase a subscription
Client/Customer invites you to join their team
Once invited, you can transfer apps to the team
Other Way: You keep all apps / teams in your main account
You will not be eligible for rev share with this model
You create a Glide Team and have your client’s apps under that team
Billing for usage can be tricky, as updates and users are counted on a Team Level.
This poses a security risk for your client, because if anything happens to your account they are affected
If you are building for clients as a freelancer or agency, the Glide Experts program is just for you. To join, sign into Glide, then go to Account Settings, and click Join Glide Experts Program.
Thanks Yall! Let me know if you have any questions
Hi Brett, so just a question. So lets say I have been doing customer work the “other way”. Would there be a possibility to move the apps I have built to their workspaces?
The reason I am asking this is that I live in Africa and a lot of people are sceptical that we are able to do what we say we can do.
We then build “trial” systems for them to test and in those trial systems need to have a lot of the “pro” content.
If its not a possibility I can understand, then we would have to change our sales process a bit.
Get them to create a Glide account, add a billing method and upgrade to the appropriate plan.
Invite you as a team member
You should then be able to transfer any Apps from your team to theirs.
NB. It’s important that they’ve added a billing method. You wont be able to transfer Apps into their team until they’ve done that.
Personally, I prefer to build Apps in the clients team from day 1. In fact, that’s the only way I work. It’s just much cleaner, especially if you’re using integrations with Make - then the client also creates their own Make account.
So - Two things.
1: Are you wanting to create an internal solution for a business, and then sell that solution to many businesses also? IF so; Glide absolutely works with this model.
2: Are you wanting to build an app and then charge companies/users to use it? This is not in the roadmap or business model of Glide, so be aware in the future there can be pricing/plan structure changes that might impact you.
Glide’s focus is to provide powerful internal solutions to businesses. This is where our product is going and pricing / plan structure as well.
Srry, but I am not understanding the difference. In either case my company (me) creates it on Glide and then other companies suscribe to use it in their project management activities. Business market is architects and property management and they would use the app for project management purposes.
1st case - You build an internal app for business A, that serves as an internal solution for that business. You can then sell that same solution, to other businesses. This means multiple apps.
2nd case - You build one app only, and use it as a SaaS app to sell the solution to multiple businesses, with a subscription model. Brett indicates that this is not the business model of Glide.
