Remix

Make your own version of Remia Business Workspace

Get an exact, working copy in your account, then change anything with chat.

Original by Subham Tripathi

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build a premium, enterprise-grade AI-powered SaaS platform named “remia— Intelligent Business Workspace”.

PROJECT GOAL:
Create a polished, modern, scalable business software experience suitable for a professional client presentation and future production development. This must look and feel like a carefully designed commercial SaaS product, not a generic template, landing page, or static dashboard mockup.

IMPORTANT:
First inspect the complete requirements and establish a consistent application structure. Prioritize a working, testable foundation over adding many superficial features. Never claim a feature, integration, database, AI capability, or security control works unless it has actually been implemented and tested.

1. VISUAL DESIGN SYSTEM

- Create a sophisticated enterprise aesthetic inspired by the clarity of Linear, the data presentation of Stripe, and the usability of leading CRM platforms, without copying their branding or layouts.
- Use deep midnight navy, charcoal, soft white, muted slate, and restrained electric-indigo accents.
- Provide both dark and light themes with a functional theme switcher.
- Use refined typography, consistent spacing, subtle borders, elegant shadows, and restrained motion.
- Use professional icons, clean data visualizations, realistic tables, and carefully designed empty states.
- Avoid excessive gradients, oversized cards, cartoon graphics, unnecessary glowing effects, and decorative clutter.
- Make the interface visually consistent across every page.

2. RESPONSIVE APPLICATION SHELL
   Create a complete responsive application layout featuring:

- A collapsible left sidebar on desktop and an accessible navigation drawer on mobile.
- A top navigation bar with global search, notifications, help, theme controls, and user profile.
- A breadcrumb system and clear page titles.
- A universal primary-action area for common tasks.
- Responsive tables, filters, forms, dialogs, charts, and mobile-friendly navigation.
- Proper loading, empty, error, success, and confirmation states.
- Keyboard accessibility, visible focus indicators, and readable contrast.

3. MAIN DASHBOARD
   Create a useful overview with:

- Total contacts or customers.
- New leads and lead conversion rate.
- Active projects and outstanding tasks.
- Upcoming appointments.
- Revenue or sales metrics only when appropriate to the configured business.
- Period comparisons and clear date-range filters.
- Trend charts with accurate labels and tooltips.
- Recent activity and pending actions.
- A “Needs Attention” section highlighting overdue tasks, unresolved issues, and follow-ups.
- A “Quick Actions” section for creating a contact, lead, task, appointment, or project.
- An AI insights panel that uses real available data or is clearly marked as a demonstration.

Use realistic demonstration data only when real data is unavailable. Label demo metrics clearly and never present fabricated business results as real customer performance.

4. CORE BUSINESS MODULES
   Build a consistent navigation and page structure for:

A. Contacts and CRM

- Contact list, profile details, notes, tags, search, sorting, filters, and contact history.
- Create, view, edit, and delete workflows with confirmation.

B. Leads and Sales Pipeline

- Lead capture form and lead detail page.
- Configurable pipeline stages.
- Kanban and table views.
- Lead owner, source, priority, next action, and follow-up date.
- Track status changes and conversion metrics.

C. Tasks and Projects

- Task creation, assignment, deadlines, priorities, and statuses.
- Project overview, progress indicators, and task relationships.
- Overdue and upcoming task filters.

D. Calendar and Appointments

- Calendar views, appointment creation, editing, and cancellation.
- Time-zone-aware date and time handling where supported.
- Clear validation for conflicting or invalid appointments.

E. Conversations and Support

- A conversation inbox interface with customer details, message history, status, and assignment.
- A support-ticket workflow with priorities and resolution status.
- Do not pretend that email, WhatsApp, or other messaging channels are connected unless a real integration is configured and tested.

F. Analytics and Reports

- Filterable reports, date ranges, summary metrics, and export options where supported.
- Charts must derive from the actual available dataset.
- Include sensible empty states when there is insufficient data.

G. AI Assistant

- Create a dedicated AI assistant interface with a conversation history, suggested prompts, and clear response states.
- Separate genuine model-powered responses from demo responses.
- Do not expose API keys or secret credentials in client-side code.
- If AI credentials or an integration are missing, show a clear setup screen instead of pretending the assistant is connected.

H. Team and Permissions

- Team member list and role-management interface.
- Design for owner, administrator, manager, and member roles.
- Enforce permissions on the backend before claiming access restrictions are secure.
- Never rely on hiding buttons in the interface as the only security measure.

I. Settings and Integrations

- Business profile, regional preferences, date and time settings, notifications, appearance, team settings, and integration status.
- Provide connection instructions and setup status for integrations.
- Never display fake “Connected” states.

5. FUNCTIONAL REQUIREMENTS

- All visible buttons, navigation items, menus, filters, tabs, forms, and dialogs must have a defined, working behavior.
- Implement real create, read, update, and delete operations wherever the configured data layer supports them.
- Validate required fields and display useful error messages.
- Show success feedback only after an operation succeeds.
- Add search, sorting, filtering, pagination, and reset controls where appropriate.
- Prevent accidental deletion with confirmation dialogs.
- Preserve valid user input when recoverable errors occur.
- Avoid broken links, dead buttons, placeholder navigation, and fake loading animations.
- Ensure charts, tables, and summary metrics remain consistent with the same underlying data.
- Use reusable components and a maintainable project structure.

6. DATA, AUTHENTICATION, AND SECURITY

- Inspect which database and authentication capabilities are actually available in the current builder and selected plan.
- If supported, configure persistent data storage and proper authentication.
- Keep customer records isolated between authorized accounts or workspaces.
- Enforce authorization and validation on the server side.
- Protect secrets using server-side environment variables.
- Do not store passwords in plain text.
- Do not expose private customer information in logs, URLs, or public pages.
- If persistent storage, authentication, or server-side authorization is unavailable, clearly identify the missing dependency and build a demonstration mode without misrepresenting it as production-ready.
- Use synthetic sample data during development, not real client or customer information.

7. FIRST-TIME USER EXPERIENCE

- Add a professional sign-in interface only to the extent supported by the configured authentication system.
- Create a guided onboarding flow for business name, business type, timezone, and initial workspace setup.
- Show a helpful empty dashboard for new accounts.
- Include concise tooltips and contextual help.
- Allow the user to dismiss onboarding guidance and access it again from help or settings.

8. QUALITY ASSURANCE
   After implementation:

- Check every navigation route and major interaction.
- Test forms with valid and invalid inputs.
- Verify responsive layouts at mobile, tablet, and desktop widths.
- Check empty, loading, success, and error states.
- Check browser refresh and direct navigation to supported routes.
- Verify that displayed metrics agree with the available data.
- Fix detected compilation errors, broken layouts, and nonfunctional controls.
- Do not report a test as passed unless it has actually been performed.
- Produce a short implementation report listing completed features, tested behavior, known limitations, and remaining setup requirements.

9. DELIVERY STANDARD
   Deliver a cohesive, premium-quality SaaS foundation that can be extended into a real business product. Prioritize correctness, maintainability, accessibility, responsiveness, and client confidence over unnecessary complexity.

Begin by building the complete application shell, design system, main dashboard, navigation, and reusable components. Then implement the core modules in a consistent order. Preserve the existing working code when making changes, and never replace functional features with visual-only mockups.

Before finishing, summarize what works, what is demonstration-only, what requires credentials or a paid service, and what must be completed before real client deployment.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.