Making LLMs understand complex CRM and ERP screen layouts
CRM/ERP platforms often need denser screens than a simple web app. A list may open into a detail view, one record may contain several tabs or sub-sections, and a workflow may continue inside the same screen. Even when an LLM is told that the product is CRM/ERP software, it can fall back to familiar web app habits: card-heavy layouts, one-purpose pages, and shallow navigation.
The hard part is not visual styling. It is planning the screen structure: information priority, how deeply information should nest, how users move between views, and how the current context stays visible while several embedded areas are open. The practical design question is when to use , a drawer, or a dedicated page.
Stronger rules or prompts may need explicit decision criteria for layout patterns, data types, feature types, navigation depth, and the structural feel of software.
Key points
- CRM/ERP screens often combine lists, detail views, tabs, sub-sections, and in one place.
- An LLM may default to simple web app patterns even when asked for software.
- The main challenge is screen structure, not just colors, spacing, or component styling.
- Useful rules should define when to use , a drawer, or a dedicated page.
- AI design prompts should include information , nesting depth, navigation depth, and context .