One of the easiest ways to lose a new user is to ask for API keys before they feel the product's value. Mufal should feel useful in the first meeting, not after a setup puzzle.
That is why the default path is Mufal-managed AI. You install the app, sign in, and start with included provider access according to your plan limits. No AssemblyAI key. No OpenRouter key. No detour.
BYOK remains available
Advanced users can still bring their own AssemblyAI or OpenRouter keys. BYOK is useful when you want direct provider billing, stricter account-level control, or a specific model routing setup. It is an option inside the same product, not a separate local edition.
Why this improves activation
The first promise of Mufal is help during a real meeting. Managed AI gets people there faster. BYOK gives power users the flexibility they expect after they understand the workflow.
The product should meet both people: the consultant who wants a useful copilot today, and the technical user who wants exact provider control tomorrow.
