# Managed Prompt Infrastructure (MPI) Strategic Fit Assessment
      
Evaluate your organizational AI maturity and identify strategic gaps in how your team manages, secures, and scales AI instructions.

## The Assessment

**Q1: Where are your organization’s "Gold Standard" AI instructions (most effective prompts) currently stored?**
- In a centralized, encrypted, and version-controlled organizational library.
- In shared folders or documents (Google Docs, Notion, or local files).
- In employees' private history or individual chat threads.
- Hard-coded within a custom engineering pipeline (e.g., LangChain/DSPy) with its own internal versioning.

**Q2: How long does it take to update the business rules of your production AI assistants?**
- Instantly via a central dashboard update without modifying any code.
- From a day to several days, for example involving software developers, code changes, and release cycles.
- We don't have a synchronization method; every employee must manually change how they prompt.

**Q3: What happens to your AI expertise and logic when a high-performing employee leaves the company?**
- The logic is permanently secured in company-owned repositories and its history is preserved.
- We try to document their work, but some refined logic and history is inevitably lost.
- The expertise walks out the door with the employee’s personal account access.

**Q4: What is your organization's strategy for shielding sensitive European intellectual property from the US CLOUD Act?**
- We use infrastructure with zero-knowledge encryption or 100% European-sovereign hosting.
- Data is in the EU, but we use standard US cloud providers without additional client-side encryption.
- We haven't audited our jurisdictional risks or data residency requirements yet.
- Not relevant to us (we are a company operating outside the European Union).

**Q5: Can you provide a certified history of the specific AI instructions used for a decision made 12 months ago?**
- Yes, we have signed, timestamped logs and version history for every instruction set.
- Partially, through technical logs, but it is mixed with application code.
- No, we only see the "current" version; historical variations are lost.
- Not relevant to us (we are a company operating outside the European Union).

**Q6: How do you manage collaborative improvements to AI logic while ensuring quality control?**
- Through a formal approval workflow where changes are vetted before going live.
- Through informal reviews in chat tools before manual updates.
- Anyone with access can change instructions at any time without oversight.

**Q7: How deeply is your AI management integrated into your custom automated developer pipeline?**
- We use individual tools or simple scripts and have no unified pipeline.
- We have basic API integrations but manage AI logic manually in code.
- We have a fully automated, programmatic pipeline (e.g., LangChain) with custom testing and databases.

## Outcomes

Based on your answers, you may fall into one of these categories:

### High Need – The AI Safety & IP Fortress
Your organization is currently exposed to significant risks regarding institutional memory loss and intellectual property leakage. Your AI logic is likely scattered across personal accounts or shared documents, making it difficult to audit, scale, or protect.

### Strategic Need – The Agility Catalyst
Your organization has begun to centralize its AI logic, but you are still facing "Logic Lag." Updates take too long because they are tied to code deployments, and your oversight mechanisms are likely manual or informal. Moving to a dedicated MPI layer would significantly increase your development speed and compliance readiness.

### Potential/Experimental Need – The Growth Foundation
You are in the early stages of AI adoption or operating as an outside-EU entity with fewer residency pressures. While you may not face an immediate crisis, establishing a centralized logic layer now will prevent "technical debt" as your team and AI usage grow.

### Low Current Need – The Mature Architect
Whether you have built a sophisticated custom pipeline or have already achieved a high level of sovereignty and version control, your current needs are well-covered. A specialized tool like PromptEasy.EU would offer low marginal utility compared to your existing infrastructure.