# Best practices for building tools for clients

**URL:** <https://community.glideapps.com/t/best-practices-for-building-tools-for-clients/44274>\
**Category:** Ask for Help\
**Created:** [July 11, 2022, 10:25am UTC](https://community.glideapps.com/t/best-practices-for-building-tools-for-clients/44274 "2022-07-11T10:25:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Brassnyo](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@Daniel\_Brassnyo](https://community.glideapps.com/u/Daniel_Brassnyo)\
**Post date:** [July 11, 2022, 10:25am UTC](https://community.glideapps.com/t/best-practices-for-building-tools-for-clients/44274/1 "2022-07-11T10:25:56Z")

</div>

Hi,  
I was wondering how other agencies use Glide when building internal apps for clients. I’m thinking about two approaches:

- Building apps using my account with a higher subscription tier and sharing the app with clients → this approach seems reasonable for small companies not wanting to have Airtable, zapier, Glide, etc subscriptions
- Building apps for clients who have their own account and subscription → this is obviously better for privacy concerns (I believe this is what official Glide Experts do).

Any suggestions, or experience around this use case? 🙂

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 12, 2022, 12:50am UTC](https://community.glideapps.com/t/best-practices-for-building-tools-for-clients/44274/2 "2022-07-12T00:50:26Z")

</div>

I think it is a bit of both. When clients don’t need to get access to the builder and allow us to manage their data, we go the first route, and vice versa.