Business best practice for Studio

I created an AI Aviation Safety Manager tool. This tool does specific safety risk analysis processes based on specific structure in compliance with FAA mandates. Each customer/company would have some of their own specific safety manuals in the knowledge base. Each company would also need their own specific Master Prompt. even though their will be some default language in it that is the same for everyone. I need help in the best way to structure this in a studio or multiple studios.

Example: I have 5 clients all need their own Knowledge base. They will also have slightly different master prompts to align with specific company needs. Do I build 5 specific Pickaxes and name them for the specific company within the studio and assign their Pickaxe to the correct user login account? each customer could have 3-5 users. if a company pays for a specific monthly plan I set up, can you attach specific users to that account so they don’t have to pay for use? Or do I create a separate studio for each customer. What would be the best practice to set up this business?

Hi @dspanier ,

I’m an FAA certified pilot myself, so I understand how important a well structured and compliant safety tool is. What you’re building sounds thoughtful, and it makes sense that you want the setup to be correct from day one.

1. Separate Studios give the cleanest setup
Each Studio has its own Knowledge Base, users, access rules, and paywalls, which keeps every client’s manuals and custom master prompts fully isolated. This is usually the safest approach for compliance-heavy tools.

2. One Studio with multiple Pickaxes can work
You can keep everything in one Studio and create one Pickaxe per company, assigning each tool only to that company’s users. Just keep in mind:
• Knowledge Base is shared across the whole Studio
• Gold plans have a 50-file limit; the Pro plan gives unlimited uploads.
• You’ll need to be careful with access controls

3. Billing flexibility
Yes, if a company buys a plan, you can assign their users to that product so they don’t pay separately. This is done inside Users and Products.

Best practice for your use case
Most B2B builders with regulated content choose one Studio per client. It keeps things clean, compliant, and easy to manage as you scale.

If you want, happy to walk through your exact structure once you have a sense of how big each client’s knowledge base will be. :slight_smile:

2 Likes

Thank you so much for that insight. a typical Customer knowledge base would max out at 30 documents.

The Gold Plan might be the right fit for you since it supports up to 50 files per AI Studio, which is what many users typically need.

Even if you think you might need 50 separate files for 50 different state compliance rules or no-fly zones, you still don’t have to upload that many. All 50 states can be placed inside one clean Word or PDF file, each state on its own page if you prefer.

The AI will break that large file into smaller chunks and pull the right state information when needed. This saves Knowledge Base slots and keeps everything much easier to manage.