How to Build for Multiple Clients/Customers on Glide

Hey Gliders!

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 :wink:


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.

Yes, you can do that. The process is as follows:

  • 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.


Awesome :grin:

And thanks for the advice. I can imagine that doing it that way takes away a lot of stress!

So they would have to create an account using my referral link

Well, they don’t have to - but it’s better for you if they do :wink:

1 Like

Brand New here. COming into this I was thinking I would create an app. Sell subscription to the app and then allow the subscriber access to their app.

If I fully understand BrettH note that is not possible. Do I have that right? Or am I too inexperienced to understand this.

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.


I think Brett means this:

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.

Please correct me if I’m wrong.


This is correct ^^ Thank you Thinh!

1 Like

Hi all, Glide newb here. If I may ask a followup question.

I’ve been building towards use case #2 and I now understand that Glide is not intended for that.

Is the main difference between the two be in the structure of the database schema/functions/roles/etc. or is it rooted in potential usage pricing differences?

Candidly I’ve fallen in love with the ease at which I’ve been able to use Glide compared to the dozens of other builders I’ve tried. It would be a bummer to have to wrap it up and migrate off of it.

1 Like

Imagine you digitized internal business processes for businesses, and you specialize in a specific business process. You build a beautiful and user-friendly Excel spreadsheet that solves the problem for businesses in your area.

Question: Based on how Excel is provided to you by Microsoft (the pricing and various security features), would you try to use one single Excel spreadsheet to service your clients (case #2), or would you sell and use one spreadsheet per client (case #1)?

It’s similar with Glide. As a Glide agency, if you want to sell your expertise to clients, you are probably better off with case #1.

1 Like


Hi, just wondering how this works:

  • You for sure have your own account using your own email address.

  • Are you using a different email account when someone invites you to their account?

Jus trying to understand how Glide differentiates the same user using different accounts.

If you are invited into a user’s team, that team will show up in your dashboard along with your own teams. You only see the teams they have shared with you and they can only see the teams you have shared with them. Each team folder is completely separate, but can be contained in the same glide account.


@Jeff_Hager I am with you, quite clever solution :).

1 Like

Not usually, but sometimes.
I have a handful of clients that have actually given me Google Accounts in their own domain, and I do everything for them using that account. But for the most part, the client just invites me to their team and I join using my own email account. From there it works as Jeff described.

1 Like

I find it helpful to think of it this way:

  • You have one Glide user account
  • Your Glide user account can belong to multiple Glide teams
  • You subscribe to Glide plans at the team level, not the user account level

So rather than having multiple teams contained within a user account, you have multiple user accounts contained within a team.

TL;DR = Very similar to Airtable and other SaaS platforms. :+1: