duodesign.md
dimax.md
mivaro.md
vilana.md
More than a website. A working system.
Client accounts, roles, requests, documents, APIs and a custom admin. I build around your real business workflow, not a generic feature template.
Roles, events, data and integrations work together.
What I build
Choose the workflow your business needs, without filler features.
Customer portal
Orders, files, payments and enquiry history.
Clients can find their details without calling staff.B2B portal
Personal pricing, stock, documents and repeat orders.
Partners order under their agreed terms.CRM / internal tools
Tasks, deals, owners, statuses and reporting.
Work moves out of spreadsheets and scattered messages.API-driven platform
Portals, suppliers, integrations and custom modules.
Data flows between systems without repeated manual entry.One product. Different actions for each participant.
Illustrative access rules, finalized during discovery.
Customer
- Array
Staff
- Array
Administrator
- Array
What gets built
The architecture matters more than a pretty screen. Data and permissions must work correctly.
Architecture & data
Entities, relationships, states and constraints.
Admin interface
Users, access rules and configuration.
Frontend & mobile
Usable interfaces for each role.
Security & QA
Permissions, edge cases and error handling.
Real SiteHub system
The SiteHub client portal handles requests, projects and documents. An actual product, not a rendered dashboard.
Open SiteHub client portal
CLIENT PORTALFrom scope to launch
- 01
User journeys
Define users and critical jobs.
- 02
Prototype
Validate the main interactions.
- 03
Development
Connect UI, backend, data and APIs.
- 04
QA
Permissions, forms, errors and backups.
Web platform pricing
Catalog starting price. The final scope depends on roles, integrations and data complexity.
Straight answers
Can we start with an MVP?
Yes. Launch the core first and add modules as needs become clearer.
Does it include an admin panel?
Yes, when defined in the approved architecture.
Can it integrate with an existing site?
Yes, via an API or another agreed data exchange method.
Have a workflow too complex for a website?
Describe the users, data and actions. I will propose a practical architecture and stages.
