Which Portals We Build
- Customer or partner portals, where customers and dealers log in to see their orders, documents and terms, and to submit requests.
- Internal corporate portals: a hub for employees with company news, a knowledge base, a staff directory and requests to different departments.
- Industry or information portals with lots of content from many authors, rankings, member directories, events and members-only sections.
- Service portals, where users register, submit requests, receive results and communicate with service providers inside the system.
The type determines what matters most in the project: content and search, accounts and documents, or data exchange with other systems.
When You Need a Portal, and When You Don't
A portal makes sense if you have several user groups with different permissions, lots of regularly updated data, and processes that currently run through email and spreadsheets. It takes routine work off your team and gives customers access to information without a phone call.
You don't need a portal if the goal is to present your company and generate leads. A corporate website is enough for that, and an account area for a few partners can be added later. Building a complex system "for future growth" before you have users is one of the most common reasons projects run late and over budget.
Roles and Permissions First
Most portal problems come from poorly thought-out permissions, not from code. Before development, we build a matrix with roles in rows and actions in columns: who can view, create, edit, approve and delete. It becomes the basis for both the interfaces and testing. We also make sure you can create new roles yourself in the admin panel, because organizations change faster than code.
Phased Rollout and Platform Choice
For most portals we recommend a phased rollout: start with sign-in, roles, the key account area and the main content, then add modules one by one. The portal starts working sooner, and later phases are planned from real feedback. The architecture has to be designed for future modules up front, and you live with temporary limitations in the meantime.
For content-heavy information portals, a customized CMS is often enough and is faster and cheaper to start. When a portal has a lot of business logic, non-standard roles and integrations, it's more reliable to build it on a framework such as Laravel. We make this choice after mapping roles and user scenarios, not before.
Security and Performance
A portal stores personal data, documents and correspondence, so we build in server-side access control, user activity logs, backups and encrypted connections from day one. If you expect many concurrent users or traffic spikes, we plan caching, a background job queue and separate file storage. After launch, a large portal can move to high-load project support so we can monitor speed and scale the server in time.
What to Prepare on Your Side
- A list of user groups and the approximate number of people in each.
- A description of how processes work today: which email accounts, spreadsheets and software you use.
- Existing data to migrate: user databases, content archives, documents.
- A point person on your side who will make decisions and gather feedback from colleagues.
What Affects the Cost of a Portal
- Number of roles and scenarios: two types of user accounts versus ten is a fundamentally different scope.
- Integrations: how many systems we connect and whether they offer a ready-made API.
- Data migration: the size of the archive and how well organized it is.
- Security and performance requirements: number of users, data sensitivity, logging.
- Scope of the first release: what launches right away and what moves to later phases.
We estimate by module, so you can see what makes up the budget and reorder priorities.
Frequently asked questions
Can you migrate users from our old system? Yes. We migrate accounts, content and documents. Passwords can't always be transferred directly, so we design a convenient way to restore access at first login.
Will the portal work well on mobile? Yes, all user accounts are fully responsive. If users work from their phones every day, we'll also discuss a mobile app.
Who will manage the portal after launch? Your administrators, through the admin panel. We train them and leave documentation, and we can continue building new modules together.
Can users sign in with their corporate account? Yes, sign-in can be connected to your company's existing account system, so employees don't have to remember yet another password.
Can we start with just some of the features? Yes, and it's usually the smoothest path. The key is to design the architecture for future modules up front.
How will we know the portal is doing its job? We agree on metrics at the start, such as how many customers log in regularly, how many requests are resolved without calling a manager, and how quickly editors publish content.
Why Promodex
Our portal projects since 2015 include Driver Work, EuroPAM, My Doctor Club and Web Awards UA. Designers and developers are in-house, so one team runs the entire project. A large portal doesn't end at launch, and we stay on to support it and add new modules.