My name is Liese, and I am a researcher and engineer who currently uses Proton Business Suite + Lumo Business as an individual user. While using the service I noticed several points of confusion that I would like to bring to your attention and suggest improvements for.

1. Inconsistent Naming Across Plans
   Lumo Plus – marketed as the premium plan for individual users.
   Lumo Professional – presented as a corporate‑oriented plan.
   Lumo for Business – essentially the same corporate plan but with a different name.
   Having three different names for what is fundamentally the same set of capabilities makes it hard for users to determine which plan best fits their needs.

2. Emphasize Functionality Rather Than “Personal vs. Business”
   Users tend to decide based on what they want to accomplish, not on whether a plan is labeled “personal” or “business.” A function‑focused naming scheme would be clearer:

Lumo Premium – High‑Performance Personal Plan
Features: Unlimited chats, access to the latest AI models, web‑search capability, large file uploads, fast response times.

Lumo Team Collaboration – Comprehensive Business‑Oriented Plan
Features: Project workspaces, 1 TB of end‑to‑end encrypted storage, VPN access for up to ten devices per user, 20 custom email aliases, an admin dashboard for managing team permissions, and the same advanced AI capabilities as Premium.

Lumo Starter – Basic Free Plan
Features: One Project, encrypted chats that are not saved, and basic AI assistance.

Presenting the plans this way lets users instantly match their desired feature set (e.g., “I need project management and shared storage”) without having to interpret whether a plan is “personal” or “business.”

1. Suggested Implementation Steps Revamp the Plan Comparison Page Replace the current “Personal / Business” tabs with a card‑style layout that highlights the functional names above, each accompanied by a concise bullet list of key features.

Run A/B Tests on Marketing Materials
Compare click‑through and conversion rates between the existing naming convention and the proposed functional naming to quantify the impact.

Update Internal Documentation
Ensure sales, support, and engineering teams use the new terminology consistently, reducing the chance of mixed messaging during customer interactions.

1. Context From My Perspective As a researcher/engineer, I frequently need to share large datasets, collaborate on project‑specific documents, and maintain strict confidentiality. Although I am an individual user, I rely on the Business Suite features (project workspaces, encrypted storage, VPN, etc.). The current naming creates unnecessary friction when I explain the service to colleagues or consider recommending it to peers.

A function‑centric naming approach would lower the adoption barrier for users like me who require advanced capabilities without belonging to a formal organization.

Thank you for considering these suggestions. I am happy to discuss further or provide additional feedback if needed.

Best regards,

Liese
Researcher & Engineer