Business websites and portals for private areas, catalogues and dashboards
At Elumad we build business websites and portals designed for real use: fast to load, easy to maintain, and able to integrate data and processes when needed.
What is a business website or portal?
A business website can be just a corporate site (brand, services, contact), or it can evolve into an operational portal: a system with login, permissions, data and workflows. The difference lies in the objective: to inform vs to operate.
We design the portal around the real process — not around "I want a website".
Types of websites and portals we build
Every business has different needs. These are the most common types in the projects we develop.
Corporate website
Professional presence, services and lead capture. The foundation before adding operations.
- Service and success case pages.
- Forms and contact.
- Positioning content (when relevant).
Client portal
The client logs in, checks their data and operates without depending on the internal team.
- Per-client login access.
- Documentation, invoices, statuses and requests.
- Communication and tracking (as needed).
B2B portal / private catalogue
Each client sees their catalogue and conditions. No more PDFs by email or manual updates.
- Catalogues by client or segment.
- Prices and conditions by profile (if applicable).
- Orders or requests with access control.
Internal portals & dashboards
Working panels for teams to operate and management to have real visibility.
- Panels by area (operations, sales, finance).
- KPIs and reports with real data.
- Internal tools to work with, not just to view.
What we deliver
Objectives and users discovery
What is consulted, what is managed and who accesses. Without this step, the portal has no real structure.
Information architecture
Navigation, sections, permissions and hierarchies. The structure defines whether the portal is usable or not.
UX/UI oriented to real use
Clarity, speed and accessibility. Designed so the user finds what they need without training.
Authentication and roles
Login, profiles and permission control. Each user accesses only what corresponds to them.
Private areas
Content, documents, panels or modules as needed. The operational core of the portal.
Catalogues and dynamic sections
Products, services or documentation with filters if applicable. Updatable without breaking the structure.
Dashboards and reporting
KPIs and panels by role/team if applicable. Real data, not decorative screens.
Stack integration
ERP/CRM/eCommerce or internal systems when required. The portal as a window to the real system.
Basic security
Access control, traceability and best practices. Without this, a portal with sensitive data is not viable.
QA + go-live
Testing, deployment and initial support. No surprises at launch.
Typical features
Each portal is different. These are the most common features in the projects we develop.
Login, roles and permissions
Access control by profile and section. The user only sees what corresponds to them.
- Profiles by role (client, supplier, internal).
- Access control by section and data.
- Basic traceability (if applicable).
Documents and private content
Centralised repository with filters, versions and secure upload/download.
- Document repository with filters.
- Statuses and versions (if needed).
- Secure upload and download.
Catalogues and dynamic sections
B2B catalogue with user control and updatable sections without breaking the structure.
- B2B catalogue with filters and user control.
- Documentation per product/service.
- Updatable sections without breaking structure.
Internal dashboards
KPIs by role with real data and basic export if needed.
- KPIs by role and area.
- Panels fed by real data.
- Basic export or reporting if needed.
Typical integrations
Systems we commonly connect
Invoices, orders, stock and statuses. The portal shows real data without duplicating management.
Clients, requests and support. The portal as an extension of the CRM towards the end client.
Orders, catalogues and tracking. The B2B portal as a private layer over the public catalogue.
Internal tools or legacy systems. We define which data source takes precedence in each system.
Our approach
The portal as a window to the real system
The portal does not duplicate data: it displays it from the systems that already have it. Controlled synchronisation to avoid inconsistencies.
Define which system owns each piece of data
Before integrating, we define the source of truth for each piece of data. This avoids duplications and errors when two systems hold the same information.
What we guarantee in every integration
- Documented data source without ambiguity.
- Validations before writing to destination.
- Structured logs with full traceability.
- Automatic alerts on failures or delays.
- Retries with backoff for transient errors.
Use case examples
Common situations we solve with business websites and portals.
Client portal with documentation and statuses
The client logs in and sees documents, order/incident statuses and downloads. Fewer emails, fewer "where is my order?" enquiries.
Private B2B catalogue
Each client sees their catalogue and conditions. The team no longer sends PDFs by email or updates price lists manually.
Internal dashboard for management
Management sees real KPIs (sales, operations, incidents) with consistent data. No more weekly Excel dependency.
How we work
Definition
We define the portal objective and who uses it. Without this, the portal has no real structure.
Structure & permissions
We design information architecture, roles and permissions. The foundation of a usable portal.
Functional MVP
We build the functional MVP: the minimum that already solves the real user problem.
Integration
We connect with the stack if needed, without breaking existing operations.
Go-live + evolution
We launch and scale by modules according to impact. Each phase with clear deliverables.
Frequently asked questions
What we are most often asked before starting a portal project.
Related services
Do you need a portal your company actually uses?
Tell us what you want to solve: clients, B2B, internal operations or dashboards. We propose an MVP and a phased plan to scale without chaos.
Talk to an expert