Customer Portals
Access, status, documents, communication, and self-service functions for customers.
- custom logins and roles
- project or case overviews
- upload and approval processes
Digital Products
Digital products that reduce process workload.
Not just look digital.
VELUNO develops customer portals, internal tools, dashboards, and web applications for companies that no longer want to manage recurring workflows through email, spreadsheets, and improvised workarounds.
Clear product logic, well-defined roles, robust data structures, and a technical foundation that actually works in day-to-day operations.
Customer Portals
Internal Tools
Web Applications
PRODUCT LOGIC
Roles, status, and data in one structure
Client→Workflow→Team
Operational impact
Fewer follow-up questions
Status remains visible
Workflow activeclear next step
PortalsAccess, uploads, status, and communication
ToolsProcessing, roles, tasks, and approvals
DashboardsData, KPIs, and operational transparency
Web AppsCustom user and product logic
Not every digital product is the same
The right system is determined by the process—not by an app label.
Customer portals, internal tools, and standalone web applications solve different problems. What they share is clear functional logic.
Internal Tools
Operational systems for teams that need to manage processing, coordination, and documentation cleanly.
- Task and processing logic
- status models and approvals
- data structures and histories
Web Applications
Products with their own user logic, specialized functionality, and digital value beyond a conventional website.
- interactive product logic
- user accounts and data models
- application-specific interface
Manual friction becomes product logic
A digital product consists of more than screens.
What later appears to be a simple interface is built on roles, responsibilities, data relationships, status models, integrations, and clearly defined process steps.
- Users and teams work within one shared structure
- Status, data, and tasks remain visible within the system
- Roles, permissions, and handoffs are clearly defined
- Recurring workflows run in a more controlled way
Roles → Data → Workflow → Interface
PRODUCT STRUCTURE
Customer portal · active case
Status: Review
Roles
Data
Workflow
Interface
1 structureinstead of scattered tools
Clear RolesCustomer, team, admin
Complete historyStatus and changes
Scope of Services
What can specifically be built within Digital Products.
Not every project needs the same functions. But robust products always require sound logic across use, interface, data, and operations.
Roles, permissions, status models, and workflows
The functional foundation is structured so that user paths, responsibilities, and process steps work unambiguously in day-to-day operations.
User RolesStatus LogicTriggerApprovalsUse Cases
Interfaces for users and teams
Dashboards, lists, inputs, and processing views translate the product logic into an understandable application.
Structures, histories, and integrations
Data models and connections to CRM, ERP, payment services, and other third-party tools are integrated in a controlled manner.
A foundation that continues to support the product after launch
Performance, stability, and extensibility are considered from the outset so that new functions are not built on technical patchwork.
Scalable expansionPerformanceMonitoringStabilityNew features
Before and after
Product logic replaces improvisation.
A digital product makes sense when recurring workflows already exist but are still held together through inboxes, spreadsheets, verbal coordination, and individual people.
Fewer Media Breaksclear statusdefined responsibility
- Coordination through email and messaging apps
- status exists only in the minds of individual people
- Data distributed across spreadsheets and tools
- roles and responsibilities are unclear
- many follow-up questions and fragmented handoffs
- shared structure for users and the team
- status, data, and tasks are visible
- roles and permissions are clearly defined
- recurring workflows are controlled
- Product logic instead of a collection of tools
When a custom product becomes worthwhile
Not every process requires custom software. But these signals are clear.
High coordination overhead
Recurring cases constantly generate follow-up questions, manual handoffs, and unnecessary coordination.
Status and data are unclear
Information is spread across several systems, and no one can reliably see the current status.
Existing tools reach their limits
Standard software no longer reflects the actual process logic cleanly—or only does so through workarounds.
Typical Use Case
Customer portal for a service provider.
Customers receive their own access for documents, status, and communication. The team processes the same case using roles, tasks, and controlled approvals.
Customer accessTeam areaStatus ModelsDocumentsCommunication
PRODUCT STRUCTURE
Client → Workflow → Team
RESULT
Every step is defined and traceable.
Product architecture
Four layers that must work together.
If one is missing, the result is either an attractive interface without logic or a technical system that no one can use properly.
Roles
Customers, team members, admins, and partners each receive the appropriate access and view.
Data
Information is organized in a traceable structure instead of being scattered across inboxes and spreadsheets.
Workflow
Status, processing, and handoffs follow a clear, controllable process logic.
Interface
The interface translates complexity into an understandable and usable application.
Operational impact
How to recognize a good digital product in day-to-day use.
Not by having as many features as possible, but by reducing friction, creating clearer workflows, and providing a stable foundation for further expansion.
Fewer follow-up questions
Users and the team can see status, tasks, and required information directly in the system.
Clear responsibility
Roles, permissions, approvals, and next steps are represented conclusively.
Clean data foundation
Information, histories, and relationships remain structured and traceable.
Extensible foundation
New functions can build on a robust product foundation instead of workarounds.
FAQ
Questions About Digital Products. Without Product-Speak.
Answered directly. No SaaS mysticism. No feature theater.
Gemeint sind digitale Werkzeuge mit echter Funktion: Kundenportale, interne Tools, Dashboards oder Webanwendungen, die Prozesse strukturieren, Daten nutzbar machen und operative Arbeit entlasten.
Nein. Gerade kleinere und mittlere Unternehmen profitieren stark, wenn wiederkehrende Abläufe nicht mehr über Mail, Tabellen und manuelle Übergaben laufen müssen.
Typische Signale sind hoher manueller Koordinationsaufwand, viele Rückfragen und Statusunklarheit, wiederkehrende Prozesse mit klarer Logik oder bestehende Tools, die sichtbar an Grenzen stoßen.
Nein. Ein Digital Product besteht nicht nur aus Interface, sondern auch aus Rollen, Datenstruktur, Prozesslogik, Integrationen und technischer Grundlage. Das Frontend ist nur die sichtbare Oberfläche.
Next Step
Not another collection of tools. Product logic that works in day-to-day operations.
When customer access, internal processes, or recurring workflows need to function properly in a digital system, we build the system behind them.