Correct!
Also correct, though more accurately the Expert would be removed from the team, rather than the app being removed from the team.
The Glide Experts program is a solutions partner program. Always has been.
The model is nearly identical to other agency/consultant partner programs.
I’m most familiar with website and ecomm builds from my agency days, so I’ll use that as an example:
- Client comes to an agency in need of a new website or online store
- Agency does their pitch and proposal, includes a line about the platform they use
- Client agrees to the scope, signs off on the statement of work
- Agency starts the build process
a. They stand up a new dev/staging environment
b. Their IP includes a mix of dev frameworks, templates, and methodologies - Agency reviews the project with the client for final approval
- Client signs off
- Agency starts the hand-off process, transferring ownership of the site/shop
- Agency begins the post-launch support and ongoing maintenance retainer
This is the standard agency build + deployment process typical of nearly every platform, ranging from the likes of Salesforce down to website hosting providers.
The client owns the instance. The partner comes in to support.
Our setup is the same for Glide Experts.
Can you build a software product and try to license that out using the Glide Experts program model? Sort of. We’ve seen it done. But it’s not the ideal setup.
If you want to launch a micro-SaaS and license it out, you’ll need to work within the constraints of the Glide platform. Otherwise it’s not what we’re building Glide for.